What is a RAID log?
A RAID log is a single document that tracks the four things most likely to derail a project: Risks, Assumptions, Issues and Dependencies. It's a core artefact in any structured project delivery method, PRINCE2, PMI, APM, and most enterprise PMOs.
The four categories explained
- Risk, something that might happen. Track impact and likelihood, agree a mitigation, name an owner.
- Assumption, something you've taken as given. If it turns out false, it usually becomes a risk or an issue.
- Issue, something that has happened and is actively hurting delivery. Needs an owner and a deadline.
- Dependency, work you need from another team, supplier, or project before you can move forward.
How often should a RAID log be reviewed?
For most projects, walk the RAID log at every weekly status meeting. High-impact items should be reviewed by the project board or steering committee monthly. Stale items (open for 30+ days with no movement) are a leading indicator of delivery trouble.
Why use this generator?
Spreadsheets work, but they don't print well, don't share well, and don't follow a consistent format across teams. This tool gives you a clean, branded export every time , in either PDF (for board packs) or CSV (for import into Jira, Asana, Monday or your own systems).
