An executive summary is the most-read part of any business document, and often the only part that reaches a senior decision-maker. If you want to write better executive summaries, the first thing to accept is that the summary isn't a warm-up act. It's the main event. Everything else in the document is the evidence behind it.
What an executive summary actually is
An executive summary is a self-contained overview of a longer document. It tells the reader what the situation is, what you're recommending, and why. It doesn't tease the document; it replaces it for anyone who won't read further.
That's a subtle but important distinction. A summary that says "see section 3 for the full findings" fails the test. A reader who gets only the summary should still walk away knowing what you concluded and what you're asking them to do.
Most executive summaries cover four things: context, findings or analysis, recommendation, and the consequence of acting or not acting. Not every document needs all four sections labelled explicitly, but the information should be there in roughly that order.
How long should an executive summary be?
The honest answer: one page for most business documents, two pages at the absolute outside for complex reports above 50 pages. Length creep is the most common problem. Writers feel obliged to reflect the full document, so they compress every section into a paragraph and end up with four dense pages that nobody reads.
A good rule: the executive summary should be no more than 10% of the total document length, and it should never exceed two pages regardless of how long the document is. A 200-page annual report still gets two pages, not twenty.
Short sentences help. Aim for an average sentence length below 20 words. Anything longer and a time-pressed reader starts skipping.
The structure that works every time
Start with the recommendation or conclusion, not the background. Business writers often open with context because it feels logical: tell the reader the situation before you tell them what to do about it. But executives read differently. They want the point first, then the reasoning behind it.
Lead with a sentence that states what you are recommending or what you found. Follow it with 2 or 3 sentences that give the most important supporting evidence. Then state the implication: what happens next, what it costs, what decision is needed, and by when.
Here's a skeleton that holds up across most document types:
- Sentence 1: The recommendation or key finding, stated directly.
- Sentences 2–4: The 2 or 3 facts or data points that justify it.
- Sentence 5: The required action, decision, or next step, with a date if one exists.
That's it. Everything else is decoration.
Language mistakes that undermine your summary
Vague openers are the most common problem. Phrases like "This report examines the challenges facing..." tell the reader nothing actionable. Start with a claim, not a description of what the document does.
Passive voice weakens the summary. "Costs were found to have increased" is weaker than "Costs increased 18% in Q2." Name the subject. State the verb. Give the number. Concrete language signals confidence and makes the summary easier to skim.
Jargon is another trap. Executive summaries often go to people outside your immediate team. If a term requires explanation, spell it out the first time or find a plainer word. The words you choose at the top of a document set the reader's expectations for everything that follows, so plain and direct beats technical and thorough.
Watch your tense, too. Report findings in the past tense ("sales declined") and recommendations in the present or future tense ("we recommend", "the board will need to decide"). Mixing them creates confusion about what has already happened and what is being proposed.
One thing most writers get wrong
They write the summary first. It's tempting because the executive summary appears at the top of the document, but writing it before the full document is finished almost always produces a vague, over-hedged paragraph that doesn't match what the document actually concludes.
Write the full document first. Then draft the summary. Then cut it in half. The discipline of cutting is what forces clarity. If a sentence doesn't answer "so what?", it doesn't belong in the summary.
It's also worth knowing that the phrases you use to close a request carry real weight with readers. Executive summaries that end with a clear, courteous ask ("We request approval by 30 September") outperform those that trail off into procedural language about the document contents.
A quick checklist before you send
Before you submit any document with an executive summary, run through these five checks:
- Does the first sentence state the conclusion or recommendation?
- Does the summary stand alone, without requiring the reader to consult the main document?
- Is it under one page (or two for very long documents)?
- Does every sentence carry information, or are some just filler?
- Is there a clear next step with a named owner or deadline?
If you can answer yes to all five, the summary is ready. If one of them trips you up, that's where to spend the next ten minutes.
Executive summaries reward bluntness. The reader is busy, the decision is real, and the summary is the one part of your document that can't afford to bury the lead. Write the point. Back it with evidence. State the ask. Stop.