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 / ImpactLowMediumHigh
High369
Medium246
Low123

Life of a risk

When a risk occurs, the app creates a linked issue.

  1. Open
  2. Reducing
  3. Accepted
  4. Occurred
  5. Closed

How to do it

  1. Identify. Describe the risk in one clear sentence. Name an owner.
  2. Assess. Set probability and impact.
  3. Respond. Pick one: avoid, reduce, transfer or accept. Write the actions.
  4. 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: