Download Mobile AppUse This Template in Edworking
Copy the template below, then paste it into Edworking Docs to start collaborating with your team.
Free plan includes unlimited docs, tasks, and team members.
What Is a RAID Log?
A RAID log is a shared project record for risks, assumptions, issues, and dependencies. It helps teams separate what might happen, what is believed to be true, what is already blocking work, and what depends on another person or team.
The best RAID logs are reviewed regularly, owned clearly, and connected to tasks, docs, chat, and status updates.
What the Template Must Include
Use these fields to make the RAID log actionable instead of a static spreadsheet.
- A clear type for each item: risk, assumption, issue, or dependency
- Plain-language description that explains the project impact
- Priority or severity so the team knows what needs attention first
- One accountable owner for follow-up and updates
- Next action, due date, and current status
- Review cadence for keeping stale items out of the log
Step-by-Step: Build the RAID Log
Create the first version during kickoff or a project reset, then keep it alive during delivery.
- 1
List open risks, assumptions, issues, and dependencies from recent planning notes.
- 2
Classify each item into one RAID type so the team can respond correctly.
- 3
Assign an owner and next action for every high-priority item.
- 4
Link mitigation tasks, decision records, or supporting docs where follow-up work lives.
- 5
Review the log during weekly project updates and milestone checks.
- 6
Close, downgrade, or escalate items that no longer match the current project reality.
Template Example: Remote Launch RAID Log
Copy this structure into Edworking Docs and adapt each row to your project.
| RAID Field | Example Content |
|---|---|
| Risk | Customer approval may arrive late; owner: product lead; action: schedule decision review. |
| Assumption | Support team can reuse the existing onboarding FAQ; owner: support lead; action: verify gaps. |
| Issue | API test environment is unstable; owner: engineering lead; action: create fix task and status update. |
| Dependency | Marketing copy depends on final pricing page edits; owner: marketing lead; action: track page approval. |
| Priority | High items are reviewed weekly until closed or escalated. |
| Status | Open, watching, blocked, escalated, resolved, or closed. |
Common RAID Log Mistakes
Avoid these patterns when projects move across people, teams, or tools.
Mixing all items together
Label every entry as risk, assumption, issue, or dependency so the response is clear.
No owner is named
Assign one accountable owner even when several people help with the response.
Issues stay hidden in chat
Move active blockers into the log and link them to tasks or status updates.
The log is never reviewed
Add RAID review to weekly updates or milestone checks.
Turn the RAID Log into Follow-Through
The template works best when it lives where the project happens. Edworking connects the RAID log with tasks, docs, files, chat, and video calls so follow-up work stays visible.
Use Edworking Docs for the log and Tasks for each owner action.
Key Takeaways
- A RAID log tracks risks, assumptions, issues, and dependencies in one place.
- Different RAID types need different responses, owners, and review rhythms.
- High-priority entries should link to tasks, decisions, docs, or status updates.
- Regular review keeps stale assumptions and hidden issues from slowing the project.
- Edworking helps teams keep the log and the follow-up work in the same workspace.
Use This Template in Edworking
Copy the template below, then paste it into Edworking Docs to start collaborating with your team.
Free plan includes unlimited docs, tasks, and team members.
Frequently Asked Questions
RAID stands for risks, assumptions, issues, and dependencies.
A risk register focuses on possible future risks. A RAID log also tracks assumptions, active issues, and dependencies.
The project manager or project owner usually maintains it, while each entry has its own accountable owner.
Review it weekly on active projects and before major milestones or sponsor updates.