How to Write an Executive Summary: A Plain Method Busy Leaders Can Skim

An executive summary is the short version of a longer report, written so a busy reader can decide what to do without reading the whole thing. It is not a preface and it is not a teaser. It stands alone: someone who reads only the summary should walk away knowing what the report says, what it recommends, and what they need to approve or decide. Most summaries fail because they repeat the report's structure instead of its conclusions. The reader gets a tour when they wanted a verdict.

The executive summary exists because the people with the authority to act rarely have the time to read forty pages. Your job is to hand them the answer first and the support second. If they want detail, the full report is one click away. If they do not, they still leave informed.

A good summary also forces the writer to think. If you cannot state the recommendation in two sentences, the report probably does not have one yet. Writing the summary first, or at least early, often exposes the gaps before you sink hours into a document nobody reads.

If your underlying report is a regular one, build it on a steady rhythm first — a weekly report gives you the running facts, and a monthly report gives you the trend. And when the document needs to read as an official piece rather than an internal note, follow a report writing format so the summary sits inside a structure readers trust.

What Goes in an Executive Summary

The summary has four jobs, in this order:

1. The recommendation. State what you want the reader to do or approve. Put it in the first two sentences. "We recommend delaying the launch to August" beats "This report examines the launch timeline."
2. The reason. One or two sentences on why, with the single strongest fact. Not every fact — the one that settles the decision.
3. The key findings. Three to five bullet points of evidence. Each should be a conclusion, not a data dump. "Churn rose 4 points after the price change" not "We looked at churn."
4. The ask and the cost. What you need from the reader, by when, and what it costs or risks if they do nothing. A summary with no ask is a memo, not a decision tool.

Keep the whole thing under a page, often under half a page. If it runs long, cut the findings, not the recommendation. The reader came for the verdict.

Template

EXECUTIVE SUMMARY — [Report title], [Date]

RECOMMENDATION
  [One sentence: what we recommend doing.]

WHY IT MATTERS
  [One or two sentences with the strongest single fact.]

KEY FINDINGS
  - [Finding] — [brief support]
  - [Finding] — [brief support]
  - [Finding] — [brief support]

THE ASK
  Decision needed: [approve / reject / fund / delay]
  By: [YYYY-MM-DD]
  If we do nothing: [the cost or risk]

Prepared by: [Name]  |  Full report: [link or location]

Real Example

EXECUTIVE SUMMARY — Q3 Pricing Review, 2026-05-12

RECOMMENDATION
  Hold the Pro plan at $49 for Q3 and pilot a 20% annual discount.

WHY IT MATTERS
  Monthly churn climbed 4 points after the April increase; the discount is the cheapest test we have to slow it.

KEY FINDINGS
  - Churn up from 3.1% to 7.2% in the month after the change
  - Annual users churn half as often as monthly users
  - Discounted annual would cost ~$18k in Q3 margin at current volume

THE ASK
  Decision needed: approve the annual discount pilot
  By: 2026-05-26
  If we do nothing: churn stays elevated through the summer peak

Prepared by: Dana  |  Full report: /reports/q3-pricing-2026.pdf

This summary gives a skipped executive everything in twelve lines. They know the call, the reason, the numbers behind it, and the date they need to decide by. The full report exists for the one person who wants the model — everyone else is done.

Common Mistakes

• Leading with background. "Founded in 2014, our company has grown..." tells the reader nothing they need to decide today. Start with the recommendation.
• Restating the table of contents. "Section 1 covers market size, Section 2 covers..." is a map, not a summary. Give conclusions, not chapter labels.
• Hiding the ask. A summary that ends with "further analysis is available" leaves the reader with no action. State what you need.
• Filling it with data instead of meaning. Ten numbers with no sentence tying them together is a spreadsheet, not a summary. Each bullet should be a takeaway.
• Writing it last and rushing. The summary is the most read part of the document, yet people write it in five minutes at midnight. Give it the first draft, not the leftover.
• No date on the decision. "Approve soon" is not a deadline. Put a real date on the ask so it does not stall.
• Being vague to avoid commitment. "We should consider options" is not a recommendation. Pick the path and defend it.

Take the Next Step

Copy the template above and write your next summary before you write the report body — lead with the recommendation and let the findings defend it. Keep it under a page and end on a dated ask so the reader knows exactly what to do. When the underlying numbers come from a regular cadence, feed them from a weekly report so the summary always has fresh facts behind it. And if the document must read as a formal piece, shape it with a report writing format that keeps the structure honest from summary to appendix.