Scope creep

Scope creep is different from a planned change. Changing your mind is normal and healthy; the problem is when the change happens informally, so nobody updates the price or the deadline. Each request looks small ("can we just add a newsletter signup?"), but ten of them can add weeks.

It hurts both sides. The client ends up with a late project and a tired team, and the supplier either absorbs unpaid work or sends an invoice the client did not expect.

How it works

Creep usually starts where the scope of work is vague. If the agreement says "blog" without defining categories, authors or search, every one of those becomes a negotiation. It also grows when several stakeholders give feedback separately, when new people join halfway through, or when a competitor launches a feature and someone wants it too.

The control is a simple change process: write down the request, estimate its effect on time and cost, and decide whether to add it, swap it for something else or move it to a later phase.

There is also hidden creep, where the request is not a new feature but a higher standard: "make it work on older phones too", "add three more revision rounds", "can the admin export to Excel?". These sound like details but can take as long as a new page. A good scope states quality limits such as supported browsers and revision counts so these are visible too. Creep is harder to see in time-based contracts, because there is no fixed price to break. The budget simply drains faster than expected. In fixed-price contracts it shows up as tension: the supplier starts refusing requests or the quality of later work drops because the hours have run out. In both cases the fix is the same written change process, applied consistently from the first week rather than introduced after things have gone wrong.

Example

A restaurant agrees a site with a menu page, reservations link and gallery. During build the owner asks for online ordering, then a loyalty programme, then a second language. Each is mentioned in passing on a call. Two months later the launch has slipped past the summer season. With a change process, online ordering might have been added for a clear fee and the rest moved to phase two, and the site would have launched on time.

A simple way to spot creep on your own project is to compare the current task list against the signed scope every couple of weeks. In the restaurant's case, that comparison would have shown three large items with no price attached, which is the moment to stop and decide.

Why it matters for your business

Unmanaged creep is one of the most common reasons web projects run late and over budget. Every week of delay is a week without the leads or sales the new site was meant to bring. Saying "not now" to a good idea feels wasteful, but shipping a smaller first version on time and improving it with real data usually beats a bigger launch months later. That said, some changes should be accepted: if research shows a feature is essential, adding it is the right call, as long as the budget and dates move too. Ask your supplier for a running list of change requests with their cost and status; if no such list exists, creep is probably happening unrecorded.

Common mistakes

• Agreeing to "quick" additions on a call without writing them down or estimating them.
• Starting with a brief so vague that every feature is open to interpretation.
• Letting several people send feedback directly to the developers instead of through one decision-maker.
• Treating every new idea as urgent instead of keeping a list for the next phase on the roadmap.

Questions people ask

How do you prevent scope creep?

Agree a detailed scope of work, name one decision-maker, and route every new request through a written change process with a cost and time estimate. Keep a "later" list so good ideas are captured without derailing the current phase.

Is scope creep always bad?

No. Some additions are genuinely needed once the team learns more. The problem is unmanaged creep, where work grows without the budget and timeline changing. A change that is discussed, priced and approved is simply a revised plan.

Who is responsible for scope creep, the client or the agency?

Usually both. Clients make the requests, but agencies often accept them informally to keep the relationship smooth. The agency is generally best placed to flag a request as out of scope and explain what it would cost.