When to use it
Use this prompt when a long document must reach someone who has little time: a consultant’s report for a director, a research paper for a policy team, an audit for a board, or a market study for a founder. It works for briefings you write for others and for your own preparation before an important meeting.
How to customize it
- [READER] and [WHY THEY NEED IT] shape the whole summary. A summary written for a decision highlights different findings than one written for general awareness.
- [MAXIMUM LENGTH] forces prioritization. One page is a useful default for senior readers.
- [REPORT] can be pasted in full if it fits in your assistant’s context window. For very long documents, summarize sections first and then combine.
- Add your organization’s briefing format if it has one, such as a fixed set of headings.
Why it works
Busy readers want the conclusion first and the background only if they need it. The prompt follows that order, sometimes called “bottom line up front”. Page references for each key number let the reader, or you, check the source quickly, which matters because summaries can drop qualifiers or misstate figures.
The caveats section and the check for conclusions that go beyond the evidence make the summary honest rather than just shorter. Decision makers are better served by knowing what the report does not prove than by a polished restatement of its claims.
Tips and variations
- Spot-check every number against the original before sending.
- Ask for a version with a short table comparing the options the report discusses.
- Our guide on how to summarize long documents with AI explains how to handle very long files.
- For an article you read for yourself, our reading summary prompt is lighter.
- Do not paste confidential reports into tools your organization has not approved.
- Ask a colleague who has not read the report to read only your summary and say what they would decide. If their answer differs from what the report supports, the summary is missing a key point or a key caveat.