Progress Claims and Variation Orders: How to Stop Disputes Before They Start

Most variation disputes don't happen because anyone is dishonest. They happen because of ambiguity — and ambiguity is almost always the result of poor documentation.

The typical sequence:

1. A site condition changes or a client requests a modification 2. The project manager and contractor discuss it verbally or via WhatsApp 3. The contractor does the work 4. The contractor invoices for the variation 5. The project manager disputes the amount, or doesn't remember authorising it, or the client says they never approved it

At this point, there's no clear record of what was agreed. The dispute is now a negotiation — and negotiations are expensive, time-consuming, and relationship-damaging.

The fix is simple: every variation needs a written record before work starts. Not after. Before.

A variation order should contain:

Description of the change: What is being done differently from the original scope? Be specific. 'Additional excavation due to rock encountered at 1.2m depth in the north-east corner of the site' is a proper description. 'Extra digging' is not.

Reason for the variation: Was this a client request, a site condition, a design change, or a compliance requirement? The reason affects who bears the cost.

Cost impact: The exact dollar amount, including labour, materials, and any margin. Itemised where possible.

Time impact: Does this variation affect the project timeline? By how many days?

Approval chain: Who needs to approve this variation before work proceeds? Client? Project manager? Both?

Approval status: Not approved / Approved / Rejected. With the approver's name and the date.

Every variation that doesn't have all six of these elements is a potential dispute.

Progress claims are the mechanism by which contractors get paid for completed work. They should be straightforward. In practice, they're one of the most common sources of conflict on construction projects.

The most common dispute triggers:

Claimed percentage vs actual completion: The contractor claims 60% complete. The project manager says 45%. There's no agreed method for calculating percentage completion, so both figures are defensible.

Variations included without prior approval: The contractor includes variation costs in the progress claim. The project manager says the variation was never formally approved.

Retention disputes: The project manager withholds more retention than the contract specifies, or disputes when retention should be released.

Defects offsetting: The project manager offsets the progress claim for defects. The contractor disputes whether the defects are their responsibility.

All four of these disputes are preventable with clear documentation and a formal approval process.

An effective variation approval workflow has four stages:

Stage 1 — Identification: The variation is identified and documented by whoever discovers it (site supervisor, project manager, or contractor). A variation request is created with the description, reason, and estimated cost.

Stage 2 — Assessment: The project manager reviews the variation request, verifies the scope and cost, and determines whether client approval is required.

Stage 3 — Approval: The variation is submitted to the required approvers. No work proceeds until written approval is received. The approval is logged with the approver's name and timestamp.

Stage 4 — Execution and invoicing: Work proceeds. The approved variation is referenced in the contractor's invoice. The project manager matches the invoice to the approved variation before payment.

BuilderHQ automates this entire workflow. Variation requests are created on mobile from site, routed to the correct approvers automatically, and logged in the project record. Contractors can only invoice for approved variations.

One of our clients — Stonegate Developments, a Melbourne commercial builder — was managing a 24-unit residential project with 18 active trades. Before BuilderHQ, they managed variations via email and WhatsApp.

On a previous project, they'd had a $87,000 variation dispute with a structural engineer that took 4 months to resolve. The dispute centred on whether a series of design changes had been formally approved. Neither party had clear documentation.

On the Stonegate project, every variation was documented in BuilderHQ from day one. Over the 14-month project, there were 47 variations totalling $312,000.

Not one was disputed.

Every contractor knew that variations needed to be in the system before work started. Every approval was logged. Every invoice was matched to an approved variation before payment was released.

The project manager estimated they saved 3–4 hours per week on variation administration compared to the previous project. And the relationship with every contractor on the project remained intact.

If you're currently managing variations via email and WhatsApp, here's how to transition to a systematic approach:

Step 1: Establish a variation register. Even a shared spreadsheet is better than nothing. Every variation gets a number, a description, a cost, and an approval status.

Step 2: Communicate the process to your contractors. Tell them explicitly: no variation proceeds without written approval. If they start work without approval, they bear the cost.

Step 3: Make approval easy. If the approval process is cumbersome, people will bypass it. Digital approval via email or mobile app takes 30 seconds.

Step 4: Audit at progress claim time. Before processing any progress claim, reconcile it against your variation register. Every variation in the claim should have a corresponding approved variation order.

Step 5: Automate. Once you've established the process manually, move it to a platform like BuilderHQ that automates the routing, reminders, and audit trail.

The investment in setting up a proper variation management process is 2–4 hours. The return is measured in tens of thousands of dollars in avoided disputes per project.