Getting AI to summarise a long document without betraying it

A 40-page report, a contract, a study: you do not have time to read it all, so you ask AI for a summary. The result is fluent, well written, convincing — and that is exactly the problem. A text can be pleasant to read while quietly erasing the nuance that mattered. Here is how to get a reliable summary, and how to spot one that is not.

The real risk is not the glaring error

We picture the danger as a visible hallucination, an invented figure that jumps out. The most frequent risk is more discreet: a nuance that disappears, a caveat in the source text that becomes a categorical claim, a secondary result that takes on the air of a conclusion. Nothing that jumps out unless you reread the original — which is precisely what a summary is supposed to save you from doing.

The four-step method

1. Do not ask for a summary too short for a document too dense. An 80-page report compressed into ten lines forces the AI to decide between what stays and what disappears. First ask for a summary per section or per chapter, then a synthesis of those summaries: Anthropic’s documentation calls this a meta-summary, and it often captures details a direct compression would have lost.

2. Place the document before the question. Counter-intuitive but documented: pasting the long text before your instructions, rather than after, clearly improves the quality of the answer — by up to 30% in some tests, according to Claude’s technical documentation. The question comes last, once the model has “read” all the context.

3. Specify what you want to keep. “Summarise this report” is a poor instruction. “Summarise this report, keeping the key figures, the decisions made and the points of disagreement between the parties” is a good one: you tell the AI what, for you, must not disappear.

4. Check the passages that matter, not the whole document. You do not have to reread everything — that would give up the time saving. But for a contract or a report that shapes a decision, go back to the original on the clauses or figures that truly weigh. That is where a lost nuance costs the most.

Three signals that should raise a flag

• The summary is sharper than the source document was (a hypothesis becomes a fact).
• A figure appears that you cannot find in the original text.
• The document contained contradictory views and the summary keeps only one.

In all three cases: ask again, explicitly specifying that nuances and points of disagreement must be kept.

When not to delegate at all

A document scanned as an image rather than selectable text degrades reading quality before the AI even summarises anything. And for any document with legal or financial stakes — contract, confidentiality clause, amendment — the summary is a starting point for your reading, never a substitute for it. It is the same reflex we detail in the confidentiality habits before pasting your data into an AI: AI prepares, you decide.

Key takeaway

A good AI summary is built, not requested in a single sentence. Split dense documents, place the text before the question, say explicitly what must not disappear, and reserve your verification for the passages that really matter. The time saving stays real — provided you keep control of what you keep.