Guide
RAID Log vs Risk Register: What's the Difference?
A risk register tracks risks. A RAID log tracks risks plus assumptions, issues and dependencies.
Both are useful. The difference is what kind of project information the team wants to manage and how broad the view needs to be.
The simple answer
Risk register
Best for tracking potential future threats with probability, impact and mitigation.
RAID log
Best for tracking the wider delivery picture including risks, assumptions, issues and dependencies.
What is a RAID log?
RAID stands for:
- R for Risks
- A for Assumptions
- I for Issues
- D for Dependencies
A RAID log gives project and delivery teams one place to monitor items that could affect progress.
| Type | Example |
|---|---|
| Risk | A vendor may miss the delivery date |
| Assumption | Business users will be available for UAT |
| Issue | Test environment is currently unavailable |
| Dependency | Another team must provide an API |
What is a risk register?
A risk register focuses on potential future problems. It usually includes probability, impact, mitigation and ownership.
- Risk description
- Probability
- Impact
- Risk rating
- Owner
- Mitigation
- Response
- Status
- Review date
A risk register is often used in formal project governance or high-risk delivery environments.
The key difference
| Area | RAID log | Risk register |
|---|---|---|
| Risks | Yes | Yes |
| Assumptions | Yes | Usually no |
| Issues | Yes | No |
| Dependencies | Yes | No |
| Main purpose | Broad delivery visibility | Risk management |
| Typical users | Delivery/Project teams | Project/Risk managers |
| Best for | Day-to-day delivery oversight | Formal risk management |
When to use each
Use a risk register when the focus is formal risk management.
- Large programmes
- Regulated environments
- High-risk projects
- Projects with formal governance
- Projects requiring structured risk reporting
Use a RAID log when the team needs a broader view of delivery health.
- Agile delivery teams
- Software projects
- Product teams
- Cross-functional programmes
- Weekly delivery reviews
- Project status reporting
A simple rule
If the team mainly needs to track risk exposure and mitigation, use a risk register. If the team needs a wider picture of delivery blockers, assumptions and dependencies, use a RAID log.
In practice, many delivery teams use a RAID log because it captures more of what affects progress in real life.