Most RAID logs die in week three. Not because the team stopped caring, but because the tool was heavier than the habit. Someone built a beautiful tracker at kickoff, with twelve columns and a scoring rubric, and by month two it was a tab nobody opened.
This one is one screen. Type the entry, score probability and impact, name an owner, come back next week. Everything saves in your browser, on your device. No login, no server, no install.
| Type | Description | Probability | Impact | Score | Owner | Status | Delete |
|---|
A RAID log is not a document. It is a meeting agenda. If you are not reviewing it, you do not have one. Here is the rhythm I run on every program, fifteen minutes, once a week, same slot:
Fifteen minutes, every week, one named person running it. That is the difference between a living RAID log and archive material.
It will hold a small program's RAID entries and run your weekly review. When the log becomes the tool you open every day, you will want more than one flat table.
The full web app: saved views, filters by owner and severity, one-click promotion of risks to issues. Built to be your permanent tool.
$49 ›If your team lives in spreadsheets. Excel + Google Sheets, conditional formatting, PDF cheat sheet with the full review cadence.
$29 ›The full DirectorPM toolkit: RAID, risk register, status reports, charters, OKRs, and more. $533 bought separately.
$99 ›One page, no cost. The exact status format I use to brief leadership in under five minutes. It is the fastest way to see how these tools read before you spend anything.