From Variation to Progress Claim Without Retyping: One Workflow in a Typical Building Business

In a typical building business, a variation agreed on site gets written down three or four times before it reaches an invoice: in the supervisor's notes, in the project manager's pricing spreadsheet, in the progress claim and again in Xero or MYOB. Every copy is a chance for it to be late, wrong or forgotten. When the workflow is joined up, the variation is recorded once on site, priced and approved in one place, and flows into the next claim and the invoice without anyone typing it again. A person still checks the price and signs off the claim. They just stop copying it.

This post is part of our series One workflow, one business like yours. Owners often tell us the thing that would help most is seeing a working example in a business like theirs. So each post follows one workflow through one typical business. The business below is a composite: it's put together from how many residential and commercial builders work, not a story about one client, and there are no invented figures in it.

The business and its systems

Picture a builder doing extensions, new homes and small commercial fit-outs, with a handful of jobs running at once. The team is a few site supervisors, two project managers, a contracts administrator, someone in accounts and the owner.

The systems are ordinary:

• an estimating or job management system (Buildxact, Simpro, Procore, or a set of spreadsheets) holding the contract and budget for each job
• the supervisors' phones: photos, texts and a notes app
• email, where most client approvals happen
• a progress claim spreadsheet per job, built from the contract's claim schedule
• Xero or MYOB for invoices, payments and the accounts

Each system works. The trouble is in the gaps between them.

What happens today, step by step

1. On site, Tuesday. The client asks the supervisor to move a window and add two power points. The supervisor agrees in principle, takes a photo and texts the project manager: "Client wants window moved, 2 extra GPOs, can you price".
2. In the office, Thursday. The project manager prices it in a spreadsheet from the electrician's verbal quote and their own rates, then writes an email to the client with the price.
3. Waiting. The client doesn't reply for a week. The work goes ahead anyway because the electrician is already there. Nobody updates the job budget, because the variation isn't approved yet.
4. Claim time, end of the month. The contracts administrator builds the progress claim. They open the claim schedule, then search their inbox and ask both project managers, "Any approved variations on this job?" The window makes it in. One of the power points was mentioned in a later phone call and doesn't.
5. Into the accounts. Accounts types the claim total into Xero or MYOB as an invoice, with a line for the variation. The job management system still shows the old contract value.
6. The owner, at night. Before the claim goes out, the owner reads through it at the kitchen table, checking it against what they remember from site visits. They find a variation from last month that was never claimed.

Count the times the same variation was written down: the text, the pricing spreadsheet, the email, the claim and the invoice. That's double entry (the same information typed into more than one system), and here it's closer to quintuple entry.

Where it breaks

• Retyping. Each copy of the variation is typed by a different person from the one before. A number transposed in the pricing spreadsheet carries all the way to the invoice.
• Waiting. Approval sits in an inbox. The work is done, but the money can't be claimed until someone chases the client, and chasing is nobody's job in particular.
• Things that drop out. Variations agreed by phone, or approved in a reply to a different email, never reach the claim. This is the most common way builders lose money they've already earned. We wrote about it in the variation that never got billed.
• Numbers that disagree. The job system says the contract is one figure, the claim says another and Xero says a third. Your WIP report (work in progress: what's been earned versus what's been billed) is wrong until someone reconciles them by hand. See WIP reporting for builders using Xero.
• Deadlines under pressure. Payment claims and payment schedules run on time limits set by your state's security of payment laws. A claim built in a hurry at month-end is where mistakes and disputes start. Our guide to progress claims, payment schedules and retentions covers the rules by state.
• The owner as the safety net. If the only reliable check is the owner reading every claim at night, the business can't take on more work without the owner working longer.

What it looks like when it's joined up

Same business, same people, mostly the same software. What changes is that the variation is recorded once and then moves.

