The Words We Sign To: Setting a Shared Vocabulary Before the Brief

Most consultancy engagements do not fail because the adviser is incompetent or the client is unreasonable. They fail because both parties signed the same words while carrying different pictures in their heads. The brief looks tidy. The proposal reads well. Six weeks later, a meeting is convened to discuss why the "deliverable" is not what the client expected, why the "stakeholder group" has grown from six people to twenty, or why the "recommendation" has been produced but nobody feels able to act on it.

These are not arguments about effort. They are arguments about meaning. And they are cheaper to settle before the engagement begins than after the invoice arrives.

Why shared words are not the same as shared understanding

Consultancy has a working vocabulary that feels universal until it is tested. Deliverable, stakeholder, recommendation, implementation, workshop, roadmap, review—each term carries professional assumptions that may not match the client's operating reality.

For a consultancy, a deliverable may be a written report with an executive summary and an appendix. For a client, it may mean a functioning process that staff are already using. For one board, a stakeholder is anyone with a veto. For another, it is anyone who receives a monthly update. Neither usage is wrong. But if the brief does not distinguish between them, the engagement is exposed.

The remedy is not a longer contract. It is a short, client-led glossary that sits alongside the brief and records what both parties mean by the words that will determine whether the work is judged a success. This is not bureaucracy for its own sake. It is a practical instrument for buying advice well.

Start with the nouns that carry consequences

The glossary should be selective. A list of forty definitions will be ignored. A list of eight to twelve contested terms, chosen because they affect scope, cost, sign-off or evidence, will be used.

Begin by asking a simple question of the draft brief: which words, if interpreted differently, would cause a dispute about time, money or acceptance? Common candidates include:

• Deliverable—a document, a decision aid, a trained team, a working process, or all four?
• Stakeholder—decision-maker, consultee, recipient of communications, or potential blocker?
• Recommendation—an option for the board to consider, a preferred course of action, or a decision the consultant expects the client to adopt?
• Implementation—advice on how to implement, hands-on delivery, or accountability for outcomes?
• Workshop—a briefing, a working session, a decision forum, or a training event?
• Review—a quality check, a progress meeting, a formal gate, or a post-engagement evaluation?

Each term should then be defined in observable language. Not "a high-quality report" but "a written document of no more than fifteen pages, containing a options appraisal, a costed recommendation and a one-page decision summary, submitted to the steering group by an agreed date." Not "stakeholder engagement" but "three structured interviews with named director-level owners, plus a single briefing note circulated to the wider group."

The test is simple: could a reasonable third party read the definition and tell whether the obligation had been met? If not, the definition is not yet doing its job.

Make 'done' a matter of evidence, not atmosphere

Many scope disputes emerge at the point of completion because the brief describes activity rather than evidence. A consultancy can demonstrate that it ran the workshops, conducted the interviews and produced the report, while the client can demonstrate that the team is no closer to a decision. Both statements may be true.

A useful glossary therefore pairs each contested term with an evidence convention. What will exist at the end that did not exist at the start? A signed-off decision log? A process map with named owners? A costed implementation plan accepted by the finance director? A training pack that has been used with staff? A board minute recording the decision?

This is particularly valuable in 2026, when many organisations are buying advice in smaller, more frequent parcels. A short engagement can still generate a disproportionate amount of disagreement if the acceptance criteria are left to memory and goodwill. The glossary gives both sides a shared reference point without turning a modest piece of work into a procurement exercise.

Use the exercise to expose hidden assumptions about roles

Definitions do more than police scope. They clarify responsibility. If implementation means the consultant will remain available for three months of advisory support, that is a very different commitment from the consultant being accountable for operational delivery. If stakeholder includes the client's regulator, the engagement may need a communications protocol. If recommendation means a board-ready decision paper, the consultant needs access to the board's decision timetable.

The glossary should therefore record, for each term, who owns the activity, who approves the output and who is responsible for the next step. This need not be elaborate. A three-column table is often enough: term, agreed definition, evidence and owner. The point is to make the handover between advice and action visible before the work begins.

Keep it short, signed and reviewable

A glossary is most effective when it is treated as a living annexe to the brief rather than a separate legal document. It should be drafted by the client, challenged by the consultancy, and agreed before signatures. It should be reviewed at the first steering meeting and updated only by agreement. It should not be used to score points or to retrofit expectations after the fact.

The tone matters. The purpose is not to imply that the consultancy is likely to be slippery or that the client is likely to move the goalposts. It is to acknowledge that professional language is ambiguous and that clarity is a shared commercial courtesy. A well-run glossary exercise often improves the quality of the brief itself, because it forces the client to decide what it actually wants before commissioning work.

A small discipline with a long reach

For UK buyers of consultancy, the case is straightforward. The cost of a two-hour glossary session is trivial compared with the cost of a disputed engagement, a stalled decision or a report that nobody can act on. The exercise also strengthens the client's position at the end of the work, because success has been defined in advance rather than reconstructed from memory.

The words we use to commission advice are not neutral. They allocate risk, shape expectations and determine what counts as completion. Setting a shared vocabulary before the brief is signed is not a legalistic flourish. It is one of the simplest ways to make 2026 consultancy engagements easier to judge—and fairer to both sides.