Government writing: communicating complex information with clarity and confidence

Early in my career, I sent a briefing note that took three pages to say what could have fit in three sentences. At the time, I was proud of it. It covered every policy clause, compliance angle and possible objection. My manager read it once and asked, “So what do you actually need me to decide?”

That question changed how I think about government writing.

In the public sector, we carry a particular kind of pressure. Our documents have to be accurate, defensible and compliant, often while explaining policy that’s genuinely complex. It’s tempting to think that the safest writing is the most detailed writing. In my experience, the opposite is usually true. Dense, jargon-heavy documents don’t protect us. They create confusion, slow down decisions and generate the very follow-up questions we were trying to avoid by including everything in the first place.

Let’s run through a few lessons I’ve learned that could help those tackling government writing.

Start with what the reader needs, not what you know

The biggest shift in my own writing came when I stopped asking “What do I need to explain?” and started asking “What does this reader need to know, do or decide?” A senior executive skimming a briefing on their phone has different needs from a case officer working through a procedural update, and both have different needs again from a member of the public reading a notice about a service change. Strong public communication starts with that audience question — not the policy detail.

Once I’m clear on what the reader needs, I write the key message first: the decision, the recommendation and the action required. Everything else supports that message rather than burying it. I learned to treat the inverted pyramid as a leadership habit, not just a journalism technique.

Plain English isn’t a compromise

For a long time, I worried that simplifying language meant sacrificing precision, particularly when writing about legislation or compliance obligations. What I’ve found is the reverse. Plain English forces real clarity. If I can’t explain a requirement in a straightforward sentence, it usually means I haven’t fully understood it myself yet, or I’m using technical language as a shield rather than a tool.

This doesn’t mean stripping out necessary detail. It means cutting the words that add length without adding meaning: “in relation to,” “in order to,” “for the purpose of,” “it should be noted that” and so on. Removing jargon doesn’t weaken accuracy. It usually exposes whether the accuracy was there to begin with.

Structure and formatting do real work

I used to think formatting was the finishing touch. Now I treat it as part of the message. Headings, bullet points and short paragraphs aren’t decoration; they let a time-poor reader find what matters in seconds. In briefing documents especially, I now lead with a short summary box: what this is, what’s being asked and what happens next. Everything below that is detail for those who need it, not a barrier everyone has to wade through first.

Tone matters just as much. Formal doesn’t have to mean distant. I write the way I’d want to be addressed if I were the reader: respectful, direct and human.

Testing before publishing

One habit I’ve built into my team’s process is asking a colleague outside the policy area to read a draft before it goes out, and tell me what they think it means. If they hesitate, or land on the wrong takeaway, I know the document isn’t ready, regardless of how technically correct it is.

Improving how we write in government isn’t about lowering standards. It’s about removing the friction between good policy and the people who need to understand it. That’s a leadership responsibility, not just a writing skill.

If you want to build these skills across your team, our Government Writing program is a practical place to start.