The Drift Ledger: Keeping Specialist Advisory Engagements Inside Their Approved Brief

The board approves a specialist advisory brief in March. By September, the work has grown a new workstream, two extra workshops, a data request that was not in the original plan and a final report that addresses a different question. None of this is necessarily improper. Specialist work is iterative, and boards should expect some adaptation. But when variations accumulate without a clear decision trail, scope creep becomes a governance issue rather than a billing dispute.

The problem is rarely a single large unauthorised change. It is the slow drift from an approved purpose. The board sees the original brief and the monthly invoices; it does not see the cumulative shift in what the engagement is doing, who authorised it and whether the organisation is still buying the advice it set out to buy.

Scope creep is a governance signal

Boards approve advisory spend because it supports a decision, a capability or a risk response. If the engagement moves beyond that purpose, the board's approval is no longer describing the work being done. That is the governance point. Scope creep can also disguise weak commissioning: an unclear brief, an absent decision owner or a reluctance to test whether the original question has changed.

The control framework should not punish legitimate adaptation. It should make drift visible early enough for the board, or its delegated authority, to decide whether the new work is worth doing.

Name the decision owner

Every specialist engagement should have a named executive owner and a board or committee sponsor. 'The team' is not a decision owner. The executive owner should be accountable for the brief, the budget, the relationship and the change record. The sponsor should receive a short monthly or quarterly summary and approve changes above the delegated tolerance.

Tolerances should be set at appointment. They might cover value, time, changes to the decision question, new business units or jurisdictions, and changes in adviser personnel. A simple rule is better than a complex matrix: for example, the executive owner may approve variations up to a defined percentage of the original value and a defined number of weeks, provided the purpose is unchanged. Anything beyond that goes to the sponsor or the board.

Set change-control triggers

The framework needs triggers, not just principles. A change note should be required when any of the following occurs:

• cumulative variations exceed a set percentage of the approved value or a stated cash threshold;
• the engagement extends beyond the approved end date by more than an agreed period;
• a new workstream, deliverable or country is added;
• the advice begins to address a different decision from the one in the original brief;
• the adviser proposes a change in the core team;
• a variation is requested verbally and work begins before written approval.

The last trigger matters. In practice, drift often starts with a conversation. Requiring a short written change note — purpose, cost, time, owner and recommendation — creates a record without turning every adjustment into a procurement exercise.

Maintain a cumulative scope ledger

The board does not need a timesheet. It needs a cumulative scope ledger. This should sit alongside the contract and record the original brief, each approved variation, the date, the decision owner, the value, the time impact and the reason. It should show cumulative variation as a percentage of the original approval and identify any work underway without approval.

Procurement or the engagement management office should own the ledger. Internal audit can sample it periodically. The ledger should be reviewed at the same time as the invoices, so that financial reporting and scope reporting do not diverge.

A short board dashboard

A one-page dashboard is enough if it is honest. Five indicators are useful:

1. Cumulative variation as a percentage of approved value.
2. Time beyond the original end date.
3. Number and value of change notes approved at each level.
4. Proportion of current spend outside the original decision question.
5. Open unapproved work or unresolved scope disputes.

Each indicator can be rated red, amber or green against thresholds set at appointment. The dashboard should not become a second board pack. Its purpose is to prompt a question: is this engagement still the one we approved?

Intervene before the purpose changes

The most important control is the willingness to stop and re-brief. If the cumulative ledger shows that the engagement has moved beyond its approved purpose, the board or sponsor should consider pausing the work, renegotiating the brief or closing the engagement. Continuing to approve variations because the work is 'nearly finished' is how drift becomes sunk cost.

A closure review should compare outcomes with the original purpose. Did the advice answer the question the board approved? If not, the lesson belongs in the next commissioning cycle.

In 2026, UK boards are under pressure to demonstrate control of specialist spend without losing access to specialist judgement. A scope ledger and a short dashboard will not solve every commissioning problem. They will, however, give the board a defensible record of what it approved, what changed and who decided. That is the difference between flexible advisory work and governance by accumulation.