How to Get ChatGPT to Summarize Long Documents for Work

It’s Tuesday afternoon. Someone has just dropped a 70-page document in your lap: a new policy, a tender, a vendor proposal, a strategy deck turned into a PDF. You’re expected to “have a look before Thursday”, next to everything else on your plate. ChatGPT can summarize long documents for work in about fifteen minutes, but not with one “summarize this” prompt. What works: upload the file, ask for a map of the document first, summarize it section by section, then write the final summary for the one person who will read it, and check every claim against the page it came from.

Imagine it’s Thursday morning. You walk into the meeting having read five lines you trust, with page numbers next to the two points that actually affect your team. When someone asks “what does it say about the deadline?”, you open page 41 and read it out.

Want more practical AI workflows like this one, free? Join Launchpad.

Short answer

Attach the document to a ChatGPT chat (DOCX, PDF or TXT). Before you ask for any summary, ask ChatGPT to list the document’s sections with page numbers, so you know it has seen the whole file. Then summarize it one section at a time, with a page reference behind every point. Only after that, ask for the final summary, written for a specific reader: your manager, your team, a client or yourself. Finish with a check where ChatGPT quotes the sentence behind each point, and read three of those quotes yourself in the original.

Why the extra steps? ChatGPT can sound confident even when it’s wrong, and OpenAI itself tells you to treat it as a first draft and to verify quotes and data (OpenAI Help Center: Does ChatGPT tell the truth?). A summary of a long document is exactly where that bites, because you’re asking it for the one thing you can’t easily check: what it left out.

Why one big “summarize this” falls short on long documents

File size is rarely the problem. ChatGPT accepts documents up to 512 MB, and text files are capped at 2 million tokens per file, which is far more than a normal work document (OpenAI Help Center: Uploading files to ChatGPT). The problem is attention. A 2023 study led by Stanford researchers found that language models use information at the start and end of a long input best, and do noticeably worse with what sits in the middle (Liu et al., “Lost in the Middle”, 2023).

In practice that means a one-shot summary of a 70-page file often sounds complete and still skips the clause on page 38 that matters to you. Section-by-section summaries keep each piece small enough to get proper attention, and the map tells you if anything was skipped.

Before you upload: three quick checks

• Is it a file ChatGPT can read? DOCX, PDF and TXT work. A Google Doc can’t be uploaded directly: export it as PDF or DOCX first (File, Download). Slides work as PPTX.
• Is the text real text? Try to select a sentence in the PDF. If you can’t, it’s a scan, and the summary will be thin or wrong. On most plans ChatGPT reads the digital text in a document, not the images inside it, so charts and scanned pages can be missed (only ChatGPT Enterprise reads images in PDFs, according to the same OpenAI file-upload page). Run the scan through your PDF tool’s text recognition first, or paste the key table in as text.
• Are you allowed to upload it? On ChatGPT Business and Enterprise, OpenAI says your workspace data isn’t used to train its models by default. On a personal Free, Plus or Pro account it is, unless you switch off “Improve the model for everyone” under Settings, Data Controls (OpenAI Help Center: data controls). Either way, follow your company’s rules for confidential files. If in doubt, ask before you upload.

One more practical note: on the Free plan you can upload 3 files a day (same OpenAI file-upload page), so start with the document that matters most.

Step 1: ask for a map before a summary

This takes one minute and saves you from the most common failure: a summary of the first half of the file.

I've attached a document I need to understand for work. Don't summarize it yet.

1. Tell me what kind of document it is, who wrote it and the date, if it says.
2. List every section and subsection in order, with the page numbers.
3. Tell me the last sentence of the document, so I know you've seen the end.
4. Flag any pages that look like images, scans or tables you couldn't read.

Check the last sentence and the page count against the file. If they don’t match, the file didn’t load fully. Re-upload it, or split it (see below).

Step 2: summarize it section by section

Now work through the map in chunks of a few sections at a time. Ask for page references every time; they’re what make the summary checkable later.

Summarize sections 1 to 3 only.

For each section give me:
- 2 to 4 bullet points with the main points, each with its page number
- any numbers, dates, deadlines or names, exactly as written
- anything that is a requirement, an obligation or a change from how things work now

If a section says nothing that matters for someone in [your role], say so in one line. Don't fill gaps with general knowledge: if it's not in the document, leave it out.

Type “next” and it continues with the following sections. For a 70-page document that’s usually four or five rounds. Skim each round as it comes in. This is where you catch “wait, that sounds wrong” while the section is still fresh.

Step 3: write the summary for the person who will read it

