---
name: RAID Log
description: Track risks, assumptions, issues, dependencies.
---
# RAID Log

A RAID log captures the four classes of thing that derail projects if unmanaged. Centralizing them ensures none is forgotten.

## The four
- **Risks** — future, uncertain, negative. Tracked with mitigation and owner.
- **Assumptions** — things believed true that, if false, change the plan. Each one is a latent risk; validate the load-bearing assumptions early.
- **Issues** — current problems needing action. Tracked with owner and resolution.
- **Dependencies** — things the project needs from others, or others need from it. Tracked with the dependency owner and due date; these are often the silent slip causes.

## Use
Review in a regular cadence. The log's value is currency, not completeness — a stale RAID log is just paperwork.