Project Management guide · Risk, quality and control
RAID Log: Risks, Assumptions, Issues and Dependencies
A RAID log is a single register for tracking a project's Risks, Assumptions, Issues and Dependencies. It gives the project manager and sponsor one place to see the things that could knock the project off course.
Key takeaways
- A RAID log tracks risks, assumptions, issues and dependencies together.
- Each item needs an owner, an action, a date and a status.
- Test assumptions and turn false ones into risks or issues.
- Review it regularly and summarise the top items for the sponsor.
What RAID stands for
| Letter | Item | Meaning | Example |
|---|---|---|---|
| R | Risks | Uncertain events that could affect objectives | Supplier may deliver late |
| A | Assumptions | Things believed true for planning but not confirmed | Users will be available for testing in May |
| I | Issues | Problems happening now that need action | Test server is down |
| D | Dependencies | Links to work or decisions outside the team's control | Needs the finance team's new chart of accounts |
Some organisations use the D for decisions instead, or add a separate decisions tab. Agree which version you use at the start.
RAID log template
| Column | Risks | Assumptions | Issues | Dependencies |
|---|---|---|---|---|
| ID | R-01 | A-01 | I-01 | D-01 |
| Description | Cause, event, effect | What is assumed | What is wrong | What we depend on, and who provides it |
| Rating | Probability x impact | Impact if false | Priority / severity | Criticality |
| Owner | Risk owner | Who validates it | Who resolves it | Who manages the link |
| Action | Response | How and when it will be checked | Resolution steps | Agreement or follow-up |
| Due date | Review date | Validation date | Target fix date | Date needed |
| Status | Open / closed | Unconfirmed / confirmed / false | Open / resolved | On track / at risk / late |
Example entries
| ID | Type | Description | Owner | Status |
|---|---|---|---|---|
| R-03 | Risk | Because the vendor has a release freeze in December, critical fixes may wait four weeks, delaying go-live. | Tech lead | Open: mitigation agreed |
| A-02 | Assumption | The current CRM licence covers 50 extra users at no cost. | Procurement | To be confirmed by 15 May |
| I-05 | Issue | Integration tests failing because of expired certificates. | Infrastructure | In progress, fix due Friday |
| D-01 | Dependency | Website redesign needs the brand guidelines from the marketing project. | PM | At risk: guidelines two weeks late |
How to run a RAID review
- Share the log before the meeting and ask owners to update their items.
- Review new and high-priority items first.
- Check that assumptions due for validation have been tested; turn any false assumption into a risk or issue.
- Check dependencies with the teams that provide them.
- Agree actions, owners and dates, then close resolved items.
- Report the top items in the project status report.
RAID log vs separate logs
| RAID log | Separate risk register and issue log | |
|---|---|---|
| Best for | Small and medium projects, programme dashboards | Large or regulated projects |
| Strength | One view of everything | More detail and workflow per item type |
| Weakness | Can become a dumping ground | Information spread across documents |
Many teams keep a detailed risk register and issue log and use a RAID summary for the sponsor.
Tips
- Keep each tab short and current; archive closed items.
- Turn false assumptions into risks or issues promptly.
- Record dependencies in both directions: what you need and what others need from you.
- Use a shared tool so owners update their own items.
Free templates for this topic
Frequently asked questions
What does RAID stand for in a RAID log?
Risks, assumptions, issues and dependencies. Some teams use decisions instead of, or as well as, dependencies.
What is a RAID log used for?
To track the main risks, assumptions, issues and dependencies of a project in one place.
Who maintains the RAID log?
The project manager or a project coordinator, with each item owner keeping their own entries current.
How often should a RAID log be reviewed?
Typically weekly or at each regular project meeting, with the top items reported to the sponsor.
What is the difference between a risk and an assumption in a RAID log?
An assumption is something treated as true for planning; a risk is an uncertain event. An assumption that might prove false creates a risk.
What is the difference between a risk and an issue in a RAID log?
A risk might happen; an issue is already happening.
What is a dependency in a RAID log?
A relationship where one piece of work relies on another, often owned by a different team or organisation.
Can I create a RAID log in Excel?
Yes. A workbook with a tab for each type is the most common format.
Is a RAID log the same as a risk register?
No. A risk register covers risks only; a RAID log also covers assumptions, issues and dependencies.
What is RAIDD and how does it extend a RAID log?
A variation of the RAID log that also tracks decisions: risks, assumptions, issues, dependencies and decisions.
Do Agile teams use RAID logs?
Some do, especially in larger organisations or programmes, though many Agile teams manage impediments on their board instead.