Turn a Long Document into a One-Page Summary (Without Losing What Matters)

Turn a 40-page report into one page of key points.

Level 2 · Assistant Free · 30 minutes · Updated Oct 31, 2026

Asking AI to “summarize this” takes five seconds. Getting a summary you could hand to your manager without worrying takes a little more. In the next 30 minutes you’ll turn a long report you haven’t read into a one-page summary: written for one specific person, with a page number on every point, and checked by you in three places.

Remember the intern: smart, fast, first day on the job. They’ll read 40 pages in a minute. But they don’t know what your manager cares about, their attention drifts in the middle of long documents, and they like to make things sound more certain than the original did. Today you’ll learn how to brief them so the summary is useful, and how to catch what they leave out.

What you’ll get

What you need

• Claude, any plan. We’ll use two features: file upload and Projects. Both work on the free plan. Free accounts can create up to five projects. Other tools work too; see the end.
• A long report, as a PDF. We’ll use this one throughout: Microsoft’s 2026 Work Trend Index Annual Report, published in May 2026. It’s free to download from the report page. It’s a good practice document. It’s long, it has lots of charts and survey numbers, and it was published by a company that sells AI tools, which is something a good summary should mention. Swap in your own document when you’re ready.
• One real reader. Ours: my department manager, who decides next week whether to pay for AI tools for our team of 12.

One rule before you upload anything at work: only use documents your company allows you to put into this tool. A public report is fine. A confidential contract may not be. See the boundaries in the framework.

The three rules

Everything below comes down to three rules. Each one is an action, not a slogan.

One more thing to keep in mind: you can only judge a summary of a document you’ve at least flipped through. If you’ve never seen the table of contents, you can’t tell what’s missing.

Part 1: One summary, done properly (30 minutes)

Six steps, from a report you haven’t read to a page you can forward. Copy the prompts as they are, then swap in your own document and reader.

Step 1. Brief the intern before handing over the file (3 minutes)

Most weak summaries start with “summarize this” and nothing else. The intern then has to guess: summarize for whom? How long? What matters?

Open a new chat in Claude and paste this, filled in. Don’t upload the file yet.

I'm going to upload a long report and I want a one-page summary. Don't summarize yet, just read this.

Document: Microsoft's 2026 Work Trend Index Annual Report, published May 2026.
Reader: my department manager.
Decision: next week she decides whether to pay for AI tools for our team of 12.
What she already knows: she has used ChatGPT a little. She hasn't read this report.
What she cares about: whether the productivity claims hold up, what a team like ours would need to get value, and the risks.
Format: one page. A three-sentence bottom line, then key points, then the report's own limitations, then what this summary doesn't cover.

The Decision line does most of the work. It tells the intern which parts of a long report matter and which they can skip.

Step 2. Flip through it yourself first (3 minutes)

This is the step people skip, and it’s what makes Step 5 possible. Open the PDF and look only at the table of contents, the section headings, the chart titles, and the methodology page (usually near the end).

Write down three things on a piece of paper:

• The main sections. (This report has an introduction, three numbered sections, a “take action” part, and endnotes with the methodology.)
• Who was surveyed. In this report, it’s people who already use AI at work, not all workers. That matters a lot for your manager’s decision.
• One thing you expect the summary to include.

Now you have a rough map. Later, when you read the summary, you’ll notice if a whole section is missing.

Step 3. Upload it and ask for a summary with page numbers (7 minutes)

Click + next to the message box, choose Add files or photos, and pick the PDF. Then send:

Here's the report. Write the summary I described, with these rules:
- After every point, give the PDF page number, e.g. (p. 14).
- Copy numbers exactly, including what they measure. Write "X% of AI users surveyed say...", not "X% of workers...".
- Keep the report's limiting words: "say", "may", "in our survey", "AI users".
- If a point is your interpretation and not something the report states, mark it [Interpretation].
- If a point comes from a chart, say so.

Read what comes back. It will look finished. It isn’t yet.

Step 4. Ask the three uncomfortable questions (4 minutes)

Three follow-ups:
1. Which parts of the middle sections did you leave out? List them with page numbers.
2. What limitations does the report itself mention: who was surveyed, where, when, and who paid for it?
3. Which of your points sounds more certain or more general than the report's own wording? Quote the original for each.

The first question goes after the most common problem with long documents: the middle gets less attention than the start and the end. The second gives your manager what she needs to judge the numbers. The third catches the intern’s habit of turning “may” into “will.”

Step 5. Check three pages yourself (8 minutes)

Pick the three points that matter most for your manager’s decision. Go to each page number and ask:

• Is the number the same, and does it describe the same people? (“AI users surveyed” is not “employees”.)
• Is it the same place and time? (Ten countries is not “globally”. One week of data is not “this year”.)
• Did a “say” or “may” become a fact?

Fix anything that fails, or delete it. Also hold the summary against your paper from Step 2. Is any main section missing completely?

Step 6. Turn it into the page your reader gets (5 minutes)

Rewrite the summary for my manager, using only the points I've kept: [paste or list the points you kept]
1. Bottom line, in 3 sentences, answering her decision directly
2. Key points, each with its page number
3. The report's limitations, including who published it and who was surveyed
4. What this summary doesn't cover

That last section is not optional. A summary that says what it left out is one people can trust.

Part 2: Set it up once for documents you read again and again (10 minutes to set up, about 10 minutes per document)