A good work summary depends on who reads it and what they have to do next. Same document, very different summaries. Pick the one you need and paste it in the same chat, so ChatGPT builds on the section notes rather than starting over.

For your manager (a brief they read in 30 seconds):

Using only the section notes above, write a brief for my manager.
- Line 1: what this document is and why it landed on our desk.
- Then the 3 points that matter most for our team, with page numbers.
- Then what we need to decide or do, and by when.
- Then anything that's unclear or that I should check with someone.
Max 150 words. Plain language, no jargon from the document unless it's needed.

For your team (actions, not a book report):

From the section notes, list everything in this document that changes what my team does day to day. Use a table: what changes, from when, who it affects, page number. Then one line: what stays the same.

For a client or someone outside the company: ask for a short plain-language version with no internal names, and read it twice before it leaves your outbox. A summary sent outside is your words, not ChatGPT’s.

For yourself (to really understand it): ask ChatGPT to explain the three hardest sections in simple terms and then ask you three questions about them. If you can’t answer, reread those pages.

Step 4: check the summary against the document

This is the step that turns a nice-sounding summary into one you can defend in a meeting.

Go through the summary point by point. For each point, quote the exact sentence from the document that supports it, with the page number. If a point is not directly supported by a sentence in the document, mark it NOT FOUND.

Then tell me: what's in the document that a reader in my role would care about, but isn't in the summary?

Open the original and read three of those quotes yourself, at least one from the middle of the document. If a quote isn’t there, or says something slightly different, fix that point and ask ChatGPT to recheck the rest. Any number in the summary gets checked against the page, every time.

Summarize a long email thread before a meeting

A 40-message thread is a long document too, just a messy one. The same method works with two changes. First, get the thread into a file: most mail apps can print or save a conversation as a PDF. Second, ask for a timeline before a summary:

This is an email thread I need to be ready for in a meeting tomorrow.
1. Give me a timeline: date, who wrote, what they said or asked, in one line each.
2. What has been decided, and by whom?
3. What is still open, and who is waiting on whom?
4. What will I probably be asked in the meeting, and what does the thread say about it?

Point 4 is the one that saves you. Check the decisions against the actual emails, because threads are full of “I think we agreed” that nobody agreed to. If what you have is notes from the meeting itself rather than an email thread, our guide on how to summarize meeting notes with ChatGPT is the better fit.

When the document is too long, or there are several

• The map doesn’t reach the end. Split the PDF into parts (most PDF tools can do this), upload part 1, do steps 1 and 2, then part 2 in the same chat. Ask for the final summary only when all parts are done.
• Several related documents. Put them in a ChatGPT Project so you can return to them all week. OpenAI’s limit is 5 files per project on Free, 25 on Go and Plus, and 40 on Business and Enterprise. Map each file separately first, then ask for one summary across them.
• Two versions of the same document. Don’t ask for two summaries and compare them yourself. Upload both and ask: “What changed between version A and version B? List every difference with the page numbers in both.”

If the long document is a contract, lease or policy, the summary steps change a little. See how to use AI for legal documents for prompts that pull out key clauses and prepare your questions.

Common mistakes

• One prompt, whole document. You get a smooth summary of the parts the model paid attention to.
• No page numbers. Without them you can’t check anything, so you end up trusting it blindly or rereading everything.
• Uploading a scan. If you can’t select the text, ChatGPT probably can’t read it properly either.
• A summary for nobody. “Summarize this” gives you a shorter document. “Brief my manager on what we need to decide” gives you something useful.
• Letting it fill gaps. Tell it to leave out anything that isn’t in the document. General knowledge sneaks in otherwise.
• Skipping your own read of the key pages. The summary tells you where to look. It doesn’t replace looking.

Related guides

• Prefer Claude for big PDFs: Claude AI analyze long PDF files.
• A long report into a brief with owners and deadlines: summarize a long report and extract action items with Claude.
• Contracts and legal documents: Claude AI key points from a PDF.
• Reviewing contracts every week: how to pick AI contract review software.
• Writing your own report afterwards: how to get ChatGPT to help write a report for work.
• Replying once you’ve read it: use ChatGPT to draft reply emails faster.
• The document is in another language: how to use AI to translate a document and check it before anyone relies on it.

Try it on the document on your desk

Pick the longest thing you’re supposed to read this week. Run the map prompt first and look at what comes back. Often the map alone pays off: you see in one minute which three sections you actually need to read, and which forty pages you can leave to the summary.

Want a new practical AI workflow like this every week? Join Launchpad.