High-stakes business documents
The executive summary that gets read
Many readers of a report will only ever read its executive summary. We look at how to write one that sets out your case and gives the reader what they need to make a decision.
Many people who open a report read the executive summary and stop there. That’s often true of board members working through a stack of papers before a meeting, and of managers who commissioned the work and want to know what to do next. They may only turn to the body of the report if something in the summary sends them there. For readers like these, the summary has to make the whole case by itself.
Writing a good summary is a different job from writing the report. The summaries we see tend to go wrong in the same few ways, and many of the fixes have more to do with structure than wording.
Summarize what you found
A common problem is a summary that describes the report instead of its findings: “This report examines… Section 2 sets out… Section 3 considers…” This gives the reader a table of contents but nothing to act on. An executive summary should set out your findings and what they mean, and then say what should happen next. Someone who read only the summary and then had to make the decision right away should have what they need.
To test it, give the summary on its own to someone who hasn’t seen the report. If they can tell you the recommendation and the main reason for it, the summary is doing its job.
Put the conclusion first
Reports are usually written in the order the work was done: background, method, findings, and conclusion. A busy reader needs the reverse, starting with the conclusion, ideally in the first sentence, followed by the reasons in order of importance. Background belongs at the end, if it’s needed at all. Often it isn’t, since the person who commissioned the work already knows why it was done.
Many authors find this uncomfortable because they want the reader to follow the reasoning before reaching the result. A decision-maker usually wants the result first, and can then choose how much of the reasoning to read.
Write for the person who has to act
A summary that isn’t written for anyone in particular tends to drift toward the author’s peers, with plenty of method and caveats and little about consequences. Decide who has to act on the report and write the summary as a briefing for that person. Think about the decision they need to make, what they need to know to make it, and the questions their own managers or board will ask them. Answering those produces a very different summary from an account of what the team did.
Make each recommendation something to say yes or no to
“The organization should consider strengthening its approach to supplier risk” doesn’t tell anyone what to do. A useful recommendation names who should do what, by when, and what needs to be agreed first, so that the reader can approve it or turn it down.
Include the figures the decision depends on
A summary without figures can read as vague, while one that repeats every figure in the report buries the ones that matter. Pick the few numbers the decision rests on, state them plainly with their source, and leave the rest in the body. If a figure is uncertain, flag that in the summary, since anyone who acts on it will need to know.
Keep it short and complete
The right length depends on the reader. For a board or a senior executive, aim for a single page; a technical audience may accept two. A summary is complete when it covers the decision and the reasoning behind your recommendation, even if it skips some sections of the report. It’s easiest to write the summary last, from the finished report, and then cut anything the decision doesn’t depend on.
Make sure it can stand alone
Summaries are often forwarded without the report or read on a phone, so they can’t rely on anything outside themselves. Spell out every acronym, and avoid references such as “the table below” or “as discussed in Section 4”. Every point in the summary should make sense to someone who hasn’t seen the rest of the report.
Where we can help
Summaries are often written by the report’s author in the last hour before the deadline. After weeks inside the document, it’s hard for an author to see which findings a newcomer would need explained, or that the summary describes the report instead of what it found. We read the summary as your decision-maker will. Restructuring it so that it leads with the findings and speaks to that reader is a focused piece of developmental editing.
Report nearly ready?
Send us the draft and tell us who has to act on it, and we’ll agree the scope with you before quoting.
Get a quote