Raid Log Update

Use when a project manager, program manager, scrum master, delivery lead, or PMO analyst needs to update a project's RAID log (Risks, Assumptions, Issues, Decisions / Dependencies) from new inputs — status-meeting notes, risk emails, blocker reports, decision memos, change-request forms — and produce a stakeholder status report. Guides intake of the prior RAID log (or initialisation if none exists), classification of each new input into the correct RAID lane, scoring of risks on a 1–5 probability × 1–5 impact scale with exposure and proximity, identification of issues with severity and target resolution date, recording of assumptions with validation owner and validation date, recording of decisions with rationale and reversibility, recording of dependencies with direction (inbound / outbound), counterparty, and need-by date; marks each entry as NEW / UPDATED / CLOSED / REOPENED so reviewers see the delta; produces a stakeholder status report with per-workstream RAG (Red / Amber / Green) ratings, top-3 risks, top decisions, open asks, and an unresolved-information list — for PM and sponsor review before circulation. Never auto-closes risks or issues without explicit user confirmation, never escalates without naming the escalation path, and never replaces the project sponsor's accountability for the project's RAG status.

by @archlab-space (devasher)·MIT-0