RAID Log
A consolidated control log for tracking risks, assumptions, issues, and dependencies that can affect project or programme delivery.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/raid-log/
01What it means
A RAID log brings four related control categories into one governed view: risks are uncertain events, assumptions are propositions treated as true for planning, issues are current problems requiring action, and dependencies are relationships on work or decisions outside an item’s direct control. Some organizations extend the log with decisions or constraints, but the categories should remain explicit.[1][2]
| Category | Meaning | Control response |
|---|---|---|
| Risk | Uncertain event that may affect objectives | Assess probability and impact; mitigate, transfer, accept, or avoid |
| Assumption | Proposition treated as true for planning | Validate by a named date; revise the plan if false |
| Issue | Current problem already affecting delivery | Assign action, due date, escalation, and resolution evidence |
| Dependency | Reliance on external work, decision, or condition | Confirm owner, timing, interface, fallback, and monitoring |
Shared ownership, due dates, evidence, escalation, and category transitions make the log useful; a static list creates false control.
02Why it matters
Delivery often fails at the boundaries between plans: an assumption expires, another team misses a dependency, or a risk becomes an issue without ownership. A RAID log gives these conditions identifiers, owners, actions, dates, and escalation paths. Reviewed well, it supports better decisions and prevents important uncertainty from disappearing into meeting notes.
03When to use it
Use a RAID log for projects and programmes with cross-team dependencies, meaningful uncertainty, external approvals, or several governance forums. A lightweight version can serve smaller initiatives. Establish it during initiation, review it throughout delivery, and retain the history needed to understand decisions and recurring problems.
04How it works
- Define category rules, required fields, scoring conventions, ownership, status values, and escalation thresholds.
- Record each item with a unique identifier, concise description, impact, owner, actions, due dates, and evidence.
- Validate assumptions and dependencies by named dates rather than leaving them as permanent background statements.
- Review high-priority and overdue items in the governance forum able to make the required decision.
- Convert realized risks into issues, link related records, close items with evidence, and preserve an audit trail.
05A practical example
A mobile-banking programme records a risk that identity testing may reveal defects, an assumption that legal review will finish by May, an issue involving an unavailable test environment, and a dependency on a vendor software release. Each item has an owner, next action, target date, and escalation threshold reviewed weekly.
06Where it breaks
Combining categories can create a long, unfocused spreadsheet that obscures specialist risk or dependency analysis. Scores are subjective, and a frequently updated log still adds little if owners lack authority or meetings merely recite statuses. Sensitive issues may also require restricted handling rather than broad circulation in one register.
Common mistakes
- Using risk, assumption, issue, and dependency as interchangeable labels.
- Recording items without owners, next actions, review dates, or escalation rules.
- Keeping resolved items open indefinitely or deleting them without history.
- Reviewing the whole log mechanically instead of focusing on decisions and change.
07Sources
- Gate 2 Review: Delivery StrategyUK Infrastructure and Projects Authority · Government assurance guidanceGate 2 Review: Delivery Strategy
- Planning and Managing DeploymentAssociation for Project Management · Professional competence guidancePlanning and Managing Deployment