Construction Paperwork is Killing Margins: What Site Managers Can Actually Automate Today

It’s 9pm. A site manager is at the kitchen table, writing up today’s site diary from memory and a camera roll full of blurry slab photos.

Was the concrete truck there at 7:40 or 8:10? Did the sparky sign in, or just wave? Dinner went cold an hour ago, and it’s starting to look like it’s given up too.

If you want to automate construction paperwork, start with that picture. Most of what happens at that table is retyping things that already exist somewhere else. Very little of it needs a site manager’s judgement.

This guide walks through what a site manager can actually take off their plate this month, in order from free to properly engineered. It also covers the parts you should never hand to software. Those matter just as much.

[Pushes the cold dinner aside. Opens laptop.]

How much does paperwork really cost a construction job?

That slice is under pressure. ASIC's insolvency statistics show 3,472 construction companies entered external administration or had a controller appointed for the first time in 2025-26. That’s about one in four of all such companies, more than any other industry.

Paperwork didn’t cause that on its own. Nobody serious would claim it did. But when margins are this tight, admin hours are one of the few costs a builder can actually control.

Here’s an illustration. These are assumed numbers, not measured ones, so swap in your own.

So in this example, one site manager’s retyping eats the profit on more than a third of a million dollars of work. Every year. Multiply by the number of site managers you employ.

If you want the wider argument, we’ve written about what manual data entry really costs a business.

What construction paperwork can site managers automate today?

Here’s the ladder at a glance.

1. Level 1: switch on what you already have.Your site platform probably does more than anyone has turned on.Usually free
2. Level 2: Microsoft 365 glue.Forms and Power Automate handle the bits your platform doesn’t cover.Tools you may already own
3. Level 3: a designed workflow.For paperwork that crosses several systems and needs checking along the way.Worth designing properly

For a lot of builders, Level 1 is the right place to start, for the boring reason that it’s the cheapest.

What does your site platform already automate that you’re not using?

Think back to the kitchen table. Half of what our site manager was trying to remember is data a machine already captured.

Weather is the obvious one. Nobody should be typing “fine, 18 degrees, light northerly” when a feed already knows.

Headcount is the next. If workers sign in on a phone, the platform already knows who was on site and for how long. HammerTech says daily site numbers and hours can be generated from its sign-in app automatically.

Inductions too. SiteBook advertises automated inductions and QR code attendance, alongside managing SWMS, licences and insurances in one place.

So what’s left for the site manager to write? The things only they know.

Delays, decisions, conversations, the crane that turned up a day early. That’s the useful part of a diary, and it’s a five-minute job when the rest is already filled in.

The diary that took an hour at 9pm becomes ten minutes in the ute before leaving site. Dinner survives. [Dinner is thrilled.]

How can Microsoft 365 handle the paperwork your platform doesn’t?

This is Level 2. It’s for the forms your site platform doesn’t cover, or for builders who don’t have a platform at all.

Good candidates look like this:

• Prestart checklists. Filled in on a phone, filed into a register automatically, with a flag if anything is ticked “no”.
• Delivery logs. Who delivered what, when, with a photo of the docket attached.
• Toolbox talk attendance. Who attended and what was covered, logged against the date without anyone typing up a sign-in sheet.
• Subcontractor document requests. A form the subbie fills in, with their certificates uploaded, landing in the right folder every time.

Microsoft’s own guide on common ways to use a form in a flow covers the building blocks. Adding a row to Excel, sending an approval and emailing an attachment are all documented patterns.

Here’s a simple test for any step you want to automate. Is it a rule, or is it a reading job?

When does construction paperwork need a proper workflow?

That’s Level 3. No single app owns those jobs, so they fall to a person who copies, compares and chases.

A few examples of what that looks like on a real job:

• A subbie emails an insurance certificate. Someone has to read the expiry date, update a register and remember to chase it next year.
• Dockets come back from site in a pile. Someone has to match each one to a purchase order and spot the ones that don’t match. (Here’s how supplier invoice and docket matching gets automated.)
• A progress claim lands. Someone has to compare it against the diary and the programme before anyone approves payment.

None of those are hard. All of them are slow, and all of them are easy to get wrong at 9pm.

A designed workflow reads the incoming document, pulls out the fields that matter, checks them against your rules, and sends only the exceptions to a person.

1. ReadThe certificate, docket or claim arrives and is picked up automatically.Automation
2. ExtractThe fields that matter come out: dates, amounts, ABNs, expiry dates.AI
3. CheckEach field is tested against your rules, the purchase order or the register.Rules
4. RouteClean records file themselves. Exceptions land in front of a named person.Human

That’s the kind of work Lumeio builds, and you can see how Lumeio handles construction document workflows in more detail on our construction page.

The paperwork doesn’t stop at your site either. Much of it ends up with a certifier, which is why we’ve also looked at the certification paperwork your building surveyor deals with.

What should a site manager never hand to software?

[Switches to serious face]

A SWMS that’s been digitally signed by everyone is not the same as a SWMS that matches the work. Software can remind people it needs reviewing. It can’t stand on the slab and see that the method has changed.

The same goes for stopping work. A form can record that a hazard was reported. The call to stop is a person’s call, every time.

Variations and extension of time claims need judgement about cause, cost and contract. Automation can gather the evidence. It shouldn’t decide the outcome.

And anything signed under a licence or registration stays with the person who holds it, because the accountability sits with them.

The pattern is the same throughout: the machine does the gathering, a person does the deciding. That’s what keeping a human in the loop actually means in practice. For the Victorian regulations behind SWMS and building inspections, our construction page covers them in detail.

Common mistakes

Buying a twelfth app. If your team already juggles a platform, email, a shared drive and a group chat, another login rarely helps. Check what your current tools can do first.

Digitising a bad form. If the paper prestart asks the wrong questions, a digital version just asks them faster. Fix the form, then automate it.

Turning SWMS into a tick box. Digital sign-on is useful. But if workers are signing a document they haven’t read on a phone they’re holding with one hand, you’ve automated the signature and lost the point.

Automating before agreeing who owns the data. If nobody owns the subcontractor register, an automated register will be wrong faster. Decide who is responsible first.

Skipping the exceptions. Every automation needs a place for the weird stuff to go. A docket that doesn’t match should land in front of a person, not disappear quietly.

Where to start this month

Start with the cheapest step and work up. Most builders don’t need new software to get hours back. They need to switch on what they have, digitise the two or three forms that cause the most retyping, and only then look at a designed workflow.

Here’s a plan for next Monday:

1. Audit your platform.List every module you pay for and check which automations are switched off. Weather and sign-in feeds are the usual suspects.Level 1
2. Pick your worst form.The one that gets retyped most often. Turn it into a Microsoft Form with a Power Automate flow behind it.Level 2
3. Write down what crosses systems.Certificates, dockets, claims. Those are your Level 3 candidates, and they’re worth mapping properly before anyone builds anything.Level 3

Do those three, and the 9pm diary session gets a lot shorter.

Maybe dinner even gets eaten warm. [Bold prediction. We stand by it.]

Frequently asked questions