# Summarization prompts that preserve meaning (not just reduce length)

> Templates to summarize long texts while keeping the right level of detail, key facts, and tone.

Source: Promptea — https://www.promptea.me/en/guides/summarization-prompts · Language: English · Last updated: 2026-11-09

## What makes summaries fail

- Not specifying the audience: the model guesses who needs the summary.
- No output length constraint: it either over-compresses or barely cuts.
- Missing 'what to preserve': key facts, decisions, open questions.
- No tone guidance: a formal report and a casual Slack message differ significantly.

## Controls that work

- Set a word or sentence limit and make it a hard constraint.
- Name the audience and their goal ('a PM who needs to decide quickly').
- List what must be preserved ('all numbers, deadlines, open decisions').
- Ask for a structured output: TL;DR + key points + action items.

## Before → after: a summary you can act on

- Before: "Summarize this meeting transcript." Result: a generic paragraph that mixes small talk with decisions and drops the deadlines.
- After: "Summarize this transcript for a project manager who missed the meeting. Max 150 words. Preserve all decisions, owners and deadlines. Format: TL;DR (one sentence), Decisions, Action items (owner, due date), Open questions."
- What changed: audience, length, what must be preserved and the structure are stated, so the summary is shorter and also more useful.

## Check that the summary is faithful

- Tell the model to use only the supplied text and not to add facts or interpretations that are not in it.
- Ask for the supporting quote for each number, name and date, then spot-check a few against the source.
- For very long inputs, summarize in parts (one section at a time) and then summarize the summaries; the full text may not fit, or the middle may get less attention.
- State what to do with uncertainty: 'if something is unclear in the text, list it under Open questions instead of resolving it'.

## Templates

### Structured document summary

```text
Summarize the document below for [audience: e.g. busy executive / junior developer].

Constraints:
- TL;DR: <= 2 sentences.
- Key points: <= 5 bullets (preserve all numbers, dates, and named decisions).
- Open questions: list anything that needs follow-up.
- Tone: [formal / casual / technical].

Document:
"""[paste]"""
```

[Open in Promptea](https://www.promptea.me/en/analyzer?prompt=Summarize+the+document+below+for+%5Baudience%3A+e.g.+busy+executive+%2F+junior+developer%5D.%0A%0AConstraints%3A%0A-+TL%3BDR%3A+%3C%3D+2+sentences.%0A-+Key+points%3A+%3C%3D+5+bullets+%28preserve+all+numbers%2C+dates%2C+and+named+decisions%29.%0A-+Open+questions%3A+list+anything+that+needs+follow-up.%0A-+Tone%3A+%5Bformal+%2F+casual+%2F+technical%5D.%0A%0ADocument%3A%0A%22%22%22%5Bpaste%5D%22%22%22&purpose=summarization&target=claude)

### Meeting notes → action items

```text
Extract a structured summary from these meeting notes.

Output:
1. Decision log: [decision] (owner, if mentioned)
2. Action items: [action] — [owner] — [deadline or 'no deadline']
3. Blocked items: [what is stuck and why]
4. TL;DR: <= 3 sentences

Notes:
"""[paste]"""
```

[Open in Promptea](https://www.promptea.me/en/analyzer?prompt=Extract+a+structured+summary+from+these+meeting+notes.%0A%0AOutput%3A%0A1.+Decision+log%3A+%5Bdecision%5D+%28owner%2C+if+mentioned%29%0A2.+Action+items%3A+%5Baction%5D+%E2%80%94+%5Bowner%5D+%E2%80%94+%5Bdeadline+or+%27no+deadline%27%5D%0A3.+Blocked+items%3A+%5Bwhat+is+stuck+and+why%5D%0A4.+TL%3BDR%3A+%3C%3D+3+sentences%0A%0ANotes%3A%0A%22%22%22%5Bpaste%5D%22%22%22&purpose=summarization&target=gpt)

## Frequently asked questions

### How do I avoid hallucinated facts in summaries?

Tell it to preserve only what is in the text and mark anything uncertain. Add: 'If a fact is not stated, omit it.'

### What if the document is too long?

Split it into sections and summarize each one. Then summarize the summaries. Specify the priority order if sections differ in importance.

### How long should a summary be?

Set the limit from the use: a one-sentence TL;DR for a glance, 100–150 words for a briefing, longer only if the reader will act on the details. Make the limit a hard constraint.

### How do I summarize a document that does not fit in one prompt?

Split it into sections, summarize each with the same instructions, then ask for a summary of those summaries. Keep the same preserve-list in every step so nothing important is dropped.