Why Most Subbies Don't Track Variations Properly
A variation register template for construction projects is one of the simplest tools that separates subcontractors who get paid from those who leave money on the table. It's not complicated. It's not expensive. And yet, the majority of Tier 2 and Tier 3 subcontractors in Australia either don't have one, or have something so disorganised it's practically useless.
Here's what I typically see: variations tracked in someone's head. Or in a folder of emails. Or in a spreadsheet that was last updated three months ago. Or — my personal favourite — on sticky notes in the site office that got thrown away when the demountable was relocated.
The consequence is predictable: legitimate work goes unclaimed, notice deadlines get missed, and at project close-out, nobody can reconstruct what actually happened. The builder's QS picks apart your final account, and you accept a settlement that's 30-40% less than what you're owed because you can't prove the rest.
What Is a Variation Register?
A variation register is a single document — usually a spreadsheet or database — that records every variation on a project from identification through to payment. It's the central source of truth for all variation activity.
Think of it as your project's financial early warning system. At any point, you should be able to open it and answer:
- How many variations are currently open?
- What's the total value of unapproved variations?
- Are any notices overdue?
- What's been approved but not yet invoiced?
- What's been invoiced but not yet paid?
If you can't answer those questions in under 60 seconds, your variation tracking isn't working.
The Essential Columns
A good variation register template for construction doesn't need to be complicated. Over-engineer it and nobody will use it. Here are the columns that matter:
Identification
- Variation Number — sequential ID (e.g., V-001, V-002). Never reuse numbers.
- Date Identified — when the variation was first recognised on site
- Description — brief but specific. "Additional excavation in Zone B due to uncharted services" — not just "extra work"
- Initiated By — who triggered it (client direction, design change, latent condition, etc.)
Notice Tracking
- Notice Date Sent — when formal written notice was issued
- Notice Due Date — the contractual deadline for notice (calculated from date identified)
- Notice Sent To — who received it (superintendent, project manager, etc.)
- Notice Method — email, letter, system (keep the delivery evidence)
Commercial
- Estimated Value — initial estimate at time of notice
- Claimed Value — the detailed claim amount submitted
- Approved Value — what the principal has agreed to pay
- Time Impact (Days) — any extension of time associated with the variation
Status Tracking
- Status — Draft / Notified / Claimed / Under Review / Approved / Rejected / Disputed / Paid
- Response Due Date — when you expect the principal's response
- Last Action Date — when anything last happened on this variation
- Notes — free text for context, conversation references, issues
Example Register Layout
Here's what a working variation register looks like in practice:
| Var # | Date ID'd | Description | Notice Sent | Notice Due | Claimed $ | Approved $ | Status |
|---|---|---|---|---|---|---|---|
| V-001 | 15/01/26 | Additional piling — rock encountered at 3.2m (geotech showed 6m) | 16/01/26 | 29/01/26 | $42,800 | $42,800 | Approved |
| V-002 | 22/01/26 | Revised steel connection details — RFI 034 response | 23/01/26 | 05/02/26 | $18,500 | $15,200 | Approved |
| V-003 | 03/02/26 | Site access delay — crane mobilisation blocked by other trade | 04/02/26 | 17/02/26 | $31,200 | — | Under Review |
| V-004 | 14/02/26 | Additional formwork to amended retaining wall profile | 14/02/26 | 28/02/26 | $12,600 | — | Claimed |
| V-005 | 28/02/26 | Dewatering — water table higher than geotech report indicated | 01/03/26 | 14/03/26 | — | — | Notified |
At a glance, you can see: two approved ($58,000), one under review ($31,200), one claimed ($12,600), and one just notified. Total exposure: $105,100. That's the kind of visibility that changes how you manage a project.
The Five Mistakes That Kill Variation Registers
1. Not Starting It Until Something Goes Wrong
The register should be created at project kickoff — not after the first dispute. Pre-populate it with the contract notice requirements, key dates, and the superintendent's details. When the first variation hits, you're ready.
2. Only Recording Approved Variations
This is the most common mistake. If your register only shows approved variations, it's not a management tool — it's a history book. The register needs to capture every potential variation from the moment it's identified, including those that are rejected or withdrawn. That's how you track your total exposure and catch items that have fallen through the cracks.
3. Letting It Go Stale
A register that's updated monthly is almost as bad as no register at all. Notice deadlines don't wait for your monthly admin day. Update it weekly at minimum — and update notice dates and status in real time.
4. No Ownership
Someone specific needs to own the register. Not "the office." Not "whoever gets to it." One person, accountable for keeping it current. On smaller projects, that's you. On larger projects, it's your project administrator or contract admin. Either way, there's a name next to it.
5. Disconnecting It From Invoicing
Approved variations that don't make it onto progress claims are pure profit leakage. Your register should feed directly into your monthly payment claim. If a variation is approved, it should appear on the next claim — automatically or by deliberate review.
The hidden cost: Research from the AIQS suggests that Australian subcontractors lose 3–5% of annual revenue on undocumented or poorly tracked variations. For a $5M business, that's $150,000–$250,000 per year walking out the door.
Spreadsheet vs Software
A spreadsheet works. Don't let anyone tell you it doesn't. For a subcontractor running 2–5 projects at a time, a well-maintained Excel or Google Sheets register is perfectly adequate.
The problem with spreadsheets is human discipline. They rely on someone remembering to update them, they don't send reminders, they don't connect to your site team, and they don't create an audit trail.
That's where purpose-built variation management tools come in. Software like Variation Shield automates the parts that humans are bad at: capturing variations on site in real time, calculating notice deadlines from your contract terms, sending reminders before deadlines expire, and maintaining a register that's always current because it's updated at the point of capture — not back in the office three days later.
The right tool depends on your size and volume. But the principle is the same: track every variation, from identification to payment, in one place.
How to Get Started Today
If you don't have a variation register, here's what to do this week:
- Create the register using the columns above. A simple Google Sheet is fine.
- Backfill current projects — list every variation you're aware of, even if notice has already been sent. Get the current state captured.
- Set a weekly review — 15 minutes, same time each week. Review every open variation. Is notice required? Is a response overdue? Has something been approved but not invoiced?
- Brief your site team — when they identify a potential variation, they need to tell you that day. Give them a simple way to do it (text message, quick email, whatever works).
- Connect it to your claims — before submitting each progress claim, cross-reference the register. Every approved variation should be on the claim.
It takes less than an hour to set up. The return — in recovered revenue, reduced disputes, and better project visibility — is immediate.
Skip the spreadsheet. Capture variations on-site in 60 seconds.
Variation Shield builds your register automatically — from site capture to notice to approval tracking. No more chasing paperwork at the end of the month.