What should a project risk register include?

Record a risk ID, cause, uncertain event, potential impact, owner, trigger, response, contingency, likelihood, impact score, status, review date, and eventual outcome. Keep fields that help someone decide what to do next.

How do I score a risk in the template?

Enter likelihood and impact as numbers from 1 to 5. The Excel sheet multiplies them when both values are present. The example bands are 1–8 monitor, 9–15 mitigate, and 16–25 escalate; agree your own definitions and thresholds before using scores to prioritize.

How often should a risk register be reviewed?

Use a regular project review cadence and set a specific next review date for each open risk. Review sooner when a trigger fires, a response slips, or new evidence changes likelihood or impact.

Is a risk register the same as a RAID log?

No. A risk register focuses on uncertain events and responses. A RAID log also tracks actions, active issues, and decisions. Avoid keeping conflicting copies of the same risk in both records.

Project risk register template: turn uncertainty into action

Download a project risk register template with a blank working sheet and completed example. Learn the fields, scoring method, and review process that keep risks useful.