How Do You Get a Useful Summary From Claude?
Tell Claude who will read the summary and what they'll do with it. A summary is a set of choices about what to keep, and "summarize this" gives Claude no basis for those choices. A reader and a decision do. Also ask what the source leaves out, since a summary can't show you that by itself.
<document> [attach or paste the source] </document> Summarize this for this reader: Reader: [role and what they already know] What they'll do with it: [the decision or action] What they must be able to answer afterward: [2 or 3 specific questions] Length: [for example, 200 words] Start with what they need for that decision. Leave out anything that doesn't affect it, even if the author stresses it. Translate terms they won't know. End with "Not covered": what this reader would want to know that the document doesn't say. If the document doesn't answer one of the questions, say "The document doesn't say" rather than inferring an answer.
- Readerwho will read it
- Decisionwhat they'll do next
- Questionwhat they must answer
- Gapswhat the source doesn't say
Try it now
- 1Click +, choose Add files or photos, and attach something you need to pass on this week.
- 2Fill in the reader and their questions, and send.
- 3Send a second version in the same chat: "Now do this for [a different reader] who has to [different action]." Compare the two.
- 4You'll know it worked when the two versions keep different things, and "Not covered" names something you'd want to go and find out.
Use it when
Board packs, contracts for a non-lawyer, research papers for a practitioner, call transcripts for someone who missed the call, and policy documents. Use it whenever the reader isn't you, or when you'll send the summary on without rereading the source.
Skip it when
When you need the source's full argument for your own study. A tailored summary removes things on purpose, so read the original or ask for a faithful section-by-section version instead. And never replace reading with this where you're signing or certifying the document.
Why it works
Anthropic's prompting guide says context about your goals helps Claude give a more targeted response, and it can generalize from the reason you give. The reader and purpose are that context. Knowing a CFO has to approve a budget tells Claude that cost and risk matter and that the methods section doesn't.
Its research guidance adds a related point: define what a successful answer looks like. For a summary, that's the question the reader must be able to answer afterward. It also suggests giving explicit permission to admit gaps, for example "I don't have enough information", which can sharply reduce false information, Anthropic says. So tell Claude that "the report doesn't say" is an acceptable answer.
Example
Say you have a 40-page vendor security review. Your CFO has to approve the contract and asks: is there a blocking risk, what does fixing it cost, and when would it be done? Your security engineer gets a different brief: which controls failed, and what evidence is there? The CFO's version should have no control numbers and might note under "Not covered" that the review gives no cost for fixes. That's your cue to ask the vendor before the meeting.
Going further
For a regular report, put the reader into project instructions, so that you can drop in next month's file and just type "summarize". Anthropic says project instructions apply to all chats in that project.
For summaries of your own email or documents, Research can draw on connected Gmail, Google Calendar and Google Docs, per Anthropic's help page. Its Academy suggests naming the source directly, such as asking it to pull context from recent emails. Do that from the web or Claude Desktop, not the mobile app, which skips connectors silently.
Common mistakes
- Naming a reader with no decision. "For the CEO" helps less than "for the CEO deciding whether to renew by Friday".
- Forgetting that the author's emphasis isn't the reader's. A vendor's report stresses its strengths, so tell Claude what your reader cares about.
- Forwarding it unread. Claude's summary goes out under your name, so check the figures against the source.
- Not allowing "the document doesn't say". Otherwise, you may get a confident inference where the source is silent.
Sources
- Prompting best practices, Claude Platform Docs
- Reduce hallucinations, Claude Platform Docs
- How can I create and manage projects?, Claude Help Center
- Use research on Claude, Claude Help Center
- Research for deep dives, Claude Academy
Checked 6 November 2026. Products change often, so confirm details with the vendor.