Risk register
Track what could go wrong, how likely it is and what you will do about it.
This page applies to every stage.
IDK templates: IDK-04
Page in the app: /p/{projectId}/r/risk
Probability and impact
Rate each risk on both scales. Work on the top right first.
| Probability / Impact | Low | Medium | High |
|---|---|---|---|
| High | 3 | 6 | 9 |
| Medium | 2 | 4 | 6 |
| Low | 1 | 2 | 3 |
Life of a risk
When a risk occurs, the app creates a linked issue.
- Open
- Reducing
- Accepted
- Occurred
- Closed
How to do it
- Identify. Describe the risk in one clear sentence. Name an owner.
- Assess. Set probability and impact.
- Respond. Pick one: avoid, reduce, transfer or accept. Write the actions.
- Review. Look at the register at every steering meeting.
Good to know
- To accept a risk you must write a trigger and a fallback.
- The customer project manager owns the register.
Related topics
Based on the IFS Implementation Docs Kit (IDK-01 to IDK-24), described in our own words.
Last updated: