Gabriel Wilson All articles
Procurement

The Extra Mile Has a Meter: Keeping Small Consulting Requests Accountable

Thomas Reid
The Extra Mile Has a Meter: Keeping Small Consulting Requests Accountable

Photo: Richard Sutcliffe , CC BY-SA 2.0, via Wikimedia Commons

Scope creep rarely arrives as a dramatic demand. It arrives as a short email: could you just add a competitor comparison, check one more site, sit in on a supplier meeting, or produce a version for the board? Each request sounds reasonable. Each one is small. Together they can consume a budget, delay a timetable and leave both client and consultant feeling that the engagement has drifted.

The answer is not to refuse every extra request. Good consulting relationships need flexibility. The answer is to make the extras visible, value them consistently and agree what happens when they accumulate. A scope-creep ledger is a lightweight way to do that.

1. Put the Boundary in Writing Before the First Extra Arrives

The engagement letter or statement of work should define what is included, what is excluded and what counts as a material change. It does not need to be adversarial. A single page of inclusions, exclusions and assumptions is usually enough. Include the number of workshops, the number of interviews, the deliverables, the review cycles and the client responsibilities.

The most useful line is often the simplest: additional requests will be assessed against the agreed scope and may be absorbed, traded or priced as a change. That sentence sets the expectation before anyone is under pressure.

2. Open a Simple Ledger on Day One

The ledger can be a shared spreadsheet with eight columns. It should be opened at the start of the engagement, not when the budget is already under strain.

Request date Requested by Request Why it matters Estimated effort Value band Decision Action
12 May Operations lead Add two competitor interviews Test pricing assumption 1.5 days Low Absorb Complete within tolerance
19 May Finance director Build a three-scenario board model Support investment case 3 days Medium Trade Swap for original appendix
27 May CEO Facilitate a supplier workshop Resolve supply risk 2 days High Charge Change request raised

The ledger is not a complaint log. It is a decision record. It shows the client what has been asked for, what it is worth and what has been agreed.

3. Classify Extras as Absorb, Trade or Charge

A three-band system keeps the conversation proportionate.

Absorb: the request is small, clearly within the spirit of the engagement and can be met without affecting the timetable or the fee. Use this sparingly and record it. Absorbed requests are still a cost, even if they are not invoiced.

Trade: the request is material but can be met by swapping it for something of similar value within the existing scope. The client gives up a lower-priority output or accepts a later date elsewhere. Trading keeps the budget neutral and forces a real choice.

Charge: the request changes the scope, the timetable or the risk profile enough to justify a change request. This is not a penalty. It is the correct treatment for work that was not priced.

4. Value Informal Extras in Client Terms

Consultants often value extras in days. Clients often think in outcomes. Both languages are useful, but the client-facing conversation should start with the client's terms: what will this extra request cost in fee, delay, risk or displaced work?

A request that takes two consultant days may also delay a board paper by a week, pull a senior manager into two extra sessions and postpone a decision that is worth more than the fee. If the ledger records effort but not consequence, it will look like a billing tool rather than a management tool. Record the consequence as well.

5. Raise Change Control at the First Material Signal

The worst time to raise change control is at the final invoice. The second worst time is after the extra work has already been done. Raise it when the request first appears and the answer is not obvious.

A neutral script helps. Say: This is outside the agreed scope. It is a sensible request. We can absorb it within the existing tolerance, trade it against another output, or price it as a change. Which would you prefer? That formulation avoids a flat refusal and avoids a silent subsidy. It puts the choice where it belongs: with the client.

6. Make the Ledger a Shared Document

The ledger should be visible to the client lead and reviewed in the weekly or fortnightly engagement meeting. It should not be a consultant's private record produced at the end. Visibility is what keeps the relationship healthy. The client can see that requests are being logged fairly, and the consultant can see that small additions are not being forgotten.

A shared ledger also reduces the risk of dispute. If a request was absorbed, the client can see it. If it was traded, the client can see what was given up. If it was charged, the client can see why.

7. Review Weekly, Not at the Invoice

A five-minute review is enough. Ask three questions: what has been added since we last met, what has been absorbed or traded, and what needs a change request? The review keeps scope creep from becoming a month-end surprise. It also gives the client an early warning if the engagement is drifting away from its original priorities.

8. Close the Ledger into the Next Phase

At the end of the engagement, the ledger becomes a useful planning document. Recurring extras may point to work that belongs in a new phase, a retainer or a different scope altogether. Absorbed requests may reveal that the original scope was too narrow. Charged requests may show where the client's real priorities sat.

Do not simply file the ledger. Use it to improve the next statement of work. A client that sees this discipline is more likely to trust the consultant with a larger engagement, because the boundaries are clear.

Why This Protects the Relationship

Scope creep is not usually caused by bad faith. It is caused by busy people making reasonable requests in the moment. A ledger turns those moments into a shared record and a shared choice. It protects the consultant from silent overwork and protects the client from unexpected invoices.

For UK clients commissioning consulting work, the practical test is simple. If an engagement has no mechanism for recording informal extras, it has no mechanism for keeping the budget honest. The extra mile is valuable. It should still have a meter.

All Articles

Related Articles

The Seal Is Not the Skill: Why Approved-Supplier Lists Need a Second Reading

The Seal Is Not the Skill: Why Approved-Supplier Lists Need a Second Reading

Outside the Orbital: How to Tell Whether a Consultant Has Actually Worked Your Patch

Outside the Orbital: How to Tell Whether a Consultant Has Actually Worked Your Patch

The Cost of the Unmade Decision: Why Governance Delay Deserves a Line in Your Budget