How to write an executive summary, with a template you can copy

What an executive summary actually has to do

Picture the reader. They were not at the meeting. They did not read the report. They are looking at your message on a phone, between two other things, and they will decide in about fifteen seconds whether to keep reading.

That reader needs three things from you, in this order: what you want them to do, why it matters now, and what it will cost. Everything else is optional detail they will read only if the first three lines earned it.

The template below turns that into five parts. Only the weight of each part changes, whether you are summarising a 45-minute meeting, a project status, or a 40-page report.

Write for one person, not a committee. If you find yourself writing "stakeholders should note", you have lost the reader. Name them. "Marc, we need your approval on the budget line by Friday."

The executive summary template, copy it as it is

Everything in square brackets is placeholder text you replace. Keep the bold labels, they are what makes the summary skimmable. Delete any part that is genuinely empty rather than filling it with "N/A".

• Subject: [Topic in six words or fewer]. [Decision needed by DATE, or: for information, no action needed]
• The ask. We recommend [specific action]. We need [name] to [approve / sign / fund / choose] by [date], because [the hard deadline that drives it].
• The situation. [What changed, with the number that makes it matter.] [Why the current path stops working.] [Why it cannot be left until next quarter.]
• What we decided. [Decision 1, stated as a completed choice.] [Decision 2.] [Decision 3.] [Anything left open, with an owner and a date.]
• What it costs. Money: [amount, and over what period]. Time: [how long, whose time]. Risk we are accepting: [the one thing most likely to go wrong].
• What we need from you. [Name] to [action] by [date]. [Name] to [action] by [date].
• If there is a real choice to make, put a small options table under "what it costs": one row per option, with the cost, how long it takes to switch, and the main risk. The filled example further down shows one.
• More detail if you want it. [Where the full notes, transcript, or report live. One line, one link.]

The five parts, and what people get wrong in each

Now the detail behind each line of the template. Here is what belongs in each field, and the mistake that shows up most often.

• The ask. What you want the reader to do, and by when. One or two sentences, at the very top. The common mistake is burying it, or softening it into "we may want to consider". If you are not asking for anything, say so plainly: "No action needed, this is for awareness." That is a valid ask and it saves the reader from hunting for one.
• The situation. What changed, in numbers, and why it cannot wait. Two or three sentences. The common mistake is writing history. The reader does not need how the contract was signed in 2023. They need that the renewal quote came in 18% higher and the notice deadline is 30 days away.
• What we decided. The decisions that were actually made, not the topics that were discussed. Three or four bullets at most. The common mistake is listing conversations. "Discussed pricing" is not a decision. "Agreed to hold pricing until January" is. If a topic ended without a decision, write "open" and give it an owner and a date.
• What it costs. Money, time, people, and the risk you are accepting. The common mistake is listing only the money. A decision that costs no money but takes two engineers away from launch work for three weeks is expensive. Say the number and say what you are betting on.
• What we need from you. One line per person, with a name and a date. The common mistake is the passive voice: "approval will be required". By whom, from whom, by when. If nobody's name appears in this section, nothing will happen.

A filled example: warehouse contract renewal

This is the template above with a real shape to it. The meeting is invented, the specificity is the point. Notice that the reader can stop after the first three lines and still act correctly.

Subject: Kestrel warehouse renewal. Decision needed by 26 September.

The ask. We recommend a six-month bridge extension with Kestrel Logistics rather than the full twelve-month renewal, and a move to Bramble Fulfilment in January. Marc, we need you to approve $28,800 of extra warehouse spend plus a one-time $15,000 migration budget by 26 September. Kestrel requires 30 days' notice and the current contract ends 31 October.

The situation. Kestrel's renewal quote came in at $49,600 per month, up from $42,000. That is an 18% increase, or $91,200 more per year. Bramble quoted $44,100 per month, but their onboarding takes six weeks, which lands the migration in November and December, our two heaviest shipping months.

