Governance
RAID Log Template
A RAID log is the single most useful governance artifact most projects never keep properly. Use this free template to capture Risks, Assumptions, Issues, and Dependencies in one table — copy it into a spreadsheet, or let Planquora keep it for you and surface new entries automatically.
What it is
RAID stands for Risks, Assumptions, Issues, and Dependencies — the four categories of things that can move a project off course. A RAID log is the living register where you record each one, who owns it, and what you're doing about it.
Risks are things that might happen. Issues are things that already have. Assumptions are things you're treating as true but haven't confirmed. Dependencies are things you need from someone else. Keeping all four in one place is what separates a governed project from a hopeful one.
When to use it
- At kickoff, to capture what you already know could go wrong or is being taken on faith.
- Weekly, as a standing agenda item — review open entries, add new ones, close resolved ones.
- Before a stage gate or steering review, to show the project is under control.
- Any time an assumption is proven false or a new dependency appears.
The template
ID R-01, I-02, A-03, D-04 | Type Risk / Assumption / Issue / Dependency | Description What it is, in one plain sentence | Impact What happens if it lands (H/M/L) | Likelihood How probable (H/M/L) — risks only | Owner One accountable person | Response / Action Mitigate, accept, transfer, or resolve | Due Date the next action is due | Status Open / In progress / Closed |
|---|---|---|---|---|---|---|---|---|
| R-01 | Risk | Key integration vendor may miss the API delivery date | High | Medium | A. Rivera | Confirm date in writing; line up a fallback vendor | 2026-08-15 | Open |
| A-01 | Assumption | Client will provide branded assets by sprint 2 | Medium | — | PM | Validate at next client check-in; flag if slipping | 2026-08-08 | Open |
| I-01 | Issue | Staging environment is down, blocking QA | High | — | DevOps | Escalated to platform team; workaround in place | 2026-08-02 | In progress |
| D-01 | Dependency | Legal sign-off needed before data migration | High | — | Legal liaison | Booked review for 08-10; migration gated on approval | 2026-08-10 | Open |
Tips
- Give every entry an owner who is a person, not a team. Unowned risks don't get managed.
- Review it on a fixed cadence. A RAID log that's only touched at kickoff is a document, not a control.
- Close entries explicitly — move them to Closed with a note, don't just delete them. The history is evidence.
- Keep descriptions to one sentence. If it needs a paragraph, it needs its own action, not a longer log entry.
Browse all free templates or read the Help Center.