Get the Short Version of a Long Document

What it opens

Word files open, DOCX and the older DOC alike, and so do PDFs. Decks come with their speaker notes, which is usually where the argument lives, not just the words on the slide. Plain text, rich text, ebooks, and a web page saved to a file all read the same way.

Page numbers only mean something on a PDF. Everything else gets pulled into one continuous stream of text, so a citation from a deck or a Word file points at a paragraph, not a page.

Two things stop it outright. A link that asks whoever opens it to sign in isn't a document, since there's no account connection to authenticate through. Download the file first and upload that instead. A link that opens for anyone works fine, because there's an actual file behind it to fetch. The other stopper is a password on the PDF: it stays sealed until you hand the password over.

A scan isn't on that list, because it still opens. It's pictures of pages rather than text, and you can tell which one you're holding the way you'd check any PDF: try dragging your cursor across a line, and if nothing highlights, you're looking at an image. The words come back either way, they just go through recognition first, which is where a 3 can quietly become an 8 in a column of figures.

Say what the summary is for

Two people ask for the same summary and want different things. One is deciding whether to read the document at all. The other has to speak about it in an hour. Say which one you are and the summary changes shape around you.

"Summarize this" gets you a summary, and it's nearly always the wrong length and the wrong shape, because the useful version depends entirely on what you're about to do with it. Name that instead, and the rest follows on its own.

Deciding whether to read it means asking, in three sentences, what this is and whether it needs you. Walking into a meeting about it: the five things you'll be asked, with the page each one is on. Chasing one thread through a long file: everything on the renewal date, nothing else. Passing it along means writing a paragraph for someone who has never seen this document.

Length behaves the same way. Ask for five bullets and five is what arrives. Ask for a sentence per section and you get the document's own outline back. The version that reads worst is the one nobody specified, which lands somewhere in the middle and is often long enough to want summarizing again.

What a summary drops, and how to get it back

A summary is a pile of decisions about what matters, made by something that has not sat in any of your meetings. It keeps what documents are usually for: what got decided, what is being recommended, who owes what, what changed since last time. It drops background, hedging, and the third example of a point already made twice.

That is right most of the time and wrong in the one way that costs you, because the sentence that mattered to you was, to anything reading it cold, a detail. Say what you care about in the same message. "Summarize this, and separately give me everything it says about indemnity." Now it isn't a judgement call.

Two habits are worth keeping. Ask what it left out, which is a question with a real answer and often more interesting than the summary itself. And when a figure is load-bearing, ask which page it came off and go and look.

Where length actually costs you

Nothing rejects a file for being long, but length isn't free. Text gets read in windows of about two thousand lines at a time, and once a document runs past that, it's covered in several passes rather than held in view all at once.

A scoped request survives that well. "Everything on indemnity" gets answered the same way on pass four as on pass one. A single summary of the whole document is where the seams show: the passes are even-handed, so a long report comes back flatter than a person would write it, chapter nine weighted the same as chapter two even though chapter two was the one that mattered. The fix costs one sentence. Ask for a summary per section, read the section names, then ask for depth on the two that matter most.

When a summary is the wrong thing to ask for

The tell is whether your question has a quotation or a number at the end of it.

If you need one clause and its exact wording, summarizing is a detour. Put the question to the document directly and ask for the page. If the file is a workbook with formulas across several sheets, the answer is a recalculation rather than a paragraph. If it is an export from your bank or your CRM, what you want is a total or a grouping, and prose is the least useful shape that could arrive.

A summary is the right tool in the other case: when you don't yet know what you're looking for, and need a cheap way to find out whether it's in there at all.