How to Write a Summary of Findings Your Client Will Actually Read

Write a summary of findings by leading with the answer to the client’s decision, not the process that produced it. State what you found, what it means, and what should happen next, in that order, on one page. The full report exists to defend those claims. The summary exists to be read.

This is for consultants and internal advisers who have finished the analysis and now have to compress it. It covers what goes in the summary, how long it should be, how to cut a long report down without stripping out the evidence trail, and when a slide beats a page.

How to write a summary of findings report?

Write the summary last, but write it as though it were the only document. Every step below removes something the reader does not need in order to act.

1. Decide which decision the summary serves. Almost every commissioned review exists because someone has to choose: invest or stop, restructure or leave alone, fix in-house or buy. Name that decision before you write a word. If you cannot name it, ask the sponsor, because the alternative is a summary that is interesting to nobody in particular.
2. Write the headline finding as a sentence with a verb. “Handover between sales and delivery” is a topic. “Handover between sales and delivery fails because nobody owns the account after signature” is a finding. Topics fill contents pages; findings change minds.
3. Group the rest into three to five findings. More than five and the reader stops ranking them. If you genuinely have eleven, some of them are symptoms of the others and belong underneath, not alongside.
4. Attach the evidence to each finding in one clause. “Nine of fourteen interviewees described the same delay” or “four of the last six projects overran at the same stage”. Specific counts survive challenge. Adjectives do not.
5. Separate what it means from what you recommend. The implication is what follows from the evidence. The recommendation is what you think should be done about it, which is a judgement the client may reject while still accepting the finding. Keeping the two apart is what lets a client disagree with you without discarding the analysis, and it is worth reading the boundary between findings and recommendations properly before you draft either.
6. State what happens next. Two or three actions, with an owner against each if you have that far. A summary that ends at diagnosis invites the client to invent their own treatment.
7. Put the method at the bottom, in two lines. What you looked at, over what period, with what access. Enough for a sceptical reader to weigh the evidence. No more.

If your opening line is “This report presents the findings of a review commissioned in March”, you have spent your best sentence on a date.

How long should a summary of findings be?

One page. For a report over fifty pages, two. In words that is roughly 250 to 600, which is far shorter than most consultants first draft and about right for the way the document is actually consumed, which is standing up, on a phone, ten minutes before a meeting.

Length is set by the decision, not by the report. A ninety-page technical review that resolves into a single yes or no still gets one page. A shorter review covering four independent workstreams may need two, because the reader has four decisions to make and cannot take them as a set.

The useful test is not word count. It is whether a director who reads only the summary can defend the conclusion in a meeting you are not in. If they would have to say “the consultants looked into it and they think we should”, the summary has failed regardless of its length.

Is a summary of findings the same as an executive summary?

Not quite, though the two are used interchangeably often enough that you should check which one a client means. An executive summary summarises the whole document, including scope, approach, findings and recommendations. A summary of findings covers only what you found and what it implies.

In practice the distinction matters most on regulated or evidence-heavy work, where the findings need to be readable on their own without the recommendations attached to them. An audit committee may want the findings circulated to one group and the recommendations discussed by another. If that is your situation, write the summary of findings so it stands alone, then let the executive summary wrap it with scope and next steps.

For ordinary consulting work, most clients say “executive summary” and mean “the page I will read”. Write that page well and the terminology argument disappears.

How do you compress a long report without losing the evidence trail?

Keep the pointer, drop the working. Every claim in the summary should be traceable to a section of the report, and the cheapest way to preserve that is a bracketed reference after each finding: “(section 3.2)”. The reader who wants proof can find it in seconds, and you have not spent a paragraph explaining where it came from.

Beyond that, the compression is mostly deletion of a few reliable categories:

