Managing scope change in client projects

Scope change is not a delivery failure. Clients learn things during a project and ask for different work — that is usually a sign the work matters. The failure is when the change is absorbed invisibly, so the team is judged against a plan nobody is delivering any more.

Keep the agreed scope where delivery can see it

If the only record of what was agreed is a signed document in a folder, every later conversation becomes a memory test. Keep the agreed scope attached to the live project, along with the document it came from. The baseline is what makes a change discussable rather than contentious.

Separate the request from the reaction

Before deciding anything, establish what is actually being asked for and why. A surprising proportion of change requests turn out to be clarifications, or things achievable by dropping something of lower value. Understanding first keeps the commercial conversation short.

Assess impact in three dimensions

• Effort: how much additional work, and from which roles.
• Timeline: what moves, and whether anything contractual is exposed.
• Cost and fee: what it costs to deliver, and what, if anything, the client is asked to pay.

Then make one of four honest decisions

1. Charge for it: the work is additional and priced as such.
2. Exchange it: swap it for something already in scope of similar size.
3. Absorb it deliberately: a relationship investment, recorded as a choice with a known cost.
4. Decline it: the work does not belong in this project, and saying so early is kinder than saying so late.

All four are legitimate. Absorbing is only a problem when it happens by default, because the cost lands somewhere — usually in the margin, sometimes in the team's evenings.

Close the loop

When a change is agreed, update the plan and the commercial baseline together, and keep the trail: what was requested, what it was assessed to cost, what was decided, who approved it and when. That record is what turns an awkward end-of-project conversation into a short one.

What this changes about the client relationship

Teams worry that a change process makes them look rigid. In practice the opposite tends to happen: clients get a clear, fast answer about cost and consequence, and the goodwill you spend absorbing work becomes visible rather than invisible.