Any phase · Ways of working
Keep a risks, assumptions, issues and dependencies log
A RAID log keeps track of risks, assumptions, issues and dependencies in one place, with owners and actions. It stops important problems slipping through.
About 1-2 hoursEvergreenLast reviewed 5 November 2026
Who this applies to
- Skills it builds
- Delivery and execution
- PM types
- All
- Product types
- All
- Starting points
- All
- Ways of working
- Hybrid / stage gates
- Experience
- All
- Size of organisation
- All
Steps, by experience
Beginner (under 1 year)
- Create one log with four sections: risks, assumptions, issues and dependencies.
- For each item, write a short description, an owner and a next action.
- Rate risks by how likely and how serious they are.
- Review the log every week with the team.
- Escalate the most serious items to your sponsor.
Intermediate (1 to 4 years)
- Keep one RAID log with owners and actions.
- Rate and review regularly.
- Escalate serious items.
Experienced (5+ years)
- Link RAID items to the plan and roadmap.
- Use the log to drive decisions, not just record them.
- Keep it short and focused on what matters.
Who can do this
Owner: Product manager
Can be delegated to
- Delivery Manager or Scrum Master: Maintain the log and run reviews
Reviewed by: Delivery Manager
Tool examples
- Confluence
- Use a RAID log template on the project page.
- Jira
- Track risks and dependencies as issues with owners.
- SharePoint / Word
- Keep a shared log in a list with owners and dates.
Definition of done
- Log created with owners and actions
- Reviewed weekly
- Serious items escalated
Common pitfalls
- A log nobody reads
- Items with no owner
- Hundreds of minor items