Risk registers
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
run a risk register that drives action rather than collecting worries.
Planned topics
- Each risk: description (cause, event, effect), likelihood, impact, owner, mitigation, trigger, review date, status.
- Phrase risks as "because X, Y may happen, resulting in Z", not as vague topics like "integration".
- Every risk has a named owner and a date; otherwise it is a note.
- Distinguish a risk (might happen) from an issue (has happened) and from an assumption.
- Review regularly; close or escalate; show top risks in the pack summary.
Draft outline details
Demonstration
a Larkspur risk row: "Because the ERP vendor releases monthly, a changed stock API may break order promises (likelihood medium, impact high); owner: integration lead; mitigation: contract tests in CI and a change notice agreement; review: monthly".
Check your understanding
What makes a risk register entry actionable?
Show answer
A named owner, mitigation, and review date.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.