Public service UX awards: designing for everyone, including people who can't opt out
Government and public service design is judged on a harder standard, because nobody using it chose to. What editors look for: plain language, no dead ends, offline routes, and accessibility as law rather than ambition.
A public service has no competitors and no churn. If it's hard to use, nobody leaves — they fail, call a helpline, ask a relative, or give up on something they're entitled to. That makes it the one field where a design failure is a denial of access, and it's why public service entries are held to the standard they are.
1. Plain language, tested with the people who need it
Public-service copy has to survive being read by someone who is worried, in a hurry, reading in a second language, or reading with a cognitive disability — often all four. The entries that score well don't simply write plainly; they can show what they changed after watching someone read it.
| Compared on | Scores | Costs |
|---|---|---|
| Eligibility | You can apply if you're over 18 and live in the county. | Applicants must satisfy the residency criteria set out in section 4. |
| Documents | You'll need your passport or a birth certificate. | Supporting documentation as prescribed. |
| Timing | We'll reply within 10 working days. That's by 14 October. | Applications are processed in due course. |
| Refusal | We can't approve this because X. Here's how to appeal. | Your application was unsuccessful. |
2. No dead ends
The defining failure of government digital services is the dead end: a page that tells you that you can't proceed and offers nothing. Editors deliberately follow the unhappy paths — the edge case, the missing document, the unusual circumstance — to see what's at the end of them.
- Every refusal names a next step: an appeal, a phone number, a different service, or a person.
- Every "you need X" says how to get X.
- Every session that can expire warns first and keeps the answers.
- Every form that can't be finished today can be saved and resumed — with a code that doesn't require an account.
3. The offline route is part of the design
Digital-by-default is a policy, not a fact about the population. A well-designed public service knows what its non-digital path is, makes it easy to find, and doesn't treat using it as a failure. Entries that show the phone, post and in-person routes as designed parts of the same service — with the same information architecture and the same language — score noticeably higher on Service Experience.
4. Accessibility as a legal floor
In most jurisdictions, public-sector digital accessibility is legislated, with published conformance requirements and accessibility statements as a formal obligation. We read your statement, and notice the difference between a genuine one — which names specific failures, their impact and a fix date — and a template.
- 01
Test properly
Assistive technology, not only automated tools. Automated checks catch a minority of issues.
- 02
Publish honestly
Name the failures, their impact, and when each will be fixed.
- 03
Provide a route
A way to report a barrier that reaches a person who can act.
- 04
Close the loop
Track what was reported, and show what changed.
5. Trust: saying what happens to the data
Public services ask for a lot: income, health, immigration status, family circumstances. The design question is whether the person understands why each question is asked and what happens to the answer. Products that explain the purpose of a sensitive question inline — one short sentence, at the field — are consistently rated higher, and it costs nothing.
6. Performance on the devices people actually have
The users of a public service skew towards older devices, slower networks and metered data more than almost any other audience. A 4MB page is not neutral; it's a cost transferred to the person with least. Entries that budget their pages, work without JavaScript where they can, and degrade gracefully are doing distributive work, and editors treat it that way.
What to send
A live service or a realistic sandbox, the refusal path as well as the success path, your published accessibility statement, evidence of testing with people who use assistive technology or have low digital confidence, and the non-digital route.
One measured outcome is unusually available in this field: completion rate, calls to the helpline about a specific step, or the drop in applications needing correction. Those numbers are the argument for design in the public sector, so put them in the entry.
Public service entries usually go to Service Experience, almost always with Inclusive & Ethical Design. Entering is free, which matters more here than anywhere: a public body shouldn't have to spend public money to have its work assessed. Enter a service.
Designing the letter as well as the screen
Public services still run on letters, texts and emails, and those are part of the service design. A beautifully designed application form followed by an automated letter written in 1994 legalese is one experience, not two, and editors treat it that way.
- The same language in the letter as on the screen, with the same nouns.
- A reference the person can actually use, printed where they'll look for it.
- One clear next action, with a deadline in plain words.
- A route to a human that does not require another letter.
Assisted digital and the people who need help
A proportion of any public-service audience cannot complete a digital journey unaided — because of disability, literacy, language, confidence or circumstance. Designing the assisted route deliberately, rather than treating it as failure, is one of the clearest markers of maturity in a public-service entry.
- 01
Detect
Notice where people stall, rather than waiting for them to phone.
- 02
Offer
Help at that point, in that channel, without starting again.
- 03
Hand over
The helper sees what the person entered. Nobody repeats themselves.
- 04
Return
The digital record reflects what happened offline.
Open evidence
Public bodies are, unusually, often able to publish their research and performance data. Entries that link to a published user-research report, a performance dashboard or a service assessment are giving editors evidence that is unusually verifiable — and that is worth a great deal in scoring.
Questions we get asked
Can a government service be entered by its agency partner?
Yes, with the body's agreement, and credits must name both. We check with the named organisation before publishing.
Does entering cost public money?
Entry is free. If the work is recognized, publishing the profile costs $89 — and if that's a problem, tell us; we would rather the work were visible.
How are services judged when the policy behind them is poor?
On the design, in context. Editors know a service cannot fix its own legislation. What is scored is how well the design handled the constraint — and honest acknowledgement of the constraint in the case study helps.
What matters most in a public-sector entry?
Completion by people who find things hard, evidence that you tested with them, and no dead ends. Visual polish is the least important thing on the list.
Assessed work in public services
Chosen by score from the work the editors have assessed, not by hand.
- public sector
- government
- industry
Written by
The UXE editors
The team that selects the work, uses it, scores the seven criteria and writes every verdict on this site.
Keep reading
Craft & practice5 min read
Healthcare UX design awards: designing for people who are not at their best
What we look for in healthcare and care products: clarity under stress, clinical safety, accessibility as a baseline, and interfaces that work for carers, clinicians and patients at once.
The UXE editors
Accessibility6 min read
Accessibility scoring: exactly what editors check, in the order they check it
Accessibility is one of the seven criteria on every UXE entry, in every category. The tests editors run in the first ten minutes, what an honest conformance claim looks like, and why disclosed gaps raise a score.
The UXE editors
Craft & practice6 min read
UX writing that scores: the words editors actually notice
Interface copy decides how competent a product feels. The error messages, empty states, button labels and confirmations that raise a UX writing score — and the habits that quietly lower one.
The UXE editors