Scope Creep Is Not a Personality Problem: Give Every Project a Change-Control Route

A customer asks for “one small extra”. Your team agrees because it sounds quick. Then the extra needs another meeting, a revised document and two more rounds of comments.

Nobody meant to create a problem. But the project now carries more work, more time and more risk than the original price allowed.

This is often called scope creep. The name can make it sound as though the customer is being unreasonable or the delivery team lacks discipline. Usually, the real problem is simpler: the business has no clear route for handling a reasonable change.

Growing businesses do not need to stop change. They need to make it visible, assess it and decide what happens next.

Start with a usable baseline

Change control only works if people can see what is changing. That means the original scope needs to be clear enough to use as a baseline.

At minimum, the project record should say:

• what will be delivered;

• what information or action the customer must provide;

• the timetable and key dependencies;

• the price and payment stages;

• how many review rounds or meetings are included;

• what is outside scope; and

• who can approve a change for each side.

This does not require a forty-page contract for every job. It does require enough clarity for the delivery team and customer to recognise when a request changes the work.

Treat a new request as a decision, not an interruption

The Government Project Delivery Function describes the purpose of change control as making sure only beneficial or necessary changes to a baseline are implemented. Its guidance also warns that unmanaged changes can create scope creep and breach time and cost constraints.

The same principle is useful for a small commercial project. When a request arrives, pause long enough to answer five questions:

1. What exactly is being requested? Turn a loose conversation into a short written description.

2. Why is it needed? A change linked to the customer’s real objective is easier to assess than a preference with no clear outcome.

3. What does it affect? Consider price, delivery date, workload, dependencies and the agreed result.

4. Who decides? The person doing the work may not have authority to give away extra time or change the deadline.

5. What is the outcome? Approve it, reject it, defer it or ask for more information.

That is change control in practical form. It gives both sides a route to say yes without pretending the extra work is free.

Use a one-page change record

A useful change record can be short. It might contain:

• project and customer name;

• date and request number;

• requested change;

• reason for the change;

• impact on deliverables;

• price adjustment;

• timetable adjustment;

• assumptions or dependencies;

• decision and decision-maker; and

• approval date.

Keep the language plain. The aim is not to make the customer navigate a new contract every time. The aim is to leave a reliable record of what changed and what did not.

Give the team a holding line

Scope creep often enters through a helpful employee who feels pressured to answer immediately. Give the team a sentence they can use without sounding obstructive:

“That may be possible. I need to check the effect on the agreed scope, price and timing before I confirm it.”

This protects the relationship because it does not reject the request. It also protects the business because it does not commit before the impact is known.

Make small changes proportionate

Not every adjustment needs a formal document and senior approval. Set sensible thresholds.

For example, a named project lead might approve a change that uses less than one hour and does not affect the deadline. Anything above that threshold might need a written price or timetable change. A request that changes the core deliverable might require a new scope altogether.

The right thresholds depend on the value and risk of the work. What matters is that the team knows them before the customer asks.

Watch for patterns, not only individual requests

A change log is useful management information. Review it after the project or once a month:

• Which extras appear repeatedly?

• Which parts of the scope are often misunderstood?

• Are sales promises reaching the delivery team?

• Are review rounds consistently underestimated?

• Is one type of customer change driving most of the lost margin?

Repeated “extras” may belong in the standard offer or need clearer exclusions. Change control can therefore improve pricing and product design, not only protect one project.

The commercial result is clarity

A good change-control route does not make a business inflexible. It makes flexibility deliberate.

Customers can ask for what they need. The delivery team can assess it. Decision-makers can see the effect before committing. The business can protect margin and deadlines while keeping a clear record of the agreed result.

If projects regularly expand through messages, meetings and informal promises, the answer may not be a tougher conversation. It may be one shared process that turns each request into a visible decision.

Are project changes living in messages and meetings? The Project Change-Control Pack gives agencies, consultancies and project-based businesses a repeatable route for recording requests, assessing the effect on scope, price and timing, and getting a clear decision. It is £495 + VAT for the fixed-scope pack; main-contract drafting or renegotiation is outside that fee. See whether it fits your business.