Back to Cookbook

RAID Log Auto-Assistant

Keep risks, issues, actions, and decisions connected to real work and reviewed on cadence

Risk management often decays into an outdated spreadsheet disconnected from daily execution. This recipe keeps a RAID log live: integrates risk triggers, promotes risks to issues, assigns owners, and enforces review cadence so surprises decrease instead of increasing.

House RecipeWork6 min

INGREDIENTS

📄Google Docs

PROMPT

Create a skill called "RAID Log Auto-Assistant". Input: any current risks/issues/actions/decisions (even messy). Output: a clean RAID log + review cadence summary. Requirements: - Keep risks and issues distinct; promote risks to issues when triggers occur. - Each entry needs owner + response/mitigation + due date (or TBD + question). - Produce a weekly summary: new/changed/aged items + top N risks by score. - Support confidentiality mode: one combined log or separate internal/external logs. Guardrails: - Never downplay high risks; if mitigation is missing, flag it prominently. - Do not invent scores; if unknown, ask for likelihood/impact.

How It Works

Paste your current risks, issues, actions, and decisions — even if they're partial or messy.

The recipe normalizes everything into a structured RAID log, identifies missing fields,

defines trigger conditions for when a risk becomes an issue, and produces a weekly review

summary so the log stays connected to real work.

What You Get

  • Structured RAID log: ID, description, owner, likelihood, impact, response, due dates, status
  • Promotion rules: clear triggers for when a risk becomes an issue
  • Weekly RAID summary: new, changed, and aged items for status meetings
  • Top risks view: exec-ready summary of the highest-scoring risks
  • Audit trail: what changed, when, and why

Setup Steps

  1. Paste existing risks, issues, actions, and decisions (any format)
  2. Identify project workstreams and owners
  3. Choose review cadence: weekly, biweekly, or monthly
  4. Review the structured log and weekly summary

Tips

  • Risks and issues stay distinct — promotion happens when a defined trigger fires
  • Scoring: low/medium/high or numeric 1–5 (configurable)
  • Supports confidentiality mode: one combined log or separate internal/external versions
  • High risks with missing mitigation are flagged prominently
  • Pairs well with Dependency & Blocker Radar for full risk visibility
Tags:#risk#raid#governance#reporting#tracking