The Meeting-to-Action Machine

Top-Prompts

Raw notes in, accountable decisions out

01 The Concept

The highest-ROI prompt in most companies is the one that turns messy meeting notes into decisions, actions, and open questions — because that's the artifact people actually need and never write. The template's power comes from three rules: every action gets an owner and a date or it goes to a 'needs owner' list (no vague 'team will look into it'), decisions are separated from discussion (what was decided vs. what was merely said), and anything ambiguous in the notes is surfaced as a question rather than silently resolved.

Keep the template stable and paste it after your raw notes — transcript, bullet chaos, or photos of a whiteboard. The consistency is the feature: same sections every time means people learn to scan it.

02 Weak vs. Strong

EX 01The template

Turn the raw meeting notes below into an action summary. Rules:

DECISIONS — only things the notes show were actually decided. If something reads 'apparently agreed' but nobody said yes, list it under 'Confirm these'.
ACTIONS — table: action / owner / due date. An action with no owner or no date goes to NEEDS OWNER instead — do not guess owners.
NEEDS OWNER — actions everyone nodded at but nobody took.
OPEN QUESTIONS — anything ambiguous or contested in the notes, with who raised it. Do not resolve ambiguity yourself.
PARKING LOT — ideas explicitly deferred.

Style: no filler, no 'productive discussion was had'. If the notes are too thin to extract something, say so.

NOTES: [paste raw notes]

→ Why it works

Each rule blocks a specific failure: invented owners, discussion laundered into decisions, ambiguity silently resolved, and the classic summary that reads nice but assigns nothing.

EX 02Follow-up variant: the accountability diff

Below are last week's action summary and this week's raw notes. Produce:

STATUS DIFF — table of last week's actions: done / slipped / silently vanished (in notes at all?)
'Silently vanished' items listed by name — these are the ones to raise
Then the standard action summary for this week (same 5-section template)

Rule: an action counts as done only if this week's notes say so. Absence of mention = vanished, not done.

LAST WEEK: [paste summary] THIS WEEK'S NOTES: [paste notes]

→ Why it works

The diff against last week's commitments is where accountability actually lives — and 'absence = vanished, not done' stops the model charitably closing items nobody mentioned.

03 Key Points

01Actions without owner+date are listed separately as 'NEEDS OWNER' — the template refuses to launder vagueness

02Decisions ≠ discussion: 'we decided X' requires evidence in the notes, else it's listed as 'apparently agreed, confirm'

03Ambiguities become explicit open questions — the model must not resolve them by guessing

04Attribute contested points: 'Sarah pushed back on the timeline' survives into the summary

05Stable section order every meeting: Decisions / Actions / Needs-owner / Open questions / Parking lot

06Works on any input: transcript, rough bullets, or 'here's what I remember' braindumps

04 Model-Specific Notes

Claude is careful about the decided-vs-discussed line when you demand evidence from the notes — and will honestly populate 'Confirm these'. Paste transcripts whole; it handles hour-long meetings comfortably.

05 For Your Role

Works for any group decision — family trip planning, club committees: decisions, who-does-what, and the things everyone nodded at that nobody took.

Next: The Slide Outline Generator →