When Is a Change a Variation in Construction? 8 Checks Before You Proceed

A client representative asks for “one small change”. The project team sees a minor adjustment, so the contractor proceeds. Weeks later, commercial identifies a substantial cost and programme effect. The principal says no formal variation was instructed. The contractor says the work was clearly requested.

The contract administrator asks the question that should have been asked before the work started: did the request actually change the contractor’s contractual scope, and what process did the contract require?

That is the real issue.

In construction, the operational size of a change does not determine whether it is contractually significant. A change that looks minor on a drawing can affect procurement, labour, plant, sequencing, temporary works, testing, rework or programme logic. Equally, work that feels “extra” may already sit within the contractor’s original scope.

The starting point is therefore not the price. It is the contract.

Direct answer: when is a change a variation in construction?

A change may be a variation when it alters the work required under the construction contract and falls within the contract’s variation mechanism. The answer depends on the original scope, the contract’s definition of variation, who requested or directed the change, whether that person had authority, the required form of instruction and any applicable notice or procedural requirements.

Key takeaways

• “Small” is not a contractual category. A minor-looking change can carry significant cost, time or procurement consequences.
• Before calling work a variation, establish the original contractual scope.
• Work already required by the contract does not automatically become a variation because it was overlooked, underestimated or more expensive than expected.
• Check who has authority to direct a variation and what form the direction must take.
• A client request, revised drawing, design comment, email or site discussion should not automatically be treated as a valid variation instruction.
• Price, programme, procurement, notice and evidence should be assessed as early as the contract permits.
• The key question is not simply “Did something change?” It is “Did the contractor’s contractual requirement change?”

Start with the baseline: what did the original contract require?

The strongest way to decide whether a change is a variation is to compare the proposed work with the contractual baseline.

That baseline may include:

• scope documents;
• drawings;
• specifications;
• schedules;
• technical requirements;
• bills or schedules of quantities;
• design obligations;
• exclusions;
• tender clarifications;
• qualifications; and
• document-precedence provisions.

In a design-and-construct contract, it may also include performance requirements and obligations to complete or develop the design.

Construction Law Made Easy, produced by MinterEllison’s construction team, describes a variation generally as a change to the scope of works under a contract and emphasises that the first step is identifying the original scope. It also explains that an item already provided for in the contract is not a variation merely because the contractor later treats it as additional work.

That distinction sounds straightforward, but it is where many live-project disagreements begin.

Consider three simplified examples.

A client asks for an additional access door that is not shown or otherwise required by the contract. That may point towards a variation.

A contractor discovers that doors already required under the contract need ordinary components necessary to function. Those components may simply form part of completing the original obligation.

A design-and-construct contractor develops its design to satisfy an existing performance requirement. Depending on the contract, that development may remain within the contractor’s design responsibility rather than becoming a variation.

The practical question is therefore not:

“Did the work change from what the project team expected?”

It is:

“Did the contractual requirement change?”

A practical test: is this likely to be a variation?

This is a practical screening framework, not a legal test. Contracts define variations differently, and bespoke amendments can materially change the process.

Why a “minor” change can create a major commercial impact

Project teams often assess a change by looking only at the visible work.

Move a penetration. Change a finish. Shift equipment. Add a short length of pipework. Alter a room layout. Revise a cable route.

The direct quantity may be small, but the consequences around it may not be.

The change could require revised shop drawings, design review, demolition of completed work, remobilisation, replacement materials, cancelled orders, additional testing, altered temporary works or resequencing of downstream trades.

That is why the physical size of the requested change and its commercial significance are not the same thing.

The reverse is equally important.

An expensive item does not become a variation merely because the contractor did not price it adequately or did not expect the full effort involved. If the original contract already allocated the obligation to the contractor, increased cost alone does not necessarily convert it into changed scope.

Does a construction variation need to be formally instructed?

That depends on the contract, but formal instruction requirements are common.

The NSW Government construction procurement guide on managing variations explains, for the contracts and procurement environment it addresses, that variation instructions should come from the authorised principal’s representative and be in writing.

Construction Law Made Easy’s guidance on how variations occur similarly explains that an instruction should be issued in the manner and form prescribed by the contract.

Many contracts also provide a proposed-variation process.

Rather than immediately directing the changed work, the principal, superintendent or contract administrator may ask the contractor to provide information about:

• whether the change can be performed;
• likely price effects;
• programme consequences;
• procurement impacts; and
• other relevant project implications.

That process is commercially valuable because it allows the parties to understand the consequences before the change becomes embedded in the project.

Where the contract supports that approach, “assess first, direct second” is usually far safer than “build now, argue later”.

What if the client simply says, “Just do it”?

This is where operational urgency and contract administration often collide.

A request from a client representative may be commercially important, but the team should check whether that person is authorised under the contract to direct a variation.

