Summarise a long document before the meeting

A twenty-page report lands an hour before the meeting. You will not read it all, and pretending is uncomfortable. Paste the text and ask for a summary shaped by your role — what it means for you, not just what it says.

Asking for the section each point came from lets you check the important ones yourself — summaries can miss nuance or get a detail wrong. And do not paste confidential or personal information unless your workplace permits the tool you are using.

Why skimming fails

The forty-page report arrives the evening before the meeting. You open it, read the first two pages properly, skim the next ten, jump to the conclusion and hope nobody asks about section six. Skimming gives you the feeling of having read something without the understanding. You notice headings, not arguments, and the important caveat on page 31 goes past unseen.

A summary made for your purpose is different. It tells you what the document says, what it wants from you and where the weak points are. With that in hand you can read the two or three sections that matter properly, which is a far better use of twenty minutes than passing your eyes over forty pages.

Ask for a summary with a purpose

1. 1

   Say who you are

   A finance manager, a parent on a school committee and an engineer need different things from the same document.

2. 2

   Say what the summary is for

   A decision, a meeting, a reply or simply staying informed.

3. 3

   Set the length

   Five points, half a page, one paragraph. Without a limit you get a shorter version of the whole thing.

4. 4

   Ask for specifics

   Numbers, dates, names, commitments and deadlines, not general themes.

5. 5

   Ask what is missing

   What the document does not address, assumes or leaves vague.

A worked example

A member of a residents’ association receives a forty-page proposal from a contractor for replacing the building’s roof. The meeting is tomorrow. She asks for a summary for a non-expert with five minutes, with key points, costs, risks and questions to ask.

The answer gives five points: the scope of the work, the total cost and what it includes, the timetable of fourteen weeks, the payment schedule with a large amount due in advance, and the guarantee period. It notes that the proposal does not say who pays if hidden damage is found, that scaffolding costs appear to be listed separately, and that there is no penalty for delay. It suggests four questions for the meeting. She reads the pages on costs and guarantees herself, confirms the figures and arrives with the most useful questions in the room.

Follow-up prompts

• “What are the three decisions this document asks the reader to make?”
• “List every number, date and deadline, with the page or section it appears in.”
• “Where does the document state opinions as if they were facts?”
• “What questions should I ask the author?”
• “Explain section four in plain language. I do not have a background in this.”
• “Summarise the arguments for and against the proposal in two short lists.”
• “Compare this version with the previous one: [paste both]. What changed?”
• “Give me a one-paragraph version I can forward to a colleague.”

For long documents, go in pieces

Very long texts can exceed what an AI app handles well in one go, and summaries of very long inputs tend to become vague. Work in sections. Summarise each chapter separately, with the same instructions, and then ask for a summary of the summaries. This takes a few more minutes and gives a much more accurate result. If your app accepts file uploads, check that it has read the whole document. Ask it how many pages or sections it saw, and what the last section was about.

Always verify what matters

This is the essential caution. A summary can be wrong in ways that are hard to notice. AI may leave out a qualification that reverses the meaning, combine two separate points, attribute a figure to the wrong year or, occasionally, state something that is not in the document at all. It sounds equally confident either way.

So use the summary as a map, not as a replacement. For every point you intend to rely on, such as a number you will quote, a deadline you will act on or a claim you will repeat in the meeting, go to the original and read that passage yourself. Asking for page or section references makes this quick. If the summary cites a section and you cannot find the statement there, treat it as unreliable.

Legal, medical and financial documents

Contracts, tenancy agreements, insurance policies, medical reports and financial products deserve extra care. A summary can help you understand the general structure and prepare questions. It should never be the basis for signing, refusing treatment or committing money. Small words carry large consequences in these documents, and a summary is exactly where small words are lost. Read the original, and ask a qualified professional about anything you do not understand.

Confidentiality

Many long documents are confidential: internal reports, contracts, client files, personal records. Before you paste or upload, check whether you are allowed to. Your employer may forbid using outside AI tools for internal material, or may provide an approved one. Remove names and identifying details where you can. If the document belongs to someone else, treat it as you would if you were photocopying it for a stranger.

Read better, not just less

Summaries are best used to decide where to spend your attention. Read the summary first. Then read the conclusion and recommendations in the original, then any section the summary flagged as risky or unclear, and finally anything relevant to your own area. That order gives you a firm grasp of a long document in a fraction of the time, and it is how experienced readers approach reports with or without AI.

Common mistakes

• Treating the summary as if it were the document.
• Asking for “a summary” without saying for whom or why.
• Quoting a figure from the summary without checking it.
• Pasting confidential material into a public tool.
• Summarising a contract and signing on the strength of it.

Quick questions

1. 1

   How long should a summary be?

   As short as lets you act. Five points is a good default.

2. 2

   Can it summarise a document in another language?

   Yes, and it can summarise into your language. Verify key terms, since translation adds another source of error.

3. 3

   What about scanned documents?

   Text in images may be misread. Check numbers with particular care.