The Executive Brief Compressor: Turn a 20-Page Report Into a One-Page Action Memo
Why this prompt matters
An unread report does not get ignored safely — it gets skimmed for whatever single paragraph happens to confirm what the reader already expected, and the decision gets made on that fragment rather than the report's actual strongest finding or clearest caveat. A structured compression step forces the decision-relevant content and its contradictions to the surface, instead of leaving it to chance which page the reader happened to stop on.
What we use it for
A VP of Operations receives a 24-page vendor due-diligence report late on a Friday, with a budget committee meeting scheduled for Monday morning at 8am where the CFO needs to approve or reject a vendor contract renewal, and there is no time for the committee to read the full report before deciding.
Prompt
Role: Act as an executive communications specialist who routinely compresses long technical and analytical reports into one-page briefs that busy decision-makers can act on without reading the source document. Context: I have a [LENGTH]-page report on [REPORT TOPIC], prepared for [AUDIENCE / DECISION-MAKER]. It needs to inform a decision about [DECISION TO BE MADE] by [DEADLINE]. Here is the full report text: [PASTE FULL REPORT TEXT] Task: Produce a one-page executive brief that: 1. States the single most important finding or recommendation in the first sentence, before any supporting context 2. Lists the 3 to 5 key findings that support or complicate that headline finding, each with the specific number, date, or fact backing it up 3. Flags any finding in the report that contradicts or complicates the headline recommendation — do not let disagreement stay buried in the source report 4. States the specific decision or action the report's author recommends, and the explicit tradeoff being accepted 5. Notes anything the report explicitly says it could NOT determine or verify, so the reader knows the limits of what they are deciding on Constraints: - Do not include any claim, number, or finding that is not explicitly stated in the source report. If the report hedges a claim, keep the hedge rather than stating it as settled fact. - Do not smooth a limitation or caveat from the original report into more confident language than the report itself uses — preserve the report's own level of certainty. - Keep the total brief under [WORD LIMIT] words, formatted to fit on one printed page. - If the report does not clearly state a recommendation, say so explicitly rather than inventing one that sounds plausible. Output Format: 1. Headline Finding (one bolded sentence) 2. Key Findings (3 to 5 bullets, each anchored to a specific fact or number) 3. Complications / Contradicting Evidence (bulleted, or "None noted in report" if genuinely none) 4. Recommended Action & Tradeoff (2 to 3 sentences) 5. What This Report Could Not Determine (bulleted, or "Not applicable" if none)
Result
Headline Finding: Vendor X's financial stability score has declined from "stable" to "elevated risk" over the past two quarters, driven primarily by a 34% drop in disclosed cash reserves, and the report recommends renewing only a 6-month contract rather than the standard 12-month term.
Key Findings: - Vendor X's financial stress score moved from 72 to 58 between Q1 and Q3 2026, crossing below the 60-point threshold the report defines as "elevated risk." - Disclosed cash reserves fell from $14.2M to $9.4M over the same period, per the vendor's most recent financial disclosure to customers. - Two of Vendor X's five publicly known enterprise clients did not renew in the past six months, though the report notes neither departure was confirmed as contract-related. - Support response SLA compliance remained stable at 97%, showing no operational degradation despite the financial signals.
Complications / Contradicting Evidence: - Vendor X raised a $6M bridge round in September 2026 that is not yet reflected in the cash reserve figures above. The report flags this as a potential stabilizing factor it could not fully verify before publication.
Recommended Action & Tradeoff: The report recommends renewing for 6 months instead of the standard 12-month term, accepting a slightly higher per-unit cost in exchange for an earlier off-ramp if Q4 financials do not show stabilization.
What This Report Could Not Determine: - Whether the September bridge round resolves the cash reserve concern, since post-raise financials were not yet available at time of writing. - Whether the two client departures were price-driven, which would indicate a different kind of risk than a financial-stability issue.
The usual fate of a long report is not that nobody reads it — it is that someone skims three paragraphs, remembers whichever one matched what they already believed, and makes the decision based on that fragment. The report's actual strongest finding, or its most important caveat, never makes it into the room where the decision happens.
Why the Role is specific
The Role names "executive communications specialist" rather than a generic summarizer, because the skill being asked for is not compression in general — it is compression that keeps a reader from mistaking confidence for certainty. A specialist in this role knows that a one-page brief is read by someone who will act on it without going back to the source, which raises the stakes on accuracy far above a casual TL;DR.
What the Task section forces
Putting the headline finding first, before any supporting context, mirrors how a decision-maker actually reads — top to bottom, often stopping after a few lines. The fourth requirement, stating the "explicit tradeoff being accepted," exists because most reports recommend an action without naming what is being given up to get it, and a decision-maker who does not see the tradeoff cannot actually weigh it.
The Constraint doing the real work
"Do not smooth a limitation or caveat into more confident language than the report itself uses" is the instruction protecting the brief from becoming more dangerous than the report it replaces. A model asked to compress naturally tightens hedged language into declarative statements, because declarative language reads as more useful — but a report that says "may indicate" is making a different claim than one that says "confirms," and a one-pager that erases that distinction can send a confident decision-maker toward a bet the source material never actually supported.
Why two sections exist purely to surface disagreement
"Complications / Contradicting Evidence" and "What This Report Could Not Determine" are the sections most summarizers skip, because disagreement and uncertainty do not compress cleanly — they are exactly the texture that smoothing erases first. Keeping them as mandatory, separately labeled sections means a reader cannot finish the brief without seeing what the report itself was unsure about.
Use this before any meeting where someone will have to decide based on a report that most of the room has not read, and the gap between what the report actually says and what everyone remembers reading is exactly the risk you cannot afford that day.