
How to Write an Executive Summary: Steps and Examples
An executive summary is a short, stand-alone version of a longer document. It gives a busy reader the problem, the main findings and what you want them to do, so they can decide without reading everything. Write it last, lead with your recommendation, keep it to one or two pages, and make sure every sentence earns its place.
This guide shows you how to do that for a business report, a proposal or a written case study. It covers what to include, how to structure it, a worked example, and how to edit it. It also covers whether AI can help.
TL;DR
- An executive summary is a stand-alone document that states the problem, findings and recommendation of a longer piece, for a reader who may read nothing else.
- Write it after the main text is finished, then open with the recommendation or main message, not the background.
- Aim for about one page, or roughly 5% to 10% of the full document, and never introduce anything that is not in the report.
- Edit for plain language, one mention of each point, and a clear action with an owner and a deadline.
- AI can produce a first draft, but you must check every figure and claim against the source yourself.
Table of Contents
- What an executive summary is, and what it is for
- What to include
- How long it should be
- Where it goes in the document
- How to write it, step by step
- A worked example
- Writing a summary for a case study or exam exercise
- Editing checklist
- Can AI write an executive summary?
- Perspective
- Getting help with written case studies
- FAQ
- Sources
What an executive summary is, and what it is for
The Harvard Kennedy School guide describes it as a stand-alone, actionable document of one to two pages and no more than 1,000 words. It demonstrates the problem, findings and recommendation of a longer policy report for a busy reader. Two words matter there: stand-alone and actionable. The reader should be able to understand the issue and consider the action you propose without opening the report.
That separates it from an abstract. Grammarly’s guide notes that an executive summary still hits all the key points of the main document, while an abstract is a synopsis. An abstract tells you what a paper is about. An executive summary tells a decision maker what they need to know and do.
A useful test comes from Carnegie Mellon University’s handout, which frames the summary around three reader questions:
- What should I know?
- Why should I care?
- What should I do?
If your draft answers all three in that order, you are most of the way there.
What to include
The exact contents depend on the document, but a few elements recur. NLR’s communication standards say a summary should be readable independently and include the problem or proposal, background, concise analysis and main conclusions, in plain language.
In practice, that gives you five building blocks:
- Purpose: why the document exists and who it is for.
- Context: only the background the reader needs to follow the rest.
- Key findings: the two or three results that matter most, with figures.
- Conclusions or recommendations: what follows from those findings.
- Action: what you need, from whom and by when.
Methods usually get little room. Carnegie Mellon advises emphasising main findings in each paragraph’s topic sentence and de-emphasising methods unless methods are the focus of the report. The IEA-EBC guide makes the same point: decision makers care about application and implications, not the processes behind the research.
How the content changes by document type
The University of Newcastle (Australia) offers a clear table by document type. I have condensed it below.
| Document | Beginning | Middle | End |
|---|---|---|---|
| Report or case study with recommendations | Topic and purpose | Key issues or points of discussion | Recommendations |
| Report with no recommendations | Topic and purpose | Key issues or points of discussion | Conclusions |
| Report based on primary research | Topic and purpose | Key issues or points of discussion | Conclusions and limitations of the research |
For a written case study specifically, the University of Guelph’s guide says the summary should contain a problem statement of one or two sentences, a recommendation, supporting arguments and evidence drawn from the major sections, and a conclusion. It also suggests imagining a sceptical audience and asking why they should believe you, and considering your role in the case, whether an internal team member or an outside consultant, because that shapes the tone.
For a business proposal, swap “recommendation” for “proposal” and add the cost, people, timing and risk in one sentence each.
How long it should be
There is no single rule, but the sources agree on a narrow band.
| Source | Guidance |
|---|---|
| Texas A&M Writing Center | About one or two double-spaced pages, or about 5% of the full report |
| Carnegie Mellon | Typically one page, up to 10% of the report |
| NLR | 5% to 10% of the paper |
| European Court of Auditors | One to two pages |
| Harvard Kennedy School | One to two pages, no more than 1,000 words |
| US GAO | Maximum of four pages, in its own column format |
A sensible default: one page for a report under 20 pages, up to two for a long report, and under half a page for a short proposal. If your reader is senior and short of time, shorter wins.
Where it goes in the document
It sits at the front. Vertex42 advises placing it at the beginning, or just after the title page, when the report is a single document. When your materials are spread over several files, you can send it as a separate document or attach it to the cover page.
The usual question is whether it comes before or after the table of contents. Conventions differ between organisations, so follow your house style or the brief you were given. If there is none, put the contents page first so readers can see the structure, then the summary.
How to write it, step by step
1. Finish the report first
The European Court of Auditors says the best moment to write the summary is once the report text is complete and has passed initial review. Vertex42 gives the same advice for business plans. Some analysts do draft a summary first to fix their structure. The NZIER policy advice brief says both orders work, provided the “need to know” points are present and the logic runs cleanly from the summary to the recommendations. If you draft early, always rewrite it at the end.
2. Name your reader and the decision
Write one line for yourself: who is reading, and what should they do afterwards? Microsoft’s seven-step guide starts from a completed document and the reader’s required action. A finance director approving a budget needs different content from a project team learning lessons.
3. Open with the purpose and the recommendation
Put the answer in the first two sentences. The Harvard guide advises a strong opening on scope and the problem, then key findings at a high level, recommendations tied to those findings, and a short conclusion with a call to action. Do not begin with the history of the topic.
4. Select two or three findings
Choose the findings that support the recommendation, and give each a figure. The GAO advises presenting each major point only once, and linking recommendations directly to the conclusions and findings they address. The GAO also warns against sections that merely repeat or summarise other sections. If a finding does not support a recommendation, it probably belongs in the report, not the summary.
5. Add the practicalities
In one sentence each, state budget, people, timing and risk. Then close on the request with an owner and a deadline.
6. Cut and simplify
The ECA says the summary should not reproduce detailed drafting of the report, use unnecessary jargon, copy the conclusions section, or carry headings, footnotes or references to the main report. Texas A&M adds that it should be original text, not pasted from the report.
A worked example
Here is a short summary for an internal proposal, written with the structure above. The figures are invented for illustration.
Recommendation: We recommend replacing the manual invoice-approval process with a single online workflow by 31 March, at a one-off cost of £18,000.
Why it matters: Approvals currently take an average of 11 working days, which delays supplier payments and puts our early-payment discounts at risk.
Evidence: A six-week pilot in the procurement team cut average approval time to four days. Errors fell from 9% of invoices to 3%. The saving in staff time is equivalent to one part-time role.
Risks: Training will take two days per user, and the pilot team was small, so results across finance may differ. We will review progress at 90 days.
Action required: The finance director is asked to approve the budget at the February meeting so that procurement can begin rollout in March.
Notice what it does. The first sentence states what, when and how much. Each section is short. The risks sit in plain view, not buried. A reader who stops after 60 words still knows the ask.
The template at theexecutivesummary.com uses a similar five-part shape: headline, why it matters, evidence, risks and trade-offs, and action required, across 250 to 500 words. It advises front-loading bad news in the risk section, which builds trust with a sceptical reader.

