Risk registers that are used
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
keep a register that changes decisions.
Planned topics
- Fields: description, likelihood, impact, score, owner, trigger, response, status, review date.
- Every risk has one named owner and an observable trigger.
- Review on a rhythm (monthly, or weekly for top risks) and close or add risks each time.
- Keep it short: track the top ten that matter.
- A register nobody reads is paperwork; link reviews to plan changes.
Draft outline details
Demonstration
Register table: ID | risk | likelihood | impact | owner | trigger | response | status. Example trigger: API contract not signed by week 3.
Check your understanding
Why does each risk need a trigger?
Show answer
So you know when it is turning into an issue and can act.
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.