RAID log: turn risks, assumptions, issues and decisions into action
A practical RAID workflow that keeps exceptions connected to owners, dates, milestones and management decisions.
Decision this guide supports
Which uncertainty or problem needs action, escalation or a documented decision now?
Key takeaways
- Risks may happen; issues have happened; assumptions need validation; decisions need an accountable owner and rationale.
- A RAID log is useful only when entries change plans, actions or decisions.
- Connect material RAID items to affected milestones rather than maintaining an isolated register.
Four records with different management jobs
| Type | Plain-English meaning | Management response |
|---|---|---|
| Risk | An uncertain event that could affect objectives. | Assess exposure, choose a response, monitor triggers and assign an owner. |
| Assumption | Something treated as true for planning purposes. | Name the validation method, owner and latest safe date to confirm it. |
| Issue | A problem or event that already exists. | Contain impact, resolve the cause, update the forecast and escalate if outside tolerance. |
| Decision | A choice that commits the project to a direction. | Record options, rationale, approver, date and affected scope or milestones. |
What a good entry contains
- A specific cause, event and effect rather than a vague topic.
- The objective, deliverable or milestone that could be affected.
- One accountable owner and a dated next action.
- Probability and impact or another agreed prioritisation method.
- A response, contingency or decision path proportionate to exposure.
- A review date, trigger and short history of material changes.
Risk-writing pattern
Because of [cause], there is a possibility that [event] occurs, leading to [effect on an objective, milestone, cost or quality measure].
Assumptions are risks waiting for a test
Projects need assumptions because not everything is known when planning begins. The problem is not assuming; it is forgetting which parts of the plan depend on an untested belief.
Give important assumptions a validation date early enough to preserve options. If an assumption proves false, convert the consequence into a risk, issue, change or decision rather than quietly rewriting the plan.
A lightweight weekly RAID workflow
- 1Capture new items close to the work, while context is fresh.
- 2Triage duplicates, clarify wording and connect each material item to the plan.
- 3Review owner, exposure, next action and due date.
- 4Escalate only when a decision, tolerance breach or cross-project impact warrants it.
- 5Close entries with an outcome and retain the history for learning and assurance.
Do not neglect the D
Teams often maintain risks and issues but lose decisions in meeting minutes and chat threads. Months later, nobody remembers which options were considered, who approved the trade-off or which assumptions supported it.
A compact decision record protects momentum and accountability. Link it to the affected work so later changes can be understood without reconstructing the conversation.
When the log becomes administrative theatre
- Recording topics such as “resources” without a cause or consequence.
- Assigning the project manager as owner of everything.
- Reviewing every low-level item in senior governance.
- Closing an issue because a meeting happened rather than because impact was controlled.
- Keeping RAID separate from milestone, status and forecast updates.
- Deleting closed entries and losing the decision history.
Sources & method
This guide is RuruPilot’s practical synthesis. Definitions and established control principles are grounded in the primary sources below; examples, operating conventions and recommendations are our interpretation unless stated otherwise.
- 1APM glossary
Association for Project Management. Reference definitions for schedules, milestones, baselines, change control, risks, issues, governance and reporting.
- 2What is project management?
Association for Project Management. Overview of project objectives, constraints, controls, stakeholders, risk and change.
Talk it through
Want to apply this to your own project?
Tell us what you are facing. We can discuss project support, practical PM training, consultancy, or how RuruPilot could support your team.
Prefer email? Write to hello@macrocyra.com.