An executive summary is not a short version of the full document. It is a standalone communication that should allow a senior reader to understand the situation, the recommendation, and the reasoning — without reading anything else.
Most executive summaries fail this test. They summarise what the document covers rather than what the reader needs to know. They bury the recommendation in the middle or omit it entirely. They lead with context and methodology when the reader wants conclusions.
For non-native English speakers, there's an additional layer: the conventions of written business English that shape what reads as confident versus uncertain, clear versus evasive, and decisive versus still-working-it-out. This post covers both.
What Senior Readers Are Looking For
Senior professionals — executives, board members, investors — read with a different goal than the author who wrote the document. The author is presenting work. The senior reader is trying to make a decision, or to understand whether they need to be involved, or to assess whether the situation is under control.
The three questions every executive summary must answer:
- What is the situation? (one or two sentences — the fact or context that creates the need for this document)
- What do you recommend? (one specific, clear recommendation or conclusion — not a range of options)
- Why? (the key evidence or reasoning — compact, not exhaustive)
The executive summary should answer all three in the first quarter of its length, not at the end. Senior readers will often stop reading after the first few paragraphs. If your recommendation appears on page two of a two-page summary, it won't always be seen.
| Common structure (wrong) | Effective structure |
|---|---|
| Background → context → analysis → options → recommendation | Recommendation → supporting evidence → context → implications |
| Passive, tentative language throughout | Declarative, owned language |
| Equally treats all findings | Foregrounds the most important finding |
| Ends with next steps as an afterthought | Ends with a clear, owned proposed action |
The Language of Declarative Writing
The most common written English problem for non-native speakers in executive documents is hedging — using language that qualifies every claim to the point of meaninglessness.
Over-hedged (avoid): "It appears that there may be some challenges that could potentially be contributing to the issues observed, which might suggest that some consideration of an alternative approach could be warranted."
Declarative (aim for): "The root cause is inadequate customer onboarding. The fix is a revised onboarding sequence."
Declarative writing is not arrogant. It is accurate and efficient. Senior readers interpret excessive hedging as one of two things: either the writer lacks confidence in their analysis, or the analysis is incomplete. Neither is the impression you want to create.
The shift from passive to active voice is part of this:
- Passive: "A decision was reached to proceed with the acquisition."
- Active: "We decided to proceed with the acquisition."
Active voice assigns ownership. In executive communication, ownership signals confidence and accountability.
Language patterns for declarative executive writing:
- "The data shows..." (not "the data seems to suggest that it might...")
- "We recommend X." (not "one option that could be considered would be X")
- "The risk is Y." (not "there may be some risk associated with Y")
- "This failed because..." (not "there were a number of contributing factors that may have played a role in the outcome")
Structuring the Body of a Report
An executive summary sits at the front of a longer document. The document itself has different structural requirements — but the same underlying principle applies: lead with what matters, support it with evidence, and don't make the reader find the conclusion.
Effective report structure:
- Executive summary (standalone, recommendation first)
- Background (only the context that is genuinely needed)
- Findings (organised by importance, not by chronology or process)
- Recommendation (specific, with clear rationale — even if it also appeared in the summary)
- Risks and mitigations (brief; the serious risks, not a comprehensive list)
- Next steps (who, what, by when)
The most common structural error: organising findings by the process that produced them (we surveyed customers, then we interviewed internal stakeholders, then we reviewed competitors) rather than by what matters. The reader does not need to follow your research journey. They need to follow your argument.
Writing for a Non-Native English Writing Standard
Written English produced by non-native speakers sometimes has tell-tale patterns that, while grammatically acceptable, read as slightly off to a senior English-language audience. The most common:
Over-formal connective phrases. "Furthermore," "in addition to the above," "it should be noted that," "it is worth mentioning" — these constructions are technically correct but make documents sound formal to the point of being stiff. In modern business English, plain connectives work better: "Also," "Beyond this," "Worth noting."
Noun-heavy sentences. "The implementation of a revised structure for the process of customer onboarding would represent an improvement in the overall quality of the experience." This construction is common in languages with different structural norms. The cleaner version: "Revising the onboarding structure would improve customer experience."
Overly complex sentence structure. Subordinate clauses multiplied across a long sentence. In written business English, short sentences are not a sign of low sophistication — they are a sign of clear thinking. If a sentence is hard to read in a single pass, it's too complex.
Misplaced emphasis. The most important word in a sentence often belongs at the end: "The problem is not the strategy — it's the execution." Compare with: "The execution is the problem, not the strategy." The first lands harder.
The Standard Business Report: Sentence and Paragraph Length
A practical benchmark for business report language:
- Average sentence length: 15–20 words. Sentences longer than 30 words are almost always improvable.
- Paragraph length: 3–5 sentences for body paragraphs. One sentence is acceptable for emphasis. More than six sentences starts to lose readers.
- Formatting cues: bullet points for parallel items; numbered lists for sequences or priorities; bold for genuinely important terms or phrases (not decorative use).
The test for any piece of written business English: can a senior reader who has fifteen seconds for this paragraph understand the key point? If not, revise until they can.
Writing Recommendations That Get Approved
A recommendation in a business document is not just a statement of what you think should happen. It is a persuasive act: you are asking a senior person to agree, commit, or act. The language structure of the recommendation affects whether it lands.
A weak recommendation: "We believe it may be worth exploring the option of bringing in an external consultant to review the current situation."
A strong recommendation: "We recommend appointing an external consultant to conduct a four-week review of the current process. Our preferred supplier is [X]; scope and cost are in Appendix B."
The strong version: uses "recommend" explicitly, names a specific action, gives a timeline, and points to more detail without requiring the reader to wade through it. It respects the reader's time and makes it easy to say yes.
Frequently Asked Questions
How long should an executive summary actually be?
One page maximum for a document of up to twenty pages; two pages for a very complex document. The length of the executive summary is not a function of the length of the document — it's a function of what the reader needs. If you can't summarise the situation and recommendation in one page, the summary needs more editing, not more length.
My reports tend to include a lot of qualifications because I don't want to overstate. How do I balance accuracy with decisiveness?
There's a difference between intellectual honesty and linguistic hedging. You can be precise about your confidence level without making every sentence tentative: "We're confident about the cost figures; the timeline is an estimate and could move by 2–3 weeks" is honest and clear. What you want to avoid is hedging every statement equally regardless of how confident you are, which makes it impossible for the reader to calibrate risk.
Is there a meaningful difference between UK and US business English in formal writing?
Yes, some. UK business English tends toward slightly more formal register; US business English tends toward shorter sentences and earlier conclusions. In practice, the international standard for executive communications is closer to the US model — direct, brief, front-loaded. If you're writing for a mixed audience, defaulting to directness and brevity will serve you well in either context.
How do I handle a situation where the conclusion I've reached is one my audience won't like?
Lead with the conclusion anyway. Delaying bad news until the reader has read the full context is a common impulse and almost always the wrong call. Senior readers who discover mid-way through a document that things are worse than expected feel manipulated. The frame that works: "The situation is [X — bad news]. Here is what we know, and here is what we recommend." The directness builds trust even when the news is difficult.
If any of this resonates, I run weekly sessions with founders and senior professionals on exactly this kind of thing. Free 10 minute fit call to see if it's a fit. Book here.