Executive Summary Prompt
Summary, Why It Matters, What Happens Next — the executive summary contract for readers who will never open the source.
The fidelity ladder: Balanced, High, Strict — and the six-rule battery that keeps a summary inside its source.
Summary hallucination is quiet: a connective sentence here, a "presumably" there, a gap filled with plausible context — and the summary now says things the source never did. The fix is a fidelity contract, and this resource demonstrates the strictest rung on the most ordinary source: weekly status updates. Strict Fidelity's battery — do not invent, do not infer unsupported conclusions, do not add missing context, only summarize what appears, preserve numbers and names exactly, and write "Not covered in the source" for empty sections — turns even a mundane roundup into a document you can trust without re-reading the source.
Match the rung to the stakes
Balanced for internal convenience, High when numbers and names matter, Strict when the summary IS the record.
Swap fidelity and diff the prompt
Load this setup, change the fidelity level, and watch the FIDELITY RULES block rewrite itself — three rungs, one axis.
Keep the gap rule
"Not covered in the source" is the cheapest hallucination insurance in the whole prompt — never delete it.
The Balanced and High rungs still lean on trust; Strict replaces the FIDELITY RULES block with the full six-rule battery — do not invent, do not infer unsupported conclusions, do not add missing context, only summarize what appears, preserve numbers/dates/names exactly, and write 'Not covered in the source' for empty sections. The other rungs relax one or more of those six; Strict enforces all of them at once.
That literal string is the gap rule doing its job: instead of padding a thin ## Key Points or inventing context to fill space, the prompt tells the model to write 'Not covered in the source' for any section with nothing behind it. The result is a visible blank rather than a plausible fill, so a forwarded summary never quietly implies coverage the source never had.
It only keeps the summary inside the source, not the source inside reality. The rule 'preserve numbers, dates, and names exactly as written' copies a mistaken figure faithfully rather than correcting it, and no rule fact-checks the original. Treat fidelity as anti-hallucination for the summary layer; verifying the source's own accuracy stays a separate step you own wherever you run the prompt.
Summary, Why It Matters, What Happens Next — the executive summary contract for readers who will never open the source.
The blocks a reliable summary prompt needs: source guidance, a fixed section skeleton, length budgets, fidelity rules, and quote handling.
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.
AI summaries read clean but quietly distort — an exception dropped, a "may" turned to "will," a target read as a guarantee. Here's how to summarize a document faithfully: scope it, name what must be preserved, keep the caveats, and check it back against the text.
Ask AI to "summarize these sources and list the findings" and one interview becomes "customers," a real disagreement disappears, and no claim shows its source. Build an evidence table instead: one row per claim, with its source, exact quote, and how strong the support really is.