RAID

Score a risk before any response, then again assuming the response works. The reduction between the two is the number worth taking to the board.

One bar per variable, the widest at the top, all of them measured against a baseline down the middle. A tornado diagram ranks what could move an outcome, and by how much.

A risk might happen. An issue already has. That single difference decides which artefact a line belongs in, what you record about it, and who you have to tell.

Contingency reserve sits inside the cost baseline, for risks already named and priced. Management reserve sits above it, for the ones nobody named. Level and authority, not size.

Most risk registers record one number per row. The number that actually justifies spending money is the distance between two of them.

The exposure a risk carries before any action has been taken to manage it, scored on the same likelihood and impact scale as the residual score it is compared against.

The list of events that have already occurred and are affecting the work, each with an owner and a resolution date. Likelihood no longer applies.

A single register holding risks, assumptions, issues and dependencies, and usually decisions, with the type recorded on every line.

The exposure remaining once the planned response has been applied, scored on the same scale as the inherent assessment so the two can be subtracted.

The list of events that could affect the work but have not yet, each scored for likelihood and impact, with an owner and a planned response.

Recomputing an outcome while one input at a time moves across its plausible range, with every other input held at its base value, to rank what drives the result.

A horizontal bar chart ranking variables by how far each one moves an outcome, widest bar at the top. The narrowing stack of bars is what gives the chart its name.