Meeting Notes Document Prompt
Attendees, Decisions, Discussion, Action Items, Next Meeting — the notes document every meeting fills the same way.
Overview
Meeting notes work when they're a form, not an essay: the same five sections, filled live or right after, comparable across weeks. This setup generates the notes document with type rules that keep it honest — decisions recorded as statements rather than discussion recaps, action items as owner — task — deadline bullets. It structures NEW notes as they're written; when you need to compress an existing hour-long transcript instead, that's the Structured Summary Prompt's job — same family, opposite direction.
Workflow
-
Same form, every meeting
Rotating note-takers produce identical documents — the structure does the standardizing.
-
Watch the decisions rule
"Statements, not discussion recaps" — the line between a record and a transcript.
-
Scan action items weekly
Owner — task — deadline bullets make the follow-up review a one-minute scan.
Why This Works
- A fixed form beats prose notes for anything that gets compared later
- Statement-form decisions are quotable in the next meeting
- The structure survives note-taker rotation
Best for
- Recurring meetings with rotating note-takers
- Teams that act on notes rather than archive them
- Anyone comparing decisions across weeks
Not for
- Compressing an existing transcript — that's the Structured Summary Prompt (the boundary: new document vs existing source)
- Extracting action items as data fields — that's the Extraction Prompt Generator
Use cases
- Writing notes in the same structure for every recurring meeting
- Recording decisions as statements, not recaps
- Keeping action items assignable at a glance