Who Agreed to That? Keeping Scope Changes Visible, Fair and Paid For

Who Agreed to That? Keeping Scope Changes Visible, Fair and Paid For

You will already know how much goodwill a well-run engagement builds with a client, and how much of that goodwill depends on saying yes to reasonable requests. Each of those yeses carries a cost, though, and the costs are easy to miss. Left untracked, they can add up to weeks of unpaid effort.

Why scope changes cost more than they look

Every consulting engagement is a negotiated agreement, and every negotiated agreement drifts once the work starts. Priorities shift, timescales move, and the client asks for one more thing. A significant change to scope, timescale or priorities means the contractual and planning agreements underneath the engagement need to be reassessed properly, rather than quietly stretched to cover something they were never designed for.

Change control is the agreed way of recording, assessing and deciding on those changes. Without it, scope additions default to being absorbed at no extra charge. The instinct to absorb a request and keep the relationship smooth is understandable. It is also how margin disappears, one small request at a time, until the engagement is no longer profitable even though it looks on paper exactly as it did at the start.

Change is a normal part of an engagement. Engagement priorities can change frequently, and consultancy requires significant adaptability. What protects the engagement is how each change is handled.

Disputes about scope almost never involve a client acting in bad faith. They involve a series of small, reasonable-sounding requests that nobody formally tracked, each easy to justify and collectively expensive. A formal process turns an awkward conversation into a routine one.

The question every change has to answer

The same question has a mirror image on the client's side: will the value this engagement was meant to deliver survive the change? A scope change waved through without proper analysis can compromise the value proposition of the original engagement just as easily as it compromises the consultant's fee.

How can you keep change under control?

A useful starting point is to separate three things and be clear about each one.

The level

Not every change deserves the same response. There are three levels of change, and sorting a request into the right one saves effort on the small ones and protects you on the large ones.

• Small changes can be incorporated with minimum deviation, often needing nothing more than a reconfirming email between consultant and client that records what was agreed.
• Larger changes call for genuine negotiation about what gets deprioritised to make room for the new work.
• Significant contract deviation requires renegotiation and may not be tolerable within the existing agreement.

A reconfirming email may look like a small thing to send. It is the cheapest way to make sure two people remember the same agreement. Sorting a request into the right level is the first judgement in the process, and it decides how much effort the response needs. The trade-off sits at both ends. Even a small change deserves a written record, so nobody disputes later whether it happened. At the other end, capacity rarely expands just because a request has, so something already on the plan usually has to move. When work has fundamentally changed shape, exiting the engagement can become the more honest option than pretending the original contract still applies.

The process

A change control process has four steps. Either side can start it: change is not something that only happens to consultants, who often need to request one themselves when circumstances on their side shift.

• Request. The client or the consultant raises the change.
• Impact analysis. The change is assessed against cost, effort, timeliness, dependencies and its effect on the value the engagement is meant to realise, so the decision rests on evidence rather than a rough guess made in a corridor conversation.
• Decision. The change committee, described below, decides what happens.
• Delivery. The agreed change is implemented and every piece of documentation it touches is updated, including plans, specifications and the contract itself.

Impact analysis is the step that replaces instinct with evidence. Looking at cost, effort, timeliness and dependencies together shows what a change really involves, and looking at its effect on value shows whether it still serves the purpose of the engagement. Delivery is the step most often skipped, and skipping it is costly. A change that was implemented but never documented tends to resurface later as a disagreement about what was actually agreed, often just when the engagement is due for renewal.

The committee

The decision sits with a change committee. The minimum viable version is small: one client member and the consultant, meeting whenever a request needs a decision rather than on a fixed schedule that might leave a change unresolved for weeks.

Meeting when a request needs a decision, rather than on a fixed schedule, avoids leaving a change unresolved for weeks. A small committee with explicit options prevents two failure modes at once. One is a change quietly implemented because nobody formally said no. The other is a change stuck in limbo because nobody was authorised to say yes.

Five outcomes of a change decision

Whenever a request reaches the committee, it has five possible outcomes.

• Approve

  The change goes ahead as requested.

• Approve in part

  Some of the change goes ahead and the rest does not.

• Ask for more information

  The committee holds the decision until the gap is filled.

• Escalate

  The decision moves to someone with greater authority.

• Decline

  The change does not go ahead.

Why the process protects both sides

A change control process is easy to mistake for paperwork that slows the work down. Its job is to keep a shifting engagement honest for everyone attached to it, long after the original contract has stopped being an accurate description of the work.

For the consultant, the process closes the gap where scope additions get absorbed at no extra charge. Margin erodes one small request at a time, so recording each change and assessing its effort helps keep the fee in line with the work actually being done.

For the client, the same process means that a change is judged against the value the engagement is meant to deliver before it goes ahead. Assessing the change before it goes ahead gives the client a decision based on evidence rather than a rough guess.

The timing matters as much as the content. Change control is far easier to run well when both sides agreed to it before they needed it.

Where to start

Three questions to put to yourself before the next engagement starts:

• The last time a client asked for something small, was the agreement recorded anywhere, even in a reconfirming email?
• Have you and the client agreed how changes will be requested, assessed and decided before any need for one arises?
• If a new request needs capacity, do you know what on the current plan would move to make room for it?

When you can size a change, follow the same steps every time and give a small committee clear options, scope changes are more likely to stay visible, fair and paid for. Agreeing the arrangement at the start makes each later conversation easier.

BoutiqAcademy

A learning platform for boutique consultancy practitioners. Dozens of courses and hundreds of tools, templates, and frameworks built around the way boutique firms actually work.

Practical guidance on delivery management is part of the BoutiqAcademy library.

Register your early interest at https://boutiqacademy.com