The Hidden Cost of Poor Writing in Government
Unclear writing creates meetings, delays and weak decisions. Better public sector writing begins with audience, purpose and the action the reader needs to take.
Every unclear piece of writing creates work for somebody else.
A vague email produces a meeting. A long submission hides the decision. Guidance written around the organisation rather than the reader creates queries, inconsistency and complaints. A report that does not distinguish evidence from recommendation leaves senior leaders uncertain about what they are being asked to do.
None of these failures looks dramatic in isolation. Together, they consume thousands of hours across the public sector.
Poor writing is therefore not merely a communications problem. It is an operational cost.
Writing is part of delivery
Government and public bodies depend heavily on written communication. Policy is converted into legislation, guidance, instructions, correspondence, briefings and public information. Programmes are governed through papers and reports. Ministers and senior leaders often encounter months of work through a document they have minutes to read.
The quality of that writing affects the quality of the decision.
When a document is unclear, the reader must reconstruct the writer’s thinking. They have to work out which facts matter, what the recommendation is and why the issue has reached them now. Busy readers may not have the time or context to do this accurately. The result can be delay, an avoidable challenge or a decision made on a different understanding from the one the writer intended.
Clear writing is not cosmetic work applied after the analysis. It is the final stage of analysis.
The problem often begins before the first sentence
Many writing courses focus on grammar, sentence length and active voice. These are useful, but they do not address the most common cause of weak writing: the writer has not decided what the document is for.
Before drafting, three questions matter.
Who is the audience? What do they need to understand or decide? What should happen after they have read it?
These questions sound basic. Yet much public sector writing is created without clear answers. A paper accumulates information because several contributors want their material included. The writer aims for completeness rather than effect. Sections follow the history of the work rather than the logic needed by the reader.
The document may be accurate and still fail.
In training work with public sector organisations, including commercial professionals at the Crown Prosecution Service, I have repeatedly returned to the relationship between audience, purpose and outcome. When those three elements are clear, many other decisions become easier. The writer knows what to include, what to remove and where to place the main message.
Completeness is not the same as clarity
Government culture often rewards evidence that work has been done. Writers therefore include extensive background, describe every stage of a process and preserve technical detail in case it is needed later.
This can feel safe. Removing information creates anxiety because the omitted fact might become important. Yet excessive detail creates its own risk. It makes the document harder to navigate and increases the chance that the central issue will be missed.
Good writing does not discard complexity. It organises it.
A senior reader may need a clear recommendation and the two or three facts that determine it, with supporting analysis available below or in an annex. A frontline colleague may need a sequence of actions, examples and a clear explanation of where judgement is permitted. A member of the public may need plain language, reassurance and a route to further help.
The same information should not be presented in the same way to all three.
Weak writing creates organisational drag
The costs of poor writing spread beyond the immediate reader.
Unclear commissioning leads teams to produce the wrong work. Ambiguous responsibilities create duplication. Passive language hides ownership. Long emails encourage partial reading and inconsistent interpretation. Guidance that has not been tested with users generates repeated questions to central teams.
This is organisational drag: effort that is consumed without moving the work forward.
The effect is particularly serious in large systems. A confusing instruction sent to ten people is inconvenient. The same instruction embedded in national guidance can create thousands of inconsistent decisions.
Clarity therefore has a multiplier effect. A small improvement at the centre can save substantial time throughout the system.
Writing for decisions
Ministerial and senior-level writing requires a particular discipline. The reader usually needs the conclusion early. They need to understand what is being recommended, why, what the alternatives are and what could go wrong.
Writers sometimes delay the recommendation because they want to build the argument first. This mirrors how the analysis was conducted, but it does not match how the document will be read. A busy decision-maker is likely to scan for the central question and then examine the evidence that matters to it.
Recommendation-first writing is not simplistic. It allows the reader to understand the relevance of the detail that follows.
The strongest briefings also distinguish clearly between fact, interpretation and judgement. Phrases such as “the evidence shows” should be used carefully. Sometimes the evidence suggests a likely effect but cannot settle the choice. Advice is more credible when it acknowledges uncertainty rather than using confident language to conceal it.
Plain language is a form of respect
Jargon is often defended as necessary precision. Sometimes it is. Technical terms can carry meanings that would take several sentences to reproduce.
But jargon also becomes a habit. Organisations develop internal language that feels obvious to those inside and impenetrable to everyone else. Acronyms compress communication for regular users while excluding newcomers and external partners.
Plain language is not the removal of expertise. It is the ability to express expertise in a form the audience can use.
This matters morally as well as operationally. Public bodies exercise authority, distribute resources and explain rights and obligations. People should not need insider knowledge to understand what government is asking them to do.
Better writing is a shared responsibility
Writing quality cannot be improved only by correcting individuals. Organisational processes shape the documents people produce.
If every paper must satisfy multiple reviewers with different preferences, the final version will often become longer and less direct. If leaders reward exhaustive detail but complain about length, writers receive conflicting signals. If deadlines leave no time for editing, the first complete draft becomes the final product.
Leaders can improve writing by commissioning clearly, limiting unnecessary clearance, modelling concise communication and protecting time for revision. Teams can use templates that reflect the reader’s needs rather than the organisation’s internal structure. Documents can be tested with representative users before publication.
Most importantly, editing should be treated as thinking, not tidying. The act of removing a paragraph forces the writer to decide whether it is necessary. Reordering sections reveals the logic of the argument. Rewriting a recommendation exposes ambiguity that was previously hidden inside complex language.
Clarity creates capacity
Public services face genuine capacity constraints. Recruiting more people or buying more support may sometimes be necessary. But organisations should also examine how much existing capacity is being absorbed by preventable confusion.
Better writing will not solve every problem. It will, however, reduce the number of meetings needed to explain documents, the time spent clarifying instructions and the risk that important decisions are misunderstood.
Every clear sentence gives time back to the reader. Across an organisation, that time becomes capacity.