Client project · UK local government software
From training guides to a task-based help centre.
A UK software company makes the systems councils use to run elections, school appeals, casework and committees. I built the content foundation, the information architecture and the first help topics for its electoral management product, starting from the live system and a set of basic training guides.
The starting point
The guides followed the software. Users follow the job.
The existing training materials were organised by software module. That works for a training course, but not for an electoral officer who needs an answer mid-task, often against a statutory deadline.
- Not: How do I use Module 4?
- Not: Where is the Module 7 guidance?
- How do I add a new elector?
- How do I process a postal vote application?
- How do I start the annual canvass?
What we delivered
Five pieces of work, each one building on the last.
- 1Discovery assetsThe products, users and existing content, mapped.
- 2Content foundationPrinciples, voice and tone, and a style guide.
- 3Information architectureFour principles for how help is organised.
- 4Help centre structure16 sections, 300+ topics and a metadata model.
- 5Task-based topicsWritten from the training guides to GOV.UK standards.
Discovery assets
Before writing anything, I worked through the live system and the training guides to understand the products, who uses them and what content already existed. Everything that follows is built on that picture.
Content foundation
One reference for every content decision across all four of the company's products, from marketing copy to in-product error messages to automated GOV.UK Notify messages. It has three parts: content principles, voice and tone, and a style guide.
Five content principles
- 1Write for the person, not the productAn electoral officer under deadline pressure and an anxious parent checking a school appeal need completely different things.
- 2Plain English is not dumbed-down EnglishStatutory terms stay exactly as they are. The skill is giving enough context on first use.
- 3Earn trust with specifics, not reassurancesNumbers, names and outcomes do the work. Adjectives don't.
- 4Help belongs at the point of needDesign help around the moments people get stuck, not around the structure of the system.
- 5Human expertise sets the standard automation has to meetAn automated message about a child's school appeal has very human stakes. Get the words right.
Voice
Direct. Competent. Warm without being breezy. The brand speaks like the expert colleague who knows what they're doing and respects your time.
Tone, by context
| Context | Tone |
|---|---|
| Website and marketing | Confident, specific |
| In-product, for council users | Direct, task-focused |
| Citizen portals and Notify messages | Calm, plain, kind |
| Errors and system alerts | Honest, actionable |
| Onboarding and help | Patient, sequential |
| User group communications | Collaborative, collegial |
Before and after
Before: We are specialists in the development of cloud-based Local Government software, including School Appeals and Electoral Management Software systems. Get in touch today to see how we can help.
After: [Company] builds cloud tools for local government: elections, school appeals, casework, and committees. Used by [number] councils across the UK.
Before: Your appeal is being processed. You will be contacted in due course.
After: We have received your appeal. You will hear from us by [date]. If you have questions in the meantime, contact [name] at [council name].
Before: Something went wrong. Please try again.
After: The file could not be uploaded. Check the file is in .CSV format and under 10MB, then try again.
GOV.UK conventions for anything citizens read
Based on the GOV.UK style guide. Where it conflicts with anything else, GOV.UK wins for citizen-facing content.
- Reading age 9, up to 11 for statutory content. One idea per sentence.
- Active voice, always. "Submit your evidence by 12 June."
- Links describe the action, never "click here".
- Text messages: 160 characters, no links, and always the council's name.
- Every notification answers four questions: what has happened, what happens next, by when, and who to contact.
Statutory terms, handled precisely
| Term | Plain English context for help |
|---|---|
| Individual Electoral Registration (IER) | Each person registers individually rather than by household. |
| Annual canvass | The process councils run each year to check and update the electoral register. |
| Subject Access Request (SAR) | A legal right to ask what personal data an organisation holds. Councils must respond within one calendar month. |
| Freedom of Information (FOI) | A legal right to ask for information held by a public body. Councils must respond within 20 working days. |
Notes for each product
Built to be finished with the client
Version 0.1 was drafted ahead of discovery, with open questions marked for the client's team, including:
- The top support ticket themes and most common user questions
- Whether citizen-facing content falls under the public sector accessibility regulations for the company's council clients
- Who signs off the guide, and how often it's reviewed
Information architecture approach
Why the structure changed, and the four principles behind the new one, written so the client's team can explain and defend every decision.
Module 5 Processing Absent Votes Processing AV synchronised from the portal
Absent votes Process online applications
Add an elector. Start the annual canvass.
Customer services: find an elector, find a polling station.
"postal vote" returns every postal vote task.
Add an elector Electors module, Registration process.
| Principle | For users | For the business |
|---|---|---|
| Task-led | Faster completion of work | Less support demand |
| Role-aware | Relevant content | Better adoption |
| Search-first | Faster answers | More self-service |
| Module-supported | Consistent information | Easier maintenance |
No single principle is enough on its own. A module-only structure reflects the software, not the user's needs.
Help centre structure
The full contents for the help centre: 16 sections and 316 topics, from first login to count night, plus guides for each role and a metadata model.
- Home 5Welcome, find help, what's new, release notes, known issues
- Get started 19New to the product, Learn the interface, User management
- Daily tasks 59Search and enquiries, Electors and registrations
- Absent votes 25Overview, Process applications, Manage absent votes, Renewals and reviews, Fraud management, Reporting
- Properties and addresses 24Property management, Manage properties, Areas and polling districts, NLPG, Boundary reviews
- Annual canvass 41Annual canvass overview, Prepare for canvass, Run the canvass, Complete the canvass
- Elections 32Election planning, Election premises, Election staff, Candidate nominations, Election events, End of election
- Documents and communications 13Document templates, Communications, Production
- Scanning 15Getting started, Templates, Scanning, Troubleshooting
- Registers and publications 16Register management, Register publications, Register outputs, Registration documents
- Reporting and auditing 12Standard reports, Auditing, Exports
- Administration 19System settings, Security, Integrations, Local authority configuration
- Troubleshooting 9Registrations, Absent votes, Canvass, Elections, Documents, Scanning, Integrations, Performance issues, Common error messages
- Reference 15Glossary, Electoral terminology, Product terminology, Acronyms, Role guides, Legal and compliance
- Training 9Learning paths, Quick start guides
- Release notes 3Current release, Previous releases, Known issues
Guides for seven roles
- Electoral Services Manager
- Deputy Electoral Services Officer
- Senior Electoral Services Officer
- Electoral Registration Officer
- Temporary Electoral Staff
- Customer Services
- Read-only Users
Plus learning paths and quick start guides for a new starter's first day, first week, first election and first annual canvass.
A metadata model for every topic
| Field | Example |
|---|---|
| Product | Registrations |
| Area | Electors |
| User role | Customer Services |
| Topic type | Task |
| Process | Registration |
| Election cycle | Annual Canvass |
| Difficulty | Beginner |
| Version | 2026.1 |
So one topic can appear in several places without being duplicated.
Task-based help topics
Rewritten from the training guides to GOV.UK content standards and Minto's pyramid principle: the answer first, then the steps. The first set covers the 11 enquiries customer services staff handle most.
Check application status
Find out the current status of an elector's registration application.
Before you start
You must have permission to view elector and application information.
Check an application
- Search for the elector.
- Open the elector record.
- Review the application information.
The application status is displayed within the elector record.
- Received
- The application has been received and is awaiting processing.
- Verification in progress
- The application is being checked against the required verification services.
- Further information required
- Additional information is required before the application can be completed.
- Approved
- The application has been approved and will be added to the register according to the relevant publication timetable.
- Rejected
- The application was not approved.
- Deferred
- The application has been temporarily held for further review.
What to tell the elector
Explain the current application status and any action they need to take.
Don't confirm registration until the application has been approved and published.
You can now provide an update on the progress of the application.
Find a polling station
Find an elector's polling station and polling place information.
Before you start
You must be able to access elector records.
Find polling station information
- Search for the elector.
- Open the elector record.
- Locate the polling information.
The record displays the elector's assigned polling district, polling place and polling station information.
- Polling district
- The geographical area used to organise polling arrangements.
- Polling place
- The building or location designated for voting.
- Polling station
- The specific room or area where the elector votes.
Common enquiries
- Where do I vote?
- Provide the polling place and polling station information shown on the elector record.
- Has my polling station changed?
- Check the elector's current polling information.
- Can I vote at another polling station?
- Electors must vote at the polling station assigned to them unless alternative arrangements have been approved.
You can now confirm where the elector should vote.
View elector history
View an elector's registration history and activity.
Before you start
You must have permission to access elector records.
View elector history
- Search for the elector.
- Open the elector record.
- Open the Registration History section.
Elector history may include registration applications, address changes, name changes, nationality changes, registration status updates, publication dates and absent vote changes.
Use the recorded dates and activity details when explaining changes. Don't rely on memory or previous correspondence.
Common enquiries
- When did I register?
- Review the registration history and publication dates.
- When was my address changed?
- Review the change history entries.
- Why has my registration changed?
- Review the most recent activity recorded against the elector.
You can now understand and explain changes made to the elector record.
How every topic works
- A task-based title in the user's words, so search finds it.
- One line saying what the topic helps you do, answer first.
- Before you start: the permission you need, so nobody gets stuck halfway.
- Numbered steps, then what each status or field means.
- What to tell the person, including what not to say.
- A result line confirming what you can now do, and related articles.
The first 11 topics
- Customer services overview
- Find an elector
- Check registration status
- Check application status
- Find a polling station
- Check absent vote status
- Search for a property
- View property history
- View elector history
- Understanding elector records
- Understanding property records
What it's designed to do
Help that lets councils find answers by the work they're doing.
The structure is designed to reduce support tickets, improve onboarding and search success, and give the business a foundation that scales to new modules and features.
- Fewer support tickets
- Better onboarding
- Less dependence on training
- Better search success
Want to talk about this work?
Help that follows the job, not the software.
If your product is complicated and your help content follows the menus instead of the people using it, I'd like to hear about it.