Summarise Long Documents Without Losing the Important Exceptions
A good document summary preserves the information needed for a decision. It should explain the main point while keeping exceptions, deadlines and uncertainty visible. Start by deciding what the reader needs to do after reading the summary, rather than choosing an arbitrary word count.
Why it matters
Compression removes information. A short summary of a policy can become misleading if it keeps the general rule but drops the one exception that applies to the reader.
A practical workflow
- Provide the document title, version and intended use of the summary so the scope is clear.
- Ask for the main conclusion, supporting points, exceptions and unresolved questions as separate sections.
- Require section or page references for consequential details, especially dates, eligibility and mandatory actions.
- Read the original passages behind those details before sharing the summary with someone who will act on it.
An example
For a scholarship notice, request a summary covering who can apply, required documents, deadline and exclusions. If the source lists different deadlines for different applicants, preserve both. A single simplified date could cause a reader to miss the relevant window.
A mistake to avoid
Do not upload several versions without identifying which one controls. A model may combine an old deadline with new eligibility rules and produce a summary that matches no actual document.
Try it and check the result
Write five questions a reader should be able to answer from the summary. Check each answer against the original, including at least one exception and one situation the document does not resolve.
Reference and further reading
Google's prompt design strategies.
The workflows and examples in this guide are illustrative. Product controls and availability can change; check the linked official guidance for your setup.
Continue with Write Better AI Prompts with a Simple Task Brief or explore all blog topics.