Research

Summarisation

Compress documents without losing the point.

Knowledge cards
Workflow
Extract Claims With Citations You Can Check
A summarising pattern where you ask Claude to return each key point paired with the exact quote or section it came from, so every claim in the summary is traceable back to the source. The output isn't just a digest — it's a digest you can audit line by line.
L2 · Context engineering
Best practice
Lead With the Headline, Then the Detail
Structuring a summary so the single most important takeaway comes first — one line, the bottom line — followed by the key points, followed by supporting detail. The reader gets the conclusion immediately and descends into detail only as far as they need. It's the inverted pyramid, applied to AI summaries.
L2 · Context engineering
Best practice
Summarise for a Specific Reader and Purpose
Telling Claude who the summary is for and what they'll do with it — 'for an executive deciding whether to fund this', 'for an engineer who needs the technical constraints' — so the summary keeps what that reader needs and cuts what they don't, rather than producing a generic shrink of the source.
L2 · Context engineering
Knowledge card
Summarise Long Documents Without Losing the Thread
Summarising a long document by having Claude condense it in sections and then reconcile those into one coherent brief — while explicitly tracking the argument that runs through it.
L2 · Context engineering
Claude summarisation

Summarise toward a purpose

Claude's long context lets it summarise genuinely long documents in one pass, but the quality still depends on purpose. 'Summarise this' gives an even paraphrase; 'summarise this for a decision on whether to proceed, focusing on risks and cost' gives you something to act on. The purpose tells Claude what is signal and what is noise. Because it stays faithful to the source, its summaries reflect what the document actually says rather than a general impression — provided you tell it what the summary is for.

Ask for the gaps too

A summary is only safe to rely on if it is honest about its limits. Ask Claude to note what the source did not cover, where it was ambiguous, or what it could not verify — so you know the edges of what you are reading. Specify the shape you want, whether that is three takeaways, a risk list, or a one-line verdict with reasons. A summary that surfaces its gaps and serves a clear decision is worth far more than a neat paraphrase that hides them.

Frequently asked
How do I summarise long documents with Claude?

Give Claude the document and tell it what the summary is for and who will read it. Purpose is what lets it separate signal from noise; its long context handles the length.

Are Claude's summaries accurate?

They tend to reflect the source faithfully, but ask it to flag what it could not verify or the source did not cover, so you know the limits before acting on it.

What shape should I ask a summary in?

Whatever your decision needs — three takeaways, a risk list, or a verdict with reasons. Specifying the shape makes the summary directly useful rather than a generic paraphrase.