Executive Summary of a Long Document for Time-Poor Leaders
Condenses a long document into a layered executive brief tailored to one reader's priorities.
Executives don't read long documents; they read the part that tells them what to do. A good executive summary respects that reality by leading with the bottom line and layering detail so a reader can stop at any point and still be informed. This prompt produces exactly that structure: a one-sentence bottom line, three to five key takeaways, a 'what this means for us' implications paragraph, and a list of decisions or actions required with anything time-sensitive flagged. The layering is what makes it work for a two-minute reader, because the most important sentence comes first instead of buried in paragraph nine. It tailors the summary to a specific reader's priorities, since what a CFO needs from a report differs sharply from what a head of product needs. The strict instruction to use only what's in the document, and to name gaps rather than fill them, is the safeguard that keeps the summary trustworthy. Paste a report, contract, research paper, or long thread and get a brief built for someone who will never open the original.
Act as an executive briefer. I will paste a long document below: [PASTE FULL DOCUMENT]. The reader is [READER ROLE] who has two minutes and cares most about [WHAT THEY CARE ABOUT]. Produce a layered summary: a one-sentence bottom line first, then 3-5 bullet key takeaways, then a short 'what this means for us' implications paragraph, and finally a 'decisions or actions required' list with anything time-sensitive flagged. Use only information present in the document; if something important is missing or ambiguous, say so explicitly rather than filling the gap. Keep the whole summary under 250 words and write for someone who will not read the original.
What you can expect back
Bottom line: The report recommends migrating the data warehouse over nine months at roughly $480k, with most spend in the first two quarters and a meaningful but manageable downside risk. Key takeaways: 1) Estimated all-in cost $480k, front-loaded in Q1-Q2. 2) Expected annual savings of ~$160k once live, implying payback in about three years. 3) Main risk is a two-to-three-month overrun if data quality issues surface during migration. 4) The phased plan lets us pause after phase one with limited sunk cost. What this means for us: A material capital commitment this year with savings that arrive gradually, so it competes directly with other Q1 budget priorities. Decisions or actions required: Approve or defer phase one (time-sensitive: vendor quote expires in three weeks); decide whether to fund a data-quality audit first. Gap flagged: the report does not state ongoing run costs after migration, which the CFO will need before final approval.
Illustrative example — your results will vary by tool and inputs.
Get sharper results
- 01Name the exact reader and their priorities. The same document yields a different, better summary for a CFO than for a product lead.
- 02Trust the layered structure: the bottom line goes first so a reader who stops after one sentence still gets the point.
- 03Watch the gap flags. When the model says something important is missing, that's usually the question your executive will ask first.
- 04For very long inputs, summarize in sections then ask for a summary of the summaries to stay within context limits.
Adapt it for your case
Ask for two versions of the bottom line, one for a CFO and one for a head of product, from the same document.
Add: 'Skip background entirely; output only the decisions required and the deadline for each.'
Have it also list the document's weakest claims or unsupported assumptions the reader should question.
Common questions
Will the AI add information that isn't in the document?
The prompt forbids it and tells the model to flag gaps instead of filling them. Still, spot-check any surprising claim against the source, especially numbers.
How long can the document be?
Limited by the model's context window. For very long inputs, summarize in chunks and then summarize those summaries, which the pro tips describe.
Why tailor the summary to one reader?
Because relevance is what makes a summary useful. A CFO and a product head need different facts from the same report, and a generic summary serves neither well.
You may also need
Board Update Memo With Metrics, Asks, and Honest Lowlights
Produces a candid, scannable board update with a metrics table, honest lowlights, and specific asks.
Summarize a Sprint Retro Into Themes and Owned Actions
Clusters messy retro notes into themes with root causes and a table of owned, dated actions.
Summarize a Long Document Into Key Points
Condense long documents into an executive summary, key bullets, and quotable stats.
Write a Board Update / Investor Memo
Write a direct, no-spin investor update memo with metrics, wins, challenges, and asks.