An 80-page report, a 40-page contract, a 200-page course pack: you want the essentials in ten minutes, without missing the one number that changes everything. AI is very good at this job. A prompt like “summarize this document,” on the other hand, almost always produces a smooth, plausible, incomplete text that leaves out the amounts, the deadlines, and the points of disagreement.
The difference doesn't come from the model you pick, but from three things: what exactly you ask for, how you split up the file, and how you check the result. This guide gives you the three methods that actually work (ranked from most thorough to fastest), a six-block prompt template you can copy as-is, the two-pass summary technique for very large files, and four checks to spot in five minutes what the AI left out. No technical skills required.
Why an AI summary loses what matters
An AI summary loses what matters because nobody told the AI what “essential” means in your specific case. With no criteria, the model does what it does by default: it produces a neutral condensation, evenly balanced across the parts of the document, that reads like back-cover copy. That's the exact opposite of what you want if you're looking for the three legal risks in a contract or the obligations that fall on you before December 31.
Three causes come up again and again.
- The goal is missing. The same report yields four different summaries depending on whether you're the salesperson, the lawyer, the executive, or the student being examined on it. If you don't specify the role and the use case, the AI decides for you.
- The document is too long to handle at once. Every AI has a “context window,” meaning a maximum amount of text it can read in a single pass. Even below that limit, accuracy drops on information sitting in the middle of a very long text: the first and last pages come back better than pages 90 to 120.
- Nothing is traceable. If the AI doesn't quote a single passage, you have no way to tell what's actually written in the document from what the model filled in on its own. That's where number errors are born.
The fix is known and documented. Anthropic's documentation on long documents recommends two habits: put the document at the top of the prompt and the instructions at the bottom, then ask the model to extract the relevant passages first before writing the synthesis. You go from a summary written “from memory” to one backed by quotes.
Method 1: summarize your document in Skilzy's AI Lab
The most reliable method is to learn the prompt structure once and for all, then apply it in a space where the tools are already set up: that's what Skilzy offers. Skilzy is a French e-learning platform for learning and using AI, with more than 15 programs: image creation, video (UGC, ads, faceless channels, avatars, voiceovers), music, automation with n8n, prompt writing, and AI-assisted development.
For the topic at hand, the prompt fundamentals program is the entry point: you work on how to structure an instruction, how to frame a goal, constrain a format, and get sources cited. These are exactly the skills that separate an unusable summary from a synthesis you can send to your team.
The practical appeal lies in the built-in AI Lab. You use the real tools directly from the platform, with credits included, without stacking three or four monthly subscriptions just to experiment. You load your document, apply the prompt template from the program, compare two phrasings, and keep the one that works.
On the certification side, Skilzy prepares you for two state-recognized, fundable credentials: the RS7439 certification in AI content marketing and RS6792 (AI and sales). If you have a personal training account to spend, that changes the math.
A B2B offering exists for training organizations that want to add these tracks to their catalog.
The other methods: general-purpose assistants and specialized tools
If you want a summary right now, with nothing to install or learn, two other routes exist and they're honestly quite solid.
Method 2: the AI assistant you already have
ChatGPT, Claude, Gemini, and Copilot all accept PDF uploads on their free tier, with quotas that vary by plan. The principle is the same everywhere: you attach the file, you write your prompt, you get an answer. You also often have a native feature already sitting in your everyday tools:
- Gemini in Google Drive and Docs summarizes a document you've already stored, without downloading it.
- Copilot in Word does the same on an open .docx.
- Preview on macOS and Adobe Acrobat Reader offer a summary built into the PDF viewer.
The limits are real. A scanned PDF with no text layer (a photo of pages, in practice) often gives a mediocre or empty result, because the tool isn't reading pixels. Very large files are sometimes truncated silently, with no warning. And free tiers rarely return precise citations.
Method 3: tools built for documents
NotebookLM (Google) is designed for this: you drop up to 50 sources into a notebook, and every sentence of the summary links back to a clickable passage in the original document. For a thesis, a press kit, or a corpus of several reports, it's the best traceability available for free. Adobe Acrobat AI Assistant plays in the same category for PDFs, as a paid add-on.
One caution before you upload anything: a client contract, a medical file, or HR data shouldn't go onto a consumer service without checking the privacy policy and, in a company setting, without your IT manager's approval.
| Method | Setup time | Source traceability | Who it's for |
|---|---|---|---|
| Skilzy (AI Lab + prompt program) | 10 minutes | High if you apply the structure you learned | You want to be able to do it yourself, on any document |
| General-purpose assistant or native feature | Immediate | Low to medium | A one-off need, a non-sensitive document |
| Specialized tool (NotebookLM, Acrobat) | 5 minutes | High, clickable citations | Several documents to cross-reference |
The summary prompt to copy, block by block
A good summary prompt fits into six blocks: role, document, goal, items never to lose, output format, truth rule. Here's the template, to adapt by replacing what's in brackets.
You are a [legal analyst / market intelligence researcher / teaching assistant]. Here is a [number]-page document: [document pasted or attached].
Goal: I need to [decide whether we sign / prepare for an exam / write a two-page brief for my leadership]. My level on the subject is [beginner / advanced].
Never lose: the figures and amounts with their units, the dates and deadlines, the names of parties or authors, the obligations and conditions, the points of disagreement or risk, the exceptions.
Expected format:
- Three sentences maximum for the core idea.
- The 7 key points as a list, each followed in parentheses by the source page or quote.
- A table of the figures and dates found.
- What remains unclear or absent from the document.
Rules: before writing, extract the useful passages and quote them. Do not add any information that isn't in the document. If a piece of information is missing, write “not specified in the document” rather than inventing it.
The last block is the one everyone forgets and it's the highest-return: an AI you explicitly allow to say “I don't know” invents far less. Point 4 of the format plays the same role in reverse — it shows you the blind spots in the source text.
If you want to understand the logic behind each of these blocks rather than copying them mechanically, the complete method for writing a good prompt breaks down the order of the elements and the common mistakes. For very large documents, the principles of structuring a language model's context explain why where the text sits in the prompt changes the quality of the answer.
Splitting up a 200-page document: the two-pass summary
Past fifty pages or so, stop asking for one global summary and switch to the two-pass technique. It consists of summarizing the chunks separately, then summarizing the summaries.
In practice:
- Split by logical unit, not every ten pages at random: a chapter, a section, an appendix. A split that cuts an argument in half produces two wrong summaries.
- First pass. For each chunk, ask for a dense 150-to-200-word summary, plus a raw list of the figures, dates, and proper names encountered. Number your chunks (“Part 3 of 7”) and tell the model not to synthesize anything beyond the chunk provided.
- Second pass. Paste the 7 summaries together and ask for the final synthesis, with a requirement to preserve every data point collected in the previous step.
- Cross-check. Ask last: “Which pieces of information from my intermediate summaries don't appear in the final synthesis, and why did you leave them out?” The answer tells you whether a loss was deliberate or accidental.
This step-by-step approach follows the same logic as the guided reasoning described in our article on chain-of-thought: you get better results by asking for work in several stages rather than a single answer to one enormous prompt.
Four checks to confirm nothing is missing
An AI summary can be verified in five minutes with four checks, and those five minutes are non-negotiable if you're going to make a decision based on it.
- The numbers. Take every amount, percentage, and date from the summary and find them in the document using search (Ctrl+F or Cmd+F). This is the most common and most expensive error: a changed unit, a rounded percentage, a year off by one.
- The random page test. Open a page you haven't read, somewhere in the middle of the document. If its content is important and completely absent from the summary, your synthesis has a hole and you need to rerun it with a finer split.
- The reverse question. Ask the AI: “What did you deliberately leave out of this document, and what contradicts your summary?” The answers are often more instructive than the summary itself.
- The usefulness test. Ask yourself the question that made you open this document in the first place (“can I cancel before June?”). If the summary doesn't answer it, it failed, no matter how well written it is.
Once these habits are second nature, you can run through them quickly on all your documents for the week. Our selection of 50 useful everyday prompts includes several variants of these checks, ready to copy.
Key takeaways
Summarizing a long document without losing what matters doesn't depend on which AI you use, but on three moves: frame the goal and the list of items never to lose, split into two passes past fifty pages, and verify the numbers and the gaps. Start with a document you already know — it's the only way to judge the quality of a summary. If you want to practice this method with the tools right at hand, Skilzy's AI Lab lets you apply it directly to your own document.