Scope creep: protect project margin after the sale

The proposal is approved. Delivery has started. Then a client asks for one more output, another review round and a small change to the original brief. Each request sounds reasonable. Together, they can turn a commercially sound project into an overloaded team and a disappointing result.

For service businesses, scope creep deserves a place in the weekly commercial conversation. The aim is to make changes deliberately, with a shared view of what they require.

Define the work before judging the request

Start with a delivery baseline that people can actually use: agreed outcomes, deliverables, assumptions, client inputs, review rounds and acceptance criteria. A long proposal is less useful if the delivery team cannot explain what completion looks like.

At the sales-to-delivery handoff, ask three questions. What has the client bought? What must the client provide? Which decisions remain unresolved?

Capture the answers in the project workspace. Include promises made during sales discussions so delivery does not discover them halfway through production.

Separate a correction from an addition

Not every revision is scope creep. Fixing an output that fails an agreed requirement is different from adding a new requirement.

Use a simple classification:

• Correction: the work does not meet the agreed brief or acceptance criteria.
• Clarification: the request resolves an ambiguity that needs a shared interpretation.
• Variation: the request adds or changes a deliverable, audience, process or requirement.

Clarifications deserve attention. Repeated ambiguity may reveal a weak briefing process. Avoid automatically treating it as either unpaid work or a chargeable addition.

PMI's 1996 article on managing scope changes describes the value of an agreed baseline, documented changes and clear communication. These are durable management principles, rather than evidence of a new trend.

Give each variation a decision record

A useful change process can fit on one page. Record the request, its purpose, who needs it and the consequence of leaving it out. Then assess its effect on effort, capacity, dependencies, delivery date and fee.

Include work that is easy to overlook: coordination, testing, additional approvals and updates to other outputs. A new presentation format may also require new quality checks and a different approval sequence.

Give the request an owner and a decision date. Work waiting for a commercial decision should remain visible rather than disappearing into someone's task list.

Offer a choice that preserves the outcome

The answer need not be a flat refusal. Present workable options:

• Swap the addition for another planned item.
• Extend the timeline to accommodate the work.
• Add capacity and revise the fee.
• Defer the request to a later phase.
• Absorb the work as a deliberate commercial decision.

Show the effect of each option in plain language. A client can make a better decision when the trade-off is concrete: “We can include this additional workshop and deliver the final recommendations the following week.”

Agree the option before starting the additional work, and update the shared plan. The delivery team and client should be working from the same decision.

Make the change budget visible

A change budget is an internal planning allowance for expected uncertainty. It might cover a small amount of additional effort or a defined contingency. Choose it for the project; there is no useful universal percentage.

Track what consumes it. A buffer should not hide recurring failures in briefing, estimating or approval.

Hypothetical example: a service project has a fee of USD 12,000 and planned delivery costs of USD 8,000. An additional request requires USD 1,000 of delivery cost. If the fee stays unchanged and nothing else changes, the amount remaining after those delivery costs falls from USD 4,000 to USD 3,000.

The business may still choose to absorb the request. The point is to make that choice visible, alongside capacity and client value. These figures illustrate project contribution before other overheads; they are not a forecast.

Review the handoff every week

Keep a short weekly review between the commercial owner and delivery lead. Look at open changes, decisions awaiting agreement, unplanned hours and upcoming client inputs.

Resolve three things: who will discuss each request with the client, what the team can progress meanwhile, and whether the plan still matches the agreed work.

At project close, review the causes. If extra review rounds appear repeatedly, improve the proposal and approval process. If client inputs arrive late, make dependencies clearer. If sales promises exceed delivery assumptions, repair the handoff.

This connects business growth and transformation with everyday delivery decisions: how work enters the business, who owns the trade-offs and whether additional revenue creates worthwhile work.

Start with one active project

Choose a project with frequent additions. Compare the agreed baseline with current tasks, identify unresolved variations and introduce the one-page decision record.

Talk to Zendral about reviewing the gap between what your business sells and what its teams deliver. Bring one project and its recent changes so the conversation starts with a concrete operational problem.

More insights →