The contract may reserve directions to a superintendent, principal’s representative, contract administrator or another defined role.

If authority is unclear, the contractor may need to seek confirmation from the authorised person or issue whatever notice the contract requires when it considers a direction to constitute a variation.

The precise response depends on the contract.

Proceeding without checking can create several problems:

• the principal may later say no authorised variation was directed;
• the contractor may struggle to establish the contractual basis for payment;
• cost records may not have been separated from base-scope work;
• programme effects may not have been assessed contemporaneously;
• the parties may disagree about whether the request was a clarification or a change; and
• subcontractor exposure may develop before the head-contract position is clear.

The phrase “we’ll sort out the paperwork later” should therefore be treated as a commercial warning sign.

Perfomir’s article on contract variation disputes in construction examines what can happen once scope, authority, notice and valuation issues harden into disagreement.

The better control is to recognise the possible variation before reaching that point.

What if the instruction is not labelled “variation”?

Labels are useful, but the project team still needs to examine what the communication actually requires.

A revised drawing, technical direction, design response, site instruction or email may change the contractor’s obligations even if nobody writes “Variation” on it.

Conversely, a document labelled “variation” does not necessarily prove that the work falls outside the original scope.

The useful comparison is:

What is the document called?

versus:

What does the document require us to do compared with the contract?

Some contracts require contractors to notify the relevant administrator if they believe a direction constitutes a variation even though the direction itself does not expressly say so.

Those clauses may also contain short contractual timeframes.

That makes early recognition important.

The commercial team should not wait until monthly valuation to decide whether a direction issued weeks earlier changed the contractual work.

Scope change or normal design development?

Design-and-construct projects make the distinction especially important.

A D&C contractor may already be required to develop the design, coordinate disciplines, satisfy performance requirements, resolve interfaces, complete design details and make the completed works satisfy the contractual requirements.

A later drawing that provides greater detail is therefore not automatically a variation.

The real question is whether the new requirement merely develops an existing obligation or alters the contractual requirement itself.

For example, a direction that changes required capacity, layout, dimensions, quality or the principal’s project requirements may point towards a variation pathway.

Holding Redlich’s discussion of variations under AS4902 illustrates how a standard-form D&C variation mechanism can address increases, decreases, omissions, changes in quality, altered positions or dimensions and additional work.

The commercial team should therefore avoid shortcuts such as “new drawing = variation”.

The original risk allocation still needs to be tested.

The event-to-contract pathway

A useful way to analyse the “small change” scenario is:

Project Event → Relevant Clause → Contractual Obligation → Notice Requirement → Potential Entitlement → Commercial Risk

Project event: the client asks the site team to relocate equipment.

Relevant clauses: scope, variation, direction, design, notice and programme provisions.

Contractual obligation: determine whether relocation was already required and whether the person giving the instruction had authority.

Notice requirement: check whether the contractor must notify that it considers the direction a variation, submit a quotation or identify time consequences.

Potential entitlement: assess possible price or time adjustment without assuming entitlement exists.

Commercial risk: consider rework, procurement, delay, disruption, subcontractor exposure, rejected variation claims and final-account pressure.

The value of this chain is that it turns an informal operational request into a structured contract review while the team can still influence what happens next.

What records matter?

A strong variation file should start when the potential change is identified, not when the monthly claim is prepared.

Perfomir’s variation claim documentation checklist provides deeper guidance on building that evidence trail once a possible variation has been recognised.

An 8-step response before the “small change” becomes a big problem

1. Capture the request. Record exactly what has been requested, by whom, when and through which communication.
2. Compare it with the contractual baseline. Check the scope, drawings, specifications, design obligations, exclusions and relevant document hierarchy.
3. Identify the correct contractual mechanism. Determine whether the issue belongs under variations, directions, discrepancies, latent conditions, legislative change or another provision.
4. Check authority and form. Confirm who can instruct the change and whether a written direction or other formal step is required.
5. Protect notice requirements. If the contractor considers the direction a variation, identify any timeframe for notifying that position, submitting particulars or providing a quotation.
6. Assess cost and programme effects where practicable before proceeding. Review labour, plant, procurement, subcontract, rework, delay and disruption implications.
7. Create a dedicated evidence trail. Keep the event identifiable from base-scope records so the commercial position can be reconstructed later.
8. Reassess as the impact develops. A change that initially appears minor may affect other packages, procurement commitments or programme logic after work begins.

This does not mean every site discussion should turn into a formal claim.

It means the project needs a consistent trigger for deciding when ordinary delivery may have crossed into contractual change.

Who should ask what?

The key is coordination.

The project manager may understand the physical change. Commercial may see the cost. The planner may see the programme consequence. Contract administration may identify an authority or notice issue.

