Executive Summary Rules

An executive summary must be readable and complete on its own, with zero dependency on the document behind it — a reader who never opens the full report should still walk away knowing the finding, the implication, and what's being asked of them.

Standalone readability

• Write the summary so it makes full sense to someone who never reads past it — no "as discussed below," no unexplained acronyms first introduced in section 3, no charts referenced by number that aren't reproduced or described inline.
• Define any term, metric, or abbreviation the summary depends on the first time it's used, even if the full document defines it again later — the summary doesn't get to borrow context from a document its own reader may never open.
• Test it by reading the summary in isolation, pretending the rest of the document doesn't exist — if any sentence only makes sense with information from later sections, rewrite or cut it.

Decision-oriented

• Every executive summary exists to support a decision, an approval, or an allocation of attention — write toward that outcome specifically, not toward a neutral recap of "what this document covers."
• State explicitly what you want the reader to do with the information: approve a budget, weigh in on a direction, simply stay informed. A summary with no clear ask defaults to being skimmed and forgotten.
• Lead with the conclusion and its business implication, not with the process that produced it — "We recommend delaying launch by 3 weeks; current defect rate would put support costs over budget" beats "We conducted a QA review across four release candidates."

Length caps

• Target roughly 10% of the source document's length, and cap it hard regardless of source length — a one-page summary for a 20-page report, a single paragraph for a 3-page memo. If it's not shorter than that, it's a second document, not a summary.
• For most business documents, one page is the practical ceiling no matter how long the underlying report is — a "one-page executive summary" that runs to page three has failed at the one job implied by its name.
• When forced to cut, cut supporting detail before cutting the conclusion or the ask — a shorter summary that keeps the decision-relevant content intact is more useful than a longer one that dilutes it with softened, padded context.

What belongs

• Finding: the single most important thing the underlying work discovered, stated as a specific claim with its key supporting number.
• Implication: what that finding means for the business, the team, or the decision at hand — connect the dot from finding to consequence explicitly rather than leaving the reader to infer it.
• Ask: the specific decision, approval, or action being requested, including any deadline — this is the section most executive summaries skip, and its absence is the most common reason a summary gets read but nothing happens afterward.

What doesn't belong

• Methodology: how the analysis was conducted, what tools or process were used, sample sizes and data sources — this belongs in the body for a reader who wants to verify the work, not in a summary meant for someone deciding whether to read further.
• Background and history the reader is presumed to already have, or that doesn't change the decision at hand — a summary is not the place to re-establish context that isn't load-bearing for the ask.
• Secondary findings that are interesting but don't change the recommendation — if a finding wouldn't alter the ask if it were removed, it belongs in the body, not the summary.
• Hedging language that dilutes the actual conclusion ("results may possibly indicate," "it could be argued that") — state the finding as plainly as the underlying evidence supports.

Writing it last

• Draft the executive summary only after the full document is otherwise complete, even though it will be placed first — you cannot accurately compress an argument you haven't finished making.
• Treat the first draft of the summary as provisional until the full document is final — if later drafting changes the conclusion or the ask, the summary written early will silently go stale and mislead readers who only see the front page.
• Use the act of writing the summary last as a genuine check on the document itself: if you can't compress the report into a page, that's often a sign the underlying argument isn't as clear as it needs to be, not just that the summary needs more work.

What to avoid

• Don't pad the summary to look more substantial by restating the same point in different words across multiple paragraphs — density is the point of an executive summary, not thoroughness.
• Don't include a call-to-action that isn't genuinely the point of the document (e.g., "Let us know your thoughts" tacked onto a summary that's actually requesting a specific budget approval) — a vague ask defeats the purpose of writing a decision-oriented summary at all.
• Don't assume the summary will be read alongside the full document — for many readers, especially senior ones, the summary is the only part they'll ever see.