Helium – AI automation agency logo
Helium – AI automation agency logo
Helium – AI automation agency logo
Helium – AI automation agency logo

What Construction Firms Lose Between Site and Office

The margin in a construction business is decided by information that never makes it back from site. Not by pricing, and rarely by productivity on the tools.

Ask a construction company where its margin goes and you get answers about material prices, labour rates and clients who negotiate hard. Those are real. They are also not usually where the money leaks.

The leak is information that exists on site and never arrives at the office in a usable form, or arrives three weeks later when it can no longer change anything.

The three day lag

Something happens on a Tuesday. A variation is agreed verbally with the client. An extra load of material is ordered. A day is lost to weather. A subcontractor turns up without the right certification.

The site manager knows immediately. The office finds out when the paperwork comes in, when somebody happens to mention it, or when the invoice does not match the job. In a lot of firms that is the end of the week, and for anything not written down it can be the end of the month.

Everything downstream inherits that lag. Invoicing goes out late because nobody is certain what was done. Variations get billed at the value somebody remembers rather than what was agreed. Job costing arrives after the job finished, which makes it a history lesson rather than a control.

Why the paperwork does not come back

It is worth being fair about this. Site teams are not careless. They are working in conditions where paperwork is genuinely difficult.

The forms were designed for a desk. They ask for information in an order that makes sense to the office and no sense on a slab. They require a signal that is not always there. And they compete with the actual job, which is the thing everybody is judged on.

So the reporting happens at the end of the day, from memory, in a van. Or it happens on Friday, for the whole week, from a worse memory. The quality of what comes back reflects that, and the office response is usually to add more forms, which makes the problem worse.

What to capture at the moment it happens

The fix is not more reporting. It is less reporting, captured where the work is, at the moment it occurs.

  • Variations. The single highest value item. A photograph, thirty seconds of voice, who agreed it, and a timestamp. That is enough to bill it and enough to defend it.

  • Day sheets. Who was on site, hours, plant used. Short enough to complete before leaving.

  • Progress against programme. Not a percentage somebody guesses. Which specific items finished today.

  • Anything that stopped work. Weather, access, materials, a missing approval. This is the record that wins the conversation about delay six weeks later.

  • Certifications and compliance. Checked when somebody arrives, not discovered when an inspector asks.

Everything on that list has to work on a phone, one handed, with gloves on, offline, in under a minute. If it does not, it will not happen, and no amount of insisting will change that.

The variation problem is a cash problem

Of everything above, unbilled variations are usually the largest single number.

The pattern is consistent. Client asks for something on site. Site manager agrees because refusing costs a relationship and a day. It gets done. It gets mentioned in passing. It never gets priced, and when it surfaces at final account the client does not recall agreeing to it, or recalls agreeing to something smaller.

The work was done, the materials were bought, the labour was paid. The revenue was never invoiced. That is not a margin problem, it is a documentation problem wearing a margin costume, and firms that fix capture at the point of agreement typically find more money there than in any procurement exercise.

What the office should stop doing

Two habits are worth breaking.

Chasing subcontractors by phone for documents. Insurance, certifications, method statements, invoices. Somebody in your office spends a day a week on this. It is a sequence of reminders that does not need a person, and the compliance risk of an expired certificate nobody noticed is considerably larger than the admin cost.

Rebuilding the same report every month. Pulling job costs from the accounting system, hours from timesheets and progress from a spreadsheet, then reconciling them by hand. It takes days, it is out of date on arrival, and it is the reason nobody looks at job profitability until the job is finished.

Where to start

Capture variations first. It is the smallest change and the one that shows up in cash within a month. One route, on a phone, that records what was asked, who agreed, a photograph and a time, and puts it in front of whoever prices it the same day.

Then subcontractor compliance, because it removes a standing admin cost and a real risk in one move.

Then live job costing, once the first two are feeding it real data. Doing it in the other order produces an accurate looking dashboard built on numbers that arrive three weeks late.

The numbers worth pulling

Days between work happening and it appearing in the system. Value of variations agreed on site against value invoiced, on the last five completed jobs. Days from job completion to final invoice. Hours per week spent chasing subcontractor paperwork. Expired certifications currently on site.

Most firms that run these five find the same answer. They are competitive on price and losing money in the gap between the site and the office, which is the cheapest part of the business to fix and the least likely to be looked at.

Why another app usually fails

Most construction firms have already bought something that was meant to solve this, and it is sitting unused.

The pattern is always the same. It required a login the crews did not remember. It needed signal on a site that has none. It asked for information in an order that made sense to a software designer. And it existed alongside the paperwork rather than replacing it, so the site team was doing the job twice.

Anything that adds a step to a site worker's day loses, however good it is. The only versions that survive are the ones that are faster than what they replaced, measured from the perspective of the person on site rather than the person in the office.

Where AI does the reading

The reason site capture never worked before is that it produced material nobody had time to process. A photograph, a voice note and a scribbled sheet still needed somebody in the office to turn them into a priced variation.

AI removes that step. It reads the voice note, pulls out what was agreed and by whom, reads the delivery ticket or the invoice and matches it to the job, and puts a priced draft in front of whoever approves it the same day.

The same capability handles subcontractor compliance. Certificates and insurance documents are read on arrival, checked against the trade and the expiry date, and flagged before they lapse rather than when an inspector asks.

That is what makes thirty seconds of capture on site worth something, instead of adding to a pile.

AI Optimize builds the site capture, the document chasing and the reporting that connects them, on the tools you already run. That work sits under Workflow Automation and Document Intake & Validation.

Related reading

WHAT WE BUILD

This is the part we solve