Summarize Long Documents Without Losing the Point
"Summarize this" is a fair request, and it's also the reason so many summaries feel useless. A flat summary treats every paragraph of the source as roughly equally important, which is rarely true. A 40-page report might have three paragraphs that actually matter to your decision and thirty-seven that don't, and a generic summary has no way to know which three.
Tip
The same document can be summarized five different ways depending on who's reading it and what they need to decide. "Summarize this" doesn't tell Claude which of the five you want.
What actually shapes a good summary
Two things determine whether a summary is useful: who's going to read it, and what they need to be able to do after reading it. A summary for a colleague who needs to approve a budget looks nothing like a summary of the same document for someone who just wants a general sense of what happened, even though the source material is identical.
A summary isn't a shorter version of the document. It's an answer to a specific question about the document.
A process for a summary that's actually useful
- 1
State who's reading it and what they need from it
Not "summarize this for me" but "summarize this for a colleague who needs to decide whether to approve the budget." That framing tells Claude what to prioritize.
- 2
Set a length
A number, not "keep it short." "Under 150 words" and "keep it short" can produce very different results, since "short" compared to a 40-page report could still mean several paragraphs.
- 3
Name what to leave out, not just what to include
"Skip anything about timeline or staffing" does more work than a list of topics to cover, since it rules out entire sections up front instead of leaving Claude to guess whether they're relevant.
- 4
Check the summary against a section of the source
Spot-check one claim in the summary against the actual document, especially a specific number or date. This catches the rare case where something got compressed inaccurately.
Summarize this 40-page report in under 200 words, for someone who needs to decide whether to approve next quarter's budget. Focus only on the sections about budget risk and cost overruns. Skip anything about timeline or staffing entirely.
”That prompt names an audience, a purpose, a length, and an explicit exclusion. Compare it to a bare "summarize this," which would produce something reasonable but generic, likely touching every major section a little instead of focusing hard on the two that actually matter here.
- The audience and their purpose are stated
- A specific length is set, not "keep it short"
What to exclude is named, not just what to include
At least one claim is checked against the actual source
Inside Claude Tutorial
The same document, summarized differently for different readers.
Reshaping the same source material for different audiences comes up constantly, in reports, in updates, in any document more than one person needs a version of. The app has a full lesson on adapting one source for multiple readers.
The same source, two different summaries
The clearest way to see this in practice is to ask for two summaries of the same document and compare them.
Now summarize the same report again, this time for someone on the engineering team who wants to know what changed in the technical approach. Skip budget details entirely and focus on what's different from the previous version.
”Run both prompts against the same upload and the two summaries will barely overlap, even though nothing about the source changed. That's the proof that a summary is really an answer to a specific question, not a neutral compression of the whole document.
When you genuinely need a general overview
Sometimes there isn't a specific decision behind the request, you just need to know roughly what a document says before deciding whether it's worth a closer read. That's a legitimate use case for a more general summary, but it's still worth stating the purpose: "give me a general sense of what this covers, so I can decide whether to read it in full" is a specific request, even though the summary itself will be broader. The difference between that and a bare "summarize this" is that Claude knows you want breadth, not depth, and won't try to guess at a narrower focus you didn't actually have.
Common mistake
Asking for a summary and then being surprised it missed something you cared about. If the purpose wasn't stated, the summary was built around Claude's best guess at what mattered, not around what you actually needed it for.
Continue reading
- Working With PDFs and Long Documents in Claude: getting a long or scanned document into good enough shape to summarize accurately in the first place.
- Comparing Multiple Documents Side by Side: when you need to compare two documents instead of summarizing one.