Clear Speech, Clear Record: Judging Consultancy Language in UK Engagements

Consultancy is a trade in words before it is a trade in recommendations. A proposal, a diagnostic note, a steering pack: each is a piece of writing that a client has to act on. That makes language a practical concern, not a matter of taste. If a report cannot be restated in ordinary working English, the client has not yet received something they can use.

The words are part of the work

UK clients often treat unclear writing as a presentation problem. It is better understood as a delivery problem. A recommendation that cannot be explained plainly is not yet a recommendation; it is a draft awaiting translation. The client may still be paying for it, and the business may still be waiting for a decision.

This is not an argument against specialist vocabulary. Every trade has its shorthand, and consultancy is no exception. The question is whether the adviser can move between registers: from the technical to the practical, from the model to the Monday morning, from the report to the decision. A consultant who can do that is usually a consultant who knows what they are saying.

Why plain language is a test of thinking

Clear writing tends to follow clear thinking. It is not a perfect correlation, but it is a useful one. When a sentence has a subject, a verb and a named owner, the reader can see who is doing what. When a paragraph explains a trade-off, the reader can see what is being given up. When a recommendation has a next step, the reader can see where the work goes.

Fog does the opposite. It hides the actor, blurs the choice and delays the decision. In a small UK business, where the same people often own the problem, the budget and the implementation, that delay has a cost. A single opaque paragraph can stall a fortnight.

The translation test

A simple test is to ask for a one-page summary in everyday English. It should cover six things: the problem as the adviser understands it; the recommendation; the cost or resource implication; who must decide; what happens next; and how the client will know whether it has worked. This is not a demand for childish simplicity. It is a demand for a working asset.

If the adviser resists, offer to accept a rough summary rather than a polished one. The point is not to grade their prose. The point is to see whether the substance survives translation. A strong recommendation usually does. A weak one often needs the surrounding apparatus to stay upright.

A short language review

Before a UK client accepts a substantial consultancy document, a short review of its language can be revealing. The following checks are not a test of literacy. They are a test of whether the document is fit to be governed.

• Acronyms are defined at first use. A glossary is helpful, but first-use definitions are better. If the reader has to hold three unexplained abbreviations in mind, the document is already asking too much.
• Verbs have owners. “It is recommended” is weaker than “We recommend”. “The workstream will consider” is weaker than “The operations director will review by 30 November”. Passive voice is not always wrong, but a pattern of it should prompt a question.
• Simple questions get direct answers. Ask what will be different on Monday morning. Ask who decides. Ask what would make the adviser change their mind. If the answer restates the question or adds caveats without substance, note it.
• The recommendation has a decision attached. A recommendation is not a theme. It should say what the client is being asked to approve, defer or reject.
• Numbers have units, dates and sources. Percentages without a base, savings without a timeframe and costs without assumptions are not evidence. They are atmosphere.
• Risks are named, not gestured at. “There are risks” is not a risk register. A named risk has a cause, a consequence and an owner.
• The document says what not to do. Good advice usually involves a trade-off. If everything is a priority, nothing is.

When specialist language earns its place

Some consultancy work is genuinely technical. A tax position, a data model, an engineering assessment or a regulatory submission may need precise terms that have no everyday equivalent. The test is not whether the document contains technical language. The test is whether the adviser can explain the term in context and say why it matters to the decision.

A useful follow-up question is: “Explain that to a shop-floor supervisor, then explain it to a finance director.” The same substance should survive both versions. If it only survives one, the adviser may be more comfortable with the audience than with the idea.

What evasive answers look like

Evasion is rarely theatrical. It often looks like a reasonable caveat. “It depends” is a legitimate answer when the adviser then says what it depends on. “We need to do more work” is legitimate when it comes with a scope, a cost and a date. The warning sign is a pattern: the question is rephrased, the answer expands, and the client is left with more words but no clearer decision.

UK clients should feel entitled to ask for the answer in writing. A short email is often more revealing than a meeting. It gives the adviser a chance to be precise, and it gives the client a record of what was said.

Put language in the record

Plain-language checks are easiest to enforce if they are agreed at the start. A kick-off note can ask for a one-page summary at each stage, a short glossary for specialist terms and a decision log that records what was agreed and why. This is not anti-intellectual. It protects both sides. The client gets a usable record; the adviser gets a clearer mandate.

At close-out, the test is simple: can the client explain the recommendation to someone who was not in the room? If not, the work is not finished. The report may be complete, but the transfer has not happened.

The earliest signal

A trustworthy adviser will welcome translation. They may need prompting, but they should not resent it. Clear language is one of the earliest signals of accountability because it shows that the adviser is willing to be understood, and therefore willing to be held to what they have said.

If the words are foggy, the client should not assume they are missing something. They should ask for the summary, test the acronyms and notice the answer. The earliest sign of a sound engagement is often unglamorous: a sentence with a subject, a verb and a named owner.