On this page
Short answer: a RAID log lists Risks, Assumptions, Issues and Dependencies. Each entry needs an owner, a score and a due date. It works only if it lives where the work does and gets reviewed on a fixed day.
What RAID means
- Risk: something that might happen and hurt the project.
- Assumption: something you treat as true but have not confirmed.
- Issue: a risk that has happened. It needs action now.
- Dependency: something you need from someone else, or someone needs from you.
What every entry needs
- A clear description, written as cause and effect.
- An owner, one named person.
- A score, such as likelihood times impact.
- A response: avoid, reduce, transfer or accept. For SAFe, ROAM: resolved, owned, accepted, mitigated.
- A due date for the next action.
- A status, so closed items leave the active view.
Running it
- Review weekly for the top risks, and monthly for the whole log.
- Convert risks to issues when they happen, and keep the history.
- Link entries to work items, so a risk is not a floating sentence.
- Close what is over. A log full of dead items stops being read.
Why it belongs in the tool
A separate spreadsheet drifts from the plan. In NUSK, the RAID register sits in the project with owners, scores and due dates. It feeds the project's Health Score, which is built from schedule slip, cost, scope, risks, blocked dependencies and team load, so a rising risk shows up in the status someone reads. The same register works in predictive, agile, hybrid and SAFe projects, and the portfolio view can show the highest-scoring risks across projects.
With AI, you can suggest risks from a project description, spot recurring ones and analyse root causes. The suggestions are drafts you approve.
Mistakes
- Writing risks so vaguely that nobody can act ("budget risk").
- No owner, or an owner who has left.
- Scoring once and never again.
- Treating the log as paperwork for audit.
When NUSK is not the right choice
If you need a formal enterprise risk programme with quantitative simulation, use a specialised tool. For project-level risk, a RAID register is what most teams need.
See it with your own project
Import a plan or a Jira project into a free NUSK workspace and judge it on your own data.