Construction Variations: Document Them, Get Paid

What actually counts as a variation

A variation is any work you’re asked to do that falls outside what you originally quoted or contracted for. It’s not a grey area you talk yourself into — it’s a specific category, and most variations fall into one of four buckets:

• Scope change. The client or builder wants something added, removed, or done differently to what was in the drawings you priced against.
• Latent conditions. Something nobody could see until the wall was opened up or the opening was exposed — out-of-square framing, hidden services, a substrate that isn’t what the drawings said.
• Builder direction. A site instruction to do the work a different way — different fixing method, different sequence, extra protection — that takes more time or material than you allowed for.
• Design change. A revised drawing or spec lands after you’ve already priced and, in some cases, already started the job.

If none of those apply — if it’s just how you’d normally do the job, or a mistake on your side — it’s not a variation, and no amount of paperwork turns it into one. Save your energy for the ones that are.

Get the direction before you do the work

This is the one rule that matters more than the rest of this guide combined: get written direction before you start the extra work, or record it same-day if you can’t.

Not because builders are all trying to stiff you. Because six weeks later, nobody — including you — remembers the conversation the same way. The project manager who told you “yeah, just do it, we’ll sort the paperwork” has moved to another site. The site supervisor swears they only asked you to “have a look,” not fix it. You’re the one holding a stack of extra labour hours with nothing to show where they came from.

In practice this looks like:

• Best case: a written instruction or approved variation order before you touch the work.
• Realistic case: the builder wants it done now, there’s no time to wait on paperwork — so you get the direction confirmed in writing the same day. An email, a text message, a signed docket, anything with a name, a date, and what was asked.
• Worst case: you’re told verbally, on site, with nothing written down, and you do the work anyway because that’s how the job actually runs. If this happens, the fix is still available — write it up yourself and send it to them before end of day. More on that below.

Check your own contract for what it actually requires. Some head contracts state that no variation gets paid without a signed variation order first — full stop, no exceptions. Others are looser in practice even if the words on paper say otherwise. Know which one you’re working under before you’re relying on it.

One more thing worth checking before you assume a same-day email covers you: the instruction has to come from someone who actually has authority under the contract to direct a variation. That’s usually the superintendent or nominated representative named in the contract — not the site foreman, not “whoever was standing there,” even if they’re the one who told you to do it. An instruction from someone without authority to give it doesn’t bind the builder, no matter how well you documented it.

And even a well-documented instruction from the right person isn’t the end of the process. Plenty of subcontracts run on a “no signed variation order, no payment” basis — the email confirms what happened, but it’s not the same as the builder agreeing to pay for it. Silence after your email isn’t agreement either; a builder who never replies hasn’t approved anything, they’ve just gone quiet. Send the same-day email for the record, then keep chasing the signed paperwork until you’ve actually got it.

Don’t miss the notice clause — or you lose the entitlement, full stop

Buried in most subcontracts — including a lot of subcontracts written off standard forms like AS 4000 or AS 2124 — is a time-bar clause: a requirement that you notify the builder or superintendent within a set number of days of becoming aware something is a variation, or you lose the right to be paid for it. Not discounted. Not negotiated down. Gone, regardless of how good the work is or how solid your records are otherwise.

This catches subbies out because it feels backwards. You’d expect a strong photo record and a clear description of what changed to be what wins a variation dispute. Sometimes it doesn’t matter, because the clock started running the moment you realised the work was outside scope, and if you missed the window, the merits never get argued at all.

Contracts vary a lot on exactly how long you’ve got and how the clock starts, so there’s no single number to memorise here — find the actual clause in your contract before the job starts, not after you’re already relying on it. Once you know the timeframe, calendar it: the moment something looks like it might be a variation, that’s the day the notice clock starts, not the day you get around to writing it up.

What a variation record needs

A variation that gets paid is a variation you can prove happened. Every record should capture:

• Who directed it. Name and role of the person who told you to do the work — not “the site guy,” an actual name.
• When. Date and, ideally, time. This matters more than it sounds like it should when a dispute drags out months later.
• What changed. Plain description of the extra or different work, specific enough that someone reading it in six months understands exactly what happened without needing you to explain it in person.
• Cost and time impact. Extra hours, extra materials, extra plant, and any delay it caused to your program.
• Photos of the condition. Especially for latent conditions — the out-of-square frame, the hidden service, the substrate that didn’t match the drawing. A photo taken before you started fixing it is worth more than any amount of written description. See our guide on site photo documentation for how to make photos hold up as evidence, not just snapshots.

None of this needs to be fancy. A dated note with a photo attached beats a beautifully formatted variation register you filled in from memory three weeks after the fact.

Pricing: day rate or lump sum

Contracts differ a lot here, so treat this as general shape, not a rule to apply blind. Two common approaches:

• Day/charge rates. Your contract sets an hourly or daily rate for variation work, sometimes with separate rates for labour, plant, and materials. You log time and materials against the variation and it gets priced against the agreed schedule.
• Quoted lump sum. You price the variation as its own mini-quote before starting, the builder approves the price, then the work happens. Cleaner for both sides when the scope is well-defined enough to price up front.

Some contracts nominate one method exclusively; others let you use whichever suits the job. Check your contract for which basis applies, and get the pricing method agreed in writing before the work happens — not once you’re chasing payment for something already built.

Getting it approved and into your next claim

A variation that’s approved but never invoiced is money you’ve earned and haven’t collected. The record needs to move from “happened” to “on the claim,” and that only happens if someone tracks it.

The usual failure mode: variations get logged in a spreadsheet tab, a notebook, or a pile of dockets in the ute, and by the time the monthly claim goes in, half of them have been forgotten because nobody cross-checked the list against what actually got approved that month. Every forgotten variation is a discount you’ve given the builder for free.

Practical habit: every time a variation gets approved, it should go straight into the pool of items for your next progress claim — not sit waiting for someone to remember it exists. If you haven’t nailed down your claims process yet, our guide on how to write a progress claim covers how to structure a claim so approved variations don’t fall through the gap between “approved” and “invoiced.”

Common ways subbies lose variation money

A few patterns show up again and again:

• Doing the work on a verbal, then asking for paperwork after. By the time you ask, the person who agreed to it has no incentive to confirm it in writing — it’s now a cost to them, not a favour.
• The approving PM leaves the project. Verbal approvals belong to the person who gave them. When that person’s gone, so is your evidence, unless it’s in writing.
• No photo of the condition that triggered the variation. Especially for latent conditions — without a photo taken at the time, you’re arguing a description against the builder’s memory of the same site.
• Variations sitting in a spreadsheet that never makes it into a claim. Approved isn’t the same as paid. If it’s not on a claim, it’s not getting paid.
• Vague descriptions. “Extra work to opening 14” tells nobody, including future-you, what actually happened. Specific descriptions survive scrutiny; vague ones don’t.
• Pricing basis never agreed up front. Doing the work first and arguing about day rate vs lump sum afterwards is a fight you didn’t need to have.
• Missing the notice deadline in the contract. Some subcontracts cut off your entitlement entirely if you don’t notify within a set window of becoming aware of the variation — a great record doesn’t save you if the notice clause already killed the claim.

Any one of these on its own might not sink a claim. All of them together, across a whole job, adds up to real money left on the table.

Where WNDW fits

Good records don’t override a missed notice clause, but they make sure the notice clause is the only thing you’re ever fighting — not your own memory of who said what. WNDW captures variations the moment they happen: photo, hours, and reason logged against the specific opening while the foreman’s still standing in front of it. Approved variations roll straight into the next progress claim instead of living in a spreadsheet tab nobody checks. See how variation management works.

FAQ