The project
Payroll that works for how you actually work.
Why
Generic payroll cannot read your agreement
Most payroll engines were built for a fixed salary and a fixed week. Put an award or an enterprise agreement in front of them and the clauses that actually decide pay, all purpose allowances, shift sequences, RDO accrual, minimum weekly super, have to be worked out somewhere else and typed back in.
Putting an industry label on that same engine does not fix it. Neither does a services team quoting for configuration. If the rules are not in the engine, someone is holding them in a spreadsheet or in their head, and both of those leave on a Friday.
How
We read the instrument and build it in
The instrument lives in the engine
We read your award or agreement and build the clauses into the interpretation engine, then maintain them as rates and increments move.
Hours are captured or synced, never uploaded
Crews clock on in CrewTime and the foreman approves on site, or approved hours sync from the site software you already run. There is no CSV step.
Super paid every run
Super is calculated and paid with wages in the same run, which is what payday super requires.
Labour costed to the code it was worked on
The job and cost code travel with the hour, so costed labour lands on the project rather than in a reconciliation later.
However your crew works
Six ways an hour reaches payroll
Generic payroll assumes everyone sits at a desk and fills in a form. A real site has a worker in a basement with no signal, a foreman doing the whole crew at once, and somebody still on paper. All six of these land in the same place, already costed, with nobody typing anything in twice.
Clock on, offline
The punch is written on the device and queued. Basement, tunnel, greenfield site, it lands either way and syncs when coverage returns.Kiosk on the shed wall
A shared tablet for crews without phones, or the mornings when the phone is flat. Tap your name, enter a PIN, get on with the day.On site or away from it
Clock-ons are checked against the job location, so the roster shows who started away from site before the first smoko. It is a flag for the foreman, not an accusation.The foreman does the crew
One pass to approve the whole crew, with condition flags confirmed at the same time. The rate comes from the agreement, not from an argument at the gate.Still on paper? Photograph it
OCR reads the sheet, a person reviews and corrects it before anything reaches payroll, and the original photo is kept as the audit record.Already in your site software
Approved hours sync from BuildPass, Procore and the rest, carrying their job and cost code. There is no CSV step anywhere in the workflow.
Every one of those arrives with its job and cost code attached, which is why the labour is already costed before the pay run starts.
Who it is for
Crews, not desks
This is built for people paid hourly under an award or an enterprise agreement, spread across sites that change through the year, supervised by a foreman rather than an HR team. Construction, civil and infrastructure, mining services, labour hire, electrical and renewable energy builds.
If your pay week is the same every week and everyone sits in one office, there are simpler products than this one and we will say so.
Rules and rates current as at August 2026.
Tell us
What breaks in your pay run?
Tell us what is broken. We read every one of these personally and reply within one business day.