PMI's 2018 Pulse of the Profession found that 52 per cent of projects completed in the previous year had experienced scope creep, up from 43 per cent five years earlier. In eight years running NPI and capital programmes, I never once saw it arrive through the front door.
Nobody submits a change request titled "uncontrolled expansion of scope". Preventing scope creep on a manufacturing project is therefore not mainly a question of enforcing your change control procedure. It is a question of noticing the moment a conversation quietly becomes a commitment, and getting that moment into the project record before it hardens into an expectation.
Because that is how scope actually moves. A supplier mentions a better connector on a call. A sponsor asks a casual question at the end of a design review. A process engineer says "while the line is down anyway". The schedule finds out weeks later.
What Scope Creep Actually Is
The standard definition is the uncontrolled expansion of product or project scope without corresponding adjustments to time, cost, and resources. The important word is uncontrolled. Scope change on a live project is normal and often correct.
The difference between a healthy change and creep is not the size of the work. It is whether the change passed through a decision point before the team started carrying it. Managed change goes through assessment and approval. Creep goes through a conversation and straight into somebody's workload.
The Three Conversations That Move Scope
Watch a manufacturing project drift and you will find the same three conversational patterns underneath, again and again.
1. The "while we're at it"
An equipment installation has the guarding off, so someone asks for a second sensor bracket while access is easy. A fixture is being machined anyway, so a spare set gets added. Each request is individually reasonable, which is precisely what makes it dangerous.
The logic of "while we're at it" is efficiency logic, and it is often locally correct. But five locally sensible additions, made across five different conversations with five different people, are a schedule slip that nobody decided to take.
2. The clarification that grows
"We assumed the fixture price included calibration." "We took it that commissioning covered operator training." This pattern surfaces as a clarification, but what is really happening is that two parties priced two different scopes, and the gap is only being discovered now.
The dangerous version is when the delivery team absorbs the gap silently, as goodwill. The work was never planned, never costed, and now it is being done anyway, invisibly.
3. The sponsor drive-by
A senior stakeholder asks, near the end of a review, "could it also handle the EU variant?" It is phrased as a question. Because of where it came from, the room hears a direction.
Nobody formally decided anything. But two engineers leave the meeting and start designing for the EU variant, because declining an implied request from authority feels riskier than absorbing the work. This is the most expensive pattern of the three, and the least likely to be written down.
Scope creep is not a documentation failure at the point of doing the work. It is a documentation failure at the point of the conversation, weeks earlier.
Why Regulated Manufacturing Pays a Higher Price
In a commercial software environment, absorbed scope costs you velocity. In regulated manufacturing, the coupling between scope and everything downstream makes the same behaviour far more expensive.
A scope addition on a med-tech or regulated engineering project rarely stays contained to the work itself. It pulls on the requirements documents, the design outputs, the validation protocols, and the training records connected to it. Add a sensor to a line after qualification runs have started and you are not adding a sensor. You may be repeating IQ and OQ activity that had already passed.
The arithmetic is brutal and worth stating plainly. The engineering hours to fit the bracket might be eight. The re-verification and documentation chain it drags behind it might be eighty. The absorbed conversation captured neither number.
Capital projects amplify this through fixed windows. Line shutdowns are booked months ahead, launch dates are committed to customers, and validation slots are shared with other programmes. Scope added inside a fixed window does not extend the window. It compresses the testing at the end of it, which is exactly where you least want compression.
Why Your Change Control Process Does Not Catch It
Most regulated manufacturers have a change control procedure, and most scope creep happens in plain sight of it. Three reasons.
First, change control triggers on artefacts. A revised drawing, an updated specification, a document number. Conversations do not cross that threshold, so the process never sees them. By the time an artefact changes, the commitment is weeks old and half-built.
Second, each increment is individually sub-threshold. Nobody raises a change request for a bracket. Creep is not one large unauthorised change; it is an accumulation of small ones, none of which felt worth the form.
Third, raising a change has a social cost. After a friendly conversation, formalising the ask can feel adversarial, as if you are accusing a colleague of moving the goalposts. So people absorb the work instead, because absorbing feels cooperative. ISO 21502 is useful here precisely because it frames change control as a continuous management practice running through the whole project, not as an occasional piece of paperwork, and that framing gives a project manager cover to treat small conversational changes as legitimate objects of governance.
A Prevention System That Fits How Teams Actually Work
You will not stop the conversations, and you should not want to. The conversations are where the engineering happens. The system has to sit downstream of them, and it has to be cheap enough that people actually run it.
- Make the work breakdown structure the arbiter. If a piece of work does not sit under an existing WBS element, it is a change, by definition rather than by argument. "That is not in the plan" stops being an accusation and becomes a classification. This only works if the WBS is genuinely the shared reference for what the project contains, which is an argument for keeping it current and visible rather than buried in a file someone owns.
- Run a live assumptions and decisions log. The clarification-that-grows pattern feeds on unstated assumptions. A log that captures "fixture price assumed to include calibration" in week two turns a week-fourteen dispute into a week-three conversation. If you already keep a RAID log, this is the A and D of it, actually maintained.
- Apply a 48-hour write-down rule. Any conversation that touches scope gets one line in the project record within two days: who asked, what was asked, and the disposition. Absorbed as trivial, declined, deferred, or raised as a formal change. Most creep survives on ambiguity about whether anything was agreed. Writing removes the ambiguity while the memory is still fresh. This is a specific case of the meeting-to-record gap: the longer a scope conversation stays out of the record, the more it hardens into commitment.
- Make raising a change cheap. If logging a change takes 40 minutes of form-filling, people will absorb the work instead, every time. The effort to record a change must be lower than the effort to do the work unrecorded. Three fields is enough at the point of capture: what, who, first estimate of impact. Assessment can follow.
- Use stage gates as the backstop, not the net. At each gate review, put the baseline scope beside what has actually been delivered and committed, and ask one question: what are we now doing that was not in the charter? A gate is too late to catch creep cheaply, but it is exactly the right place to make the accumulation visible to the sponsor who has been causing some of it.
The Cost of Writing It Down
Silently absorbing a five-day ask costs five days, plus a precedent that asks are free. Logging the same ask costs about ten minutes and one slightly awkward sentence: "happy to look at that, I will log it against the project so we can see the impact".
In my experience the awkwardness evaporates within a few weeks, for an unexpected reason. Sponsors and functional managers start filtering their own asks before making them, because they know each one will become visible. The discipline does not just record the creep. It reduces the supply of it.
The Conversation Is Not the Enemy
Projects are steered by talking. A team that stopped discussing improvements, gaps, and possibilities would be failing in a much worse way. The risk was never the conversation.
The risk is the gap between what was said and what was recorded. Close that gap within 48 hours, every time, and most scope creep dies quietly before your schedule ever feels it. What remains becomes what it always should have been: a visible, costed decision that someone accountable chose to make.
Frequently Asked Questions
What is scope creep in project management?
Scope creep is the uncontrolled expansion of product or project scope without corresponding adjustments to time, cost, and resources. The key word is uncontrolled. Scope on a project is expected to change, but each change should pass through a decision point where its impact on schedule, budget, and risk is assessed. Scope creep is what happens when work grows without that assessment, usually through small additions that never felt significant enough to raise formally.
What is the difference between scope creep and change control?
Change control is managed scope change: a proposed addition or alteration is documented, its impact is assessed, and someone with the right authority approves or declines it before work proceeds. Scope creep is unmanaged scope change: the work expands through informal requests, assumptions, and conversational commitments that never pass through any decision point. The same piece of work can be either one. What decides it is whether the change was recorded and assessed before it was absorbed.
Why is scope creep more expensive in regulated manufacturing?
In regulated manufacturing, scope changes rarely stay contained to the work itself. A change to equipment, product design, or process typically pulls requirements documents, design outputs, validation protocols, and training records along with it. A small addition made after qualification runs have started can mean repeating those runs. The direct engineering effort of an added item is often a fraction of the cost of the re-verification, re-validation, and documentation chain it triggers. Fixed launch windows and booked shutdown windows amplify this further, because added scope inside a fixed window converts directly into overrun or compressed testing.
How do you prevent scope creep on manufacturing projects?
The most effective prevention combines a clear baseline with a low-friction recording habit. Use the work breakdown structure as the arbiter: if a piece of work does not sit under an existing WBS element, it is a change by definition. Record every conversation that touches scope within 48 hours, including who asked, what was asked, and how it was dispositioned. Keep the cost of raising a change request low, so logging a change is easier than silently absorbing the work. Then use stage gate reviews as a backstop, comparing delivered and committed scope against the baseline at each gate.
Should every scope conversation become a formal change request?
No, and attempting that usually kills the discipline within a month. Every scope-touching conversation should be recorded and given a disposition: absorbed as trivial, declined, deferred to a later phase, or raised as a formal change. Only the last category enters the change control process. The goal is not more paperwork. The goal is that no commitment exists only in conversation, so the cumulative picture of absorbed work stays visible to the project manager and the sponsor.
What has crept into your current project since the charter was signed?
I am talking to programme managers and engineering leads in regulated manufacturing about how scope moves between the baseline and the record. If you would like to compare notes, let us talk.
Book a 20-Minute Call