The variation you did on a handshake is the margin you gave away

A foreman agrees to a bit of extra work on site. Cut a longer trench, shift some material, deal with a service that wasn’t on the plan. He says yes because that’s the job, and everyone gets on with it. Three weeks later someone in the office goes to put the claim together and there’s no record it happened. No note, no photo, no sign-off, no marked-up plan. The work got done. The money for it quietly evaporated, because you can’t claim what you can’t prove, and the client’s not going to remind you.

That’s where civil contracting leaks margin, and it’s rarely one dramatic loss. It’s the variation done on a handshake and never captured. The plant sitting on standby while you wait on site access, costing money nobody’s tracking. The claim that gets questioned and you’re scrambling for the evidence that backs it. Civil work has a lot of moving parts, crews, plant, subbies, materials, variations, dockets, safety records, and a small gap in the field turns into an office problem days later, when the margin’s already walked off site. A job system isn’t admin. It’s the thing standing between the work you did and the money you actually keep.

Put rough numbers on it and the politeness stops. Say each crew lets one variation a month go uncaptured, averaging $3,000 to $5,000 of work. That’s $40,000 to $60,000 a year from a single crew, and most contractors run more than one. Add the odd day of standby at $1,500 to $2,500 for an excavator and operator, plus a claim or two a year shaved back because the evidence was thin, and the leak clears six figures without anyone making what you’d call a mistake. Nobody stole anything. The work just moved faster than the record.

Follow one variation from the trench to the claim

Say the crew’s on a subdivision job west of Toowoomba, out past Wellcamp. Tuesday morning the excavator turns up a conduit that isn’t on the plans. Work stops. The foreman rings the superintendent’s rep, they agree on the spot to realign the trench and add forty-odd metres, and the rep says something like “get it done, we’ll square the paperwork later”. By smoko the crew’s moving again, because a stopped crew costs more per hour than any form ever will.

Now run the clock forward three weeks. The rep who said yes has rolled onto another project. The foreman remembers the conversation but not the date. The photos of the conduit are on a phone that’s since been upgraded. The contract administrator assembling the progress claim finds one line in the daily diary, “extra trenching as discussed”, and nothing else. The client’s quantity surveyor asks for substantiation. There isn’t any. So the variation gets haggled down to half, or waved through as goodwill to keep the relationship sweet, and the contractor eats the difference on work that was done well, agreed fairly, and never disputed by anyone standing in the trench.

Nobody in that story did anything wrong. The gap is structural. The moment of agreement and the moment of claiming sit weeks apart, and nothing carried the evidence across.

Evidence has to attach itself, in the moment

Photos, notes, signatures, GPS, timestamps and dockets are worth a fortune when they’re tied to the right job, and next to nothing as a pile of loose files someone means to sort later. A photo on a phone isn’t evidence. It becomes evidence the moment it’s attached to a claim, a variation, a defect or a completion record, and that has to happen when the work is done, not in a Friday catch-up that keeps slipping until the detail’s forgotten.

So the field side has to be quick enough for someone with one hand free, standing in the wind on a haul road. Log the variation, snap the photo, capture the sign-off, and have it land against the job automatically while the office can see enough to act without ringing around for the rest. Make it slower than a text message and the crew won’t do it, and a job system nobody uses in the field is worse than nothing, because now you’re paying for it and still losing the variation.

Run this test before committing to any field tool. Hand it to your least patient foreman and time how long it takes him to log a variation with a photo and a sign-off against the right job. Under a minute, you’re in with a chance. Three menus and a search box, and he’ll tell you he’ll do it tonight, which means never, and next month you’re back to reconstructing a Tuesday from memory.

Stop being the integration layer

Most civil contractors run separate systems for accounting, estimating, scheduling, payroll, safety and document storage, and when none of them talk, your people become the glue, keying the same job details from one screen into the next. That re-entry is slow, it’s where errors breed, and it’s completely avoidable.

API integration pushes approved job data into finance, raises tasks off submitted forms, keeps dashboards and customer records current, and makes every tool respect one job record. Enter the truth of a job once, and let it flow to the places that need it, rather than paying people to copy it around and then reconcile the copies when they inevitably disagree. A custom job system gives the crew a workflow they’ll actually use on a flat-out day, which is the only kind worth building.

The tell is easy to spot: count how many times one job’s details get typed in across its life. Job number into the estimating tool, again into the scheduler, again into payroll, again into the safety system, again into the accounting package at invoice time. Five entries is four chances for a mismatch, and every mismatch means someone in the office loses a Thursday afternoon working out why the claim total doesn’t agree with the cost report.

Where AI helps, the source still rules

AI starts to pull its weight on the messy inputs: emails, site notes, photos, scanned dockets, contract clauses, the long job history nobody wants to read end to end. It can summarise a job before a project meeting, flag missing evidence before you invoice, or pull the fields off a form for someone to check, and that saves real time.

But for claims and compliance the source document still rules, so the system has to show you the photo, docket or clause sitting behind any answer, not just a confident summary of it. On a job that’s being disputed, “the system reckons it’s fine” is worthless without the evidence you can put in front of the client. The AI reads the pile faster. The proof still has to be real and attached.

Plant, people and claims belong on one record

Plenty of civil work looks profitable right up until you count plant time, standby, rework and the variations that never made it onto a claim, and by the time you spot it weeks later the margin’s gone. A job system that connects the daily field record to plant allocation, labour, subbies and claims gives the manager that picture while the job’s still running and the money’s still recoverable, not in a hindsight review where all you can do is note the loss.

Standby is the sneakiest leak because it never looks like a loss while it’s happening. The float delivers the excavator on time, the site isn’t ready, the access gate’s locked or the permit hasn’t landed, and the machine sits. Everyone on site knows it sat. But if nobody logged when it arrived, when it started work and whose hold-up caused the gap, there’s no delay claim, just a plant cost that lands quietly against the job. A daily record that captures plant hours by activity, including the hours spent waiting and why, is the difference between recovering that money and donating it. The same record can feed a dashboard that shows which jobs are drifting while there’s still time to do something about it.

Off the shelf, or built around how you run jobs

There are packaged job systems for civil, and for some contractors one of them is the right answer. Before you sign, ask the questions the brochure skips. Can a foreman capture a variation with photos and a sign-off, offline, in under a minute, or does the field app assume mobile coverage you won’t have out past Oakey? Does the daily diary feed the claim, or does the claim still get assembled by hand at month end from whatever the diary happened to catch? Do job costs flow into your accounting package, or does the bookkeeper rekey them? And when the tool doesn’t match how you run jobs, who bends, the software or every crew you’ve got?

If those answers come back wrong, a custom system starts to make sense. Not because custom is fashionable, but because the workflow is the asset. The strongest first version is usually narrow: field capture for variations, dockets and plant hours, wired into the estimating and accounting tools you already run. Grow it once the crews trust it, not before.

This bites harder for Toowoomba and Darling Downs contractors because crews are usually spread across several jobs at once, council work, private developments, sites out past Dalby or down the range, moving between them through the day while photos come in, customers ring, and the office needs evidence before the next claim run. The software has to cope with that normal chaos, not a tidy version of it.

Start where the money leaks: the variations not captured, the plant time nobody can pin down, the claims short on evidence, the close-out that drags. Build the smallest system that hands the team a job record they can rely on. It doesn’t need to be flash. It needs to make the field record usable, the office calmer, and the margin easy to defend when a claim gets questioned. If you know there’s work you did last month you never got paid for, tell us where it slipped and we’ll start there.