1. On site. The supervisor logs the variation on their phone against the job: a short description, photos, and who asked for it. This takes about as long as the text message did.
2. Pricing. The project manager gets a notification, prices it from the job's rates and the trade's quote in the same record, and sends it for approval. The client gets an email with a clear description and an Approve button, or a PDF to sign.
3. Approval. When the client approves, the variation's status changes, the job budget and contract value update, and the supervisor sees it's approved. If it hasn't been approved after a set number of days, the project manager gets a reminder. Unapproved but completed work shows on a list the owner can see.
4. The claim. At claim time, the claim draft is built from the claim schedule plus every approved variation on the job. The contracts administrator reviews it rather than assembling it.
5. The invoice. Once the claim is signed off, the invoice is created in Xero or MYOB automatically with the right lines and job tracking, through an integration between your job system and your accounts.
6. The numbers. Contract value, claimed to date and approved variations agree across the job system, the claim and the accounts. On Monday you can see, for every job, what's been earned, what's been claimed and what's waiting on approval.

Who still checks what:

• The project manager checks every variation price before it goes to the client.
• The contracts administrator reviews every claim before it's sent.
• The owner signs off claims above a value they choose, and looks at the "done but not approved" list weekly instead of reading every claim at night.

Nothing about this needs a new all-in-one system. Often it's one connection between the job system and the accounts, a variation register everyone uses, and a few simple rules (reminders, approval status, who signs off). That's the core of construction process automation: take out the copying, keep the judgement.

What to measure before and after

Don't take anyone's word for how much time this costs, including ours. Count it in your own business for two or three weeks before anything changes, then count the same things again a couple of months after. Useful measures:

• Times each variation is written down between site and invoice.
• Days from variation agreed to client approval.
• Days from approval to the variation being claimed.
• Variations done but not claimed, found when you go back through the last few months of jobs.
• Hours spent building each month's claims, across everyone involved, including the owner's evening check.
• Claim corrections and credit notes, and disputes about variations.
• How far apart your job system, claims and accounts are on contract value for a sample of jobs.

If you're not sure where to start counting, the free Admin Time Count gives you a quick estimate of the time your team spends on re-keying and chasing.

The next step: one workflow, done properly

Most builders don't need to fix everything at once. Pick the workflow that hurts most (for many it's variations to claims; for others it's timesheets to payroll to job cost) and fix that one first.

Our Process & Systems Audit ($5,000) maps how the work really moves through your systems, counts a few baseline measures like the ones above before anything changes, and gives you a written report on what to fix first. If you then go ahead, we fix that one workflow as a First Workflow Sprint: a fixed-scope project with a fixed quote and timeframe, handed over with written steps your team can follow, and you own everything we build. Part of your audit fee comes off the sprint. There's more about how we work with builders on our construction industry page, and with trades on the trades and field service page.

Frequently asked questions

Is this example a real client?

No. It's a typical example built from how many building businesses work, so you can compare it with your own. Kenomont has been building systems that pass information between steps for 20+ years, including a purchase order approval system a large retirement living provider has used since 2014, but this post doesn't describe a specific client.

Do we need to replace our job management system to do this?

Usually not. Most of the gain comes from recording the variation once and connecting the systems you already have. If your current system genuinely can't hold variations or approvals, that shows up in the audit, and you can decide then.

Can the client approve variations without a portal login?

Yes. An email with a clear description, the price and an Approve link, or a PDF they sign, is usually enough. The important part is that the approval updates the job record, not just someone's inbox.

What if our variations are mostly agreed verbally on site?

That's normal. The fix is making it quick for the supervisor to log the verbal agreement on their phone straight away, so there's a record to price and send for written approval. The faster that first record is made, the less drops out.

How long does fixing one workflow like this take?

It depends on your systems and how many jobs and people are involved, so we scope it first. Single-workflow projects like this are usually measured in weeks, not months, and you get a fixed quote and timeframe before anything starts.

If your variations, claims and invoices are typed out more times than they should be, book a free initial chat and we'll talk it through.