Project management practice

RAID log example: separate risks, assumptions, issues and dependencies

Use a four-part RAID log to distinguish uncertainty, unverified beliefs, current problems and external commitments, with linked actions and owners.

Give each entry the right treatment

This guide uses RAID for Risks, Assumptions, Issues and Dependencies. Some teams use different expansions, so confirm your convention. The value is in the action each category requires, not the acronym.

A risk needs a response to uncertainty. An assumption needs validation. An issue needs resolution. A dependency needs a confirmed input or commitment. Treating all four as “things to monitor” hides the work needed to protect delivery.

Worked example: one rollout, four distinct entries

TypeEntryAction and trigger
RiskReaders may arrive after installation starts.Obtain allocation confirmation; escalate if absent on day 3.
AssumptionThe network supports the new readers.Technical lead validates compatibility before configuration.
IssueThe test network is currently unavailable.Infrastructure lead restores access or supplies an agreed substitute.
DependencyFacilities must provide room access before installation.Confirm named owner, access window and escalation route.

Link entries when reality changes

If the compatibility check fails, close or revise the assumption and create an issue linked to it. If a supplier confirms a late shipment, turn the relevant uncertainty into a known issue and update the schedule forecast.

Keep the original record and dates. Deleting an assumption after it fails prevents a useful review of how the decision was made. The log should show the evidence available at the time, without blaming people for information that arrived later.

Copyable RAID entry

ID / type / date raised:
Statement and delivery objective affected:
Evidence or validation needed:
Owner / next action / due date:
Escalation trigger and decision authority:
Linked schedule task / risk / issue / change:
Status / resolution evidence / closure date:

Run a short decision-focused review

Review overdue actions, new evidence and entries that threaten the next milestone. Ask each owner what changed and what decision is now needed. Archive resolved items with evidence; do not spend every meeting rereading the entire register.

A dependency without an owner outside your team is a request, not a commitment. A log entry cannot make that commitment real; a confirmed conversation or agreement must support it.

Method background

These sources provide general background. The worked examples and worksheets are original Response Shift teaching material; the organisations do not endorse this product.