Control / v1.0 clean-room
RAID Log
Keep risks, assumptions, issues, and dependencies visible enough to drive action.
When to use
Use from initiation through closure, reviewed at least weekly.
Sample suggested content
Project example: Weekly control review
- Risk: Acceptance criteria remain unclear; owner: Product Lead; action: confirm by Wednesday.
- Issue: Data owner blocked; owner: Project Manager; action: escalate in sponsor note.
- Dependency: Supplier test environment; owner: Supplier Lead; due: Friday.
Minimum version
- Type
- Description
- Owner
- Impact
- Next action
- Due date
- Status
Fuller version
- Probability
- Impact score
- Escalation path
- Response plan
- Decision link
Field guide
- ID
- Type
- Statement
- Owner
- Response
- Due
- Status
- Escalation
Tailoring notes
- Use one combined log for Lite projects
- Separate risk and issue registers for Enhanced controls
Common mistakes
- Logging items without owners
- Using the log as archive rather than agenda