Content Design for Public Sector Websites: Writing for Everyone

Public sector websites exist to serve people. That sounds obvious, but the gap between what a council or NHS trust wants to publish and what a resident or patient actually needs is often wider than anyone expects. Content design closes that gap by putting user needs at the centre of every page, every form and every piece of guidance. For organisations looking to get this right, working with a team that understands digital services for public sector organisations makes a real difference to how content performs.

The discipline has its roots in the Government Digital Service (GDS), which set out to make GOV.UK the clearest, most usable government website in the world. That ambition has since filtered through to local authorities, NHS trusts, housing associations and arms-length bodies. Content design is now a recognised profession across the public sector, with its own frameworks, standards and career paths. But the principles behind it apply to any organisation that needs to communicate clearly with a broad audience.

What Content Design Actually Means

Content design is not copywriting with a new name. Copywriting starts with a message the organisation wants to communicate and works out how to phrase it. Content design starts with a user need and works out the best way to meet it. Sometimes that means writing clear prose. Other times it means building a calculator, creating a flowchart or removing content entirely because it was causing more confusion than it solved.

The GOV.UK content design guidance describes this as designing content rather than creating copy. The distinction matters because it shifts the starting point from “what do we want to say?” to “what does the user need to do?” A council tax page, for example, shouldn’t open with the history of council tax legislation. It should help someone pay their bill, apply for a reduction or understand what they owe. Everything else is secondary.

This user-first approach changes how teams think about every piece of web content. Pages are shaped around tasks and questions rather than departmental structures. Navigation follows the way people think about their lives, not the way an organisation chart is drawn.

Plain English as a Legal and Practical Requirement

Writing in plain English isn’t a stylistic choice for public sector websites. It’s a practical requirement rooted in the reality that government services need to reach the entire population. That includes people with low literacy, people reading in their second language, people who are stressed or unwell and people using assistive technology.

GDS recommends writing for a reading age of 9. That’s not about dumbing content down. It’s about removing unnecessary complexity so that information is as clear as possible for the widest audience. Short sentences, common words, active voice and a logical structure all contribute to this. A sentence like “You may be entitled to a discretionary housing payment if your Housing Benefit does not cover your rent” is clearer than “Applications for discretionary housing payments may be submitted by eligible claimants whose Housing Benefit entitlement is insufficient to meet their rental obligations.”

The pressure to write in complex, formal language often comes from internal stakeholders who believe plain English sounds unprofessional. It doesn’t. The best legal guidance, medical information and policy documents in the UK are written in plain English precisely because the consequences of misunderstanding them are so serious. Organisations that invest in strong content marketing understand that clear writing builds trust with every audience, not just public sector users.

Accessibility Is Not Optional

The Public Sector Bodies (Accessibility Regulations) 2018 require public sector websites to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. That’s a legal obligation, not a recommendation. It covers everything from colour contrast and heading structure to link text and alternative descriptions for images.

Content design sits at the heart of accessibility compliance. Poorly structured content, vague link text like “click here” and PDFs that haven’t been tagged for screen readers all create barriers for people with disabilities. The accessibility regulations make it clear that publishing inaccessible content is not just poor practice. It’s a failure to meet a legal duty.

Accessibility is a content design issue as much as a technical one. Getting the HTML right matters, but so does writing descriptive headings, using meaningful link text and structuring pages so that screen reader users can find what they need without reading every word on the page.

Councils and NHS trusts that treat accessibility as a separate workstream often struggle to maintain compliance over time. When content designers build accessibility into their process from the start, it becomes part of how the team works rather than an afterthought. Priority Pixels works with organisations on website accessibility to make sure that technical compliance and content quality go hand in hand.

The GOV.UK Service Standard and Style Guide

GDS publishes two resources that shape content design across the public sector. The GOV.UK style guide covers everything from abbreviations to years, giving content designers a consistent reference for how to write. The service standard sets out the broader expectations for digital services, including research, testing and iteration.

Not every public sector body is required to follow the GOV.UK style guide. Central government departments must, but councils, NHS trusts and other organisations are free to create their own. Many choose to adopt the GOV.UK guide as a starting point because the underlying principles are sound. Writing dates as “15 January 2026” rather than “15/01/2026,” spelling out acronyms on first use and avoiding jargon wherever possible are all conventions that make content more accessible regardless of the organisation publishing it.

Where organisations deviate from the GOV.UK guide, they should do so deliberately and document their decisions. A local authority might choose to use “council tax” in lower case throughout because that’s how residents search for it, even though the formal name is capitalised. That’s a defensible content design decision. What doesn’t work is having no guide at all and leaving every author to make their own choices, because the result is inconsistency that confuses users.

How Content Design Differs from Traditional Web Content

Traditional web content often starts with a blank page and a brief from a subject matter expert. Content design starts with research. What are people searching for? Where are they getting stuck? What tasks are they trying to complete? The answers to those questions determine what content gets created, how it’s structured and what format it takes.

The differences are practical, not theoretical.

A well-designed content piece might remove half the words from an existing page and still provide a better experience. Cutting content that doesn’t serve a user need is one of the hardest parts of the job, particularly when stakeholders are attached to text they’ve spent weeks writing. Content designers need the confidence to make those decisions and the evidence to back them up.

Content Governance and Maintenance

Publishing is not the end of the content lifecycle. Public sector websites accumulate pages over years, sometimes decades. Without a governance process, content becomes outdated, duplicated and contradictory. A council might have three different pages explaining how to apply for a parking permit, each written by a different team at a different time, with none of them fully accurate.

Good content governance includes clear ownership of every page, scheduled review dates, a defined process for retiring content that’s no longer needed and training for anyone who publishes on the site. The GOV.UK accessibility blog regularly publishes insights on how government teams manage content over time. Many of those lessons apply directly to councils and NHS trusts.

• Assign a named content owner for every section of the website
• Set review dates at the point of publication, not as an afterthought
• Audit existing content before creating anything new
• Use analytics to identify pages that aren’t serving user needs
• Retire outdated pages rather than leaving them to collect dust

Without governance, even well-designed content degrades. Review cycles keep pages accurate, analytics reveal which pages are underperforming and user feedback highlights where content isn’t meeting expectations. The organisations that maintain high-quality websites over time are the ones with clear processes rather than the ones with the largest content teams.

Structuring Content Around User Tasks

Most people arrive at a public sector website with a specific task in mind. They want to report a missed bin collection, find out when their next council tax payment is due or check whether they’re eligible for a particular benefit. The website’s job is to get them to the right answer as quickly as possible.

That means structuring content around tasks rather than departments. A resident searching for “report a pothole” doesn’t care whether potholes fall under highways, infrastructure or environmental services. They care about getting the pothole fixed. The content structure should reflect that. When the web design and information architecture work together with content design, the result is a website where people can find what they need without understanding how the organisation works internally.

Task-based content also lends itself to better search performance. Pages that answer specific questions with clear headings tend to rank well in traditional search as well as AI-powered search tools. A page titled “Apply for a council tax reduction” will outperform one titled “Council tax: reductions, exemptions, discounts and appeals” because it matches the language real people use when they search. The W3C guidelines on writing for the web reinforce this principle, recommending that headings and labels describe the topic or purpose of the content they introduce.

Public sector organisations that invest in content design don’t just produce better pages. They build a way of working that puts the needs of residents, patients and service users ahead of internal politics and departmental preferences. That shift in mindset is what separates a website that works for everyone from one that works for the people who built it.