Writing a summary for a case study or exam exercise
If you are writing under timed conditions, such as a written case study in a selection process, the principles hold but the clock changes the tactics. You will not have the luxury of finishing the analysis and then polishing. Decide your recommendation early, write the body to support it, and leave a few minutes at the end to compose a summary that matches what you actually wrote.
Keep the structure rigid: problem in one or two sentences, recommendation, two or three supporting arguments, conclusion. A marker or reader often looks at the summary first, so a clear one signals clear thinking. Also remember your role. Whether you are an internal adviser or an external consultant changes the voice you use.

Editing checklist
Once the draft exists, read it as the busy reader would.
- Stand-alone test: can someone who has not read the report act on it?
- Consistency: does every number match the report, in the same units and rounding?
- Single mention: is each point made only once?
- Plain language: have you removed jargon and acronyms the reader may not know?
- Linkage: does every recommendation trace back to a finding?
- Action: is it clear who must do what, and by when?
The ECA suggests asking a colleague outside the project team to read it and question anything that is not immediately clear. It also suggests drafting in a different language from the report, which forces simpler wording. If you do not work across languages, you can get a similar effect by explaining the point aloud to someone unfamiliar with it, then writing what you said.
The NZIER brief offers another habit: spend half your time cracking the problem before you open the template, and use a whiteboard with colleagues to test the main ideas. A summary is only as clear as the thinking behind it.
Can AI write an executive summary?
It can produce a usable first draft, quickly. It cannot take responsibility for the content. The Corporate Finance Institute’s guide says AI helps you draft and structure summaries, but you own the analysis and the final judgement. It also lists the main risks: confident but wrong statements, lost nuance, and generic corporate wording.
To use it well:
- Feed it your conclusions, not raw data. Give it the findings and recommendation you have already decided on.
- Tell it the reader and the format. For example: “one page, for a finance director, recommendation first.”
- Check every figure against the source document. The same guide calls this manual check non-negotiable.
- Restore what was flattened. Add back caveats, risks and the reasons behind your recommendation.
- Rewrite the vague lines in your own voice, and delete anything that is not in the report.
If you are writing for an assessment, check the rules first. Many selection processes expect you to produce the work yourself, under timed conditions, with no tools at all.
Perspective
Most people who struggle with an executive summary do not have a writing problem. They have a decision problem. They have not yet settled what they think the reader should do, so the summary wanders through everything they know.
In our coaching, we see the same pattern in written case studies for EU competitions. Candidates under time pressure spend almost all their minutes on analysis and leave a thin, rushed conclusion. The fix is to commit to a recommendation early, then write every paragraph to serve it. That is also what makes a summary persuasive: it sounds like someone who has made up their mind and can defend it.
We also teach candidates to perform, not recite. A memorised template reads as a template. A candidate who understands why a recommendation follows from the facts can adapt to any case, any role and any jury or marker. That is the approach we take with our clients, on written tests as well as presentations and interviews, and it is why our coaching centres on original, authentic answers and not polished scripts.
the author
Getting help with written case studies
If you are preparing for an EU internal competition, the written case study is where a clear summary and a firm recommendation count most. At Concours Coach, we offer tailored coaching on written case studies, presentations and interviews, led by Neil Urquhart, who has trained over 450 clients.

