Risk Register
Build or update a project risk register that a team will actually use. Writes each risk as cause, event, and effect; scores probability and impact on a stated 1-5 scale with explicit band cut-offs; adds expected monetary exposure when amounts exist; names a single owner, a response type, a concrete mitigation, an observable trigger with a threshold and date, a residual score, and a review date; separates risks from issues, assumptions, and dependencies; and on updates reports new, changed, closed, and realized risks. Use when someone asks for a risk register, to log or rescore project risks, what could go wrong with a plan, which risks need an owner or a trigger, or how to refresh a stale register before a steering meeting. Do not use for mapping what depends on what (use dependency-map), for a live production incident (use coordinate-production-incident), or for pricing a scope request (use scope-change-brief).