RAID log
Track Risks, Assumptions, Issues, and Dependencies in one place — prioritize by probability and impact, assign owners, and drive resolution.
About this template
The RAID Log is a project management essential: a single view of everything that could derail your project. Risks are potential problems, Assumptions are unverified beliefs, Issues are current problems, and Dependencies are external blockers.
Columns track item lifecycle from Open through Mitigated to Closed, so you always know what needs attention and what's been resolved.
Built-in fields cover Probability, Impact, Owner, Mitigation Plan, Target Date, and Category — giving you a complete risk register without a separate spreadsheet.
What's inside
Columns included
Task types
Custom fields
Key features
- Four item types: Risk, Assumption, Issue, Dependency
- Lifecycle columns from Open to Closed
- Probability and Impact scoring
- Owner assignment and mitigation planning
- Category tags (Technical, Resource, Schedule, Budget, Scope, External)
- Task relations for traceability
Who is this template for?
- Project managers tracking risks
- PMO teams standardizing risk management
- Delivery teams surfacing blockers
- Stakeholder communication on project health
- Audit and compliance documentation
How to use this template
Use this board as a living RAID log, so risks and blockers stay visible, prioritized, and connected to the work they affect.
Step 1
Capture each item with the right type
Create entries as Risk, Assumption, Issue, or Dependency so the team knows whether it is managing a possible threat, an active problem, or an external blocker. Fill in Probability, Impact, Owner, and Trigger early to make prioritization easier.
Step 2
Track mitigation as active work
Move items from Open into In progress or Monitoring as soon as someone is actively handling them. Use Mitigation plan, Target date, and Category to make the next action visible instead of turning the log into a passive register.
Step 3
Close the loop with traceability
When exposure is reduced or resolved, move the item into Mitigated or Closed and link any Related tasks that were affected. This makes reviews easier because the log shows both the original risk and the delivery work created to address it.
Compare this template
Explore how this raid log workflow compares with other tools across real use cases.
Jira vs Vaiz for RAID log management
Jira alternative for RAID log management. Track Risks, Assumptions, Issues, and Dependencies in one place. Prioritize by probability and impact, assign owners, and drive resolution.
Learn moreAsana vs Vaiz for RAID log management
Asana alternative for RAID log management. Track Risks, Assumptions, Issues, and Dependencies in one place. Prioritize by probability and impact, assign owners, and drive resolution.
Learn moreMonday vs Vaiz for RAID log management
Monday alternative for RAID log management. Track Risks, Assumptions, Issues, and Dependencies in one place. Prioritize by probability and impact, assign owners, and drive resolution.
Learn moreLinear vs Vaiz for RAID log management
Linear alternative for RAID log management. Track Risks, Assumptions, Issues, and Dependencies in one place. Prioritize by probability and impact, assign owners, and drive resolution.
Learn moreFrequently asked questions
What does RAID stand for?
What's the difference between a Risk and an Issue?
How do I prioritize items?
What's a Trigger?
How often should I review the RAID log?
Can I link RAID items to tasks?
Related templates
Scrum
A ready-to-run Scrum board with ceremonies, sprint tracking, WIP limits, and engineering task categories.
Kanban
Classic Kanban flow with a strict WIP limit — visualize work, reduce bottlenecks, and ship continuously.
Waterfall
A phase-based Waterfall template for fixed-scope projects — move work through requirements, design, build, QA, release, and maintenance with clear gates.