An executive summary is not an introduction. It is the document.
This distinction matters because of how policy audiences actually read. A minister preparing for a committee session, a senior adviser briefing a delegation, or a department head reviewing incoming publications does not read reports in sequence from cover to cover. They read the executive summary. If it works, they may read further. If it does not, the rest of the document is irrelevant.
Most executive summaries we edit fail on this test. They are written as introductions: setting up context, situating the organization that produced the report, explaining what the document will cover. This is not what a policy reader needs. It is what the author needs in order to feel confident that the reader has been properly oriented. The reader's needs are different.
What a policy reader needs from an executive summary
A policymaker or senior official reading your executive summary is asking four questions, usually in this order:
- What is the problem? Not the broad topic — the specific problem that this document addresses.
- What do you conclude? Your finding, position, or central argument — stated plainly, not hedged.
- What do you want me to do? The recommendation, directed at the right actor.
- Why should I believe you? The one or two most compelling pieces of evidence.
An executive summary that answers these four questions in under one page has done its job. Most executive summaries we receive bury questions two and three in the final paragraph, after extended treatment of question four and a lengthy answer to a question that was not asked.
The structure of a working executive summary
The most effective structure for a policy-facing executive summary is direct and front-loaded. It does not mirror the structure of the full report. It presents the argument in the order that serves the reader, not the order in which the research was conducted.
A workable structure looks like this:
Paragraph one: the problem and its significance. Two to three sentences. What is happening, why it matters, and what is at stake if it is not addressed. This is not background or context — it is the specific problem that this report addresses.
Paragraph two: the central finding or position. One to two sentences. What your research shows, or what position your analysis supports. This should be as direct as the evidence allows. "Our analysis finds that the current subsidy structure is regressive and benefits the top income quintile disproportionately" is a finding. "The report examines questions of subsidy incidence and equity" is not.
Paragraph three: the recommendations. Two to four bullet points, each directed at a specific actor. "The Ministry of Finance should revise the eligibility criteria for the subsidy scheme by [date]." Each recommendation should be specific enough to act on and attributed to the right body.
Paragraph four: the evidential basis. Two to three sentences on the research basis for the conclusions. This is where you mention the methodology — briefly — so that the reader knows the recommendations are grounded in evidence rather than assertion.
Target length: One page for reports up to 30,000 words. Two pages for major reports. Three pages only for book-length documents intended for senior decision-makers who will read no further. If your executive summary is longer than this, it is trying to do the work of the full document — which means the full document is not doing it.
Common mistakes
Leading with context rather than the problem
The opening sentence of an executive summary should state the problem, not the context. "India's energy transition is proceeding at an uneven pace" is context. "At current investment rates, India will miss its 2030 renewable energy targets by an estimated 35%" is a problem. The first sentence tells the reader something they probably already know. The second gives them a reason to read on.
Treating recommendations as conclusions
Recommendations and conclusions are different things. A conclusion is what the evidence shows. A recommendation is what someone should do about it. Many executive summaries conflate the two, producing a final section that reads like a conclusion ("It is clear that significant reform is needed...") rather than a recommendation ("The Planning Commission should convene a working group to review the regulatory framework within six months").
Recommendations should be specific, attributed, and time-bound where possible. Vague recommendations — "greater investment is needed," "more coordination is required" — are recommendations with no one responsible for acting on them. They will be noted and ignored.
Hedging certainty where the evidence is strong
Research culture values epistemic caution, and rightly so. But there is a significant difference between appropriate acknowledgement of uncertainty and systematic under-stating of what the evidence actually shows. If your data from four countries over ten years shows a consistent relationship, writing that "there appears to be a possible association" does not accurately represent your findings — it represents a habit of caution that is obscuring what you actually know.
An executive summary should state conclusions at the level of confidence the evidence supports. Where uncertainty is genuine, say so. Where it is not, do not manufacture it.
Writing for the researcher, not the reader
Executive summaries often contain terminology that is meaningful to the researchers who produced them and opaque to the policymakers who need to act on them. Technical terms, sector-specific acronyms, and references to methodological debates are appropriate in the full report. They are rarely appropriate in the executive summary, unless your specific audience is expert in the subject — in which case, the summary can reflect that.
The test is always: does the target reader know what this means? If not, either define the term or replace it with language that does not require definition.
Writing the executive summary last, but editing it first
A practical note on process: the executive summary should almost always be written last, after the full document is complete and the argument is clear. Writing it first produces a summary of what you intend to argue rather than what you actually concluded. The most common reason executive summaries diverge from the report they summarize is that one was written before the other was finished.
Once written, however, the executive summary should be the first section to be reviewed and edited — ideally by someone who has not read the full document. If that reader cannot reconstruct the argument, the recommendation, and the key evidence from the summary alone, it is not yet working.
If you are working on a report or policy brief and the executive summary is giving you difficulty, our structural editing service frequently starts exactly here — reviewing the summary against the full document and identifying the gap between what the document concludes and what the summary communicates.