RAID Log
A RAID log tracks a project's Risks, Assumptions or Actions, Issues, and Decisions or Dependencies in one place, usually owned by the project manager.
A RAID log is a project management register that keeps a project's Risks, Assumptions or Actions, Issues, and Decisions or Dependencies in one place. The letters vary by team.
Per Asana's guide, the project manager usually owns it, the team contributes, and it is reviewed in weekly status meetings and updated whenever a new risk, issue, or key decision arises.
What goes in each section
| Letter | Holds | Example |
|---|---|---|
| R | Risks: what could go wrong | The tax vendor may not support India by launch |
| A | Assumptions or actions | We assume EU customers can wait for v2 |
| I | Issues: what has gone wrong | Staging data is three weeks old |
| D | Decisions or dependencies | Billing migration depends on the new ledger |
RAID log vs decision log
The D overlaps with a decision log, but the purpose differs. A RAID log exists to keep one project on track and is usually archived when it ends. A decision about how invoices are rounded shouldn't disappear when the billing project closes. Most teams link the two: the RAID log entry points to the decision log. For a side-by-side with ADRs and changelogs, see decision log vs ADR. For the role models teams use alongside it, see RACI vs DACI.
- What does RAID stand for?
- Risks, Assumptions (or Actions), Issues, and Decisions (or Dependencies). Teams pick the variant of A and D that fits their project.
- Who owns a RAID log?
- Usually the project manager, with the whole team contributing. It is typically reviewed in weekly status meetings and updated as new risks, issues, or decisions come up.
- Is a RAID log the same as a decision log?
- No. A RAID log's decisions are the ones that keep one project moving, and the log usually ends with the project. A decision log is meant to outlive projects and hold every decision that constrains future work.
Related