• The project narrative. What you did in week two is of no interest. The report can carry it; the summary cannot afford it.
• Balanced framing. “There are strengths as well as areas for development” is a sentence that survives every draft and informs nobody. If the strengths matter, name one specifically. If they do not, cut them.
• Quotations. One short quotation can carry a finding. Three turn the summary into evidence rather than conclusion.
• Caveats that apply to everything. Sample limitations, access constraints and time boxes go in the method line at the bottom, once, not attached to each finding.
• Anything that only makes sense if you read the report first. This is the defect a colleague who did not write the report will catch and you will not.

What survives is claim, count, implication, action. If a sentence is none of those, it is describing the work rather than the answer, and it belongs in the body of the findings report instead.

Should you write it as a page or a slide?

Match the format to how the summary will first be encountered, not to how you like writing. Most engagements need two versions of the same content, and the mistake is producing one and hoping it works everywhere.

Format	Use when	Rough length	What goes wrong
One-page written summary	The report is circulated for reading, or the decision is taken without you present	250 to 600 words	Written as prose paragraphs, so nothing is scannable
Summary slides	You are presenting, and discussion will follow each finding	3 to 5 slides, one finding each	Bullet fragments that do not make sense once the slide is forwarded on
Email summary	The client asked for the short version before the report is finished	150 words, findings only	Becomes the version everyone quotes, before it has been checked

The email version is the one to be careful with. A summary sent early to be helpful has a habit of being pasted into a board pack, where it will be read as your considered position. If you send one, say plainly that it is provisional and give the date the full report lands.

If you are building the slide version, the structure of a findings presentation differs from the structure of a written summary in ways worth planning for before you start cutting.

What makes a summary of findings unreadable

Four failures account for most of them, and all four are easier to fix in the summary than anywhere else in the report.

• Findings that are activities. “We interviewed 14 staff and reviewed 30 documents” tells the reader what you were paid to do, not what you learned.
• Hedging on every claim. “There may be some indication that handovers could be improved” is a sentence written to survive review, not to be acted on. If the evidence is thin, say the evidence is thin and state the finding anyway.
• No numbers. “Widespread concern about resourcing” is unfalsifiable. “Nine of fourteen interviewees raised the same resourcing problem, unprompted” is a fact a client can act on or dispute.
• Recommendations with no owner. The most common ending to a good summary is a list of sensible actions belonging to nobody, which is how a report ends up cited approvingly for two years and implemented never.

That last one is a fifteen-minute conversation, held before the summary goes out, with the people who will actually do the work. Projan handles that conversation inside Microsoft Teams or Slack, pressing each recommendation for a named owner, a date and a test that would show it had happened, and writing the agreed list into Asana or Notion. However you run it, hold it while the client’s attention is still on the report.

Frequently asked questions

What to write in a summary of findings? Five things a reader can check: the headline finding stated as a claim, three to five supporting findings, the evidence behind each one in a clause, what the findings imply for the client, and what happens next. Anything that describes the project rather than the organisation belongs in the report, not the summary.

How do you write the summary of your findings? Draft it twice. Write a rough version before you finish the analysis, as a hypothesis you are trying to disprove, because it exposes which evidence you still lack. Then rewrite it from scratch once the report is complete, working from the finished findings rather than editing the earlier draft down.

Should a summary of findings include recommendations? Usually yes, kept short and clearly separated from the findings themselves. A summary that states problems and stops leaves the client to invent their own response, which is rarely the one you would have chosen. Two or three lines of recommendation is enough; the reasoning stays in the report.

Does a summary of findings need a methodology note? One or two lines, placed at the end rather than the beginning. State what you looked at and over what period, in enough detail that a sceptical reader can judge the weight of the evidence. Anything longer belongs in an appendix. Method at the top pushes the finding below the fold.

Who should review the summary before the client sees it? Someone on your team who did not write the report. They will spot claims that only make sense if you already know the evidence, which is the most common defect in a summary written by the analyst. If the engagement has a sponsor who is not the day-to-day contact, test the summary against their decision too.

A summary that could be true of any organisation in the sector is not a summary, it is a genre. Write it so the first sentence would be wrong about a different client, put a number behind every claim, and let the report do the arguing.