How to write an executive summary, step by step

To write an executive summary, finish the full document first, then open the summary with your conclusion or recommendation, add the two or three facts that support it, and end with the decision you need. Keep it to one page or less, about 250 to 400 words, and make sure it reads on its own without the rest of the document.

I've written these for board memos, sales proposals, fundraising docs, and a 60-page market study nobody was ever going to read end to end. The hard part is never the words. It's the discipline: stating the conclusion up front instead of building to it, and cutting your favorite detail because the reader doesn't need it to decide. Below is what an executive summary is, what goes into one, the six-step process I use, a worked example, and the mistakes I still catch myself making.

#What is an executive summary?

An executive summary is a short, standalone overview at the front of a longer document (a business plan, report, proposal, or deck) that lets a decision-maker understand the main findings and the recommendation without reading the rest. It exists so a busy reader can act in a minute or two. The University of Maryland Global Campus writing center describes it as a document directed at top-level managers who sometimes decide based on the summary alone, and that is the constraint to write for.

Two tests separate a real executive summary from the things it gets confused with:

• It gives away the ending. An introduction sets up what's coming; an abstract describes the document in miniature. An executive summary states the conclusion and what should happen next.
• It stands alone. No "as discussed in section 4," no assuming the reader saw the appendix. Hand it to someone cold and it should still make sense.

#What goes into an executive summary?

An executive summary contains the purpose, the key findings, the recommendation, the numbers that justify it, and the ask. Add one or two sentences of background only if the reader can't follow without it. Not every document uses every row, but this is the menu:

What to leave out matters as much: methodology, caveats, detailed data, and any background that doesn't change the decision all belong in the body. Which row leads depends on the reader. A board update opens with results against plan, a sales proposal with the buyer's outcome, a report with the recommendation. I show each version filled in on executive summary examples.

#How do you write an executive summary, step by step?

Six steps. The order matters more than any single step.

1. Write it last. You can't summarize a document that doesn't exist yet. Finish the full thing, then distill it, even though the summary sits first on the page.
2. Open with the answer. The first or second sentence states the recommendation or the headline finding. A summary that makes the reader wait for the point has failed its one job.
3. Pull only the deciding numbers. One cost, one return, one timeline. A summary stuffed with figures hides the one that matters.
4. State the ask. Name the single decision you need, with enough detail (amount, date, owner) that the reader can say yes.
5. Cut to a page. If it runs long, you're explaining instead of summarizing. Move the explanation to the body.
6. Read it cold. Hand it to someone who hasn't seen the document, or reread it as if it's all you'll see. If they get the point and know what you want, it works. Anything you stumble on reading it aloud, simplify.

The step people skip is the first one, and it shows. A summary written before the document is really a plan, and the finished document rarely keeps its promises cleanly.

#What does a good executive summary look like?

Here is a before-and-after for an internal proposal to replace a customer support tool (a made-up company, realistic numbers).

Before (the version most people write first):

This document provides an overview of our current support tooling and explores several options for the future. Over the past year, the support team has experienced a number of challenges with our existing platform, including performance issues and rising costs. We evaluated three alternative vendors against a set of criteria, which are described in detail in section 3. Based on this analysis, we believe there may be an opportunity to improve efficiency.

After:

We recommend moving customer support from our current platform to Vendor B by March 31. Our license cost rises 35 percent at renewal on February 28, to $148,000 a year; Vendor B quotes $96,000 for the same seats. In a four-week pilot with six agents, median first-response time fell from 3.1 hours to 1.4 hours. Migration takes about six weeks and one contractor at $18,000. We need approval of the $18,000 migration budget by January 15 to finish before the renewal date.

The "after" version is shorter, and it puts the recommendation in sentence one, gives three numbers that decide it, and ends with an ask that has an amount and a deadline. The "before" version is an introduction pretending to be a summary.

#How long should an executive summary be?

One page is the usual ceiling. A common rule of thumb is 5 to 10 percent of the document, or about 250 to 400 words for a long report. A two-page proposal needs a paragraph; a 50-page report can use a full page. In a deck, it's one slide.

If you can't get it onto a page, the document usually has more than one argument in it, not too little room. Tighten the document's focus and the summary shrinks on its own.

#How do you format an executive summary?

Put it first, right after the title page and before the table of contents in a formal report, so it's the first thing a reader opens. Label it "Executive summary". Use short paragraphs or a few bullets, put the most important number where the eye lands first, and bold nothing except, perhaps, the recommendation.

The title can be plain ("Executive summary") or can carry the conclusion ("Executive summary: move support to Vendor B by March 31"). The second version is better when people will only skim the heading.

#Should you write the executive summary first or last?

Last, almost always. It's a distillation, and you can't distill conclusions you haven't reached. Drafting it first turns it into an outline you commit to before the thinking is done, and it drifts from the document by the time you finish.

A rough summary as a planning tool for yourself is fine, as long as you treat it as scaffolding and rewrite it from the finished work.

#What are the most common executive summary mistakes?

• Burying the conclusion. Writers build to the point the way they would in an essay, and the reader who only reads the summary never reaches it.
• Writing a teaser. Withholding the findings to push people into the body annoys exactly the reader you're writing for.
• Relabeling the introduction. Different job, different content.
• No numbers, or every number. Vague claims don't persuade, and a wall of figures hides the one that matters.
• Depending on the document. If it only makes sense next to the appendix, it can't stand alone.
• Length creep. A summary as long as a section isn't a summary.

#How do you turn the summary into a slide?

Often the executive summary needs to open a deck: the first slide of a board update, a QBR, or an investor update. The writing rules are the same; the slide just holds less. Put the recommendation as the headline, two or three numbers as big figures, and the ask at the bottom.

Here is a board update deck on a sample brand. Click through the opening slides for the pattern: the result as the headline, the numbers set large, and the ask stated plainly.

I do the layout step with heydecks. Claude or ChatGPT writes the summary over the heydecks MCP server, and heydecks renders it on your brand as a live deck and a PDF, with an editable PowerPoint on paid plans. If the summary opens a bigger review, the board deck generator and the QBR generator build the rest of the deck around it. You still bring the findings and the ask.

For a single summary slide from your own document, the executive summary generator shows the brief I use and what comes back.

#Frequently asked questions

#What goes into an executive summary?

The purpose, the recommendation or main finding, the two to four key facts behind it, the numbers the decision turns on, and the ask. Background is optional and should be a sentence or two at most.

#How do you start an executive summary?

Start with the conclusion or the ask, not background. The first sentence should tell the reader what you recommend or what you found; the context can follow in sentence two.

#Does the executive summary go before the table of contents?

Yes, in most formal reports and business plans the executive summary comes right after the title page and before the table of contents, so it's the first thing a reader sees.

#What is the difference between an executive summary and an introduction?

An introduction sets up what's coming and saves the conclusions for later. An executive summary delivers the conclusions up front and can be read entirely on its own.

#What is an executive summary in a business plan?

It's the opening section that sums up the whole plan: the company, the problem it solves, the market, the business model, traction, and what you're asking for. Investors often read it first and decide from it whether to keep going.