Drafting and Structure
Executive Summary Builder
Condense a longer report into decision-relevant findings, implications, evidence, uncertainty, tradeoffs, risks, options, and required leadership actions.
Free editable Markdown · Analysts, executive communications teams, and program managers ·
Accessible HTML preview
Blank template
The downloaded file contains the same fields in editable Markdown.
Summary purpose
- Source report and version
- [Enter]
- Evidence cutoff and scope
- [Enter]
- Executive audience
- [Name/role]
- Decision or awareness needed
- [Enter]
- Decision authority
- [Describe]
- Deadline and reason
- [Enter]
- One-sentence situation
- [Write]
Finding card
Duplicate for each decision-relevant finding.
- Finding
- [State directly]
- Source section and evidence
- [Reference]
- Observation versus interpretation
- [Label]
- Magnitude, denominator, and period
- [Enter]
- Implication for the decision
- [Explain]
- Limitation or uncertainty
- [State]
- Counterevidence or dissent
- [Enter or None]
- Confidence
- [High / Medium / Low and why]
Options and recommendation
- Option
- [Enter]
- Expected benefit
- [Evidence]
- Cost and effort
- [Enter]
- Dependencies
- [List]
- Risk and affected groups
- [Describe]
- Reversibility
- [High / Medium / Low]
- Recommendation
- [Choose or state none]
- Reason
- [Connect to findings and tradeoffs]
Action and verification
- Decision requested
- [Write exactly]
- Decision owner
- [Name/role]
- Immediate next action
- [Enter]
- Action owner and deadline
- [Enter]
- Review or stop condition
- [Enter]
- Reviewers and version
- [Names/date]
- Summary statements trace to the final report.
- Material limitations and disagreement remain visible.
- A fresh reader identified the intended decision correctly.
How to use this template
- Define the audience, decision, authority, deadline, source report, and evidence cutoff.
- Select only findings that change the decision, recording their evidence and limitations.
- Distinguish observations, interpretations, options, recommendations, and unresolved uncertainty.
- State tradeoffs, risks, requested action, owner, deadline, and review condition.
- Compare the summary with the final report and test comprehension with a fresh reader.
Identify the decision before selecting details
State who will read the summary, what authority they have, which decision or awareness it supports, and when action is needed. Then list the few findings that materially change that decision. Do not summarize every section in equal proportion; explain what leaders need to know to understand the recommendation, risk, and tradeoff. If no decision is requested, state the purpose as information, escalation, or alignment. Name the report period, scope, and evidence cutoff so the summary cannot be mistaken for a timeless or comprehensive assessment.
Preserve evidence, uncertainty, and disagreement
For each headline finding, record the source section, evidence strength, metric or observation, and key limitation. Separate observed facts, interpretation, forecast, and recommendation. Use absolute numbers and denominators when percentages could mislead, and keep ranges or confidence statements meaningful. Include important counterevidence, unresolved disagreement, and who was not represented. Leaders should not need to open the full report to discover that the result applies only to one market, that data is incomplete, or that a recommended option creates a serious operational risk.
Make action and ownership explicit
Present realistic options, including delay or further research when appropriate. State benefits, costs, dependencies, reversibility, and risks under comparable assumptions. Finish with the requested decision, owner, deadline, immediate next step, and review condition. Link to the full report, evidence, and appendices for traceability. Ask a subject reviewer to compare the summary with the source and an uninvolved leader to explain what decision they think is requested. If those answers differ, revise the summary rather than adding more jargon.
See the fields in context
Fictional example: help-center migration decision
The company, costs, traffic, and migration below are invented and should not inform a real investment.
- Decision: Whether to pilot an imaginary help-center migration for one product area.
- Finding: Fictional support feedback shows navigation failures in that area, but the sample excludes mobile users.
- Options: Maintain, run a limited pilot, or migrate all content; the summary compares cost and reversibility.
- Recommendation: Pilot 20 articles with a mobile research step, not a full migration.
- Action: An imaginary program owner approves scope by August 15 and reviews task completion after six weeks.
Frequently asked questions
How long should an executive summary be?
As short as possible while preserving decision, evidence, implications, material risks, options, and requested action. Complexity, not a universal page count, should determine length.
Should the recommendation appear first?
Often, if the reader needs a decision quickly, but include enough immediate context and clearly distinguish it from established findings.
Can the summary introduce new evidence?
No. Add important evidence to the source report first so reviewers can trace and evaluate it.
What if there is no clear recommendation?
State the uncertainty, options, and evidence needed for the next decision rather than manufacturing confidence.