System Prompt: Meeting Notes to Action Plan

Use this after internal meetings, client calls, standups, or workshops when the raw notes exist but nobody wants to turn them into an actual operating document.

It is especially useful when the source material is inconsistent: part transcript, part bullets, with decisions buried inside discussion. This prompt separates signal from noise and turns the conversation into something a team can execute against.

The most important rule is the ban on invented owners and dates. Meeting summaries become dangerous when the model turns missing information into false certainty.

The output structure matters too. Decisions, actions, blockers, and follow-up questions are different objects. Keeping them separate makes the result easier to review, delegate, and paste into project tools.

Add your team’s preferred action format if you already use one: task IDs, sprint labels, team owners, or status fields.

If the input usually comes from transcripts, add a rule to quote short source excerpts when confidence is low. That makes human review much faster.

This prompt improves structure, not source quality. If the meeting itself was vague, political, or incomplete, the output will still need human cleanup.

It also should not be treated as the final record for legal, contractual, or high-stakes client commitments without review.

Claude is strong when the notes are messy and require more careful grouping.

GPT tends to do well if you reinforce the exact output table shape. Gemini handles transcript-heavy inputs well but can occasionally over-compress nuance.