Guide · Portfolio

RAID log: risks, assumptions, issues and dependencies

A RAID log only works if every entry has an owner, a date and a consequence. Here is the structure that keeps it alive past week three.

Columns that matter

  • Type (Risk, Assumption, Issue, Dependency)
  • Description and impact
  • Probability × impact score
  • Owner and due date
  • Linked milestone or task
  • Mitigation and status

Keep it linked to the plan

When a risk is linked to the milestone it threatens, the schedule shows the exposure and leaders can see which risks really matter.

Frequently asked questions

How often should a RAID log be reviewed?

Weekly by the project team, and the top risks monthly by the steering committee.

Run it live in Capittance

Stop rebuilding status in spreadsheets.

  • Testing, cutover and hypercare control tower
  • C-Suite dashboard with live RAG and RAID
  • Board pack, PDF and PowerPoint exports
  • NAVBOT AI answers from your own programme data