The Ledger Beneath the Recommendation: Keeping Consultancy Assumptions Visible

Most consultancy engagements do not fail at the point of recommendation. They fail earlier, in the quiet space between a plausible assumption and a board paper that treats it as settled fact. The recommendation may be sound. The logic may be elegant. But if the foundations are never made explicit, nobody knows what would have to be true for the advice to remain valid — and nobody notices when circumstances move.

The problem is not the recommendation

A recommendation is a conclusion. An assumption is a belief that supports it. The two are often presented together so smoothly that the distinction disappears. A consultant writes that a new operating model will reduce lead times; the board reads that lead times will fall. A paper states that customers will accept a revised service tier; the meeting hears that revenue will hold. Nothing is necessarily dishonest. The difficulty is that the belief has been absorbed into the conclusion without being named, owned or dated.

Over time, that belief hardens. It appears in the next paper without its caveat. It becomes a line in the business case. It is repeated in a progress update as though it were evidence. By the time it is tested, the organisation has built decisions on top of it. This is not a failure of intelligence. It is a failure of record-keeping.

A ledger, not a risk register

An assumption ledger is a single page. It is not a risk register, although the two are sometimes confused. A risk register tracks things that might happen. An assumption ledger tracks things that are currently believed to be true. The distinction matters because assumptions are often invisible precisely when they are most influential.

The page should be short enough to read in a meeting and specific enough to challenge. At minimum, each line should carry six fields:

• the assumption, written as a plain sentence;
• the decision it affects, so the reader knows why it matters;
• the evidence currently held, rated simply as verified, indicative or untested;
• a named owner, not a department;
• a review or expiry date;
• the test that would confirm or challenge it.

The one-page limit is not an aesthetic preference. It is a discipline. If the assumptions cannot fit on a page, the engagement has not been thought through carefully enough to be commissioned. A longer document tends to hide the very judgements that need air.

Before the work is commissioned

The most useful moment to introduce the ledger is before the consultancy begins. Ask for a draft assumption ledger alongside the proposal. This is not an adversarial request. It is a request for clarity about what the advice depends on.

A strong proposal will already contain these beliefs, but usually in prose. The ledger pulls them into the open. It allows the client to see where the consultant is confident, where they are relying on client data, and where they are making a professional judgement that should be tested. It also gives the client an opportunity to correct the record before the work starts. Many engagements begin with a misunderstanding about what is known, what is assumed and what is merely hoped for. A single page can prevent weeks of drift.

For a UK professional services firm weighing a new office, for example, an assumption might read: clients will accept a 15 per cent fee increase in exchange for faster turnaround. That is not a plan; it is a belief. It needs an owner in the commercial team, evidence from recent renewal conversations, an expiry date tied to the next pricing review, and a test drawn from a sample of client discussions or proposal outcomes. Once written in that form, it can be examined. Until then, it is simply a mood in the room.

During delivery, expiry dates do the work

An assumption ledger is not completed at kick-off and filed away. It should be a live document, reviewed at agreed points in the engagement. Progress updates should say not only what has been done but which assumptions have changed. Has the evidence improved? Has the owner confirmed the position? Has the expiry date passed?

Expiry dates are especially useful because they stop beliefs from becoming permanent by default. An untested assumption with no review date will survive longer than it deserves. A dated assumption creates a natural moment to ask whether the recommendation still rests on solid ground. If the date passes and nobody notices, the ledger has failed; if it prompts a short conversation, it has done its job.

When an assumption expires, the recommendation does not automatically fail. It must simply be re-earned. That is a healthier position than treating the original advice as fixed. Circumstances change, evidence accumulates and priorities shift. A recommendation that cannot accommodate those changes is brittle, however well written it may be.

A board-level habit

Boards are often good at recording decisions and poor at recording the beliefs behind them. Minutes capture the resolution; they rarely capture the conditions under which the resolution made sense. A one-page ledger can sit alongside the decision paper and give non-executives a practical way to challenge without turning the meeting into a seminar.

The questions are straightforward. Which of these assumptions are untested? Who owns the most consequential one? When will we know? What would cause us to revisit the decision? These are not hostile questions. They are the questions a serious organisation asks before it commits resources.

For consultancies, the ledger is also a mark of professional confidence. It says that the advice is strong enough to be examined and specific enough to be corrected. That is more persuasive than a proposal that presents certainty it cannot support.

Clarity about what is provisional

Good consultancy does not pretend that every belief is a fact. It separates the two, gives each its proper weight and makes the provisional nature of advice visible. The assumption ledger is a modest artefact — one page, six columns, a handful of dates — but it changes the conversation. It moves the organisation from admiring a recommendation to understanding what the recommendation depends on.

That is not a hedge. It is clarity. And in 2026, with UK organisations making long-term commitments in an unsettled environment, clarity about assumptions is not a bureaucratic extra. It is part of how good decisions are made and kept honest.