How to Write an Executive Summary (Step-by-Step)
Here’s the uncomfortable truth about reports: most decision-makers read the executive summary and nothing else. That one-to-two-page section at the front carries the entire weight of your work — your findings, your recommendations, your credibility — in the space of a coffee break.
An executive summary is a condensed, standalone overview of a longer document: what it set out to do, what it found, and what should happen next. This guide gives you the three golden rules, the standard structure, a seven-step writing process, the variations for business plans versus reports versus proposals, and the mistakes that sink most summaries.
What Is an Executive Summary?
An executive summary is a self-contained miniature of your full document. It covers the purpose, the key findings, and the recommendations — in the same order as the report — so a busy reader can grasp the whole thing without reading the whole thing.
The operative word is standalone. A good executive summary makes complete sense to someone who never opens the report. If your summary only makes sense alongside the full document, it’s an introduction wearing a costume — and it will fail the only test that matters: the executive who reads it on a phone between meetings and decides based on it alone.
Length discipline is part of the definition. The standard rule: 10–15% of the full report’s length, which in practice usually means 1–2 pages. A 40-page report gets a 4–6 page summary at most; a 10-page report gets about a page. Longer than that and it’s not a summary anymore — it’s a second report nobody asked for.
The 3 Golden Rules
Everything below is detail. These three rules are the foundation — violate any of them and the rest doesn’t matter.
Rule 1: Write It Last
The summary goes first in the document and last in your workflow. You cannot summarize a document that doesn’t exist yet — and every attempt to write it first produces either vague filler or a summary the final report contradicts. Finish the report, then distill it. The order of operations is non-negotiable: complete analysis first, summary second.
Rule 2: Keep It 10–15% of the Report
Proportional length keeps the summary honest. At 10–15% of the full document — typically 1–2 pages — you’re forced to include only what matters: the findings that change decisions and the recommendations that follow. If you’re struggling to fit, the problem isn’t the page limit; it’s that you haven’t decided what’s actually important yet. That struggle is the work.
Rule 3: No New Information
Nothing appears in the summary that doesn’t appear in the report. No new data, no new arguments, no recommendations you didn’t make in the body. The summary is a distillation, not an extension. New information here breaks trust twice: the reader can’t verify it, and the report contradicts its own structure. If it’s important enough for the summary, it’s important enough to be in the report — put it there first.
The Standard Structure
Mirror the report’s order with matching headings. The reader should be able to move between summary and full document without reorienting. Five blocks, in this order:
Introduction
One paragraph: what this document is about and why it exists. Context, not background — the situation that made this report necessary, stated plainly.
Objectives
What the report set out to accomplish. Two to three sentences, specific. “Evaluate three CRM options against cost, integration effort, and support quality” — not “explore CRM solutions.”
Key Findings
The three to five findings that matter. Lead with the most important one — the finding that changes the decision. Each finding gets a sentence or two, with the critical numbers attached. Findings without numbers are opinions; attach the metrics.
Recommendations
What should happen next, stated as direct actions. Each recommendation ties visibly to a finding above it — the reader should be able to draw the line from “we found X” to “therefore do Y” without effort.
Conclusion
One paragraph: the bottom line. If the reader remembers one thing, this is it. Short, decisive, forward-looking.
This structure flexes slightly by document type — which we’ll cover below — but the skeleton stays the same: context, objectives, findings, recommendations, conclusion.
Step-by-Step: Part 1 — Before You Write
Step 1: Know Your Audience
Write for the actual decision-maker, not a generic “executive.” What decision are they making? What do they already know? What do they care about — cost, risk, speed, growth? A summary for a CFO leads with numbers; a summary for a COO leads with operational impact. Same report, different emphasis. Get the audience wrong and even a perfect summary persuades no one.
Step 2: Read the Full Document
Read your own report start to finish, as a stranger would. You’re looking for the spine: the three to five points without which the document collapses. Mark them. Everything else is supporting material — it stays in the report, not the summary.
Step 3: Pull the Key Points — In Report Order
Extract the marked points in the order they appear in the document, under matching headings. Report order matters because the summary is a map of the report — same sequence, same landmarks, compressed. Reordering in the summary forces the reader to re-navigate when they dive into the full text.
Step-by-Step: Part 2 — Drafting and Refining
Step 4: Draft in Report Order
Write the first draft following the structure above: introduction, objectives, key findings, recommendations, conclusion. Don’t polish yet — get the content right first. Aim for completeness over elegance; you’ll cut in the next steps.
Step 5: Write Clear, Active, and Jargon-Free
Now sharpen the language. Active voice throughout: “we recommend” not “it is recommended.” Short sentences. Zero jargon — if a term needs explaining, it doesn’t belong in a summary. Open with a strong hook: the single most important finding or the decision at stake, in the first two sentences. Executives decide in the opening paragraph whether to keep reading; earn the next paragraph immediately.
Step 6: Add Metrics
Every claim that can carry a number should carry one. “Reduced costs in the pilot” — with the actual figure attached — persuades; “improved efficiency” evaporates. Pull the two or three numbers that anchor your findings and make sure they’re in the summary, stated exactly as they appear in the report — remember Rule 3, no new information means no new numbers either.
Step 7: Test and Revise
Run the standalone test: hand the summary to someone who hasn’t read the report and ask them to explain back what the document found and recommends. Where they stumble, you rewrite. Then check the length — 10–15%, 1–2 pages — and cut until it fits. Cutting is not losing content; it’s the summary doing its job.
Business Plan vs Report vs Proposal Summaries
The mechanics are the same; the emphasis shifts. If you’re writing in a business-plan context, this step-by-step business plan guide covers the full document your summary will front.
Business plan summary. Leads with the opportunity and the ask. The reader is deciding whether to invest, partner, or approve — so the summary foregrounds the market opportunity, the business model in one paragraph, the financial highlights, and what you’re asking for. It’s the most persuasive of the three types.
Report summary. Leads with findings. The reader commissioned analysis and wants conclusions — so findings and recommendations dominate, with methodology compressed to a line or two. Objectivity is the currency here; the summary reports what the analysis showed, including inconvenient findings.
Proposal summary. Leads with fit. The reader is choosing between vendors or approaches — so the summary foregrounds understanding of their problem, your proposed approach in brief, why you’re the right choice, and the investment required. It’s part summary, part pitch, and the differentiator needs to be unmistakable.
Know which one you’re writing before you start. A report summary’s neutral tone will lose a proposal; a proposal’s pitch tone will undermine a report.
Common Mistakes
Writing it first. The summary drafted before the report is finished always drifts from the final document. Write it last — Rule 1 exists because this mistake is so common.
Too long. A five-page “summary” of a twenty-page report isn’t a summary; it’s an abridgment nobody reads. Enforce the 10–15% rule ruthlessly. If it doesn’t fit in 1–2 pages, you haven’t prioritized — go back to Step 2.
New information. Findings, numbers, or recommendations that appear only in the summary. It breaks the document’s integrity and strands the reader with claims they can’t verify. Everything in the summary must exist in the report first.
Jargon and passive voice. “Leveraged synergies were effectuated to optimize outcomes” — this is how summaries go to die. Active voice, plain words, short sentences. If it sounds like a corporate press release, rewrite it.
Burying the lead. Opening with background and methodology while the key finding sits in paragraph four. Lead with what matters — the decision, the finding, the recommendation. Background is the report’s job.
No standalone readability. A summary that only makes sense with the report open beside it has failed its one purpose. Test it on a cold reader every time.
Executive Summary vs Introduction: What’s the Difference?
This confusion is widespread enough to deserve its own section. An introduction opens the document and sets up what’s coming — background, context, scope, roadmap. It points forward: “here’s what this report will cover.” It assumes the reader will continue.
An executive summary condenses the entire document — including the ending. It contains the findings and recommendations, the parts the introduction deliberately withholds. It assumes the reader may read nothing else.
The practical test: if you removed everything after it, the introduction would leave the reader uninformed; the executive summary would leave them decided. They serve opposite ends of the reader’s journey. Write both, confuse neither — and never submit an introduction labeled as a summary.
If your summary work sits inside a larger planning effort, these companions help: a business plan guide for the document the summary usually fronts, a marketing plan guide for campaign documents, and startup context in what a startup actually is when the summary fronts a pitch.
Frequently Asked Questions
How long should an executive summary be?
Aim for 10–15% of the full report’s length, which typically works out to 1–2 pages. A 40-page report gets at most a 4–6 page summary; a 10-page report gets about a page. Longer than that and it stops being a summary — enforce the proportion ruthlessly and cut until it fits.
Do you write the executive summary first or last?
Last — always. The summary goes first in the document but is written after the report is complete. You can’t accurately distill findings and recommendations that don’t exist yet, and summaries written first almost always drift from the final document.
What should an executive summary include?
Five blocks in report order: introduction (context), objectives (what the report set out to do), key findings (the 3–5 that matter, with metrics), recommendations (direct actions tied to the findings), and conclusion (the bottom line). Use headings matching the report’s structure so readers can move between the two easily.
Should an executive summary have headings?
Yes. Use headings that mirror the report’s structure and order. Matching headings turn the summary into a map of the full document — the reader can jump from a summary section to the corresponding report section without reorienting. It also forces you to keep the summary in report order.
Can an executive summary contain new information?
No. Nothing — no data, no arguments, no recommendations — should appear in the summary that doesn’t appear in the report body. The summary is a distillation, not an extension. If something is important enough for the summary, add it to the report first.
What’s the difference between an executive summary and an introduction?
An introduction sets up the document — background, scope, and what’s coming — and assumes the reader will continue. An executive summary condenses the entire document including findings and recommendations, and assumes the reader may read nothing else. If everything after it were removed, an introduction leaves the reader uninformed; a summary leaves them decided.
