Why a good summary is hard to write
Most summaries fail in the same two ways: they hedge (every point starts with “the speaker discussed…”) or they list (10 bullet points, no shape). Neither is what a busy reader needs.
A good summary leads with the thesis, names the 5–8 things worth remembering, and stops. It tells you whether to re-listen. It works as a Slack message or a paragraph in a wiki — both readers get the same answer.
What a good summary contains
- TL;DR — one paragraph, ≤80 words, leading with the actual point — not a topic.
- Key points — 5–8 bullets, each a complete claim a reader can act on.
- Speaker attribution — who said what, when it matters (debate, interview).
- No filler — no “the speakers discussed,” no “various topics were covered.”
- Skim length — should fit on one screen — if it doesn't, it isn't a summary.
How audien·to summarises yours
What lands in the doc
- TL;DR paragraphone tight paragraph, ≤80 words, leading with the answer or thesis — not a recap.
- Key points5–8 bullets, each a single claim or decision. Ordered by importance, not chronology.
- Speaker attributionadded when more than one speaker matters (interview, debate). Dropped for monologue.
- Numbers preservedif a number was said (revenue, percent, deadline), it makes it into the summary verbatim.
- No invented claimsif it wasn't in the audio, it's not in the summary. We summarise what was said, not what should have been.
Summary length & shape
- Lead with the answeropen with the conclusion, not the topic. Readers came for the answer, not the agenda.
- Bullets are claims“Pricing rose 12%” beats “Pricing was discussed.” Each bullet should be act-on-able.
- 5–8 points, not 15if everything matters, nothing does. Pick the points worth remembering.
- One screen, not twoa summary that needs scrolling has lost the plot.
- Names and numbersconcrete details survive; vague references get dropped.
Knobs in the Options panel
- LengthShort (3 bullets) · Standard (5–8) · Long (10+) — for the cases when 8 is genuinely too few.
- ToneNeutral · Conversational · Punchy. Match the source audio.
- Speaker attributionby name · by role · off — depending on whether speakers carry the meaning.
- Bullet styleClaims (default) · Topics · Mixed — claims read fastest.
- Output language23 supported. Useful for a meeting in one language, summary in another.