How to Write an Executive Summary

An executive summary is not an introduction – it is the whole report compressed for someone who may never read the rest.

An executive summary sits at the front of a report and gives a reader the complete picture in a page or two: the problem, what you found, and what you recommend. The defining feature is that it must stand alone. A busy decision-maker should be able to read it, understand the situation, and act – without turning another page. That single constraint dictates almost everything about how it is written.

How it differs from an introduction

An introduction sets up what is coming; a summary delivers it. An introduction may pose questions the report will answer, while a summary answers them outright. This is why an executive summary contains your conclusions and recommendations, which feels wrong to writers trained to build toward a finding. Withholding the answer is the most common mistake in the form: a summary that describes what the report covers without saying what it concluded has failed at its only job.

Write it last

You cannot summarise a document that does not exist yet. Draft the report, reach your conclusions, then write the summary from the finished text. Working this way also gives you a useful check: if you cannot summarise your own report clearly, the report itself is probably muddled, and the difficulty is telling you where.

What to include

Most effective summaries move through the same sequence, proportioned to the reader’s interest rather than to the length of the sections they represent.

• The problem or purpose – why the work was commissioned, in a sentence or two.
• Scope and method – briefly, only enough to establish credibility.
• Key findings – the three or four that matter, with the numbers that support them.
• Recommendations – what should happen, stated as actions.
• Implications – cost, timing, or risk, where the reader will need it.

Note the proportions: methodology may take a third of the report and two sentences of the summary. You are writing for what the reader needs to decide, not mirroring the structure of the document.

Keep it to the right length

The conventional guide is around ten percent of the report, capped at two pages. For a fifteen-page report, a page is usually right. Longer than two pages and it stops being a summary; a reader who wanted that much detail would read the report. If you cannot fit it, the problem is usually that you are including explanation rather than conclusion.

Write for a non-specialist

Assume your reader is intelligent, busy, and not an expert in your subject. Spell out acronyms on first use, avoid technical vocabulary that has a plain equivalent, and do not assume familiarity with the background. This is not dumbing down – it is recognising that the person authorising your recommendation may sit two departments away from the work.

Lead with findings, not process

Compare two openings. “This report examines the causes of rising delivery delays across the northern region and considers a range of possible responses” tells the reader nothing they did not already know. “Delivery delays in the northern region have risen 34% since March, driven primarily by a single distribution bottleneck that can be resolved within one quarter” gives them the situation, the cause and the outlook in one sentence. The second version respects the reader’s time; the first spends it.

Make recommendations specific

Vague recommendations are the second most common failure. “Improve communication between teams” cannot be actioned, budgeted or measured. “Introduce a weekly fifteen-minute handover between dispatch and warehouse leads, beginning in April” can be. Where you can, attach an owner, a timeframe and an expected effect – even approximate figures make a recommendation far more likely to be adopted.

Test it before you submit

Give the summary alone to someone who has not read the report and ask them to tell you what the problem is and what you are proposing. If they can, it works. If they ask questions answered in the body of the report, the summary is incomplete – it is leaning on material the reader may never reach. Read it aloud as a final pass, since the awkward sentence you skim past on screen is impossible to miss when spoken.

Match the summary to the reader’s decision

Before drafting, identify who will read it and what they must decide. A board approving expenditure needs cost, risk and expected return foregrounded; an operations manager needs the practical change and its timing; a regulator needs compliance and evidence. The same report can carry a different summary for a different audience, and the strongest summaries are visibly written for a particular decision rather than as a generic condensation.

Common failures to check for

Before submitting, read your summary against the errors that appear most often.

• It describes the report rather than reporting the findings.
• It introduces information that appears nowhere in the body.
• It depends on a table or figure the reader cannot see.
• It uses undefined acronyms or internal shorthand.
• It hedges the recommendation so heavily that no action follows from it.

The last is the most damaging. A summary exists to enable a decision, and a recommendation qualified into meaninglessness leaves the reader exactly where they started.

Write for the decision, not the document

Before drafting, name the decision your reader has to make and what they need in order to make it. A board approving expenditure needs cost, risk and expected return; an operations lead needs the practical change and its timing; a regulator needs compliance and evidence. The same report can carry a different summary for a different reader, and the strongest summaries are visibly written for one.

Lead with the conclusion, then support it

Business and policy readers expect the answer first — the opposite of academic convention, where the argument builds. Open with what you found and what you recommend, then supply the reasoning. A summary that withholds the conclusion until the final paragraph has been written in the wrong idiom for its audience.

This inversion is the single most common structural error when academic writers move into professional formats.

Quantify wherever you can

Numbers carry more per word than adjectives and are what decisions actually turn on. “Significant savings” tells a reader nothing; “£240,000 annually, recovering the implementation cost within eleven months” tells them whether to proceed.

• Give the size of the problem, not just its existence.
• Give the cost of the recommendation and the expected return.
• Give a timeframe for when effects would appear.
• State the confidence attached to estimates, briefly.

Common failures to check for

Read the draft against the errors that most often undermine an otherwise good summary.

• It describes the report rather than reporting the findings.
• It introduces material that appears nowhere in the body.
• It depends on a table or figure the reader cannot see.
• It uses undefined acronyms or internal shorthand.
• It hedges the recommendation until no action follows from it.

The last is the most damaging: a summary exists to enable a decision, and a recommendation qualified into vagueness leaves the reader exactly where they started.

Format for scanning

Executive summaries are skimmed before they are read. Short paragraphs, a bulleted list of recommendations, and bold for the two or three figures that matter make the structure visible at a glance. Avoid dense blocks: a reader who cannot find the recommendation in five seconds may not look for it at all.