RAID Log Builder

How it works

1. 1Four registers in one place: risks, assumptions, issues and decisions. Switch between them with the tabs.
2. 2Each type asks for what it actually needs — risks get likelihood and impact, decisions get who made them and why.
3. 3Risk scores are likelihood multiplied by impact on the standard 1 to 25 scale, colour-banded so the serious ones stand out.
4. 4Export all four registers as a single Excel workbook, one sheet each, or take the current tab as CSV.

Common questions

What does RAID stand for?

Risks, Assumptions, Issues and Decisions. Keeping all four together matters because they turn into each other: an assumption that proves false becomes a risk, a risk that lands becomes an issue, and resolving it produces a decision.

What is the difference between a risk and an issue?

Tense. A risk has not happened yet and may never happen, so it gets a likelihood. An issue has already happened, so likelihood is meaningless — it needs an owner and an action instead.

Why log assumptions at all?

Because every assumption is a risk nobody has priced. "The client will supply test data on time" is fine until it is not, and by then you have lost four weeks. Writing them down makes them arguable.

How is the risk score calculated?

Likelihood multiplied by impact, each rated 1 to 5, giving 1 to 25. Anything 15 or above is banded critical, 10 to 14 high, 5 to 9 medium. The bands are a convention, not a law — adjust how you act on them to suit the project.

Is my register saved?

It is kept in this browser, so a refresh will not lose it. It never leaves your machine, which also means it will not appear on another device and will vanish if you clear site data. Export the Excel file to keep it properly.