A project rarely loses commercial control through one dramatic variation. It loses control through many small decisions that become irreversible before anyone sees their combined effect.
Variation clauses exist because projects change.
Clients refine requirements. Designers correct or complete information. Site conditions reveal new needs. External factors alter constraints. The Week 11 material identifies these as recurring causes of variation and asks a practical question: how should changes be controlled so they do not drive the project over budget?
The supplied AS 4000—1997 historically provides a structured mechanism for written variations, proposed variations, contractor estimates of program and cost effect, and pricing.
The deeper strategic lesson is straightforward:
A variation is not merely an instruction to change work. It is a decision to alter the commercial baseline.
The Strategic Context
Projects manage change through several systems at once.
Design teams revise drawings.
Operations teams request functionality.
Project managers manage schedule.
Quantity surveyors assess price.
Contract administrators govern entitlement.
Finance tracks budget.
If these functions act separately, the same change can look different depending on who is viewing it.
To the engineer, it may be a technical improvement.
To the contractor, it may be additional scope.
To the planner, it may affect the critical path.
To the principal, it may create a future operating benefit.
To finance, it is a budget movement.
The variation system has to reconcile all of those perspectives before the organisation commits.
What Leaders Commonly Misread
The first mistake is assuming a small variation is low risk because its immediate price is small.
A modest change can trigger delay, rework, procurement disruption or interface effects that exceed the direct cost.
The second is focusing on valuation only after work has started.
Once labour and materials are committed, negotiating leverage falls.
The third is treating verbal instructions as harmless operational coordination.
A direction that changes the required work can have commercial consequences even if no one used the word “variation”. The enforceability and treatment of informal or constructive variations depend on the contract and applicable law. [FACT CHECK REQUIRED]
The fourth is controlling client-requested changes while overlooking design-development changes, consultant corrections or external requirements.
The fifth is evaluating each variation independently without asking what the cumulative change is doing to the original project business case.
Reframing the Issue
Variation governance should operate as a commercial change gate.
Before changed work proceeds, leadership should understand five dimensions:
- cause — why is the change required?
- authority — who can approve it?
- scope — what baseline is changing?
- commercial effect — what cost and price consequences arise?
- time effect — what happens to the program and completion date?
For major changes, add a sixth dimension:
- benefit effect — does the change improve, preserve or weaken the intended project outcome?
This reframes variation approval from paperwork into investment decision-making.
Strategic Analysis
The supplied AS 4000—1997 historically allows the superintendent to direct defined categories of variation before practical completion and establishes a hierarchy for pricing. It also contemplates proposed variations where the contractor provides estimates of cost and program effect before a direction is finalised.
That sequence is strategically valuable.
It creates a window in which the principal can understand consequences before commitment.
The Week 11 material similarly recommends assessing, quoting and approving variation activity before commencement where possible.
The phrase “where possible” matters.
Projects sometimes face urgent work, safety issues or time-critical conditions. In those cases, governance needs a rapid pathway rather than abandonment of control.
Speed should change the process duration, not the requirement for evidence.
Cause Matters
A variation register should not record only price.
The cause of change is strategically important.
If a large proportion of changes come from client decisions, the project may have weak scope governance.
If consultant corrections dominate, design maturity or assurance may be weak.
If unforeseen conditions dominate, front-end investigation may have been insufficient or the risk allocation may be operating as intended.
The Week 11 slides include a generic 40/20/40 diagram allocating variation causes among client, consultants and unforeseen work. That statistic is not supported strongly enough to generalise and should not be republished as contemporary evidence. [FACT CHECK REQUIRED]
The useful principle is to measure the project's own cause profile.
Strategic Analysis: Change Has a Reversibility Curve
The timing of a variation matters because the cost of changing direction usually rises as delivery advances.
A requirement altered during concept design may affect drawings and estimates. The same requirement altered after procurement may require supplier renegotiation. After fabrication, it can create rework. After installation, it can affect commissioning, access and operations.
The project should therefore distinguish between changes that are still reversible and changes that have crossed a commitment threshold.
A hypothetical hospital-project example illustrates the point. A user group requests a revised equipment layout. Early in design, the change may be relatively simple. After services are installed, the same request can affect electrical capacity, mechanical systems, structural supports, testing and programme. The visible change is one layout decision; the commercial effect is a chain of dependent changes.
Variation governance should make those dependencies explicit.
This also helps leadership challenge late preference changes. Not every beneficial idea deserves implementation immediately. Some changes should be deferred to a future operational improvement because the current project's reversibility is already low.
The executive question is not merely “Can we do this?” It is “Is this the right point in the lifecycle to do it?”
That distinction protects both project economics and portfolio capacity.
Decision Framework
Use a Variation Decision Record containing seven fields.
1. Trigger
What event or requirement created the change?
2. Baseline
Which scope, drawing, specification, program or requirement changes?
3. Authority
Who is contractually authorised to approve or direct it?
4. Cost
What is the estimated direct and consequential commercial effect?
5. Time
What is the schedule, milestone or EOT effect?
6. Risk
What new risk is created or removed?
7. Benefit
Why is the change worth making?
This record should precede commitment where circumstances permit.
From Strategy to Execution
Immediate action: require every proposed variation to identify cause, authority, cost, time and affected baseline.
Medium-term capability building: integrate technical change control with the commercial variation register so drawing revisions cannot bypass budget governance.
Long-term strategic positioning: analyse variation causes across the portfolio. Repeated causes should lead to changes in design maturity, procurement planning, contract allocation or client decision-making.
This is how variation data becomes organisational learning.
Signals to Monitor
Watch for work starting before price or time effects are understood, large numbers of “pending” changes, verbal directions, consultant instructions bypassing commercial approval, contractor quotations arriving after work is complete, approved variation value rising faster than contingency, or design revisions that cannot be traced to a commercial decision.
Another signal is a project team that can report total variation value but cannot explain why the changes occurred.
Questions for the Leadership Team
- What is causing our variations?
- Who can legally and commercially authorise them?
- What changed in the baseline?
- Are we considering time and consequential effects before approval?
- Which changes are preserving benefits and which are adding preference?
- What portion of contingency is being consumed by recurring causes?
- What should future projects change to prevent the same variation pattern?
Closing Perspective
Change is normal.
Uncontrolled commitment is not.
A strong variation process makes the commercial consequence visible before the organisation loses the ability to choose. That is why variation governance belongs at the centre of project control.
Related article: A Variation Register Is an Executive Control System
Related article: Which Contract Document Controls? Managing the Evidence Behind the Deal
Related article: Paying More for the Same Work: The Contract Variation Problem Leaders Underestimate
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.