Construction software that works where the work happens
A site has no signal, gloves on every hand, and a dispute waiting six months out. Software written for an office desk gets abandoned by the second week.
What makes site software different
5 things that decide this
- 01Offline is the normal condition, not an edge case. A basement, a plant room and a rural site all kill a connection, so the app has to hold the whole task rather than degrade to read-only.
- 02Record the time work happened, and keep the upload time separately. Capture at seven in the morning and sync at five means an honest record looks like a late one, and that is the record someone will question.
- 03Photographs are the evidence and the bandwidth problem at the same time. Compress on the device, upload when there is signal, and never block a completed record on a picture that has not gone yet.
- 04The people fixing the problem usually work for someone else. TankAware runs a deficiency to work-order lifecycle with a contractor portal and payments, because the loop crosses company boundaries.
- 05Money and disputes belong in the design, not in a later phase. WorkMateAI holds payment until work is accepted, freezes it on a dispute, and assembles the evidence.
The argument arrives long after the work
Nobody argues on the day. The disagreement turns up months later, when a defect appears and two firms remember the same afternoon differently. Whoever has the better record wins, and usually neither party has one.
This is why site software is really evidence software. A photo with a time and a person attached settles a question that a group chat cannot. A checklist frozen as it was on that day proves what was actually asked of the crew.
Build for that reader from the start. Corrections should add a new version rather than overwrite the old one. Editing a template must never change what past inspections appear to have covered.
- 01Every record names a person, not an account. An anonymous tick is not evidence.
- 02Freeze the checklist version with the record it produced.
- 03Prove the negative too. You will be asked which sites were missed, not only which were done.
- CaptureOffline, in gloves. Syncs when signal returns.
- StampThe time of work, not of upload.
- SignA named person and their role.
- RaiseDeficiency becomes a work order.
- CloseContractor evidence, then payment.
- RetainLong past the end of the job.
Steps five and six cross a company boundary, which is where most site software stops and email takes over. That handover is where deficiencies go quiet.
Where we are useful
Offline field capture
TankAware captures scheduled inspections across sites on React Native, with photos, deficiencies and audit logs. Built for places where the connection is not a given.
Contractor and vendor workflow
A deficiency turns into a work order, reaches an outside contractor through their own portal, comes back with evidence and ends in a payment. Shipped on TankAware.
Payments held against the work
WorkMateAI runs hold-and-release payments on Stripe Connect for Australian trades, freezes funds on a dispute and generates chargeback evidence.
Access that matches the site
Five permission tiers on TankAware, each organisation isolated. Your contractor sees their sites and nothing else, which is a data separation question before it is a login one.
Write the dispute process before you need it
WorkMateAI came to us because growth had outrun its paperwork. Payments, contracts and disputes were creating real legal exposure, and every new job increased it.
We built a three-layer agreement model with version history. Platform terms at signup, a provider agreement at onboarding, and a job contract for each accepted quote. Payments run held-and-released, freeze on a dispute, and produce evidence. The dispute path itself runs in phases, manual first and rule-based after.
Version history is the part teams skip. Without it you cannot say which terms a job was accepted under, and that is the first question anyone asks.
- Tie every job to the exact contract version in force that day.
- Decide who can release held money before launch, then log every release.
- Manual dispute handling first. Automate only the patterns you have actually seen.
Systems running in trades and site businesses
“TankAware has revolutionized how we manage petroleum sites. The real-time data and automation have exceeded expectations.”
Blake Sutherland · President, Sutherland Excavating Ltd.
The stack behind these builds
Built with
Field work
Money and paperwork
Questions buyers ask us first
01Will the app work in a basement with no signal?
It has to, and fully rather than in a read-only mode. Crews need to open the task, record results, attach photos, sign and queue the record without a connection. The record stamps the time work happened, and stores sync time separately. An honest entry made underground then never reads as a late one.
02How do we prove what a subcontractor actually did?
Attach a named person, a timestamp and photographs to every completed item, and freeze the checklist version alongside it. TankAware then turns a deficiency into a work order the contractor closes through their own portal with evidence attached. A group chat cannot do this, which is why the dispute is usually lost there.
03Can we hold payment until work is signed off?
Yes, and WorkMateAI is the build to look at. Money is held after the customer pays and released against accepted work, it freezes when someone raises a dispute, and the platform assembles chargeback evidence. Decide who is allowed to release funds before launch, because that is an access question that looks like a finance one.
04Our crews refuse to use the last system. What changes?
Usually the number of taps and whether it works offline. A form built for a desk is unusable in gloves on a windy site. A crew left waiting on a spinner goes back to paper. Watch someone complete a real task before you write the requirements. That hour changes more than a workshop does.
05Do you integrate with the accounting system we already run?
Usually yes, and we would keep it as your financial record rather than duplicating it. New software should be the operational and evidence layer around it, and your accounting system wins any conflict about a number. Name the system early, since its access model tends to set the schedule.
06How do you scope a construction build?
Scoping calls are free. Where the work starts inside your existing codebase, there is a paid two-week diagnostic ending in a fixed price rather than a range. The first thing we ask for is the record you could not produce last time somebody asked for it.
