A person looking for help with housing, addiction, bereavement, mental health or debt may have one clear window to act. If your website, leaflet or referral message makes that next step hard to understand, they may leave without getting support. Plain language service communications are not a cosmetic copywriting exercise. They help people find out whether a service is for them, what will happen next and how to get in touch.
For charities, healthcare organisations and public bodies, every word carries practical consequences. Clear communications can increase appropriate referrals, reduce missed appointments, ease pressure on frontline teams and help funders see the value of the work they support. Poorly explained services can do the opposite, even when the service itself is excellent.
What plain language service communications really mean
Plain language means writing so the intended audience can find what they need, understand it the first time and use it. It does not mean talking down to people, removing necessary detail or making serious issues sound simplistic. It means respecting people’s time, attention and circumstances.
That distinction matters when your audience may be anxious, in pain, short of money, newly arrived in the UK, supporting someone else, or reading on a phone between shifts. A phrase that makes sense inside an organisation can create a barrier outside it. “We provide holistic, person-centred interventions” may be accurate in a strategy document. It does not tell someone whether they can get help today, what kind of help is available or whether they are eligible.
A clearer version might say: “We offer one-to-one support for adults who are worried about their alcohol or drug use. You can speak to us without a referral.” The work has not been diminished. It has become usable.
Start with the moment someone needs help
The best service communications begin with the person’s question, not the organisation’s structure. People rarely arrive thinking, “I need to access an integrated community pathway.” They think, “I do not know where I will sleep tonight,” “I am worried about my child,” or “I need someone to talk to.”
Before rewriting a page or campaign, identify the action it needs to support. It may be making a self-referral, calling a helpline, attending a drop-in, asking a GP for support, donating, joining a membership scheme or sharing information with a neighbour. One page should not try to achieve all of these equally.
Then make the essential answers easy to spot. Who is the service for? What support is offered? Is it free? Where does it operate? Do people need a referral? What happens after they contact you? What should they do if they need urgent help? These are not minor details to tuck beneath a broad statement about your mission. They are the information that helps someone decide whether to act.
Lead with the answer, not the background
Organisations understandably want to explain their history, model and partnerships. Those details can be valuable, particularly for commissioners, funders and professional referrers. But they usually do not belong at the top of a page for someone seeking help.
Put the immediate answer first. Explain the background afterwards, where it adds context. This approach also works for service directories, appointment letters, social posts and automated emails. A subject line such as “Your appointment with the respiratory team: what to expect” is more useful than “Important information regarding your care pathway”.
Write for clarity without losing care
Plain language is not just about swapping long words for short ones. It is about making choices that reduce effort. Use active sentences where possible: “Call us to book” is clearer than “Bookings can be made by contacting the service.” Name the person taking action. Say “we will call you within two working days” rather than “contact will be made in due course”.
Keep one main idea in each sentence and use familiar words when they mean the same thing. “Help” is usually clearer than “assistance”; “use” is usually clearer than “utilise”. Explain unavoidable clinical, legal or safeguarding terms at first use. If a specialist term is required because it has a precise meaning, retain it, but do not leave people to decode it alone.
Tone matters just as much. Direct language can still be warm. “You do not need to have everything worked out before you contact us” may reassure someone more effectively than a general statement about inclusive provision. Equally, avoid promises you cannot keep. If there is a waiting list, say so plainly, explain what happens while someone waits and signpost urgent alternatives where appropriate.
Design the information as carefully as the words
Even excellent copy fails when it is buried in a dense page, hidden behind unclear buttons or presented in a format some people cannot use. Plain language service communications need accessible design as well as accessible writing.
Use descriptive headings that help people scan. Make calls to action specific: “Refer yourself online”, “Find today’s drop-in times” or “Call the advice line” tells people what will happen. “Learn more” often does not. Break long information into logical sections, but do not fragment a simple task across multiple pages just because it suits an internal website structure.
Accessibility also means considering how information is received. A text-heavy PDF may be difficult on a mobile phone and inaccessible to some screen-reader users. Videos need captions. Images should not be the only place essential information appears. Translated content, Easy Read versions, large print and British Sign Language provision may be necessary depending on your communities and service. There is no single format that works for everyone, so the right approach depends on who you need to reach and what they need to do.
Be precise where the stakes are high
There can be a tension between simplicity and accuracy. Eligibility criteria, consent, medication, data use and safeguarding procedures cannot be reduced until their meaning changes. The answer is not to retreat into jargon. It is to layer information.
Give people the short, practical version first, then offer fuller detail for those who need it. For example, start with “This service is for people aged 18 or over who live in Leeds.” Follow this with a clear explanation of exceptions, referral routes and the evidence required. This protects accuracy without forcing everyone through policy language before they can establish whether the service is relevant.
Be especially careful with language that can feel blaming or stigmatising. Terms chosen by systems are not always terms people choose for themselves. Ask people with lived experience how they describe their needs and how they want services to speak about them. The goal is not performative sensitivity. It is communication that makes it easier, rather than harder, to ask for help.
Test the message before you publish it
Internal approval is not the same as audience understanding. Colleagues know your acronyms, funding arrangements and service boundaries. The people you need to reach may not. A quick test with a small group of service users, volunteers, carers or community partners can reveal where a message becomes unclear.
Ask practical questions: What do you think this service does? Is it for you? What would you do next? What do you think will happen after you contact us? If people hesitate, guess or reach different conclusions, the communication needs work. This is not a test of their reading ability. It is a test of whether the organisation has explained itself well.
Use service data too. Look for pages with high exits, forms that are started but not completed, repeated calls asking the same question, inappropriate referrals and appointment no-shows. These patterns often point to a communication problem. They can also guide priorities when a small team cannot rewrite everything at once.
Make clarity part of everyday service delivery
A one-off rewrite helps, but language drifts when different teams create content under pressure. Establish a short, practical style guide that covers preferred terms, abbreviations, reading level, tone, dates and times, contact details and how to describe urgent support. Give staff usable examples rather than abstract rules.
Most importantly, involve the people delivering the service. Frontline colleagues hear the questions people ask and know where confusion occurs. Their insight can turn a technically correct page into one that genuinely helps someone get through the door.
When a service is difficult to explain, the answer is rarely more words. It is usually a clearer route through them. Give people the information they need, in language they recognise, at the moment they are ready to act. That is how vital work becomes easier to reach.
