Worked example library

Executive Summary Examples: Report to Decision Summary

Start with the worked examples to see complete reasoning, then use the shorter pattern library for variation. Level guidance and frameworks show how the same task changes as the evidence, audience, or assignment becomes more demanding.

Guide Examples 15 Templates

Before you copy

What to notice in the examples

A strong executive summary stands on its own, leads with the main conclusion rather than background, preserves the source document’s important qualifications, and makes recommended actions or decisions easy to locate.

Open with purpose and the main finding or recommendation.
Summarize the few facts that materially support that conclusion.
State implications, risks, or tradeoffs that affect the decision.
End with the requested action, decision, or next step when applicable.

Worked format lab

See complete reasoning, not just isolated lines

Use these fuller examples to see what changes between a recognizable pattern and a finished piece of writing. The examples are original or explicitly illustrative, so they demonstrate structure without inventing real-world evidence.

Worked example 1Complete executive summary

Illustrative customer-support process report.

This report recommends replacing the current free-text support handoff with three required fields: current owner, transfer reason, and next-response date. In a four-week illustrative review, 31% of transferred cases required a clarification message before work resumed, compared with 12% among cases already using a structured handoff.

The comparison is directional rather than causal because adoption was not randomized and case complexity differed across teams. The operational risk is therefore not that the current process is proven to cause delay, but that important transfer information is inconsistently visible.

A six-week pilot can test the change with limited implementation cost. Success should be evaluated using clarification messages, response delay, reopen rate, and staff feedback.

Decision requested: approve the pilot, assign an operations owner, and review results after six weeks before any company-wide rollout.

Why it works: The summary stands alone, preserves the evidence limitation, and ends with the exact decision required.

Worked example 2Long report opening → executive summary

Illustrative transformation.

Weak: This report was commissioned in May and contains five sections. Section one describes the history of the process. Section two presents survey results. Section three discusses options...

Stronger: Recommendation: retire the duplicate intake form and move its two required fields into the existing request workflow. The duplicate form adds an estimated 4–6 minutes per request and does not supply information used in approval. The main implementation risk is migration of 83 open requests. A two-week parallel run can validate the new workflow before the old form is disabled. Approval is needed by 18 September to complete the change this quarter.

Why it works: The rewrite summarizes the decision, evidence, risk, implementation approach, and ask instead of describing the report’s table of contents.

Prompt → finished structure

See the decisions between the assignment and the final form

These transformations make the hidden planning step visible so the template does not become a fill-in-the-blanks substitute for judgment.

Transformation 140-page report → one-page decision summary

Starting material: Source includes background, method, five findings, appendices, and three recommendations.

Decisions
Start from the decision the reader must make. Keep only findings that materially affect that decision, preserve the strongest qualification, synthesize recommendations into a prioritized action, and point detailed evidence back to the report.

Result: Finished structure: decision context → conclusion → decisive evidence → material risk → recommendation → ask.

Transformation 2Table of contents → executive summary

Starting material: Draft says what each report section contains.

Decisions
Replace section descriptions with actual findings and implications. A reader needs the result, not a map of where the result is located.

Result: Finished structure: bottom line → evidence → tradeoff → next action.

Depth by level

Increase the reasoning, not just the word count

Level	What changes	Quality test
One-page management summary	Lead with the conclusion or recommendation, preserve the few decisive facts and the main risk, and state the decision needed.	The reader should understand the bottom line without opening the full report.
Proposal / business case summary	Compress problem, recommended approach, economics, timing, risk, and approval into a coherent decision narrative.	Do not turn the summary into a table of contents.
Research / audit / technical summary	Preserve scope, methodology boundary, strongest finding, qualification, and implication without introducing claims absent from the source.	Compression must not erase uncertainty or provenance.

Reusable frameworks

Start from the decisions the format requires

Framework 1

Observation → function
1. What can the viewpoint actually perceive?
2. Which 1–2 details matter now?
3. What do those details change in image, pace, relationship, or action?
4. What interpretation remains uncertain?

Framework 2

Generic → specific revision
Generic line: [x]
Observable evidence: [x]
Context/constraint: [x]
Unnecessary inference removed: [x]
Revised line: [x]

Recommendation: Consolidate the two onboarding flows into one role-based path. Support data shows that 38% of setup tickets come from choosing the wrong account type in step two.

Finding: The pilot reduced average handling time by 14% without increasing reopen rates. Expansion should wait until the two unresolved permission defects are fixed.

Proposal summary: The project requires six weeks and two engineering teams; the main schedule risk is external data access.

Incident summary: Service was unavailable for 47 minutes after a certificate renewal failed. Traffic has been restored, and certificate monitoring is being changed.

Research summary: Across four studies, retrieval practice improved delayed recall more consistently than rereading, though effects varied by test format.

Budget summary: The revised plan stays within annual budget by delaying the office move and protecting customer-support hiring.

Audit summary: Three control gaps were found; one is high priority because it affects privileged-account termination.

Market summary: Demand is strongest among existing enterprise customers, but the current onboarding model makes smaller accounts expensive to serve.

A useful executive summary for a pilot does not recount every test; it states the result, confidence/limitations, recommendation, cost, and decision needed.

When the full report contains mixed results, the executive summary should preserve that qualification rather than presenting the preferred metric alone.

The pilot reduced manual review time by 31% but increased exception handling for complex accounts; we recommend expanding only to the two standard account types while redesigning the exception workflow.

Decision summary: recommend delaying the rollout by one week because two unresolved permission defects can expose customer data; quantify affected scope and name the exact go/no-go check.

Proposal summary: state the business problem, recommended approach, expected cost and duration, the main implementation risk, and the approval required without repeating the proposal section by section.

Research summary: state the question, strongest finding, evidence boundary, and practical implication while preserving uncertainty that would disappear in a promotional summary.

Audit summary: lead with the highest-risk control gap, distinguish confirmed findings from observations, and list owners and deadlines for corrective action.

Turn an example into your own writing

Keep the underlying decision or pattern, then replace the subject, evidence, relationship, constraints, and tone with details that belong to your situation. If your final line still works after swapping only one noun, it may be too close to the example.

What to notice in the examples

See complete reasoning, not just isolated lines

See the decisions between the assignment and the final form

Increase the reasoning, not just the word count

Start from the decisions the format requires

Related writing guides