Extract a RAID log from meeting notes
Quickly pull out risks, assumptions, issues, and dependencies from raw, unstructured project sync notes into a clean tracking table.
Prompt
Act as a project manager. Read the raw meeting notes below and extract every item into a structured RAID (Risks, Assumptions, Issues, Dependencies) log.
Rules:
- Categorize strictly: Risk (potential future problem), Assumption (unverified premise taken as true), Issue (active current problem), Dependency (blocking external deliverable).
- Assign a realistic priority (High, Medium, Low) based on impact.
- Name an owner only if the notes mention or clearly imply one; otherwise write Unassigned.
- Give every line item one immediate next action.
Output format:
Markdown table with columns: ID, Category, Description, Impact/Priority, Owner, Next Action
Key Discussion Summary (3 bullet points)
Immediate Blockers requiring escalation
My notes are below:Example output
Paste the prompt into ChatGPT, Claude, or Gemini, then paste your raw transcript, bullet points, or Slack thread. You can follow up by asking the model to write a quick Slack update focusing only on the High priority items.
Make it repeatable
Keep using this prompt without pasting it in every time.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Audit project estimates for hidden optimism bias
Spot hidden assumptions, under-budgeted handoffs, and optimistic delivery timelines within detailed project task breakdowns.
Classify task dependencies by finish and start types
Structure unorganized project backlogs into precise chronological logic. Use this when setting up Gantt charts, critical paths, or sprint sequences.
Define out-of-scope boundaries before kickoff
Protect delivery timelines by establishing unambiguous project exclusions. Use this before sharing proposals, client contracts, or sprint charters.
Extract continuous phase-gate lessons from sprint notes
Identify recurring delivery risks and early project friction from sprint summaries before problems get buried at the final closeout.
Map vendor dependencies threatening project milestones
Flag critical third-party bottlenecks and deliverable handoffs before they create schedule delays. Use this when planning integration phases or reviewing delivery roadmaps.
Structure vague project lessons into searchable entries
Transform unstructured retrospective notes into categorized, searchable knowledge base entries with specific triggers and preventative actions.