Apeiron Comms All articles
Opinion

Two Languages, One Truth: Mapping Regulatory and Customer Speech in UK Regulated Sectors

Priya Nair
Two Languages, One Truth: Mapping Regulatory and Customer Speech in UK Regulated Sectors

Photo by Photo by Age Cymru on Unsplash on Unsplash

Regulated organisations in the UK are often asked to speak two languages at once. One language is built for the regulator: precise, qualified, auditable and careful about what it does not say. The other is built for the customer: direct, human, timely and useful at the moment of need. Both are legitimate. The trouble begins when the organisation treats them as rival versions of the truth rather than two registers of the same truth.

The collision is familiar. A compliance team approves a sentence that is technically accurate but impossible to use on a phone call. A customer team writes a sentence that is clear but drops a condition the regulator expects to see. A public statement tries to satisfy both audiences and ends up satisfying neither. The customer hears evasion. The regulator sees imprecision. The comms team is left holding a document that no one can defend with confidence.

The collision point

Most collisions occur at the sentence level. A regulated statement may say that an application 'may be subject to verification checks'. A customer-facing colleague, under pressure, translates this into 'we will need to check your ID'. The second sentence is clearer, but it may overstate certainty or omit an important condition. Alternatively, the customer team may avoid the first sentence altogether and say something vaguer, which creates a different risk.

The problem is not that one language is good and the other bad. The problem is that the two languages are often developed separately. Compliance writes for the regulator. Marketing writes for the customer. Operations writes for the process. Communications is asked to reconcile the results after the fact, usually close to publication. A dual-language map is a way of doing that reconciliation earlier and more systematically.

Why one language fails

A single language cannot easily serve both purposes. Regulatory language carries qualifications because qualifications are part of the meaning. Customer language carries directness because directness is part of the service. If the organisation forces regulatory language into customer channels, customers may misunderstand or disengage. If it forces customer language into regulatory contexts, it may lose the precision that protects both the customer and the organisation.

The answer is not to abandon plain English. Regulated sectors have made real progress in recent years in using clearer language, and that progress should continue. The answer is to recognise that clarity and precision are not opposites. A sentence can be plain and still be accurate. It can be human and still be defensible. The work lies in mapping the relationship between the two registers rather than pretending that one can replace the other.

A dual-language map

A dual-language map is a simple working document. For each high-risk or frequently used phrase, it records four things: the regulatory statement, the customer-facing sentence, the proof point that supports it, and the escalation trigger that tells colleagues when the customer sentence is not enough.

Take a generic example. The regulatory statement might read: 'Charges may apply in certain circumstances.' The customer-facing sentence might read: 'You could pay a fee if you do this.' The proof point is the relevant schedule or policy clause. The escalation trigger is any case where the customer asks for a specific figure or disputes the condition. The map does not replace the regulatory statement. It gives customer-facing teams a usable route into it.

The map should also record prohibited shorthand. These are phrases that have become common internally but are inaccurate or unsafe in public. A shorthand that works in a team meeting may fail in a customer conversation. Naming it explicitly helps prevent drift.

Building the map

The map should be built jointly. A communications lead can convene compliance, customer service and, where relevant, legal or risk colleagues. Start with the ten phrases that cause the most friction. These are usually the phrases that appear in complaints, trigger repeat calls or cause spokespeople to hesitate in media interviews. Write the regulatory statement first, then the customer sentence, then test the customer sentence with frontline colleagues. If they would not say it naturally, it is not yet working.

The map should be owned by a named individual and reviewed on a fixed cycle. Regulated language changes. Customer expectations change. A map that is not maintained becomes another document that colleagues ignore. Version control matters, but usability matters more. A one-page map that is used is better than a twenty-page manual that is filed.

When to escalate

A dual-language map should make escalation easier, not harder. Customer-facing colleagues need clear triggers: when a customer asks for a specific commitment, when a complaint suggests a regulatory issue, when a journalist makes an enquiry, or when the customer sentence would change the meaning of the regulatory statement. In those moments, the map should point to a person or a process, not simply to a policy document.

This is where communications teams add value. They can test whether a sentence survives contact with the public. They can brief spokespeople on where the two languages meet. They can prepare holding statements that are accurate without pretending that every question has been answered. They can also spot when a customer-facing phrase is drifting into a claim that compliance has not approved.

The argument for mapping

The case for a dual-language map is not that it eliminates risk. It does not. The case is that it makes risk visible earlier, in language that operational teams can use. Regulated UK organisations do not need to choose between speaking to the regulator and speaking to the customer. They need to know which language belongs where, how the two relate and who is responsible when they meet. That is a communications discipline as much as a compliance one. Done well, it gives customers clearer answers and gives the organisation a more defensible voice.

All Articles

Related Articles

The Story That Will Not Ship: Seven Symptoms of Over-Editing in UK Brand Work

The Story That Will Not Ship: Seven Symptoms of Over-Editing in UK Brand Work

Employees Before Headlines: A Pre-Launch Briefing Sequence for UK Brands

Employees Before Headlines: A Pre-Launch Briefing Sequence for UK Brands

Five Media Training Myths UK Spokespeople Can Retire in 2026

Five Media Training Myths UK Spokespeople Can Retire in 2026