ClaudeSummarizationLevel 2: Context

How Do You Get Claude to Put the Conclusion First?

Spell out the shape: one sentence with the conclusion, then three to five supporting facts, then detail for whoever needs it. An explicit format decides what comes first, where "summarize this" leaves that to chance. Attach long documents above your instructions, not below them.

Prompt to copy 
<document>
[attach or paste the source]
</document>

Summarize this for [reader], who needs to answer: [the exact question].

Format:
Line 1: one sentence that answers that question directly, with no introduction.
Then: 3 to 5 bullets, each a specific fact with a number or name, in order of importance to that question.
Then: a section headed "Detail" of up to 150 words for anyone who needs more.
Last: one line saying what the document doesn't tell us about this question.

Someone who reads only line 1 should still get the correct answer. If the document doesn't answer the question, make line 1 say that.
  1. 1One sentence: the conclusionread first
  2. 23 to 5 facts behind itskim
  3. 3Detail and sourceson demand
A rule of thumb, not an Anthropic chart: each layer lets the reader stop once they have what they need.

Try it now

  1. 1Attach a long report or paste an email thread, placing it above your instructions as in the prompt.
  2. 2Replace the question with the exact one your reader will ask.
  3. 3Cover everything except line 1 and ask: could my reader act on this? If not, tell Claude what's missing.
  4. 4You'll know it worked when line 1 answers the question without needing the bullets, and the last line names a real gap.

Use it when

Status updates to busy managers, briefing notes, meeting recaps, long email threads, research digests, and the opening of a report. It's right whenever some readers will stop after one line and others will need everything.

Skip it when

Bad-news messages where the reader needs context first, or a persuasive piece for someone who'd reject the conclusion before hearing the reasons. Also think twice with creative or narrative work, where the order is the point.

Why it works

A source's order reflects the author's reasoning, and a reader usually wants the outcome. Saying "bottom line first" isn't enough on its own, because what counts as the bottom line depends on the question. So say exactly what line 1 has to answer.

Anthropic's prompting guide offers several things that help here. Be specific about format and constraints. Tell Claude what to do, not what to avoid. Match your prompt's style to the output you want: removing markdown from your prompt can reduce markdown in the reply. Place long documents near the top, above your query and instructions. Its help page for Google Docs lists a related job, rewriting an executive summary to lead with the recommendation.

Example

Say your COO asks whether last quarter's pricing test should continue, and you have a 30-page analysis. Your question is: "Should we extend the pricing test, yes or no, and why?" Line 1 should state the recommendation in the report, if there is one. The bullets carry the numbers behind it. The final line might note that the report doesn't cover existing customers. If it makes no recommendation, line 1 should say so, which is itself useful to know before the meeting.

Going further

Works on Research too. Anthropic's Academy suggests specifying the sections or structure you want, so tell it: "Open with a 3-sentence answer, then findings, then sources." Otherwise, you get a long report to read through.

To make it a habit, add the format to project instructions. If your reports are written in Word, use Claude's add-in on the existing document: "Rewrite this executive summary to lead with the recommendation". If it comes back in too many bullets, Anthropic's guide includes a sample instruction telling Claude to write flowing prose and use lists only for truly discrete items.

Common mistakes

  • Asking for a "TL;DR" with no question. Claude then has to pick the main point, which may not be the one your reader cares about.
  • Allowing an introduction. "This report examines..." on line 1 isn't a conclusion, and it pushes the answer out of sight.
  • Forcing a conclusion the source doesn't support. Tell Claude that "the document doesn't answer this" is an acceptable line 1.
  • Putting instructions above a 100-page attachment. Anthropic advises placing long documents above your query and instructions.

Sources

Checked 6 November 2026. Products change often, so confirm details with the vendor.

Related

Best practice How Do You Get a Useful Summary From Claude? Best practice How Do You Get Claude to Explain Something at the Right Level? Workflow How Do You Get Claude to Cite Its Sources? Workflow How Do You Build a SaaS With Claude, One Slice at a Time?

Beyond the course

Glossary Hallucination Pricing guide Claude pricing, plans and models