Construction work is spread across sites, and the crew on each one is different by the morning. NOWORX puts roll call, safety checks, material requests and the approval chain in one place a supervisor can reach from a phone at the gate. Each department gets an AI agent that tallies, chases and files the parts nobody wants to sit down and do at six in the evening.
You booked eleven and nine turned up, two of them from a crew you have not worked with before. The supervisor writes it on a sheet, photographs it and drops it into a chat group. By the time the month closes, nobody can say which site that photo belonged to, so the subcontractor's invoice becomes the only surviving record — and it wins the argument by default.
Each site grows its own chat group, its own spreadsheet and its own way of naming things. Moving a foreman from one site to another means teaching them somebody else's filing habit. When the office asks a simple question — how many days did that crew work in block B — someone scrolls three months of messages to answer it.
Daily checks are signed on a clipboard and filed on site, which is fine until a client, an insurer or the main contractor asks for three months of checks on one work area. Then someone drives out to fetch a folder and hopes it is complete. The records were done properly; retrieving and proving them is the failure point.
A supervisor calls the office, the office calls the supplier, and the only trace is a call log. Weeks later the delivery note and the invoice disagree by four pallets and nobody remembers who authorised the extra load or which cost code it belonged to. It is never one big loss — it is a small leak on every site, every month.
A machine finishes on one job and sits behind a fence for two weeks because the site that needs it does not know it is free. Nobody is at fault. There is simply no list that says where each item is today, who has it, when it is due back and when it is next due for service.
Tap an app name in any step to see what it does.
The supervisor opens the board on a phone at the gate and records who is present, by crew and by site, in under a minute. The department agent compares the tally against what was ordered for that day, flags the gaps, and posts a single summary to the office before the first delivery arrives. Site notices go out as one short digest instead of five chat groups, so a rule change reaches every gate the same morning.
Build a check sheet per trade or per work area — a lift, an excavation, a hot works permit — and the person doing the check fills it where they are standing. Anything that fails becomes an item with an owner and a date instead of a sentence in a group chat. The site log is a few lines at the end of the day, and the agent assembles the day's sheets and log into a per-site record you can hand over without a site visit.
Requests go from site to office with quantity, cost code and required-on-site date, so the office is ordering from a record rather than from a phone call. Plant and equipment sit in a register that says where each item is, whose site it is charged to, when it is due back and when its next service falls. Spend above your threshold routes to whoever is supposed to see it, and the agent chases the approver who has been sitting on it since Tuesday.
Subcontractors and suppliers live in one directory instead of three phones, with documents attached to the party rather than filed under whoever scanned them. Signed subcontracts, insurance certificates and retention dates are stored with their expiry so the agent can warn you before a certificate lapses mid-job. Variations are priced and sent from the same place they will later be invoiced from, which is how a variation stops being an argument.
Ask across sites instead of per site: labour days by crew, requests raised versus approved, plant sitting idle, cost by code against the same week last month. Watches run on the numbers you file, so a site whose headcount has drifted from plan four days running gets surfaced while the job is still open. The board pack comes out of the same data rather than from a night of copy-paste.
Fair. So the site side is deliberately thin: a roll call, a check sheet and a few lines of log — one screen, a minute or two a day, on the phone they already carry. Everything else is the office's job. When something is missing, the department agent asks for it in chat rather than the site having to learn a new menu to find it.
We keep the interactions small on purpose — short forms and a handful of fields, not large uploads over a weak signal. If a supervisor files after leaving the site, the entry is still recorded against the correct site and the correct date, so late filing does not corrupt the tally. We would rather tell you that plainly than promise you a system that works down a lift shaft.
No. In most setups the site supervisor records crew numbers for a subcontract team, and only the people who genuinely need to file for themselves get an account. Approvals, cost data and contract documents stay inside your organisation regardless of who is standing on site.
No, and it should not. The agent prepares the request, routes it to the right person, chases it when it stalls, and summarises what came in. A named person approves and a named person signs. What you get from the agent is that nothing sits unnoticed for a week, not that a machine took a decision it has no business taking.
No. NOWORX is the operations layer in front of it — the part where the site records what happened and the office turns that into requests, approvals and documents. Your ledger of record stays where it is, and data from it can be brought in for browsing so people stop asking the finance team to look things up.
Pick one site and two apps: roll call and the daily log. That is enough to see whether the tally reaching the office each morning is worth anything to you. Safety sheets, material requests and the plant register come after the site team has stopped noticing the first two.