How to Write an Executive Summary for a Report, with an Example

This fictional example summarizes an operational report about a four-week service desk trial. The full teaching report appears below so you can compare the brief with its source.

The service desk's four-week trial assessed a revised arrangement combining a response template with six additional staffed hours per week. The share of requests receiving a first response within two business days rose from 80 of 100 requests (80%) in the preceding period to 108 of 120 (90%) during the trial, a rise of 10 percentage points.

The result supports further evaluation, but the comparison cannot isolate the template's effect from extra staffing or differences in request complexity. It also does not establish faster resolution, better answer quality or higher satisfaction, which were not measured.

The report recommends a further four-week trial, subject to approval for the additional staffing hours. The service desk lead would add complexity, resolution and quality checks before a decision on permanent adoption.

The opening establishes the period, intervention and measured outcome. Keeping the counts beside the percentages makes the comparison easier to interpret: the two periods had different request volumes.

The middle paragraph preserves the uncertainty relevant to adoption. “Responses improved” would be vague because the report measures the timing of first responses. “The template improved service quality” would introduce both an unsupported cause and an unmeasured outcome.

The final paragraph attributes the recommendation to the report and keeps approval separate from action already taken. It does not turn a proposed continuation into a confirmed staffing commitment.

The summary omits daily scheduling detail and the calculation of total additional hours because neither is needed to understand its immediate decision. Those details remain available in the source report below.

Use five elements as a starting structure:

- Purpose: the problem or question the report addresses. - Scope: what was examined, over what period and with what boundaries. - Main findings: the results that matter to the reader's decision. - Conclusion and limits: what the results support and what remains uncertain. - Recommendation or requested decision: the action proposed in the report, if there is one.

Monash University's business-report guidance identifies purpose, work performed, main findings, conclusions and recommendations as core elements. It also advises writing the executive summary after the report. Follow your organization's or assignment's requirements where they specify a different structure.

Do not add a recommendation merely to fill a heading. Some reports inform a decision without recommending an action. If the report leaves a question open, make that visible.

Before drafting, finish this sentence: “After reading this summary, the reader needs to decide whether to…” For an operational trial, that might mean continuing the trial, requesting more evidence or changing the proposed rollout.

Use the decision to choose relevant findings. A report may contain useful details about daily operations that do not change the requested decision. Retain those in the full report and give the summary space to explain the evidence that does matter.

Identify the audience as well. A team leader may need responsibility and timing; a steering group may also need unresolved resource requirements. Avoid assuming that every reader knows the project's abbreviations.

The following Service Desk Response Trial Report is the original fictional source for the example. Its five sections let you check the summary's figures, conclusions and proposed next step.

The service desk ran a four-week trial to examine whether a revised working arrangement could improve the share of requests receiving a first response within two business days. It compared trial totals with the immediately preceding four weeks. The periods contained different requests; they were not matched by complexity.

During the trial, the team used a new response template and added six staffed desk hours each week. Both changes began together. The additional hours totalled 24 across the trial.

In the preceding period, 80 of 100 requests received a first response within two business days. During the trial, 108 of 120 did. These figures measure first response, not resolution. The report did not measure answer quality or user satisfaction.

The first-response rate rose from 80% to 90%, while request volume also rose. The comparison does not isolate the effect of the template from the extra staffing, and differences in request complexity could affect the result. It does not establish whether the arrangement would perform the same way over a longer period.

The report recommends another four-week trial before permanent adoption. The service desk lead would track request complexity, time to resolution and a defined quality check alongside first-response time. Continuation requires approval for the extra six staffed hours each week; no permanent staffing change has been approved.

Use the prompts below to draft a connected summary. Replace the fields with information your report actually supplies. Purpose and scope [Report name] examines [problem or decision] using [scope, period or method].

Main findings The most important finding is [result, with units and comparison]. [Second finding] matters because [supported implication for the decision].

Conclusion and limits The report concludes [conclusion]. This is limited by [material uncertainty, missing measurement or condition].

Recommendation or requested decision The report recommends [action, if supplied]. [Named role] would [next step], subject to [approval or dependency actually stated in the report].

Keep evidence locations in your working notes beside each statement. When preparing the final version, follow the required report style for citations and references; retain the checking notes even if they do not appear in the summary itself.

For each figure, confirm the quantity, unit, population and period. In the example, 90% is a share of trial requests, not a share of users or completed cases. Six additional hours per week becomes 24 over four weeks, not six hours for the whole trial.

The change from 80% to 90% is 10 percentage points. The relative increase in that rate is 12.5%, calculated as (90 − 80) ÷ 80. Use the expression that answers the task and label it clearly; “a 10% improvement” would obscure which comparison you mean.

Check recommendations with the same care. A role mentioned as a proposed owner has not necessarily accepted the work, and a request for approval is not an approved plan.

Use the required length and the complexity of the decision. A short operational report may need only a few paragraphs. A larger report may require more space to cover several findings and their implications.

Monash's business-report guidance describes a usual limit of one page in its context. Treat that as contextual guidance rather than a rule for every organization. Avoid expanding a straightforward report to fill a page or deleting material limitations to meet an assumed percentage.

KnowledgePilot's document analysis workflow lets you work from a document and ask focused questions about its content. A suggested request is:

Draft an executive summary for a reader deciding whether to continue this trial. Include the report's purpose, measured findings, material limitations and stated recommendation. Keep first response separate from resolution, and do not add approvals, owners or outcomes the report does not supply.

Compare the draft with your evidence notes. Use citation-bearing answers to inspect supporting passages, then edit the executive brief for the reader. Keep any new proposal you develop separate from the report's own recommendation until it has been assessed and added to the report.

An introduction sets up the report's question, context and scope. An executive summary also gives the principal findings, conclusion and any recommendation, so a reader can understand the report's outcome.

Yes, when the report supports them. Preserve the status of each action, including dependencies or approvals. Do not introduce a recommendation that the report never evaluates.

Use the conclusion as one input, then add the purpose, scope and evidence needed to understand it. A conclusion copied alone may assume knowledge that a reader of the summary does not have.

Headings help when several findings or decisions need to be distinguished. A short brief can use connected paragraphs. Choose the format required by your reader or organization.