Those views need to be connected before the changed work disappears into the general project record.

Common mistakes when a change looks “small”

• proceeding simply because the requested work appears minor;
• assuming every client request is automatically a valid variation direction;
• assuming extra cost automatically proves a variation;
• failing to establish the original scope before pricing the change;
• treating every revised drawing as changed scope;
• overlooking contractor design obligations;
• allowing unauthorised personnel to change scope informally;
• waiting until month-end to assess programme consequences;
• combining changed-work costs with base-scope cost codes;
• failing to deal with verbal discussions in the manner required by the contract; and
• focusing only on direct work while missing procurement, disruption or downstream effects.

These are also the conditions from which variation disputes tend to grow.

Perfomir’s broader guide to claims and variations management in construction examines how unresolved changes can develop into wider commercial and claim exposure.

Does every variation need written agreement before work starts?

Not necessarily across every contract, sector and jurisdiction.

Construction contracts can use different variation mechanisms. Some empower an authorised administrator to direct changed work before final price agreement. Others use proposed-variation procedures. Certain residential building regimes may also impose statutory documentation requirements.

For example, the Housing Industry Association’s current guidance on its HBCA Lump Sum Building Contract demonstrates how variation requirements can depend on the specific contract and applicable residential building framework.

The practical lesson for construction and infrastructure teams is not to import a rule from another contract.

Check your own variation clause, authority provisions, notices and applicable law.

How Contriqo can support earlier variation recognition

Contriqo by Perfomir is an AI contract intelligence and decision-support platform for construction and infrastructure.

Its role is not to decide conclusively that a change is a variation or that a contractor is entitled to payment.

Its relevant role begins earlier: helping teams connect a live project event with the contractual mechanisms that may matter.

For a “small change” event, that can mean surfacing relevant scope, variation, direction, notice and potential claim-exposure pathways for professional review.

Instead of waiting until commercial prepares a variation claim weeks later, the event can be considered against the contract when the instruction occurs.

That is the practical value of contract risk intelligence: project events are considered alongside contractual clauses and obligations rather than treated as disconnected operational information.

Where an apparently routine instruction begins developing into broader commercial exposure, Perfomir’s claim exposure prediction framework provides further context on how change, delay and notice events can form part of a developing claim pathway.

Contriqo supports professional judgement; it does not replace the commercial manager, contract administrator, planner, project manager or appropriately qualified adviser.

Frequently asked questions

What constitutes a variation in construction?

A variation generally involves a change to the work required under the contract, but the precise definition depends on the contract. It may include additions, omissions, changes in quantity, quality, position, dimensions or other requirements. The original contractual scope should be established before deciding that work is additional.

Does every client-requested change become a variation?

No. The requested work may already fall within the contractor’s scope, design responsibility or coordination obligations. The contract may also require the change to be directed or confirmed through a particular process.

Does a variation have to be in writing?

Many construction contracts prescribe written variation directions and identify who is authorised to issue them. Additional statutory requirements may apply in particular sectors or jurisdictions. Teams should check the contract and applicable law rather than assume an informal instruction is sufficient.

Can a revised drawing be a variation?

Potentially. The key question is whether the revised drawing changes the contractor’s contractual requirement or merely develops or clarifies work already within scope. Design responsibility and document hierarchy can be important.

Can a contractor refuse to carry out a variation?

That depends on the contract, the variation power and the circumstances. Some contracts require contractors to carry out properly directed variations even if valuation is still being resolved. Project teams should examine the actual contract before refusing or delaying instructed work.

What if the changed work has already been completed?

Preserve the instruction, scope comparison, authority records, notices, cost evidence, programme records and communications immediately. Once work is complete, entitlement and evidence issues may become harder to resolve. Appropriately qualified advice may be appropriate if the contractual position is disputed.

Key conclusion

The project manager may be right that the requested work looks minor.

The commercial manager may be right that it has significant financial consequences.

The contract administrator is right to ask what the contract required before the work started.

The strongest response is not to label every change a variation. It is to recognise a possible change early enough to test the original scope, identify the authorised instruction process, protect required notices, assess time and cost consequences and create a reliable evidence trail.

A small instruction can become a large commercial issue when the project event and the contract are not connected early.

The project event is the trigger. The contract determines what happens next.

This article provides general educational information only and does not constitute legal, contractual or financial advice. Contract terms and project circumstances vary. Obtain appropriately qualified advice for your specific contract and situation.

Have a contract? See how Contriqo analyses project events against your contractual obligations.

References

• NSW Government — Construction procurement guide: managing variations
• Construction Law Made Easy — What are variations?
• Construction Law Made Easy — How do variations occur?
• Holding Redlich — Decoding design and construct contracts: Variations (Part 5)
• Housing Industry Association — Variations under the HBCA Lump Sum Building Contract