Why variation management is high-stakes
Every UK construction project has variations. The question is whether the consultancy controls them or they control the consultancy. A project with 5 variations is a non-event. A project with 50 variations, half undocumented, is a commercial dispute waiting to surface.
Variations are unavoidable because design is never complete at contract signing. New information emerges from site investigation; the client refines requirements; statutory consultations require changes; sub-contractor input drives buildability adjustments. The role of the consultancy isn\'t to prevent variations — it\'s to manage them with discipline.
Done well, variation management protects margin, preserves the client relationship, and provides clean evidence for any future dispute. Done poorly, it accumulates a fog of "we agreed something" conversations that resolve unfavourably six months later.
The JCT variation lifecycle
Under JCT contracts (Standard Building, Design and Build, Intermediate, Minor Works), variations follow a relatively informal process. The contract administrator (architect or PM) issues a written instruction; the contractor prices it; the consultant agrees the price; the variation is added to the contract sum and implemented.
The simplicity is JCT\'s strength and weakness. Variations can move through the process in days, which is good when scope clarifies quickly. But the lack of structured timelines means variations can also drift for months without resolution — particularly when the contractor is in dispute about scope or value.
JCT requires instructions in writing (or confirmed in writing within seven days). Site verbal instructions are a leading source of dispute. The discipline that makes JCT variation management work is rigorous instruction documentation. Most consultancies fail here, accepting verbal instructions and meaning to write them up later. Later doesn\'t come.
NEC compensation events
Under NEC contracts, the equivalent of a variation is a compensation event. NEC\'s process is more formal than JCT. It runs five steps: notification, instruction to quote, quotation, assessment, implementation. Each step has contractually defined timelines — typically eight weeks for notification, three weeks for quotation.
The discipline is built into the contract. NEC4 also mandates an early-warning system: any party who becomes aware of an event that could affect cost, time, or performance must issue an early warning notice. The early-warning system is the most underrated feature of NEC; in the projects that genuinely use it, surprises are rare.
Consultancies coming from a JCT background often find NEC paperwork-heavy. The reality is that the formality protects both parties. Missing the eight-week notification window can cost a contractor hundreds of thousands of pounds; missing the assessment deadline can cost the client equally. The discipline is worth learning.
Capturing programme impact
Cost impact is the easy part of variation management. Programme impact is where most consultancies fall down. A variation adds three days to the programme; the cost is captured on the variation record; the programme impact lives separately, usually in P6 or Asta. The reconciliation between them is manual and inconsistent.
The consequences are predictable. The client receives a cost number that doesn\'t match the date impact. The contractor claims an extension of time the consultant hasn\'t fully accepted. The variations log says +14 days net; the master programme says +21 days net. Nobody is sure which is right.
The discipline is to capture cost and programme impact on the same variation record at the moment of approval. If a variation adds £18,000 and 7 days, both numbers are recorded together with the variation reference. The net programme impact across all approved variations is reconciled with the master programme on a regular cycle. The numbers presented to the client match.
The audit trail nobody maintains
Six months after practical completion, the client questions a £42k variation that landed in approved cost. They want to know who asked for it, when, what was agreed, and on what basis. The consultancy that maintained a structured audit trail has a five-minute conversation. The consultancy that didn\'t spends three days reconstructing emails and meeting minutes.
The audit trail every variation needs: the originating instruction (with date, author, reference), the contractor\'s quotation (with date and value), the consultant\'s assessment, the approval (with date, author, approval level), and any client correspondence relating to the change. Each of these is a single small artefact; the discipline is keeping them attached to the variation record.
Most UK consultancies maintain this in scattered email threads, meeting minutes, and Excel comment cells. The information is technically present but not retrievable. A platform-based variation log keeps the audit trail attached at source, queryable in seconds.
Where consultancies lose control
Three patterns appear consistently in projects where variations escape control. Pattern one: verbal instructions. Site decisions are agreed in conversation; nobody writes them up; six months later the contractor claims for work nobody remembers authorising. This pattern alone accounts for a majority of variation disputes on UK construction projects.
Pattern two: pending variations not recorded. A variation is instructed but not yet priced. It sits in limbo — instructed but not in the variations log, anticipated but not committed. The cost report under-states the project picture. The client is surprised at month-end when half a dozen pending variations land at once.
Pattern three: pricing drift. A variation is priced at instruction; the price is "agreed in principle"; the formal agreement is deferred; weeks pass; the contractor revises the price upward citing changed circumstances. The consultant either accepts the revision or fights it; either way, the discipline of agree-on-instruction is lost.
The countermeasures are simple to state and harder to maintain. Every instruction in writing. Every variation logged the same day it\'s instructed. Every price agreed within a defined window or escalated. The consultancy that holds these three lines runs cleaner projects.