What we decided. Take the six-month bridge at $46,800 per month and migrate in January, when volume drops. Priya runs a 200-unit cold-chain test with Bramble in October before we commit. We are not renegotiating pick-and-pack rates this cycle, that conversation moves to the January migration. Still open: whether the 14 serum lines move in the same wave as everything else. Priya decides by 24 October.

What it costs. Money: $28,800 more than today's rate across six months, plus $15,000 one-time for migration. Time: roughly two weeks of Priya's capacity in January. Risk we are accepting: Bramble has never handled our cold-chain SKUs at volume. The October test is there to catch that before it becomes a returns problem.

What we need from you. Marc to approve the budget by 26 September. Dana to sign the bridge agreement by 30 September. Priya to report the cold-chain test result by 24 October.

More detail if you want it. Full notes and vendor quotes from the 12 September operations review are in the shared Ops folder.

Why a chronological summary fails an executive

Most people write the summary in the order things happened. "We opened with the budget review, then Priya presented the vendor comparison, then we discussed the migration risk, and finally we agreed to..." That order feels natural because it matches your memory of the room.

It fails because the conclusion is at the bottom. The reader who stops after two sentences, which is most readers, leaves with the agenda instead of the decision. You made them do the work of finding the point.

The fix is the inverted pyramid, borrowed from newspapers. Put the conclusion in the first sentence. Put the evidence that supports it underneath. Put background and history last, where it can be cut without damage. A reader can stop at any line and still leave holding the right thing.

• Chronological, weak: "The operations review on 12 September covered the warehouse contract, the peak season forecast, and the cold-chain test plan. After discussion, the group leaned toward a shorter extension." Two sentences in and the reader still does not know what you want.
• Inverted, strong: "We recommend a six-month bridge extension with Kestrel Logistics instead of the full renewal. It costs $28,800 more than today's rate but avoids a warehouse migration during peak season. Marc, we need budget approval by 26 September." Same two sentences, and the reader can act.
• The test: delete everything except your first sentence. Does the reader still know what to do? If not, the first sentence is wrong. Rewrite it before you touch anything else.

Variant 1: the project status executive summary

Status updates go wrong in a specific way. They report activity instead of position. "The team completed 14 tickets and held two design reviews" tells a sponsor nothing about whether the date holds.

For a status summary, the ask is usually one of three things: keep going, give us something, or change the date or the scope. Say which one in the first sentence, then show the position underneath.

The ask. Checkout rebuild is in week 9 of 14. We will hit the 24 October launch date only if we get one more backend week. Otherwise we ship without address validation and add it in November. Aisha needs your call by 19 September.

Position. Two of four workstreams are done or on track. Address validation is blocked on a vendor API quota that has been open for eleven days. Load testing cannot start until payments is in staging, which slips the whole test window by a week.

What it costs. One more backend week means pulling Tomas off the subscriptions work, which pushes that to November. Shipping without address validation means an estimated extra 40 support tickets a week from failed deliveries, based on the rate we saw before the old validator was removed.

The table is the whole point of a status summary. One row per workstream, one honest status word, one name, one next date. If every row says "on track", the reader stops trusting the table.

Variant 2: the executive summary of a long report

When you are summarising a document rather than a meeting, the reader's question changes. It is no longer "what did you decide", it is "what does this mean for us, and do I have to read the rest".

So the shape shifts. The ask becomes a finding plus a recommendation. "What we decided" becomes "what the evidence says". And you owe the reader an honest line about how strong the evidence is, because they are trusting your reading of forty pages they will never open.

The finding. Eighteen customer interviews say the annual-only pricing page is not the problem. Fifteen of eighteen understood the price. Eleven of eighteen stalled on a different thing: they could not tell whether their existing data would carry over.

The recommendation. Stop the annual-only pricing test and put that sprint into a migration explainer on the signup flow instead.

How strong the evidence is. Eighteen interviews, all from the mid-market segment, all conducted in August. It does not tell us anything about enterprise buyers or about people who never reached the pricing page at all.

