Start With the Exclusions: What a Consultancy Proposal’s Quiet Pages Reveal

Most UK boards do not sign a consultancy proposal without reading the methodology, the team biographies and the fee schedule. That is sensible. It is also, in 2026, an incomplete form of diligence. The pages that matter most are often the ones no one presents: assumptions, exclusions, dependencies and client responsibilities. They sit at the back, in smaller type, and they tell you more about fit than any capability slide.

My argument is simple. Read the exclusions first. If the exclusions narrow the problem to something the consultancy can solve comfortably, you are not buying advice on your problem. You are buying advice on an adjacent problem, with the awkward parts left with you.

The back pages are the brief in disguise

A proposal is not only a description of what a consultancy will do. It is also a description of what it will not do, what it expects you to do, and what it has decided to assume. Those three categories are not administrative clutter. They are the commercial and operational outline of the engagement.

Consider a familiar example. A firm asks a consultancy to improve decision-making across a growing operation. The front of the proposal talks about governance design, operating rhythms and executive alignment. The exclusions state that the work does not cover data quality, line-manager capacity, incentive structures or implementation support. Each exclusion may be defensible. Taken together, they may remove most of the reasons decisions are slow in the first place.

That does not make the consultancy dishonest. It makes the proposal narrower than the original brief. The question for the buying team is whether the narrower version is still worth buying. Often it is. But the board should know that it is buying a diagnosis, not a cure, and that the cure has been assigned to internal staff who may not have the time or authority to deliver it.

Three kinds of exclusion, three different responses

Not every exclusion is a warning sign. It helps to sort them into three types.

The first is a legitimate boundary. The consultancy is explicit that it does not provide legal advice, regulated financial advice or software implementation. That is useful honesty. It tells you where to bring in another specialist and prevents a false sense of coverage.

The second is risk transfer. The consultancy excludes responsibility for client-side data, stakeholder availability, internal approvals or benefits realisation. Some transfer is normal. Too much transfer turns the engagement into a consultancy-shaped report with the client left holding the operational risk.

The third is a capability gap dressed as a scope decision. The consultancy may exclude culture change, union engagement, systems integration or post-merger integration because it does not have the depth to lead that work. Again, that can be honest. But if those excluded areas are central to the problem, the proposal is not a fit, however polished the front section.

A practical audit for boards and buying teams

Before signing in 2026, put the exclusions next to the original problem statement. Not the consultancy’s restatement of the problem. Your version, written before the proposal arrived.

First, map each exclusion to the outcome you need. Ask whether the exclusion removes a workstream that is merely adjacent or a workstream that is causal. If the excluded work is causal, the proposal may be describing a symptom rather than the system.

Second, price the client responsibilities. Internal steering time, data extraction, workshop preparation, change communications and implementation oversight all consume management capacity. Put a notional internal cost against them. A modest consultancy fee can become an expensive engagement once the client-side burden is counted.

Third, test the assumptions for vagueness. Phrases such as ‘reasonable access to stakeholders’, ‘appropriate data quality’ and ‘timely decisions’ are not neutral. They are conditions. Ask what happens if those conditions are not met. Ask who bears the cost of delay.

Fourth, ask two direct questions of the consultancy. Which exclusion would you challenge if you were sitting on our side of the table? And if we removed this exclusion, what would change in your fee, your team and your timetable? The answers are often more revealing than the proposal itself.

Good exclusions can be a sign of strength

It would be wrong to treat every exclusion as a red flag. A consultancy that declares what it cannot do is often safer than one that claims to cover everything. The problem is not the presence of exclusions. The problem is a mismatch between the exclusions and the client’s real problem, or a set of exclusions so broad that the engagement cannot deliver the outcome the board has in mind.

There is also a cultural test here. A firm that reads the exclusions carefully signals that it will manage the engagement carefully. A consultancy that resists discussing them, or treats them as legal boilerplate, is telling you something about how it will behave when scope pressure arrives.

Read the quiet pages first

The front of a proposal is designed to reassure. The back is where the engagement actually lives. For UK firms buying specialist advice in 2026, the exclusions, assumptions and client responsibilities are not the fine print. They are the brief in disguise.

Read them first. Then decide whether the proposal is really describing your problem, or quietly narrowing it to something more convenient. The answer will not always be no. But it should always be a conscious yes.