Introduction
Most construction businesses have some form of variation process. Very few of them would describe it as bulletproof.
The gap between the two usually looks something like this. An instruction arrives. Someone on site acknowledges it verbally and the work begins. A variation request lands from the subcontractor six weeks later. The QS tries to work out what was instructed, when, and by whom. The records are patchy. The pricing is the subcontractor's own. The agreement, if it is reached, takes three times longer than it should.
Meanwhile, the corresponding upstream variation has not been submitted. Or it has been submitted at the wrong value. Or it has been submitted and is sitting in the client's inbox, unacknowledged.
A bulletproof variation approval workflow does not prevent changes from happening. Changes are inevitable. What it does is ensure that every change, from first instruction to final agreement, is managed through a process that protects your commercial position.
This article explains what that process looks like, why it matters, and how to build it across a commercial team.
Why Variation Workflows Break Down
Understanding where variation processes fail is the starting point for fixing them.
No single point of authority. On many projects, instructions come from multiple directions. The client's architect. The project manager. The employer's agent. A site visit observation. When it is not clear who has authority to instruct a variation, instructed work slips through without being captured.
Instruction and execution happen simultaneously. The commercial discipline of getting an instruction confirmed before work begins is constantly under pressure from site delivery. A subcontractor is already mobilised. The client needs the change done now. The instruction gets issued retrospectively, if at all.
No tracking system. Variation logs in separate spreadsheets, maintained by individual QSs in different formats. When a project has three subcontract packages each with their own variation correspondence, and an upstream position that does not map to any of them, the picture is fragmented.
Approval is not the same as agreement. Approving a variation internally, deciding it should proceed, is different from agreeing a value with the client or the subcontractor. Many commercial teams conflate the two, assuming that an approved variation is a paid variation. It is not.
No escalation path. When a variation is disputed, whether downstream by the subcontractor or upstream by the client, there is no defined process for what happens next. It sits in the log, marked as disputed, and nothing moves.
The Five Stages of a Bulletproof Variation Workflow
Stage 1: Instruction Capture
Every potential variation should be captured at the point of instruction, before the work begins where possible.
This means a clearly defined process for who receives instructions, how they are logged, and what information is recorded. At minimum: who gave the instruction, when, in what form (written or verbal), and what work was instructed.
Where instructions are received verbally, they should be confirmed in writing to the instructing party immediately, whether that is the client, their representative, or a subcontractor. The confirmation creates the contemporaneous record that the commercial process needs.
Some businesses appoint a specific person on each project to own the instruction log. This removes ambiguity about who is responsible for capturing new instructions and ensures nothing falls through the gap between site and commercial.
Stage 2: Internal Assessment and Approval
Before a variation is instructed downstream or submitted upstream, it should go through an internal assessment.
For downstream variations (instructions to subcontractors): does the instruction trigger a contractual entitlement for the subcontractor? Is there an agreed rate for the work? Has the corresponding upstream entitlement been identified?
For upstream variations (submissions to the client): is there a clear entitlement under the main contract? What is the correct valuation basis? Is the submission within the contractual notification period?
The internal assessment should have a defined approval authority. Not every variation needs to go to the commercial director, but there should be a clear threshold above which senior sign-off is required. This is not bureaucracy; it is commercial governance.
RICS guidance on construction commercial governance identifies defined approval authorities and documented decision trails as essential elements of effective commercial risk management.
Stage 3: Upstream Submission
Every downstream variation instruction should trigger an upstream submission review. The question is always: does this add cost that is recoverable from the client?
If yes, a corresponding upstream variation should be drafted and submitted within the contractual period. The upstream submission should reference the relevant instruction, provide a clear scope description, and be priced using the contract rates or agreed valuation basis.
Upstream submissions should have a tracking reference and a submission date. The commercial team needs to know exactly which variations have been submitted, when, and what the current status is.
The workflow should make it impossible for a downstream variation to be approved without the upstream submission being considered. The link between the two is where margin is protected or lost.
Stage 4: Agreement and Certification
A variation is not complete until it is agreed in writing by both parties and reflected in the certified value.
For downstream variations: the subcontractor's claim has been assessed, a value has been agreed, and a variation order has been issued confirming the agreed amount.
For upstream variations: the client has agreed the variation in writing, confirmed the amount, and the agreed value is included in the next interim certificate.
Until both of these are achieved, the variation remains a risk item in the CVR, not a settled figure. The workflow should include follow-up milestones for chasing agreement on outstanding variations, not just submission dates.
StoneRise's commercial management software connects the downstream and upstream variation workflows in a single system, with automated status tracking from instruction through to certified value. Every variation has a clear status: instructed, submitted, under review, agreed, or certified.
Stage 5: Dispute Resolution
Where a variation is disputed, either by the client refusing to agree the upstream value or a subcontractor disputing the downstream assessment, the workflow should define what happens next.
A structured response to a dispute includes: providing the supporting information requested, following up within a defined period, escalating to senior commercial management if the dispute is not resolved within an agreed timeframe, and maintaining a complete correspondence record.
Disputes that are not actively managed do not resolve themselves. They compound over time as records become harder to reconstruct and both parties' positions harden. The workflow needs an escalation path so that disputes move through a resolution process rather than sitting indefinitely.
Practical Steps for Implementation
Define who can instruct. Publish a list of the individuals authorised to issue instructions on each project, both upstream (client's team) and downstream (your team to subcontractors). Instructions from anyone outside this list should be flagged and confirmed before work proceeds.
Create a single register per project. One variation register per project, maintained by a named individual, covering all downstream and upstream variations. Format should be consistent across every project so that commercial directors can review and compare without having to interpret different structures.
Set submission timescales. The internal standard should be that upstream submissions are made within a defined number of days of the instruction, not when there is time. Most contractual notification periods are short. Matching that urgency internally is essential.
Review the register at every commercial meeting. The variation register should be a standing agenda item. Outstanding submissions, unresolved disputes, and variations approaching agreement should be reviewed, not filed. The meeting should drive action, not just record status.
Link to the CVR. The CVR should draw directly from the variation register: downstream variations feed the cost forecast, upstream variations feed the value forecast. A CVR that is disconnected from a live variation register is not giving you a reliable commercial picture.
For further context on what good upstream variation management looks like in practice, see our article on main contract variations.
Conclusion
A bulletproof variation workflow does not eliminate disputes or prevent contractors from trying to submit inflated claims. What it does is ensure that your commercial team is always in the strongest possible position: records are current, submissions are timely, agreements are documented, and disputes have a clear path to resolution.
The businesses that manage variations most effectively are not necessarily better resourced than their competitors. They have better process. And better process is a choice.
Build Your Variation Workflow in StoneRise
StoneRise gives commercial teams a structured variation management workflow: instruction capture, downstream assessment, upstream submission, agreement tracking, and live CVR integration. One system from instruction to certification.
FAQ: Variation Approval Workflows in Construction
What should a variation approval workflow include?
A complete variation workflow covers five stages: instruction capture, internal assessment and approval, upstream submission, agreement and certification, and dispute resolution. Each stage should have defined responsibilities, timescales, and a documentation standard.
Who should have authority to approve variations on a construction project?
This depends on the value and nature of the variation. Most businesses define a tiered authority: a QS can approve low-value variations within a defined threshold; a commercial manager approves mid-range variations; a commercial director or senior management approves high-value or contractually complex variations. The thresholds should be set and published at the start of each project.
What is the difference between approving a variation and agreeing a variation?
Approving a variation is an internal decision that the change should proceed and will be instructed or submitted. Agreeing a variation is the bilateral confirmation of the value between contractor and client (upstream) or contractor and subcontractor (downstream). Approval is within your control; agreement requires the other party.
How should variations be tracked across multiple projects?
Each project should have its own variation register in a consistent format. At portfolio level, commercial directors should be able to review the outstanding variation position across all projects without needing to interrogate individual spreadsheets. This is one area where software has a clear advantage over spreadsheet-based tracking.
What is the most common reason variation workflows fail?
The instruction is given and the work starts before the commercial process has caught up. From that point, the variation is always being managed retrospectively: reconstructing records, pricing without agreed rates, submitting late. Building a culture and a process where instructions are captured before execution is the most impactful change a commercial team can make.
