Create a RAID Log with AI
Intermediate · Save 2-3 hours per project
Overview
Stand up a complete RAID log—Risks, Assumptions, Issues, and Dependencies—from your project context, with owners, impact levels, and action plans already scaffolded. This workflow gets the single most useful project-governance document started in minutes instead of an afternoon.
Best For
- Project managers
- Program leads
- PMO analysts
- Operations leaders
Problem
A RAID log is one of the most useful tools a project manager has, but it's tedious to populate from scratch—four categories, each needing descriptions, impact, owners, and action plans. Because the blank version is so much work, teams either skip it or start one and never maintain it, losing the governance visibility it's meant to provide.
Solution
AI scaffolds all four RAID categories from your project context, giving you a populated first draft: candidate risks, the assumptions you're implicitly making, issues already surfacing, and dependencies across teams and systems. You edit for accuracy and assign real owners. The log doesn't need to be exhaustive on day one—it needs to be started and then maintained, and AI removes the friction of starting.
Workflow Steps
- 1
Provide your project context: goal, timeline, team, dependencies, and anything already going sideways.
- 2
Prompt the AI to generate entries across all four RAID categories using the prompt below.
- 3
Review each entry for accuracy—remove anything that doesn't apply and add anything obvious it missed.
- 4
Assign a specific owner to every item; unowned items fall through the cracks.
- 5
Set impact levels and target review dates.
- 6
Move it into a spreadsheet or PM tool and schedule a recurring RAID review.
Recommended Tools
Example Prompt
Help me create a RAID log for this project: - Goal: [what it delivers] - Timeline: [dates] - Team & stakeholders: [list] - Known dependencies: [systems, vendors, other teams] - Anything already going wrong: [issues, if any] Produce entries in four sections: - Risks: potential problems that could affect the project (with likelihood + impact) - Assumptions: things being taken as true that, if wrong, would change the plan - Issues: things already happening that need managing - Dependencies: what this project relies on from others For each entry give a short description, a suggested owner role, and a suggested action or mitigation. Flag assumptions I should validate. Keep entries concise enough to drop into a spreadsheet.