The Unread Instruction: Dunbar’s Language Access Audit for 2026

A form is often described as a gateway to help. In practice, it is also a test of language. For a resident whose first language is not English, or whose reading confidence is limited, the first barrier may not be the appointment, the eligibility rule or the waiting list. It may be a single instruction printed in a font size that assumes fluency.

Dunbar Neighbourhood Hub has spent recent months reviewing how public-facing services in the town handle translation, interpretation and limited English literacy. The aim was not to audit individual officers or to single out particular organisations. It was to trace the ordinary moments where language becomes a practical obstacle: the paper form at a front counter, the automated phone menu, the online application, the public meeting notice pinned to a board.

Four pressure points in the resident journey

The audit looked at four common points of contact. The first is the written form. Many forms are designed around administrative categories rather than everyday speech. Terms such as “household”, “evidence of residence”, “consent” and “sole occupant” may be clear to staff but ambiguous to anyone translating quickly, or reading under pressure.

The second is the telephone. Automated menus often rely on fast speech, standard accents and a series of options that must be remembered rather than written down. A resident with limited English may reach the right department but still be unable to explain the reason for the call. Call-backs, which ought to reduce pressure, can intensify it if the resident is unsure who will ring or what information will be requested.

The third is the website. Machine translation has improved, but it remains uneven. A translated page may preserve the layout while losing the meaning of a legal or procedural phrase. Links may lead to English-only documents. A resident may understand the headline and still miss the deadline.

The fourth is the public meeting. Notices often advertise a venue, a time and a purpose, but rarely say whether an interpreter can be arranged, whether a friend or family member may attend, or whether a written summary will be available afterwards. For residents who cannot follow rapid discussion, the meeting may be technically open and practically closed.

Where the gap becomes visible

The most revealing part of the review was not the number of translated documents. It was the number of informal workarounds. Residents described asking adult children to interpret benefit letters, neighbours to explain housing forms, and friends to sit beside them during phone calls. These arrangements are often kind and sometimes effective. They are also fragile.

Confidentiality is one concern. A resident may not wish a family member to know about a debt, a health condition or a domestic situation. Accuracy is another. A relative may summarise a form quickly, omit a question or use a word that sounds correct but changes the meaning. Consent is a third. If a resident signs a document because someone they trust has explained it, the quality of that explanation matters.

Staff, too, have developed informal practices. Some front counters keep a short list of colleagues who can speak another language. Some services use machine translation on a screen and check key points aloud. Some meeting organisers have quietly arranged interpreters when asked, even where no formal process exists. These practices are valuable, but they depend on who is on shift, which community contacts are available and whether the resident knows to ask.

A practical checklist for clearer multilingual access

A language access plan does not need to begin with a large budget. It needs to begin with consistency. The following checklist is intended for service managers, community groups and anyone who designs public information in Dunbar.

1. Write the English version plainly first. Translation cannot rescue a sentence that is already unclear. Short sentences, defined terms and step-by-step instructions reduce the burden for everyone.

2. Identify the documents that genuinely matter. Not every leaflet needs translation. Priority should go to application forms, eligibility guidance, appointment letters, complaint routes and urgent safety information.

3. State how to ask for an interpreter. Put this on the form, on the website and on the phone menu. Say whether the service is free, how much notice is needed and whether a friend or advocate may attend instead.

4. Provide a telephone route that does not depend on fast listening. Offer a call-back, a text option where appropriate, or a named contact. Allow time for the resident to find documents and to ask for repetition without feeling rushed.

5. Check translated materials for meaning, not just words. A competent translator should review forms and notices, especially where legal, financial or housing terms are involved. Machine translation can be a first draft, not a final assurance.

6. Make meetings accessible in advance. Meeting notices should say whether interpretation can be arranged, whether written summaries will be available and who to contact. A brief follow-up note can be as important as the meeting itself.

7. Record what happens. Services should note requests for interpretation, common languages, recurring confusion and missed appointments. This does not require identifying individuals. It requires noticing patterns.

The informal network needs support, not assumption

Dunbar has a strong habit of neighbourliness, and it would be wrong to dismiss the informal help that already exists. Community groups, faith contacts, school staff and local volunteers often bridge gaps that formal services have not yet designed for. But an informal network should not be treated as a substitute for accessible public information. It should be recognised, supported and, where possible, brought into the design of services.

That might mean offering short training for staff on working with interpreters, producing a simple card that explains how to request language support, or inviting community representatives to review a form before it is printed. It might also mean sharing a language access statement across local services so that residents hear the same message from more than one place.

What Dunbar can do next

The 2026 audit points to a modest but meaningful programme of work. Services could review their five most important forms, publish a clear interpretation request route, and test their phone menus with people who do not read English fluently. Public meeting organisers could add a standard accessibility line to every notice. Local partners could agree a shared list of translation and interpretation contacts, with clear arrangements for confidentiality and consent.

None of this removes the need for good will. It simply gives good will a structure. The test of a public service is not whether its forms exist, but whether people can use them. In a town that values practical help, language access should be treated as part of the front door, not an exceptional arrangement made after someone has already struggled to get through it.