Office guide

How to Use RAID Log Builder

A RAID log keeps Risks, Assumptions, Issues, and Dependencies distinct. That separation helps teams respond to uncertain events, validate beliefs, resolve current problems, and track required inputs.

Open the RAID Log Builder

What to prepare

A few reliable inputs make the first result easier to review.

  • A project name and clear definitions for the four RAID types
  • Descriptions, owners, due dates, statuses, and supporting evidence
  • A review cadence and escalation route

How to Use RAID Log Builder

  1. Name the project
  2. Add each entry with type, description, owner, due date, and status
  3. Build the log and check whether every item is classified correctly
  4. Review open items regularly, update statuses, and export a dated snapshot

Worked example

A supplier might miss a deadline is a Risk. Supplier capacity is sufficient is an Assumption. A shipment already failed is an Issue. Final design approval before manufacturing is a Dependency.

Review the result

Convert assumptions that prove false into risks or issues as appropriate. Close entries only when the response is complete or the item is no longer relevant, and record the reason.

Practical tips

  • Write risks as cause, event, and effect
  • Give assumptions a validation date
  • Link dependencies to the owner of the required input

Common mistakes to avoid

  • Calling every concern a risk
  • Leaving assumptions ownerless
  • Keeping resolved issues open indefinitely

Build it in your browser

The free RAID Log Builder processes entries locally in your browser. Review the generated draft against source information and any policy that applies before sharing it.

Use the RAID Log Builder