The executive summary of a business report is not an introduction. It isn't a teaser, and it isn't a list of chapter headings in prose form. It's a compressed version of the entire report, written for someone who may never get past the first page. Get it right and busy readers make decisions. Get it wrong and the rest of the report sits unread.
What an executive summary actually does
An executive summary serves one purpose: to let a time-pressed reader understand the full picture without reading the full document. That means including the purpose, the key findings, the conclusions, and the recommendations. All four. A summary that covers only three of them forces the reader to search for the missing piece inside the report body.
Length depends on the report. For a 10-page internal report, one page is right. For a 50-page external report, two pages is the ceiling. A 200-word summary is not an executive summary. It's a blurb. Conversely, a five-page summary defeats the point.
The executive summary also stands alone. It circulates separately in board packs, email attachments, and briefing documents. That means it can't contain references like "as shown in Figure 4" or "see the appendix." Every claim needs to be readable without the report beside it. If you've already written your report's appendix, you know that supporting detail belongs there, not here. The same logic applies in reverse for the summary: the summary carries conclusions, not raw data.
The four-part structure that works
A reliable executive summary moves through four blocks in order:
- Purpose. One to two sentences on why the report exists and what question it answers.
- Findings. The most important things you discovered. Not everything. The findings that directly support the conclusions.
- Conclusions. What the findings mean. This is the analytical step most writers skip, jumping straight from data to action.
- Recommendations. What should happen next, stated plainly and in priority order.
Writers who struggle with executive summaries usually collapse findings and conclusions into one block. The distinction matters. A finding is a fact: customer satisfaction scores dropped 14 percent in the second quarter. A conclusion is an interpretation: the drop is attributable to extended wait times rather than product quality. A recommendation is an action: add two frontline staff to the support team before November.
Keep the same order as the main report. Readers moving from the summary into the body should find the structure familiar, not rearranged.
Write the summary last, not first
Most writers draft the executive summary before they write the report. The logic seems sound: know where you're going before you start. In practice, this produces summaries that don't match the report they're meant to represent, because the analysis changes as you write.
Write the full report first. Then write the summary. This approach takes fifteen extra minutes and produces a summary that actually reflects what the report says. It also forces you to identify which findings matter most, which is a useful discipline on its own.
If you need a planning document to guide the drafting process, write a brief outline. Don't mistake an outline for a summary.
Common mistakes writers make
The most common failure is writing an introduction instead of a summary. Phrases like "this report examines" or "the following sections will explore" signal that the writer is describing the report rather than condensing it. A reader doesn't need to know what the report will explore. They need to know what it found.
Passive voice is a close second. "It was found that" buries the subject and weakens the sentence. "The audit found" is shorter and clearer. If you're working on proofreading your draft for these patterns, pay particular attention to your headings and section titles, which often carry the passive-voice problem from body to summary.
Hedged language is the third common problem. Words like "may," "could," and "potentially" make recommendations sound tentative. Recommendations are only useful if they're clear. "The company should consolidate its two distribution centres" is a recommendation. "The company may wish to consider whether consolidation of distribution assets could potentially be viable" is noise.
Numbers without context mislead. "Sales increased by 30 percent" requires the reader to know the baseline. If that context isn't obvious from the rest of the summary, provide it in one clause: "Sales increased by 30 percent from a 2024 low, reaching $4.2 million in Q2 2026."
Connecting the summary to the rest of the report
The executive summary and the discussion section carry the heaviest analytical load in any business report. The discussion is where you build the argument at length. The executive summary is where you deliver the verdict. Readers who want the verdict first get it in the summary; readers who want the reasoning get it in the discussion. Both groups should find what they need.
Recommendations in the summary should match the recommendations section of the report exactly. Not paraphrased. Not reordered. Identical wording. A reader who finds a recommendation in the summary and then searches for it in the body should land on the same sentence. Divergence signals that one version was edited without updating the other, and it damages credibility.
Your appendices carry the technical detail that supports the findings. The executive summary should acknowledge their existence only if a reader genuinely needs to know that supporting data exists. Otherwise, leave appendices out of the summary entirely.
Tone and language
Write for a senior reader who knows the organisation but may not know the project in detail. Avoid jargon that requires specialist knowledge. Avoid acronyms on first use. Assume your reader is competent, not expert in your subject area.
Sentences should be short. Paragraphs should be short. The summary is not the place for subordinate clauses stacked three deep. If a sentence runs past 25 words, split it.
One thing to check at the end: does the summary make sense without the report? Read it in isolation, as if you've never seen the main document. If a sentence relies on context you haven't provided, rewrite it. The executive summary should earn its keep independently, every time.