Dropping a long PDF into a chat box and asking "what does this say?" is now a normal way to start. It is also a reliable way to end up with a confident summary that has the wrong figure, a missing condition, or a citation that does not support the sentence it sits beside.
The assistants are useful. They are fast at finding a passage you would have searched for, and they can hold a long report in a single sitting. They also compress, smooth and sometimes invent, especially when a table, a footnote or two conflicting sections are involved. The fix is not to avoid the tools. It is to question the document the way you would question a helpful intern who has only skimmed it.
1. Decide what you need, then give the tool the right file
Be specific about the job: a number, a clause, a timeline, a comparison between two sections, or a list of open questions. "Summarise this" is how you get a generic page of headlines with the important qualifier gone.
Check the file itself before you upload it:
- Is it the final version, not a draft or a scan of a scan?
- Are the pages in order, and is the text selectable? A scanned PDF without a text layer will be read poorly, or not at all.
- Are you allowed to upload it? Client contracts, personnel files and unpublished research often should not leave your machine or your existing document store.
If the tool accepts multiple files, name them clearly and start with the one document that should answer the question. Adding everything you have makes contradictions easier to hide.
2. Ask narrow questions and demand a quotation
Work through the document in small steps rather than one grand prompt. Useful patterns:
- "What does the document say about X? Quote the sentence or table note you are relying on, and tell me where it appears."
- "List the conditions attached to Y. If they are split across sections, quote each one."
- "Here are two figures that seem to disagree. What is the context for each?"
A quotation is more useful than a citation badge. Some tools will highlight a passage or jump to a location in the file; that is a help, not a conclusion. Open the original PDF and read the surrounding paragraph, the table heading, and any footnote attached to the number. The page number you write down in your own notes should come from that file, not from a snippet in the chat.
If the assistant cannot produce a quotation, treat the answer as a hint and go find the passage yourself, or ask the question again with a section heading from the table of contents.
3. Watch the places summaries usually break
Certain parts of a PDF cause the same class of error, regardless of the tool:
- Tables and figures. A model may read a column in the wrong direction, drop a unit, or report a subtotal as a total. Check every number you plan to reuse against the original table, including the caption and footnotes.
- Conditionals and exceptions. "Subject to clause 12" or "except for customers on the old plan" is easy to leave out of a fluent sentence.
- Definitions. A word may be used in a special sense later in the document. If your question depends on a defined term, ask for the definition first.
- Scanned pages, headers and repeated footers. These confuse extraction. If a passage looks garbled in the tool's source view, trust the original file.
- Conflicts. Two sections may disagree because one is an older appendix, or because a later amendment applies. Ask the tool to list both, then decide which one governs. Do not let it quietly pick.
Break compound claims apart. "The pilot cut waiting time by a third, so the process should be rolled out" contains a measurement and a recommendation. The document may support only the first.
4. Keep your own record, not only the chat
For each fact you intend to use, write a short line of your own: the claim, the document name and version, the page or section, a short quotation, and whether you have checked it. Unresolved items stay in the list as unresolved, so a later summary cannot tidy them away.
Do not copy the assistant's prose into a brief or a paper and then look for sources afterwards. That order is how invented connective tissue — a cause, a date, a "the authors conclude" — slips through.
If you do this often, it is worth comparing tools on the one feature that actually changes the work: how clearly they show the passage behind an answer, and how they behave on tables and long scans. The PDF analysis category on Toolbit lists the main options, and this comparison of chat-with-PDF tools is a useful starting point. Whichever you pick, keep the original file open.
5. Know when to stop and read the document
An assistant is the wrong tool when you need a close reading of tone, when a typo in a clause would change the meaning, or when you would not be comfortable explaining the conclusion without having read the pages yourself. It is also the wrong tool for anything you are not allowed to upload.
Use it to find the relevant pages faster. Then do the last part of the work yourself.
The short version
Ask a specific question, demand a quotation, and check that quotation in the original file — especially where tables, exceptions and definitions are involved. Keep a short record of what you verified. The assistant can save you a first pass through a long report. It cannot take responsibility for a number you repeat later.