Prompt templates for summarization: documents, meetings, and research

Copy-paste templates to summarize long documents, meeting notes, and research reliably — with format and length controls built in.

← Back to guides

Why most summarization prompts fail

No length constraint: 'summarize this' gets whatever length the model prefers, not what you need.
No format specified: prose summaries and bullet lists carry different information density — pick one explicitly.
No audience specified: a summary for a technical team looks nothing like one for an executive or a customer.
No signal about what matters: the model weights recency and repetition by default, not importance to your actual goal.
No instruction for missing info: when input is ambiguous, the model fills gaps with assumptions rather than flagging them.

What makes a reliable summarization prompt

State the audience and purpose: 'For an executive who will not read the original' produces a different summary than 'For a teammate who needs to take action.'
Set a hard length: '5 bullets max', 'under 150 words', '3 sentences'. The constraint forces prioritization.
Name what to preserve: key decisions, numbers, dates, open questions, action items — whatever must survive the compression.
Name what to skip: background the reader knows, examples that only illustrate a point already made, repeated caveats.
Ask for a structured format: headline + bullets + action items is easier to scan and act on than unbroken prose.

Templates

Document or article summary

Summarize the following document.

Audience: [who will read this — e.g., a product manager, a non-technical executive, a customer]
Purpose: [what they will do with the summary — e.g., decide whether to read the full doc, prepare for a meeting, share with their team]

Output format:
- Headline (1 sentence): the single most important takeaway
- Key points (3–5 bullets): decisions made, numbers that matter, open questions
- Action items (if any): who needs to do what

Constraints:
- Under 200 words total
- Do not include background the audience already knows
- If something is unclear in the source, flag it rather than guessing

Document:
"""
[paste document here]
"""

Opens on home with the prompt prefilled.

Open in Promptea

Meeting notes summary

Summarize the following meeting notes into a concise record.

Output format:
## One-line summary
[What was decided or accomplished in one sentence]

## Decisions made
- [Decision 1 — who decided it, if mentioned]
- [Decision 2]

## Open questions
- [Question that was raised but not resolved]

## Action items
| Owner | Task | Due date |
|-------|------|----------|
| [name] | [task] | [date or "TBD"] |

## What was NOT decided
[Scope, timeline, or resource questions still open]

Constraints:
- Keep the format exactly as above
- If the notes don't mention something (e.g., no due dates), use "not mentioned" — do not invent
- Flag any conflict or unresolved disagreement you see in the notes

Meeting notes:
"""
[paste raw meeting notes here]
"""

Opens on home with the prompt prefilled.

Open in Promptea

FAQ

Why does AI miss important details in my summaries?

By default, models weight recency and frequency — content that appears late in the document or is mentioned multiple times is more likely to surface. If your key detail appears once, early, or in a footnote, it gets compressed out. The fix is to explicitly tell the model what must survive: 'Preserve all decisions, numbers, and action items.' If a specific detail is critical, name it: 'Do not lose the budget figure, even if the section around it is cut.'

How do I summarize a document that is too long to paste?

If the document fits in the model's context window (which for modern models is typically 128k–200k tokens, or roughly 100k–150k words), paste it in full — models handle long inputs well when given explicit output constraints. If it doesn't fit, divide the document into logical sections, summarize each one with the same template, then ask the model to synthesize the section summaries into a final summary. Keep the section summaries short so the final synthesis step has room to work.