The Biggest Writing Mistakes Government Organisations Still Make
Government writing often becomes long, passive and unclear because it is produced around internal processes rather than the needs of the reader. Here is what to change.
Most poor writing in government is not caused by poor writers.
It is caused by people trying to satisfy too many purposes, reviewers and organisational anxieties in a single document. The result is writing that is technically accurate but difficult to use.
The same mistakes appear across briefings, reports, guidance and emails. They persist because they are reinforced by how work is commissioned, cleared and rewarded.
Improving them requires more than a list of grammatical rules. It requires a clearer idea of what writing is supposed to achieve.
Mistake one: writing for completeness rather than action
A document often begins as an attempt to support a decision. As it moves through the organisation, more background, evidence and qualification are added. Each addition is reasonable. The final product contains everything except a clear sense of what the reader should do.
Completeness feels safe because it reduces the risk that somebody will accuse the writer of missing information. But the reader carries the cost. They must identify which facts matter and how they relate to the central issue.
The correction is not to remove evidence indiscriminately. It is to organise information around purpose.
What decision, action or understanding is required? Which information materially supports it? What can sit in an annex, link or separate technical document?
A document should be complete for its purpose, not complete in the abstract.
Mistake two: hiding the main point
Government writers frequently build towards a conclusion. The first pages describe history and context before the recommendation finally appears.
This mirrors the writer’s process of discovery. It does not serve a senior reader who needs to understand the destination before assessing the route.
Lead with the main point. State the recommendation, issue or required action early. Then provide the evidence and reasoning needed to test it.
This principle applies beyond formal submissions. The first sentence of an email should often explain why the recipient is receiving it. Guidance should tell users what they need to do before describing the policy history. Reports should surface the finding before documenting the methodology in detail.
Clarity is created through sequence as much as sentence style.
Mistake three: using passive language to avoid ownership
Phrases such as “it has been decided”, “work will be undertaken” and “consideration is being given” appear neutral. They often conceal who is responsible.
Passive voice is not always wrong. It can be useful when the action matters more than the actor or when the actor is genuinely unknown. The problem is habitual passivity.
Unclear ownership creates operational risk. Who decided? Who will complete the action? Who is considering the issue, and when will they conclude?
Active language forces the organisation to answer these questions. “The programme board agreed” and “the policy team will provide advice by Friday” are easier to act upon and easier to hold accountable.
Mistake four: confusing jargon with precision
Every profession needs technical language. Legal, analytical, commercial and policy terms can communicate precise meanings efficiently among specialists.
Jargon becomes a problem when it is used with audiences who do not share that meaning, or when vague organisational language replaces thought.
Words such as “strategic”, “transformational”, “robust”, “holistic” and “stakeholder-led” may sound positive while saying little about what will change. Acronyms allow insiders to read quickly but create friction for partners and new colleagues.
The test is not whether a term is common inside the organisation. It is whether the intended reader will understand it consistently.
Plain language respects the complexity of the subject by making it accessible. It does not reduce professional standards.
Mistake five: treating the template as the argument
Templates can improve consistency and ensure important issues are considered. They can also produce documents in which sections are completed because they exist, not because they help the reader.
Writers fill a background section, an options section and a risk section even when the real logic would be clearer in a different order. Repeated information appears under several headings. The document becomes compliant but not persuasive.
A template should support thinking, not replace it.
Teams should understand which elements are mandatory and where flexibility is permitted. Organisations should review templates that routinely generate long, repetitive documents. If writers constantly work around the structure, the structure may be wrong.
Mistake six: failing to distinguish fact, analysis and recommendation
Weak documents blur different types of statement.
A piece of evidence is presented beside an interpretation without signalling the change. A likely outcome is described as certain. A recommendation appears as though it follows automatically from the data when it also contains a judgement about risk or priorities.
Readers need to know which is which.
Phrases such as “the data shows”, “we assess” and “we recommend” can help when used honestly. Uncertainty should be described proportionately. Where evidence is contested or incomplete, explain why the recommended course remains reasonable.
This distinction strengthens advice because it makes the writer’s reasoning visible.
Mistake seven: editing only at the end
Writing is often treated as a production task. The team completes the analysis, drafts the document and allows a short period for clearance. Editing becomes a final check for errors.
But editing is where much of the thinking becomes clear.
When a writer tries to reduce three pages to one, they must decide what matters. When they rewrite a vague recommendation, they may discover that the team has not agreed on the action. When they test guidance with users, they expose ambiguities that subject experts no longer notice.
Editing should therefore happen throughout development. An early outline can test logic before prose is produced. A quick reader review can reveal missing context. Time should be protected for a genuine second draft.
Mistake eight: writing for the reviewers rather than the reader
Documents often accumulate language designed to satisfy internal clearance. A paragraph is retained because one team insisted on it. A caveat is repeated because a senior reviewer might ask. The final reader receives the history of organisational negotiation.
Reviewers have legitimate responsibilities, but they should assess whether the document serves its purpose, not use it to preserve every internal position.
Clear commissioning helps. Who is the final audience? Which reviewers are essential? What is each one checking? Who has authority to resolve conflicting comments?
Without these answers, drafting becomes an exercise in consensus and the document loses its centre.
Better writing requires better leadership
Individuals can improve their writing through practice and feedback. Organisations must also remove the conditions that produce weak documents.
Leaders should model concise communication, make clear decisions about purpose and avoid rewarding length as evidence of seriousness. They should give specific feedback: not “make this punchier”, but “the recommendation is unclear because the action and owner are missing”.
Writing training is most effective when it uses real organisational products and connects language to decisions, behaviour and outcomes. The aim is not to make every employee sound the same. It is to help people communicate complex work in a form others can use.
The biggest writing mistake is forgetting that writing is an interaction. The document succeeds only when the reader understands, decides or acts as intended.