RAID Log

A RAID log is a single register that tracks a project’s Risks, Assumptions, Issues and Dependencies — the four categories of uncertainty and constraint a project manager must keep on top of.

A RAID log is a consolidated project management tool that records four related things: Risks (potential future problems), Assumptions (things taken to be true that the plan depends on), Issues (problems that have already occurred), and Dependencies (things the project relies on from — or provides to — outside itself). Some variants read the "A" as Actions. Each entry has an owner, a status and relevant details. The RAID log gives the PM one place to see all the "watch items" that could derail delivery, and it is reviewed regularly throughout the project.

Why it matters

Risks, assumptions, issues and dependencies are the things that most often surprise projects, and they are easy to lose track of when scattered across emails and meetings. Consolidating them into one reviewed log ensures none is forgotten, each has an owner, and their status is visible. It is a lightweight governance tool that turns vague worries into tracked, assignable items — and it doubles as an audit trail of what the project was watching and how it responded.

When to use it

Start a RAID log at project initiation and maintain it throughout, reviewing it in regular status meetings. It suits projects of almost any size — a small project may keep a simple combined sheet, while a large one may split each category into its own detailed register (risk register, issue log, etc.) that the RAID log summarises.

How to use it

1. Set up four sections: Risks, Assumptions, Issues, Dependencies (or Actions).
2. Log each item with a description, owner, date raised, status and next step.
3. For risks, add probability, impact and response; for issues, add priority and resolution.
4. Review the log at every status meeting — update statuses and escalate as needed.
5. Close items when resolved and keep them for the audit trail and lessons learned.

Example

A project’s RAID log holds: Risk — "vendor may miss deadline" (owner: PM, mitigate); Assumption — "test environment available by week 3" (owner: IT, to validate); Issue — "key developer left" (owner: PM, backfill in progress); Dependency — "needs sign-off from Legal before launch" (owner: Legal). One glance shows every threat to delivery and who owns it.

Template

A RAID log template has four tabs or sections — Risks, Assumptions, Issues, Dependencies — each with ID, description, owner, status and actions.

Browse templates →

Tools

Related topics

FAQs

Alternatives

• Separate registers — a dedicated risk register, issue log, etc. for larger projects
• Assumption log — the assumptions portion tracked on its own
• Kanban impediments board — the Agile way of surfacing blockers