Our Case Study Reviews x2 Upgrade lets you get your written work looked at. For practising under pressure with others, there is the Written Test Hackathon live online workshop. Our monthly case study plans start at $47 per month for Basic Case Study, with PRO Case study at $97 per month and Ultimate Case study at $147 per month. You can see everything we offer on the Concours Coach site.
FAQ
What is the difference between an executive summary and an introduction?
An introduction opens the report and prepares the reader for the detail. An executive summary replaces the detail for readers who will not read it, so it includes findings and recommendations. If your summary only describes what the report covers, it is an introduction.
Should I write the executive summary first or last?
Last is the safer choice. The European Court of Auditors and Vertex42 both advise writing it once the main text is complete. If you draft one early to shape your thinking, revise it at the end so it matches what the report actually says.
How long should an executive summary be?
Usually one page, and rarely more than two. Texas A&M suggests about 5% of the report, while Carnegie Mellon allows up to 10%. Harvard Kennedy School caps its version at 1,000 words.
Can I use bullet points?
Yes, where they make findings or actions easier to scan, as in the template and worked example above. Keep the opening recommendation as a full sentence, and make sure each bullet is a complete, specific point. Check your organisation’s style guide, as some bodies prefer continuous prose.
Can ChatGPT write an executive summary for me?
It can draft one from your conclusions, but it can invent or distort figures and flatten nuance. Treat the output as a rough draft, verify every number, and rewrite it so it reflects your own reasoning.
Sources
- How to Write an Executive Summary, Harvard Kennedy School
- How to Write a Great Executive Summary, Grammarly
- Executive Summaries, Carnegie Mellon University
- Executive summary, NLR Communication Standards
- Executive Summary Writing Guide, IEA-EBC
- Assignment Types: Reports, University of Newcastle
- Case Study Report, University of Guelph
- Executive Summary Template, theexecutivesummary.com
- Guide for Writing Executive Summaries, US GAO
- Executive Summaries, Texas A&M University Writing Center
- Executive Summary Template for Word, Vertex42
- Executive summary, European Court of Auditors
- Policy advice, NZIER
- How to write an executive summary, Microsoft Word Blog
- Using AI for Executive Summaries, Corporate Finance Institute
