Project risk register software: how to run a RAID log that people use

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

What every entry needs

  1. A clear description, written as cause and effect.
  2. An owner, one named person.
  3. A score, such as likelihood times impact.
  4. A response: avoid, reduce, transfer or accept. For SAFe, ROAM: resolved, owned, accepted, mitigated.
  5. A due date for the next action.
  6. A status, so closed items leave the active view.

Running it

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

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.

Start free

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.

↑ Back to top  ·  All articles

Keep reading