Structured Summary Prompt — the Anatomy
The blocks a reliable summary prompt needs: source guidance, a fixed section skeleton, length budgets, fidelity rules, and quote handling.
Summary, Why It Matters, What Happens Next — the executive summary contract for readers who will never open the source.
An executive summary has one reader contract: someone who will not read the source must be able to act anyway. This setup turns meeting transcripts into exactly that — a Summary section that leads with the single most important point in a strict sentence budget, a Why It Matters section grounded in the source, and a What Happens Next section of stated steps and deadlines, with an Action Items appendix. High fidelity keeps the model from "improving" the meeting; brief length keeps the executive reading.
Generate once, reuse per meeting
The prompt is the standard; paste each transcript below it and every brief comes back in the same shape.
Check the lede rule
"Lead with the single most important point" — the sentence budget forces a choice, which is exactly what executives pay for.
Let Action Items carry the follow-through
The appended section holds owner — task — deadline, so the brief doubles as the follow-up list.
A plain summary request lets the model choose its own shape; this locks it to three markdown sections in order — ## Summary (lead with the single most important point), ## Why It Matters, and ## What Happens Next — plus an ## Action Items appendix. The fidelity rules compress only what the transcript says, preserving numbers, dates, and names, rather than rewriting the meeting.
Four, in fixed order. ## Summary gives 3-4 sentences leading with the most important point; ## Why It Matters states the consequence for the reader per the source; ## What Happens Next lists stated steps, deadlines, or open decisions; and an appended ## Action Items holds one bullet per commitment as owner — task — deadline, omitted entirely when the source names none.
Yes — rewrite the TASK line for your reader and loosen the '1-2 sentences each' length rule if executives want more depth. Keep the fidelity rules intact, though: it compresses what the transcript actually says and preserves numbers, dates, and names exactly. It won't verify those facts or turn discussion into decisions, so treat it as a brief, not a formal decision record.
The blocks a reliable summary prompt needs: source guidance, a fixed section skeleton, length budgets, fidelity rules, and quote handling.
The fidelity ladder: Balanced, High, Strict — and the six-rule battery that keeps a summary inside its source.
Action items only: every commitment from the call — owner, task, deadline — straight into the CRM, with quotes for the promises that matter.
The contract that stops AI documents from restructuring themselves: a pinned section skeleton, forced tables, and strict consistency rules.
Free text in, named fields out. The extraction prompt pattern that turns any unstructured text into consistent, parseable records.
'Make it good', 'be detailed', 'keep it interesting' — vague prompts get vague output. The fix is mechanical: replace every fuzzy word with a checkable instruction.
Build summary prompts with fixed sections, length caps, and no-invention fidelity rules.
Cut a product idea down to the smallest first release that proves the core value — separate the real must-haves from everything that can wait, then define the MVP and its success signal.