Get the template
BlankRAID log with dropdowns, an automatic Red/Amber/Green rating and a likelihood × impact grid.
Filled exampleFilled in for the running example: five teams moving a support assistant onto in-house inference.
Free to use and adapt. Save this page to get an email when the template is updated.
When to use it
Start the register at kickoff and keep it open until the retro. A risk is something that might happen; an issue is something that already has. The register exists so risks get an owner while they are still cheap to deal with.
| Use | When |
|---|---|
| Risk register | Most programs: you mainly need to track what could go wrong and who owns it |
| RAID log | Programs with many teams or vendors, where assumptions and dependencies cause as many surprises as risks |
| Neither | A short, single-team project: a risks section in the plan is enough |
A filled example
The top risks on Lantern, plotted by likelihood and impact. Anything in a red cell gets reviewed every week.
| Likelihood | Impact: Low | Impact: Medium | Impact: High |
|---|---|---|---|
| Likelihood: High |
| ||
| Likelihood: Medium |
|
| |
| Likelihood: Low |
|
And a few rows from the RAID log, one of each type:
| Type | ID | Description | Owner | Status |
|---|---|---|---|---|
| Risk | R‑01 | Index rebuild too slow for the cutover window; mitigation: run it in parallel batches | Data lead | Open |
| Assumption | A‑01 | The vendor API stays available for rollback after cutover, until the contract ends | Eng lead | Confirmed |
| Issue | I‑01 | Staging GPU cluster down, blocking the second shadow run | Eng lead | Blocked |
| Dependency | D‑01 | Security & privacy sign-off before customer traffic moves | Security | Open |
Good vs bad
| Flag | What it looks like | Fix |
|---|---|---|
| No owner | A risk owned by “the team” or by nobody | One named person per risk |
| No mitigation | A risk written down and never acted on | Every red or amber risk has a next action and a date |
| Vague risk | “Timeline risk” with no cause or effect | Write it as cause, event, effect: “Because X, Y may happen, which would Z” |
| Never closed | A list that only grows, so nobody reads it | Close or downgrade risks at each review; archive closed ones |
How to run it with a team
- Seed the register at kickoff: ask each workstream lead for their top worries and write them as cause, event, effect.
- Rate likelihood and impact together, so the scale means the same thing to everyone.
- Give every risk one owner and a next action, then agree which ratings get reviewed weekly.
- Review the red and amber risks in the weekly program meeting; skim the rest at milestones.
- Pull the risks that changed into the weekly status report.
Inside the template
| Field | What to put there |
|---|---|
| ID and type | R, A, I or D plus a number, so items can be referenced in status reports |
| Description | Cause, event and effect in one sentence |
| Likelihood and impact | Low, Medium or High each; the rating cell works out the RAG color |
| Owner | One named person |
| Mitigation and next action | What you are doing about it, and by when |
| Status | Open, blocked or closed; assumptions are confirmed or not |
Get the template
BlankRAID log with dropdowns, an automatic Red/Amber/Green rating and a likelihood × impact grid.
Filled exampleFilled in for the running example: five teams moving a support assistant onto in-house inference.
Free to use and adapt. Save this page to get an email when the template is updated.