If you regularly read the same kind of document (monthly industry reports, supplier proposals, policy updates), you don’t want to retype the brief and rules every time. Give the intern a sticky note on their desk instead: a Project with standing instructions.

Step 1. Start from a run that worked

Only set this up after Part 1 has worked once by hand. Save a sloppy prompt and you’ll get sloppy summaries every time.

Step 2. Create the project

In Claude’s left sidebar, choose Projects, then + New Project in the upper right. Give it a name like “Reports for my manager.” Claude can’t see the name or description, so put nothing important there.

Step 3. Write the standing instructions

Open the project. On the right side of the page, click Set project instructions, paste the text below, and click Save instructions.

In this project I upload long documents and you write one-page summaries.

Default reader: my department manager. She makes budget and tooling decisions for our team of 12, has little time, and has used ChatGPT a little.
In each chat I'll tell you what decision the summary is for. If I don't, ask me before writing.

Rules for every summary:
- Give the PDF page number after every point.
- Copy numbers exactly, including who or what they measure.
- Keep the document's limiting words ("say", "may", "in our survey").
- Mark your own interpretations [Interpretation].
- Say when a point comes from a chart.

Format:
1. Bottom line in 3 sentences, answering her decision
2. Key points with page numbers
3. The document's own limitations, including who published it and who or what it is based on
4. What this summary doesn't cover

After the summary, always list: which middle sections you left out, and which points sound stronger than the original.

The last line builds the three uncomfortable questions from Part 1 into every run.

Step 4. Use it for each new document

Open the project, start a new chat, upload the document, and add one line: what decision this one is for. That’s it.

Step 5. Still check three pages, every time

The instructions make the summary better. They don’t make it checked. Do Part 1’s Step 5 on every document. It’s the part that takes most of your 10 minutes, and it’s the part that matters.

Step 6. Tune it once a month

Is a certain kind of mistake showing up again and again? Add a rule for it. Has your manager asked for something every time? Put it in the format. Treat the instructions as a living document.

Why you can’t skip the checking

When AI summarizes a document you gave it, it rarely invents a whole fact. The more common problems are quieter: it leaves things out, and it makes things sound bigger than they were. Researchers have measured both:

• It overstates. A 2025 study compared 4,900 summaries of scientific papers written by 10 popular AI models with the original papers. Most models drew broader conclusions than the papers did, even when asked to be accurate. AI summaries were about five times more likely than human-written summaries to make broad generalizations, and newer models tended to do worse than older ones (Peters & Chin-Yee, 2025).
• It leaves out the center. A 2026 study found that AI summaries from ChatGPT and Gemini left out 51.6% of the central details on average, and that people who read a misleading summary remembered the original event less accurately (Georgetown University, Sept 2026). That study summarized a video, not a report, but the pattern is the same one you’re checking for.
• The middle gets less attention. Researchers at Stanford and elsewhere found that language models use information best when it sits at the beginning or end of a long input, and noticeably worse when it’s in the middle (Liu et al., 2024). The models they tested were older, but it’s why Step 4 asks about the middle sections.
• It still adds things, sometimes. Vectara’s public leaderboard measures how often models add claims that aren’t in the document they’re summarizing. As of its May 2026 update, rates across 105 models ranged from 1.8% to 24.2% of summaries (Vectara). Even the best rate isn’t zero.

You can’t see an omission by reading the summary. It just isn’t there. And an overstatement often reads as a stronger, clearer point. That’s why the check uses two things the summary can’t fake: your own map from Step 2, and the page numbers from Step 3.

Checklist

Before you send the summary to anyone:

• I’m allowed to put this document into this tool
• The summary is written for one specific reader and answers their decision
• Every point has a page number
• I opened the three most important pages, and the numbers, people, places and dates match
• No “say,” “may” or “in our survey” from the original got dropped or turned into a fact
• The middle sections are represented, not just the beginning and the end
• Important information from charts wasn’t skipped
• Interpretations are marked as interpretations
• The summary says who published the document, what it’s based on, and what the summary doesn’t cover

What you just learned

On the surface you summarized a report. Underneath, you practiced the step of the loop most people skip: checking (Steps 4 and 5). You also did the two things that make checking possible: giving context about the reader (Step 1), and building your own rough map of the document before the AI showed you its version (Step 2). The AI did the reading; you decided what mattered and whether it was said fairly.

The same method works for: getting a guided overview of a contract or policy before you read it closely, comparing supplier proposals, catching up on a long email thread, preparing for a meeting from a pile of background documents, and reading internal documents when you start a new job. Change the brief in Step 1, and keep everything else.

Using a different tool?

The prompts work anywhere. Only the buttons change.

Features and plan names change often. This table was checked in October 2026.

Sources

• Microsoft 2026 Work Trend Index Annual Report: report page and methodology (Microsoft WorkLab, May 2026)
• Upload files to Claude (Claude Help Center, updated Jul 2026)
• How can I create and manage projects? (Claude Help Center)
• Projects in ChatGPT (OpenAI Help Center)
• Use Gems in Gemini Apps (Google Help)
• Create a summary of your document with Copilot in Word (Microsoft Support)
• Generalization bias in LLM summarization of scientific research (Peters & Chin-Yee, arXiv / Royal Society Open Science, 2025)
• Misleading AI-generated summaries can distort human memory (Georgetown University, Sept 2026)
• Lost in the Middle: How Language Models Use Long Contexts (Liu et al., TACL 2024)
• Hallucination leaderboard (Vectara, May 2026 update)