One hundred forty dollars: that single figure opens Kentucky’s 2015 guide to court costs and fines, before a single sentence of background and before any definition of what the guide even is. It works as an opening because it behaves exactly like a good executive summary example: the reader already has the single most useful fact before anything else competes for their attention.
What an executive summary is actually for
An executive summary states the conclusion first, in enough detail that a reader who stops after one paragraph still knows what a report found and what it recommends. It is not a preview or a teaser; it is the report’s argument compressed into its smallest useful form, written for a reader who may never read past it. That reader is not hypothetical. Executives, funders, editors, anyone deciding whether a longer document deserves their time, routinely read only the summary and act on it, which is exactly why a weak one is more costly than a weak paragraph buried on page thirty.
Treating the summary as an afterthought, written in the last ten minutes before a deadline, is one of the most common ways a genuinely strong report undersells itself. A reader forms an impression of the entire document from its first page, and if that page hedges, generalizes or delays, the impression sticks even when the body of the report contains sharp, specific findings a few pages later. The summary is not lesser writing because it is short; if anything it is harder to write well than the sections around it, since every sentence has to carry more weight with no room for the qualifications and context a longer section can afford.
Executive summary vs introduction
An executive summary and an introduction sit near the front of most reports, and they get confused constantly, but they do close to opposite jobs. A summary front-loads the conclusion: the finding, the recommendation, the reason it matters, stated immediately so a reader who never turns the page still leaves informed. An introduction instead sets up the question a report will answer, giving context, defining scope, explaining why the report was commissioned, without giving away where the argument actually lands. A reader who wants the answer reads the summary. A reader who wants to understand how the report is going to get there reads the introduction. Confusing the two produces a summary that reads like a throat-clearing preamble, or an introduction that spoils its own argument on page one.
A closely related distinction is worth naming too: an executive summary is not the same thing as an abstract, the short neutral description common in academic papers. An abstract typically describes a paper’s content without arguing for anything, written to help another researcher decide whether the full paper is relevant to their own work. An executive summary is persuasive by design, built to help a specific decision-maker act, and it usually closes with a recommendation an abstract would never include. Confusing the register of the two produces the same problem in both directions: an abstract that sounds like it is trying to sell something reads as biased, and an executive summary that reads like a neutral abstract, all description and no recommendation, leaves the actual decision unmade.
A template for a report’s executive summary
A dependable four-part template covers most reports regardless of subject. First, state the problem or the reason the report exists, in a sentence or two, not a page. Second, state the main finding or recommended response directly, the actual answer, not a hint that an answer exists somewhere inside. Third, state concretely why that finding matters, ideally with a specific number or consequence rather than a general claim like “this is significant.” Fourth, close with what should happen next, whether that is a decision, an allocation, or simply a recommendation to read a specific section in full.
Length matters as much as structure. A commonly used guideline keeps an executive summary to roughly 5 to 10 percent of the full report’s length, which in practice means most reports, even fairly long ones, should be summarized in one or two pages. A summary that runs to five pages has usually stopped summarizing and started duplicating the report it was meant to compress.
The order the four parts appear in is not arbitrary either. Problem before solution establishes why the reader should care at all before asking them to accept a recommendation; a recommendation with no stated problem reads as an opinion looking for a justification, rather than a conclusion earned by the evidence behind it. Value before next steps answers the question a reader is silently asking the whole way through, why does any of this matter to me specifically, before asking them to act on it. Skipping straight from problem to next steps, without stating the finding or its value in between, is one of the fastest ways to produce a summary that sounds urgent without actually being informative.
One good executive summary example, and one padded one
Consider two openings for the same imaginary workplace survey. The padded version: “This report explores several important dimensions of employee engagement across the organization, drawing on a range of data sources to provide valuable insights that stakeholders may find useful going forward.” That sentence could open almost any corporate report on almost any topic, and a reader finishes it knowing nothing they did not already know from the title.
The working version: “Employee turnover rose from 9% to 14% this year, concentrated almost entirely in staff under two years’ tenure; the report recommends restructuring the first-90-days onboarding process, projected to cut that gap by roughly a third within a year.” Same underlying report, same underlying data, but the second version states a number, names a cause, and recommends a specific action, all inside one sentence. Nothing about the second version is more sophisticated language; it is simply ordered so the most important fact comes first instead of last, which is the single habit that separates most working executive summaries from most padded ones.
Turning a padded summary into a working one is rarely a rewrite from scratch. It is usually a matter of finding the one sentence, often buried near the end, that actually states the finding, and moving it to the front. Everything ahead of that sentence in the padded version, the throat-clearing about scope and methodology and stakeholder value, either gets cut outright or gets folded into the “why it matters” step of the four-part template, where it belongs rather than sitting in front of the conclusion delaying it. A useful exercise for anyone reviewing their own draft summary: read only the last sentence first. If the last sentence turns out to be the strongest, most specific one in the paragraph, the summary is very likely upside down.
Kentucky’s own 2015 costs, fees and fines guide rewards the same test. Its opening states a concrete figure, a hundred and forty dollars in standard court costs, before any throat-clearing about what a guide to court fees is or why it might matter to a public defender. A reader stopping after one sentence already has something usable. That is not an accident of good writing; it is what happens when a document is built, deliberately or not, around the same rule an executive summary depends on: say the most important thing first, and let everything else follow from there.
The broader habit of separating a report’s claim from the evidence behind it, covered in the how to read a report guide, applies just as well in reverse, to writing a summary as to reading one: state the claim plainly, then let the rest of the document carry the proof.