Project Toolkitby Maxime Lab
Governance · tool 9 of 14

Governance · tool 9 of 14

RAID Log

RAID Log: puts risks, assumptions, issues and dependencies in one place you actually review.

Best for: Weekly project control · Time: 15 min a week
Domain: Governance · Focus area: Executing

How it works

RAID stands for Risks, Assumptions, Issues and Dependencies. A risk might happen, an issue is happening, an assumption is believed but unproven, and a dependency is something you need from someone else.

  • Each line has an owner and a next action date.
  • Assumptions become risks if they start looking doubtful.
  • Review the top items weekly, not the whole list.

How to apply it

  1. Start with one table and a type column.
  2. Fill it in during kick-off.
  3. Review the top five items every week.
  4. Close items and record what happened.
In practice

Dependency: security review from IT by 10 May. Owner: Sara. If it’s late, testing slips one for one.

Pro tip

An item without a date is a note. Give everything a next action.

Use it

Quick check

A server failed this morning. Which type is that?

Sources

  • PMBOK® Guide, 8th edition, and The Standard for Project Management (PMI, 2025)

Last reviewed 2026-11-02 against the PMBOK® Guide, 8th edition · Practitioner review pending · How this guide is made