By the Operations Team: SPM
People often describe scope creep as a project becoming bigger than originally planned. That definition makes it sound obvious, as though someone has added a major new requirement and everyone can see that the scope has changed.
In practice, scope creep usually enters more quietly. It may begin when a client asks the team to inspect an additional piece of equipment, when a supervisor gives a verbal instruction to complete work outside the agreed scope, when restricted site access requires an extra mobilisation, or when another contractor leaves preparation work unfinished. Each addition may seem manageable on its own. The full effect only becomes clear later, when the project comes under pressure, resources stretch beyond the original plan and the team has already completed the extra work.
Requirements will change during some projects. The problem begins when teams accept additional work without considering how it will affect the programme, cost, resources and responsibility.
1. A small favour is accepted on site
Many changes begin with a seemingly harmless request: “While your team is here, can they also look at this?”
The task may take an hour. The team may already have the necessary equipment on site. Refusing the request can feel unnecessarily rigid, particularly when the team wants to maintain a good relationship with the client.
The risk is that small favours rarely remain isolated. One request leads to another, and the project begins carrying work that nobody included in the original price or programme. Because the team handles these requests informally, their cumulative effect may only become clear later.
The team should still recognise a small request as additional work. The level of administration can match the size of the task, but the request should not disappear simply because the team could accommodate it easily.
2. A verbal instruction is treated as approval
People often give instructions during site meetings, telephone calls or conversations between supervisors. The person receiving the instruction may assume that the person giving it has the authority to change the scope.
That assumption can become expensive. A client representative may understand the operational need for the work but may not have the commercial authority to approve it. Later, the organisation responsible for payment may argue that nobody formally authorised the variation.
The team then has to prove what the client requested, who made the request and why the work went ahead. Before the team acts, it should confirm whether the person giving the instruction has the authority to commit the client.
3. The delivery team fills gaps in the original scope
A scope may describe the expected outcome without explaining who must take responsibility for every part of the work. Once the project begins, the delivery team may discover gaps.
Someone must arrange access. Someone must provide drawings, remove existing equipment, prepare the work area or restore the site afterwards. When nobody has clarified those responsibilities, the team already on site may step in because waiting would delay the job.
The team then absorbs the work through action rather than agreement.
Clear exclusions and interface responsibilities matter as much as the list of included activities. Where the scope leaves room for doubt, the parties should settle responsibility before the delivery team quietly inherits the work.
4. Site conditions differ from what the team expected
Project teams price and plan work using the information available at the time. Once the team arrives on site, it may find different conditions.
Access may be restricted. Equipment may be in worse condition than the inspection suggested. Isolation periods may be shorter than expected. The team may need additional lifting equipment, temporary works or protective measures.
Teams sometimes treat these changes as part of “getting the job done”, even when they materially alter the way the work must be delivered. Before the workaround becomes the new baseline, the team should assess how it will affect time, resources and cost.
5. Programme changes create work that nobody recognises as additional scope
A client may change the sequence of work without changing the final deliverable. On paper, the scope may still look the same.
Operationally, the effect can be substantial. The team may need to mobilise more than once, keep equipment on site for longer, work outside normal hours or split activities that it originally planned to complete together.
Because the client has not added a new technical task, people may classify the extra burden as a scheduling issue rather than a scope change. Yet any programme change that increases labour, standby time, supervision, transport or equipment requirements also changes the cost of delivery. The team should treat it accordingly.
6. Another contractor’s unfinished work becomes your team’s responsibility
Industrial projects depend on several teams completing connected activities. When one contractor falls behind or leaves work incomplete, the next team faces a choice: stop and wait, or solve the problem so that the project can continue.
The second option often looks practical. It may also transfer another party’s responsibility into your scope without discussion.
Your team may need to correct preparation work, move equipment, provide temporary support, trace missing information or complete activities that another contractor should have finished before handover.
The team should record the condition in which it received the work and clarify who must correct it. Otherwise, the client may later treat the additional effort as part of the team’s original obligation.
7. A temporary solution becomes a permanent commitment
Projects often need temporary measures to overcome an immediate constraint. A team may install a provisional arrangement, provide temporary equipment or agree to support an activity until another party becomes ready.
Problems begin when the temporary measure remains in place without a clear end date. The organisation that introduced it may gradually take responsibility for maintaining, monitoring or replacing it.
What began as a short-term response then becomes an ongoing obligation, even though nobody formally added it to the contract.
Temporary arrangements should have a defined purpose, an owner and an endpoint. The parties should also agree who will carry the cost if the arrangement remains in place longer than expected.
8. Work begins before the variation receives approval
This is one of the most common ways scope creep becomes embedded in a project.
The team identifies the additional work, and everyone agrees that the project needs a variation. The client then asks the team to begin while the paperwork moves through the approval process because waiting would delay the project.
Once the work starts, the urgency shifts. The client already benefits from the progress, while the contractor carries the cost and waits for retrospective approval. By the time the commercial discussion takes place, the team may have completed most of the work.
In some situations, waiting will not be practical. Even then, the team needs clear authority, an estimate of the likely exposure and a limit on how far it may proceed before receiving formal approval.
Keeping change visible
Controlling scope creep does not mean refusing every request that falls outside the original plan. Projects change, and capable operations teams must respond.
The discipline lies in making each change visible before the team absorbs it into daily activity. Operations teams often solve problems quickly. That strength becomes a commercial risk when nobody can see where the original project ended and the extra work began.