Executive Summary

What an executive summary is

An executive summary is a short, self-contained section at the front of a longer document that gives a busy reader the whole picture without making them read the rest. In one page or less it states why the document exists, the few things that matter most, what you found or concluded, and what you want the reader to decide or do next.

The word "executive" is the clue to its purpose. It is written for someone who has the authority to act but not the time to read forty pages — an executive, a sponsor, a board member, a client. They should be able to read the summary alone, understand the situation, and make a confident decision. Everything else in the document is there to support and prove what the summary already told them.

A strong executive summary is not an introduction and it is not a teaser. An introduction sets up what is coming; a summary delivers the conclusions up front. If your reader only ever reads this section, they should still come away knowing the point, the recommendation, and the implications.

Where executive summaries are used

Almost any document written to inform a decision benefits from one. The most common homes for an executive summary are:

• Reports — an audit, a research study, an operations review, or a post-incident report. The summary gives leadership the findings and the recommended response before the methodology and the detail.
• Plans — a business plan, a strategic plan, or a project plan. The summary states the goal, the approach, the headline numbers, and what is being asked for.
• Proposals — a sales proposal or an internal funding request. The summary frames the problem, the recommended solution, the cost, and the value the buyer or sponsor gets.
• Business cases — a request to spend money or change direction. The summary carries the recommendation, the expected return, and the decision being requested.
• Grant and tender submissions — where a reviewer skims many submissions and the summary determines whether yours is read closely or set aside.

In every case the job is the same: let a decision-maker grasp the whole thing fast, and make it easy for them to say yes, no, or "tell me more".

What to include

An executive summary should cover, in roughly this order:

• Context and purpose — one or two sentences on why this document exists and what question it answers. Orient the reader before you hit them with conclusions.
• The key points — the two to five things that matter most. For a report these are the main findings; for a plan, the core of the approach; for a proposal, the problem and the offer.
• Findings or recommendation — the actual conclusion. Do not hide it. State what you found and, crucially, what you recommend doing about it.
• Impact — what the recommendation is worth or what is at stake: the cost saved, the revenue gained, the risk avoided, the deadline met. Quantify it wherever you honestly can.
• The ask or next step — exactly what you want from the reader. Approval to proceed? A budget sign-off? A decision by a date? Be specific; a summary that ends without a clear next step leaves the reader unsure why they read it.

You do not need every element in every document, but you should never omit the recommendation and the ask. Those two are the reason the summary exists.

Write it last

The single most useful habit is to write the executive summary last, even though it appears first. You cannot reliably summarise a document you have not finished writing — the conclusions shift as you work through the detail, and a summary drafted too early ends up describing a document you no longer have.

Once the full document is done, the summary almost writes itself: pull the one most important point from each major section, lead with the conclusion, and trim until only the load-bearing facts remain. A good test is to delete the rest of the document in your head and ask whether the summary still stands on its own. If it does not, it is an introduction, not a summary.

Length and skimmability

Keep it short. A common rule of thumb is that the summary runs about five to ten percent of the document, and for almost anything under fifty pages it should fit on a single page. Length is borrowed from the reader's attention, so spend it only on what changes their decision.

Design the page for a skim, because that is how it will be read:

• Lead with the conclusion, not the background. The most important sentence belongs in the first paragraph, not the last.
• Use short labelled sections or bullets so the reader can jump straight to the part they care about — the recommendation, the cost, the timeline.
• Bold the headline numbers — the saving, the return, the budget, the date — so the eye lands on them.
• Prefer plain language over jargon. The summary is the one section a non-specialist sponsor will definitely read; write it so they understand it without the appendix.
• Make it self-contained. Do not refer to "the chart on page 14" or "as discussed below". The summary must work even if it is photocopied and handed across a desk on its own.

Common mistakes to avoid

• Treating it as an introduction. The most frequent error: writing what the document will cover instead of what it concluded. Lead with the answer, not the agenda.
• Burying the recommendation. If the reader has to hunt for what you actually advise, the summary has failed. Put the recommendation where it cannot be missed.
• No clear ask. Ending without a specific next step or decision leaves the reader thinking "so what?" Always close with what you want them to do.
• Vague impact. "Significant savings" persuades no one. "Cuts processing time by 30% and saves an estimated $120,000 a year" does the work.
• Copy-pasting from the body. Stitching together paragraphs lifted from later sections produces a disjointed summary that reads like offcuts. Write it fresh, as a single coherent overview.
• Letting it run long. A two-page "summary" of a ten-page report defeats the purpose. If you cannot make the point briefly, you have not yet decided what the point is.
• Writing it first and never revising. A summary drafted before the document is finished describes a document that no longer exists. Always reconcile it with the final version.