How to summarize a long document with AI, step by step

· 4 min read

Pasting a hundred-page report into an AI assistant and asking for a summary is tempting, and sometimes it works. When it does not, the failure is quiet: a fluent summary that skips a section, blends two sections together, or states something the document never said. A short, repeatable process avoids most of that.

Why one big request can fail

Three limits show up with long documents:

  • The window. A model can only consider so much text at once, and very long documents may not fit at all. If an app trims the input to make it fit, you may not be told. For the background, see what a context window is.
  • Uneven attention. Studies of long inputs, including the 2023 paper "Lost in the Middle," found that models often used information near the beginning and end of an input better than information buried in the middle.
  • Averaging. A single summary of a very long text tends to describe the general shape and drop the specific details, which are often the reason you opened the document.

A step-by-step method

Step 1: Decide what the summary is for. "Summarize this" produces a generic result. "I am deciding whether to renew this contract; list the cost, the term, the exit conditions, and anything unusual" produces something you can act on. Write down the purpose and the questions you need answered before you start.

Step 2: Split at natural boundaries. Use chapters, headings, or sections rather than arbitrary page counts, so that each piece makes sense on its own. If ideas run across a boundary, repeat a paragraph or two at the start of the next piece.

Step 3: Summarize each piece with the same instructions. Use one prompt for every section, for example: "Summarize this section in five bullet points. Keep numbers, names, dates, and decisions. Quote any sentence that states an obligation or a risk." Identical instructions make the pieces comparable. This pattern is sometimes called map-reduce: the same task is applied to each piece, and the results are then combined.

Step 4: Combine the section summaries. Paste the summaries, not the full text, into a new conversation and ask for the overall picture, organized around your purpose from step 1.

Step 5: Ask for quotes and locations. For every important claim, ask for the exact sentence from the source and where it appears. A quote is something you can check in seconds; a paraphrase is not.

Step 6: Spot-check against the source. Pick three or four claims, especially numbers and anything surprising, and find them in the original. If one is wrong, treat the rest of the summary with more suspicion and go back to the section it came from.

Step 7: Ask follow-up questions of the right section. After the overview, go back to the specific sections that matter and ask targeted questions of the full text of those sections only.

Common pitfalls

  • Scanned documents. Text extracted from a scan can contain errors, and tables or figures may be lost entirely. If a number matters, read it in the original.
  • Summaries of summaries. Each round of condensing can lose detail or introduce small distortions. Keep the number of rounds low, and keep the quotes.
  • Leading questions. "Confirm that the contract allows early exit" invites agreement. Ask "what does the contract say about early exit?" instead.
  • Confidential material. Before pasting a sensitive document into any assistant, check what the service keeps and who can see it. A privacy checklist covers what to look for.

When to skip summarizing

If you need the exact wording of a clause, a figure from a table, or a legal or medical conclusion, a summary is the wrong tool. Use the assistant to point you to the right place in the document, then read that place yourself.

Quick answers

Can an AI summarize a PDF? Yes, if the PDF contains real text. A scanned PDF is a picture of text, so it needs text recognition first, which can introduce errors, and tables and figures often lose their structure.

How long a document can it handle at once? That depends on the model's context window and on the app around it. Some apps trim long input without saying so, so check the stated limits or split the document yourself.

Is a summary enough to make a decision? It is enough to decide what to read closely. For a decision with consequences, read the relevant sections yourself and use the summary as a map.

Should I ask for a particular length? Yes. Ask for a length and a structure, such as five bullets per section, so the pieces are comparable when you combine them.

Where NAMELESS stands

NAMELESS is an AI model that is still in training, built for unlimited context, so a long document does not have to be split before it can be discussed. Splitting, quoting, and checking remain good habits whichever assistant you use.

You can join the waitlist to follow progress. For another way assistants handle material that does not fit in a window, read RAG vs. long context.

Keep reading

All posts