A business one-pager is a short document — usually a single page or two — that communicates a situation, recommendation, or proposal clearly enough for a busy reader to act on it. It might be an executive summary, a project proposal, a strategy brief, or a product overview.
The challenge for anyone writing one-pagers in their second language is that the document is short enough that every awkward phrase is visible, and formal enough that the standard for natural English is higher than in casual email. A grammar checker will not catch the patterns that make a one-pager "read as translated" to a native English professional.
This article gives a systematic checklist of the patterns to look for, with before/after examples for each.
The Checklist
1. Noun-Heavy vs Verb-Driven Sentences
One-pagers that read as translated often use noun phrases where native English writers would use verbs. This is partly first-language transfer — many languages nominalise more readily than English — and partly a misunderstanding that formal English means more nouns.
Before: "The utilisation of this approach will result in the achievement of cost reductions and an improvement in efficiency."
After: "This approach reduces costs and improves efficiency."
Count the nouns in your key sentences. If you can convert noun phrases to verbs, do it.
2. Passive Voice in Action Statements
Recommendations and proposed actions should be in active voice. Passive voice makes it unclear who is responsible for what.
Before: "It is recommended that the process be reviewed and that improvements be implemented."
After: "We recommend reviewing the process and implementing the following improvements."
3. Vague Quantifiers
"Some," "many," "various," "a number of," and "several" are weak in a business document. Where possible, use specific numbers or replace with something concrete.
Before: "Various stakeholders have expressed concerns about the current process."
After: "Three of the five department heads have flagged concerns about the approval process."
If you genuinely do not have specific numbers, "multiple stakeholders" or naming them specifically is stronger than "various."
4. The Buried Action
In a translated or first-language-influenced one-pager, the recommended action or decision often appears in the last paragraph. English professional writing expects the main point — what you need the reader to do — to appear early.
Before: [Long background section] [Long analysis section] "In conclusion, we therefore recommend that the board approve the proposed budget."
After: "We recommend the board approve the $X budget for Project Y. [Background and analysis follow to support this recommendation.]"
5. False Connectors
Words like "moreover," "furthermore," "in addition," "additionally," and "consequently" come from formal academic writing and appear frequently in professional documents written by people who learned English in an academic context. They are not wrong, but overuse makes a document sound like a translated academic paper.
Replace with shorter transitions or restructure:
- "Moreover, this approach provides..." → "It also provides..."
- "Consequently, we recommend..." → "We therefore recommend..." or just state the recommendation.
- "Furthermore, the data shows..." → "The data also shows..."
6. Inappropriate Certainty Language
Writers sometimes overuse certainty language — "it is clear that," "obviously," "undoubtedly" — when the conclusion is actually contested or depends on the reader's judgement. This can read as presumptuous.
Before: "It is clear that the current approach is inefficient."
After: "The current approach has three specific inefficiencies:" [followed by the list]
Show the evidence. Let the reader draw the conclusion.
7. Heading Style
Headings in business one-pagers should be direct and informative, not chapter-title style.
Before: "Analysis of Current State and Identification of Gaps"
After: "Current State: Three Key Gaps"
Use the heading to tell the reader what they will find in the section. They can then decide whether to read it.
8. The Abstract Opener
Many one-pagers open with a paragraph that establishes abstract context — the importance of the topic in general terms — before getting to the specific situation. Business readers find this padding.
Before: "In today's rapidly changing business environment, organisations must continually adapt their processes to remain competitive. Digital transformation has become a key priority for businesses across all sectors..."
After: "Our order fulfilment process currently takes 12 days from receipt to dispatch. Industry standard is 5–7 days."
Start with the specific situation, not the general context.
9. Consistent Tense and Voice in Recommendations
The recommendation section of a one-pager should use consistent grammatical structure. Mixing imperative, passive, and nominalisations in the same list looks fragmented.
Before:
- "Review of the process to be completed by June."
- "The team should implement the new system."
- "Stakeholder communication plan."
After:
- "Review the process by June."
- "Implement the new system."
- "Communicate the change to stakeholders."
Parallel structure. Active verb. Clear ownership.
10. Sign-off and Next Steps
A one-pager should end with a clear statement of what happens next and who is responsible.
Before: "We look forward to further discussion of these matters."
After: "We will present this proposal at the 2 May leadership meeting. Decision needed by 15 May to meet the Q2 implementation window."
Applying the Checklist Before You Send
Run the checklist after you have finished a first draft — not while writing. Editing mode and writing mode use different mental processes, and trying to apply these rules mid-draft usually produces stilted text.
A practical sequence: write the draft freely, then do a single read-through focused only on the list above. Mark any instances. Revise in one pass. For a one-pager, this process should take less than ten minutes once you have internalised the patterns.
If you find you are making the same errors repeatedly — noun-heavy sentences, abstract openers, passive-voice recommendations — those are first-language transfer patterns worth tracking. The same fixes will appear across all your one-pagers until the English-native pattern becomes more automatic.
How Local Tone Handles This
One-pager mode in Local Tone applies the above checklist systematically. The analysis flags noun-heavy sentences, passive-voice recommendations, and abstract openers — and provides rewrites that move the document toward the direct, verb-driven style that works in English business contexts. The accompanying notes explain the specific pattern for each suggested change.
For related reading, see the review cycle: writing feedback a native reader won't rephrase and how to escalate politely in English.
Quick Reference: Translated-English Tell-Signs
| Original phrasing | How a native reader interprets it | Improved version |
|---|---|---|
| "The utilisation of this approach will result in the achievement of cost reductions." | Overly nominalised; reads like a translated academic document | "This approach reduces costs." |
| "Various stakeholders have expressed concerns." | Vague; no specificity; sounds like padding | "Three department heads have flagged concerns about the approval process." |
| "Moreover, it is clear that the current situation is unsustainable." | Academic connector + presumptuous certainty | "The current situation has two specific unsustainable elements:" |
| "In today's rapidly changing business environment..." | Abstract opener; business readers skip this paragraph | Start with the specific situation: costs, timelines, or figures |
| "It is recommended that improvements be implemented." | Passive voice; unclear who owns the action | "We recommend implementing the following three improvements." |
| "We look forward to further discussion of these matters." | Vague sign-off; no next step, no owner, no date | "We will present this at the 2 May meeting. Decision needed by 15 May." |
In Practice
Mei-Ling is a strategy consultant originally from Taiwan, working for a management consultancy in Sydney. She has been asked to prepare a one-pager for a board member summarising a cost-reduction initiative. Her first draft opens: "In the current global business landscape, organisations face significant pressures to optimise their operational costs. It is therefore of paramount importance that the utilisation of resources be examined with a view to identifying inefficiencies and achieving improvements in overall performance." Her senior partner reads it and asks her to tighten it. Mei-Ling runs through the checklist: abstract opener, nominalised verbs, vague language, no specific figures in the first paragraph. She rewrites the opener as: "Our procurement costs increased 18% last year while revenue grew 4%. This paper outlines three changes that would reduce procurement spend by $1.2M annually." She converts the recommendations from passive nominalisations to active imperatives. The final document is half the length and twice as clear. The board member responds with a one-line approval request within the hour.
How to Self-Check Before You Send
- Read your opening paragraph and ask: does it contain a specific number, a named situation, or a concrete recommendation? If it is all abstract context, cut it and start with the specific.
- Search for the words "moreover," "furthermore," "additionally," and "consequently" — if any appear more than once, replace or remove the extras.
- Highlight every sentence in your recommendation section: each one should begin with an active verb ("Review," "Implement," "Approve") rather than a noun phrase or passive construction.
- Check the final paragraph: does it contain a specific next step, a named person or team responsible, and a date? If not, add all three.
- Read each sentence in your key argument and replace every noun that can be a verb — "utilisation of" becomes "using," "achievement of" becomes "achieving," "improvement in" becomes "improves."
- Find every vague quantifier (some, many, various, several, a number of) and replace with a specific number or remove it; if you genuinely cannot be specific, use the most concrete phrasing available.
Frequently Asked Questions
Why do business one-pagers reveal translated-English patterns more than emails do?
In email, the format itself provides structure — a greeting, a context line, a request, a sign-off. Readers have expectations for each part and fill in gaps naturally. A one-pager has no such scaffolding. The writer has to build the argument from scratch, and the document is short enough that every sentence is under scrutiny. When the structure comes from a non-English writing tradition — topic-comment organisation, background-before-recommendation sequencing, heavy nominalisation for formality — it is visible in a way that it might not be in a routine email. This is why a one-pager is a useful diagnostic: it shows your baseline phrasing and structural habits clearly.
I have been writing business documents in English for years. Why is my one-pager still being rewritten by native-speaker colleagues?
The patterns that make a document read as translated are not grammar errors. They pass every spell check and grammar check. The issue is typically structural (buried action, abstract opener), lexical (nominalisations, vague quantifiers), or stylistic (academic connectors, passive recommendations). These patterns are deeply embedded — they reflect how business writing is taught and modelled in many non-English educational systems. The checklist in this article is designed to make those patterns visible. Running through it systematically on a completed draft, rather than trying to write "in English style" during composition, is more effective because it separates the two cognitive tasks.
How important is it to put the recommendation first? My industry expects a background section before the recommendation.
The sequence matters less than the density. If your industry or organisation expects background before recommendation, provide it — but keep the background section short and factual (two to three sentences maximum), and make sure those sentences contain specific details, not abstract framing. The pattern to avoid is a long background section that re-establishes general context a reader already knows. Get to the specific situation quickly, even if the formal recommendation comes later. A reader who knows what decision they will be asked to make is more engaged with the background that supports it.