Plainly Said: An Audit for the Language UK Teams Use When News Is Poor

Bad news rarely arrives in plain terms. It arrives in a draft with a sentence such as 'we are simplifying the operating model' or 'some customers may experience a short delay'. Each phrase has a purpose: to protect the reader, the speaker or the organisation. Yet the effect is often the opposite. Softening language does not make difficult news easier to hear; it makes it harder to trust.

This article sets out a short audit for UK communications teams. It is not a campaign against courtesy. It is a way to separate care from concealment, and to give teams a repeatable method for checking the language they use in internal notes, customer emails and crisis statements.

Why soft language hardens suspicion

A euphemism is a word or phrase chosen to make a difficult fact less direct. In ordinary social life, that can be a kindness. In organisational communication, it often creates three problems.

First, it removes agency. 'A decision has been taken' does not say who decided. 'Roles will be affected' does not say how many people, in which teams, or by when. The reader senses that someone knows more than the sentence admits.

Second, it minimises. 'A short delay' is accurate only if the delay is short. When a customer has waited three weeks, the phrase reads as a refusal to acknowledge their experience. The gap between the words and the facts becomes the story.

Third, it borrows authority without evidence. 'Following a thorough review' may be true, but it tells the reader nothing they can check. In a crisis, vague reassurance is rarely reassuring. It invites speculation, and speculation is usually worse than the fact.

UK teams often soften language because understatement is a social virtue here. Politeness is not the problem. The problem is when politeness replaces specifics. Care is not demonstrated by making a fact sound smaller. It is demonstrated by making the fact clear, then showing what happens next.

A short audit format for a comms team

The audit works best as a 60-minute workshop with three or four people who write or approve external and internal messages. It should be run before publication, not after a complaint arrives.

1. Gather three samples

Ask each participant to bring one recent draft from each of three channels: an internal note, a customer email and a crisis or holding statement. Anonymise names and commercial details where necessary. The aim is not to review the whole communications output, but to examine the language habits that recur.

2. Mark the softening moves

Read each sample aloud. Ask the group to underline phrases that do one of the following:

• abstract a concrete event into a process, such as 'operational changes' instead of 'site closure';
• use the passive voice to hide the actor, such as 'mistakes were made';
• minimise with adjectives, such as 'minor', 'brief', 'some' or 'limited';
• promise future clarity without a date, such as 'we will communicate more soon';
• express empathy without an action, such as 'we understand this is frustrating'.

These are not forbidden constructions. They are signals. Each one needs a reason, and the reason should be tested against the facts.

3. Ask three questions

For every marked phrase, the group should answer three questions in plain terms:

• What happened?
• Who is affected, and how?
• What can we commit to, and by when?

If the draft cannot answer those questions, the problem may be the message rather than the words. The audit should surface that early.

4. Rewrite with care, not bluntness

Plain language is not the same as cold language. A plain sentence can still acknowledge difficulty. The structure is usually: state the fact, acknowledge the impact, set out the next step, and give a route to support or further information.

5. Test with an outsider

Ask a colleague outside the communications team to read the revised message and answer one question: what happened, to whom, and by when? If they cannot answer without guessing, the message is still too soft.

6. Keep a ledger

Record the recurring phrases, the reason they were used and the plain alternative the team prefers. Call it a euphemism ledger or a softening register; the name matters less than the discipline. The ledger should not become a list of banned words. It should become a record of decisions, reviewed quarterly and used in onboarding.

Before and after: three common cases

Redundancies

Before: 'We are simplifying our operating model to position the business for future growth. A number of roles will be affected.'

After: 'We are closing our Leeds site. Forty-two roles are at risk. We are starting formal consultation today. Affected colleagues will be invited to individual meetings this week, and we will publish the support available, including redundancy pay and counselling.'

The second version is harder to read, but it is easier to trust. It does not use growth language to describe job losses.

Delays

Before: 'Due to unprecedented demand, some orders may experience a short delay. We apologise for any inconvenience.'

After: 'Orders placed between 10 and 12 November will arrive up to 14 days later than the delivery date shown at checkout. We will email every affected customer by 17:00 on 14 November with a revised date. Delivery charges will be refunded automatically.'

The first version protects the organisation from a precise commitment. The second protects the customer from uncertainty.

Service failures

Before: 'We are aware of an intermittent issue affecting some customers. Our teams are working hard to resolve it.'

After: 'Between 09:10 and 11:40 today, customers could not sign in to their accounts. The cause was a database fault. Service is restored. We will publish a full incident note by 16:00 tomorrow, including what we are changing to prevent a repeat.'

In a service failure, the reader wants three things: the timeline, the impact and the next update. Soft language delays all three.

The ledger as a living document

The value of the audit is not a single rewrite. It is the habit of noticing where language is doing protective work rather than communicative work. Over time, the ledger will show patterns: teams may soften delay messages more than redundancy messages; crisis statements may rely on passive voice; customer emails may overuse 'we understand'.

Those patterns are useful. They show where approval processes, legal caution or fear of blame are shaping the words. The answer is not to remove caution. It is to make caution specific. A legal constraint can be stated plainly. A limited commitment can be bounded clearly. An apology can be direct without becoming an admission that the organisation has not yet verified.

The test is simple: if a reader later discovers the full facts, will they feel the message prepared them, or managed them? The first builds trust. The second spends it.

Plain language is not a lack of care. It is care made visible.