The executive summary is the most misunderstood document at work. It is not an introduction, not a teaser, and not the first section you write. It is the whole document at 10x compression — written so that a busy decision-maker could read only the summary and still decide correctly. Most fail because their authors couldn't bear that standard.
Start with the decision, not the journey
The reader of an executive summary has one question: what do you want from me? Answer it in the first sentence or two:
- Weak opening: "This report examines the current state of our vendor landscape across three dimensions..."
- Strong opening: "We recommend consolidating from four vendors to two (Acme and Nortech), saving ~$240K/year with a one-quarter migration. Approval needed by July 30 to hit contract renewal windows."
Recommendation, magnitude, deadline — before the reader's attention expires. The analysis exists to support the recommendation, not to precede it.
The four-part skeleton
Nearly every effective summary is these four moves, in about this proportion:
- The ask/recommendation (1–2 sentences) — what should happen.
- The reason (2–3 sentences) — the two or three strongest drivers, with the key numbers inline. Not all the evidence; the deciding evidence.
- The risk and its answer (1–2 sentences) — name the biggest objection yourself and how it's handled. Unmentioned risks get discovered in the meeting, with worse framing.
- The next step (1 sentence) — who does what upon approval, by when.
That's one page maximum — for most decisions, half a page. If it can't compress that far, the underlying thinking isn't finished yet; the summary is where that becomes undeniable.
Write it last, edit it hardest
Write the full document first, then distill. The summary inherits none of the document's structure — it gets its own, organized by what the decider needs rather than how the analysis unfolded. And because it's the only part everyone reads, it deserves the majority of your editing budget: every hedge cut, every sentence load-bearing, numbers verified twice. This is the natural habitat for a compression-focused rewrite pass — running the draft through a tool like Wrivio and reviewing its word-level diff is a fast way to find the padding your own eyes have stopped seeing, while keeping veto power over anything that shifts meaning.
Numbers over adjectives
Executives are professionally immune to adjectives. "Significant savings" bounces; "$240K/year, 11% of category spend" lands. Every claim in the summary should be either a number, a named fact, or a clearly labeled judgment call. If the source document has the number, the summary uses it; making the reader dive into page 14 for the figure defeats the genre.
Respect the forwarding chain
Summaries travel: your reader forwards it to their boss with two lines of endorsement. Write for that second and third reader who lack all context — expand the acronyms, name the project plainly, make it standalone. And send it in a format that survives the journey with formatting intact; a PDF of the final version arrives everywhere looking exactly as you shipped it.
The uncomfortable truth
A good executive summary is hard to write precisely because it removes all the places to hide. No methodology section to gesture at, no appendix to defer to — just the claim, the evidence, and the ask, exposed on one page. That exposure is the value. If writing the summary feels easy, check whether it's actually saying anything.