What we need from you. Sam to approve stopping the pricing test before the 22 September sprint planning. No budget change, the work is already staffed.

More detail if you want it. The full report is 41 pages. Pages 12 to 19 carry the migration finding. Everything else is background you can skip.

How long it should be, and how to cut it

One page. Around 250 words. If it needs a scroll on a phone, it is not an executive summary, it is a report with a nice title.

Treat the word budget below as a diagnostic, not a rule. A part that keeps running over its target is usually the part you have not decided yet.

Cutting is easier if you cut in this order. First, delete every sentence that describes process rather than outcome. "We reviewed three vendors and scored them against six criteria" becomes nothing, because the table already shows it. Second, delete every adjective doing emotional work: significant, critical, exciting, concerning. Give the number instead. Third, delete background the reader already lived through. Fourth, and only fourth, start shortening the parts you actually need.

One more cut most people miss. If a sentence would be equally true next month, it is probably filler. "Alignment across teams remains important" survives any edit because it says nothing.

Write the first sentence last, and check it against this list

The first sentence is the hardest one and it is the one people write first, which is why so many summaries open with "This document summarises the outcomes of the operations review held on 12 September." That sentence tells the reader nothing they cannot see from the subject line.

Write the middle first. Get the situation, the decisions and the costs down in whatever order they come out. Then read it back and ask which single sentence the reader has to have. Naming the point is much easier once the point is sitting in front of you.

A second trick that works: say the summary out loud to a colleague in one breath. Whatever you actually said is your first sentence. People are naturally good at the inverted pyramid when they speak and naturally bad at it when they type.

Then run the finished thing through this list before you send it.

• Can the reader act after sentence one? If not, rewrite sentence one.
• Is there a name and a date in the last section? Every commitment needs both, the same discipline that makes an action items list work.
• Does every number have a unit and a period attached? "$28,800" means nothing without "over six months".
• Did you separate decisions from discussions? Anything still open should be labelled open, not smoothed over.
• Did you state the risk you are accepting? A summary with no risk in it reads as either dishonest or unfinished.
• Is it under one page? Read it on your phone before you send it, not on your laptop.
• Have you removed the words that add nothing: significant, various, ongoing, alignment, strategic, going forward?
• If the summary is going to people who missed the meeting entirely, does it work on its own, without the full minutes attached?

Getting this structure out of a recording instead of writing it

Everything above works with a blank document. The real problem with executive summaries is not the format, it is writing one while you still remember what was said, usually right after the meeting and usually when you are already late to the next one.

If you record the meeting, Noter AI can produce this shape for you. Its Formal report output style gives you the situation, what was decided, the costs and the commitments people made, with speaker labels and timestamps so you can check any line against the audio. The Custom output style matches this page more closely: you describe the format you want and paste in the headings from the template above, and the recording comes back in that exact structure.

There is a second reason to build the summary from a recording rather than from memory. Names, numbers and dates are the parts of an executive summary that must be right, and they are exactly the parts people misremember. If the transcript gets a vendor name or a figure wrong, you can fix it and re-run the summary so the corrected version flows through.

It also handles bilingual meetings, which is normal in a lot of companies. The transcription tags language word by word instead of locking to one language when you press record, so a sentence that mixes Arabic and English arrives with each half written in its own script. Tools that make you pick a language first spell the second one out phonetically, which turns a name or a figure into nonsense. There is more on that in the guide to transcribing multilingual meetings.

On price it is $9.99 a month, or $49.99 a year, per person. Not per seat, but be clear about what that does and does not buy: five people writing summaries is five separate subscriptions, not one shared workspace with company-wide search and a single invoice. On annual billing those five cost roughly $21 a month between them. The comparison worth running is against your own hourly rate rather than against another tool. If writing one summary by hand takes forty minutes and you write two a week, the year's subscription is paid off somewhere in the first fortnight. There is a free trial, so test whether the Formal report output lands close enough to the structure on this page to save you the writing.

It runs on iOS and Android.