All insights

How do you get site paperwork captured properly?

6 min readBy Brendon Whiting, Founder · 29 May 2026

Capture it where the work happens, on a device that works without a signal, with a form short enough to complete on a busy site. The paperwork that never gets captured is the paperwork you never get paid for, and in construction that is most often the variation nobody wrote down.

The economics here are unusually stark. A variation done and not recorded is work performed for free, and it happens constantly because the moment it is agreed is the moment everyone is busy. The client asks for something, the supervisor says yes, work proceeds, and the paperwork is meant to follow. Sometimes it does. When it does not, the business discovers at invoicing that it cannot substantiate a claim, and either absorbs the cost or has an awkward conversation months after the fact.

So the design goal is not comprehensive record keeping; it is capture that is faster than not capturing. That inverts how these systems are usually specified. The instinct is a thorough form with every field somebody might want, and the result is a form nobody completes on a wet Thursday afternoon. A form with four fields and a photo, completed every time, produces vastly more usable evidence than a form with twenty fields completed occasionally.

Photos deserve special emphasis because they are the cheapest and most persuasive evidence available, and they require no typing. A dated photo of the site condition before work, of the thing the client pointed at, and of the completed variation settles most disputes without argument. Field staff will take photos when they will not write descriptions, so any system that makes photographing easy and attaching automatic gets far better real-world compliance than one that treats images as an afterthought.

Offline capability is a hard requirement rather than a preference. Australian sites regularly have no fixed connection and patchy mobile coverage, and plenty of platforms that advertise mobile support quietly need a signal to save anything. Test that specifically before rolling anything out, in aeroplane mode, on the actual device you intend to issue, because discovering it on a rural site after a week of lost entries destroys adoption permanently.

The flow matters as much as the capture. Information captured on site should end up in the job record, and from there into an invoice or a claim, without anyone re-typing it in the office. Where that connection is missing, field capture becomes double handling and the office quietly reverts to its own version, which is worse than paper because now there are two records that disagree. Integration between your field tool and your job management or accounting platform is what makes the whole thing worth doing.

Adoption is won or lost in the first fortnight, and it is a people problem rather than a technology one. Involve the supervisors and leading hands in choosing the tool, because they will decide whether the crew uses it regardless of what management says. Show people the reason: this is how we get paid for the extra work you did, not this is how we check up on you. And fix the first three complaints quickly, since a form that is annoying in week one and unchanged in week four teaches everyone that feedback is pointless.

Timesheets deserve their own mention because they are the other thing captured badly. Time recorded at the end of the week from memory is guesswork, and it is usually guesswork that costs the business rather than the client. Capturing time against a job as it happens, even roughly, produces better costing, better future estimating and fewer arguments about who was where.

The measurement worth taking is simple. Before you change anything, count the variations claimed in a month and ask the supervisors how many they think actually occurred. That gap is your business case and it is usually uncomfortable. Afterwards, count again. Most businesses find the system pays for itself on recovered variations alone within a few months, which is a rare thing to be able to demonstrate.

The honest caveats. No system captures everything, and some variations will always be agreed verbally and forgotten. A tool people resent will be circumvented no matter how good it is, so simplicity beats completeness every time in this sector. And field capture will not fix a business that does not enforce variation approval with clients, since the paperwork only helps if someone acts on it. If you want capture set up so it actually gets used, call 1800 456 567.

Stop losing variations

We set up field capture that works offline and flows into your job system, so what happens on site becomes something you can invoice.

Frequently asked questions

That is usually a design complaint rather than a willingness one. If capturing a variation takes four minutes and eleven fields, it will not happen on a busy site. If it takes forty seconds, a photo and three taps, it will. Shorten the form before concluding people will not use it.

Then the tool must work offline and sync later, which is a hard requirement rather than a nice feature. Plenty of platforms claim mobile support and quietly need a connection to save anything. Test it in aeroplane mode before rolling it out, because discovering this on a rural site is expensive.

Enormously, and they are the cheapest evidence available. A dated photo of site conditions, of a variation being requested, or of completed work settles disputes that would otherwise come down to recollection months later. Photos also require no typing, which is why field staff will actually take them.

Questions? Let's talk.

Call 1800 456 567 or fill out the form.

  • 30-minute discovery — no jargon, no pressure
  • Plain-English Essential Eight Cyber Security Scorecard
  • A clear plan tailored to your business

Prefer to talk?

Call 1800 456 567

Powered by Calendly — your data is handled securely.

Our office · Level 2, 25 Grenfell Street, Adelaide

By submitting, you agree to our terms and privacy policy. No spam — ever.