The Quiet Addition: Detecting Scope Drift Before It Reaches the Programme

Scope drift is rarely announced by a variation order. It tends to arrive quietly: a revised finish specification in an email, a request to “just move that wall slightly”, or a drawing circulated for information that later becomes the basis for work. By the time the commercial effect is visible, the programme has usually absorbed several unofficial changes. The task for UK commercial teams is not to eliminate every request. It is to detect the point at which a request starts to alter the agreed scope, and to deal with it while the cost and time consequences are still manageable.

At SEH Ltd, the commercial view is straightforward: an undocumented addition is not a saving. It is a deferred decision with interest attached. The following five signals are worth monitoring on any commercial project in 2026, whether the delivery model is traditional, design and build or a framework arrangement.

1. The adjective that changes the obligation

A single adjective can shift a specification without triggering a formal change control process. “Standard” becomes “premium”. “Equivalent” becomes “approved equivalent”. “Where practicable” becomes “where reasonably practicable”. Each refinement may appear minor in isolation, but the cumulative effect on procurement, installation and sign-off can be substantial.

Commercial teams should watch for language that introduces a new performance expectation without a corresponding instruction. The test is not whether the wording sounds important. The test is whether it changes what must be supplied, by whom, and by when. If it does, it belongs in the change record, not in a general email chain.

2. Drawings marked “for information”

Information status is not a neutral label. A drawing issued for information can quickly become the reference point for site activity, particularly when programme pressure is high. The risk is that the drawing is treated as instruction by the delivery team while remaining unofficial for commercial purposes.

A useful discipline is to record every drawing issue with its status, date and stated purpose. When a drawing marked for information is later relied upon, the project team should be able to show when that reliance began and whether the commercial position was updated. If the answer is unclear, the drawing has probably crossed from information into instruction without the necessary controls.

3. The meeting action that becomes an instruction

Minutes are often where scope drift gains its first credible foothold. An action such as “confirm whether additional sockets are required” is a request for information. An action such as “install additional sockets” is an instruction. The difference matters.

UK commercial teams should review meeting actions for verbs that commit resource. Words such as install, supply, revise, relocate and complete should prompt a check against the agreed scope. Where an action implies work, the team should confirm whether it is already included, whether it is a variation, or whether it is still subject to a decision. Leaving the action open may keep the meeting harmonious, but it does not keep the budget intact.

4. Programme optimism in the weekly update

The programme is an early warning system as well as a delivery tool. Scope drift often appears first as unexplained float being consumed, a sequence being revised or a trade package being brought forward without a clear instruction. If the programme is absorbing additional work without a corresponding change to the commercial record, the project is likely carrying an unpriced obligation.

Commercial and delivery teams should compare the current programme against the scope baseline at regular intervals. The question is not simply whether the programme has changed, but whether every change can be traced to an agreed instruction. Programme movement without commercial explanation is a signal worth investigating.

5. The repeated favour

A one-off favour may be commercially tolerable. A repeated favour is a pattern, and patterns become expectations. Requests to “just add this to the next visit”, “use the spare material” or “deal with it while you are there” can appear efficient on site. Over time, however, they normalise unpaid work and make the original scope harder to defend.

A simple log of informal requests is often enough to expose the pattern. The log does not need to be elaborate. It should record what was asked, by whom, when, and what commercial action followed. If the same type of request appears more than once, the team should consider whether the scope needs clarification or the change control process needs reinforcement.

A short weekly routine

Detection is more reliable when it is routine rather than reactive. A thirty-minute weekly scope clinic can be sufficient on many projects. It should involve the commercial lead, the project manager and, where appropriate, the site supervisor.

The routine has four steps. First, review all email and meeting requests from the previous week for language that may imply additional work. Second, check drawing issues and revised documents for changes in status or content. Third, compare programme movements against the scope baseline. Fourth, agree an action for every item that may constitute a change: include, clarify, price or reject. Each action should have an owner and a date.

The purpose is not to create bureaucracy. It is to prevent small, ambiguous requests from becoming large, disputed facts. A documented decision taken early is usually cheaper than a retrospective argument conducted under programme pressure.

Keeping the record commercial

Scope drift is a commercial risk before it is a contractual dispute. Teams that monitor language, document status, meeting actions, programme movement and informal requests are better placed to protect both budget and programme. They are also better placed to maintain constructive relationships, because the conversation moves from “who agreed what” to “what does the record show”.

For UK commercial clients in 2026, the discipline is not about resisting every change. It is about ensuring that every change is visible, assessed and owned. The quiet addition is only harmless while it remains identified. Once it enters the programme without a decision, it has already begun to cost.