Executive summary: writing the page that actually gets read

An executive summary is a self-contained account of a longer document, written so that a decision can be made from it alone. That last clause is the whole definition. If a reader has to turn to page fourteen to understand what you are asking for, the summary has failed at the only job it has.

It appears at the front of business plans, proposals, reports and business cases, and it is almost always written badly — because most people write it first, as a warm-up, when it is the one section that can only honestly be written last.

What an executive summary is not

• It is not an introduction. An introduction prepares you to read on; a summary substitutes for reading on.
• It is not an abstract. An abstract describes what a document covers; a summary states what it concludes.
• It is not a table of contents in prose. Nobody needs "section three discusses the market".
• It is not a teaser. Withholding the conclusion to create interest works in fiction and nowhere else.
• It is not the place for background. Context, yes, in a sentence. History, no.

The test is simple and unforgiving: hand somebody the summary alone and ask them what you want and why. If they can answer both, it works. If they say "it seems to be about the new warehouse", it does not.

What goes in it

The order matters more than the content, because readers of executive summaries stop early. Put the answer at the top and the reasoning underneath, which is the reverse of how you thought about the problem and the reverse of how the full document is structured.

1. Open with the situation in one or two sentences — enough for someone who has been in no meetings about this.
2. State the recommendation or conclusion plainly, in the second paragraph at the latest.
3. Give the two or three reasons it holds, with the numbers that carry the most weight.
4. Say what it costs, what it needs, and by when.
5. Name the main risk and how it is handled — including it builds far more trust than omitting it.
6. End with the specific decision you are asking for, and who has to make it.
7. Cut it to a page. Two only if the underlying document runs to fifty.

Write it last, then rewrite it

Writing the executive summary last is not a scheduling preference. Until the analysis is done, you do not know what the conclusion is, and a summary written in advance quietly turns into the thing the rest of the document has to justify. Several bad business cases have that exact origin.

When the document is finished, write the summary from scratch rather than by pasting sentences out of the body. Pasted summaries read as disjointed because each sentence was written to follow a different sentence. Start with a blank page and answer the question: what does this say?

Length and numbers

A page is the working limit. The constraint is what makes the summary useful; anything longer stops being a summary and starts being a shorter version of the document, which nobody asked for.

Include numbers, but few of them. Three figures a reader remembers beat twelve they skim: the cost, the return, the timeframe. Anything else belongs in the body where it can be presented properly with its assumptions.

Match it to the reader

The same underlying document needs different summaries depending on who is deciding. A board wants the financial exposure and the risk. A prospective client wants to know what they get, by when, and what it costs them. An investor wants the market, the traction and the ask. The body can stay the same in all three cases; the summary should not.

If you write proposals or reports regularly, keeping the structure in a document you copy each time saves the fifteen minutes usually spent rediscovering the order. Ettex Docs holds that as a normal document you duplicate and edit, and comments let a colleague push back on the recommendation before it goes out — which is when that feedback is worth having.

It will not write it for you, and that is deliberate rather than a limitation we are apologising for: the whole value of an executive summary is that a person decided what mattered enough to go on the page. A generated one reads like a generated one, and the reader you are writing for notices.

Common failures

• Written first, so the document becomes an argument for a conclusion reached too early.
• Recommendation buried on the second page, after the methodology.
• Assembled from copied sentences, so it reads as fragments.
• Every number from the full document included, so none of them land.
• Risks left out, which experienced readers read as either naivety or concealment.
• No specific ask, so the reader finishes it agreeing with you and doing nothing.
• Same summary sent to a board, a client and a bank.

Write the executive summary last, put the answer in the first two paragraphs, keep it to a page, and finish with the decision you want. Then test it by handing it to someone who has read nothing else.