Hours logged on the job, not remembered on Friday.
Time goes on with a tap where the work is, lands under the right job on the right day, and comes out the other end as a payroll file that reconciles with the screen you read it on.
Matt Reilly · this week
LockedClocking on is one tap, and it lands on the right job.
Time is logged where the work is — on the stage the person is standing on, not reconstructed at the end of the week. Walking from one job to the next is the everyday case, so clocking on at the second one closes the first at that moment and tells them what it came to.
Every entry is credited to a calendar day in your business’s own timezone, and a shift that runs past midnight stays on the day it started.
An hour can be marked as one the customer isn’t being charged for, or priced against a weekend or after-hours rate from your own rate card.
Logging hours against somebody else takes its own permission and is recorded against whoever did it, so a week always says who put what on it.
The office reads the week and fixes it, in one place.
The whole team’s week is one grid, days across the top, with a flag against anyone who logged hours but hasn’t handed the week in. Open a day or a week total and the member’s whole week is there to correct — fix an hour, move it to the right day, add the Tuesday somebody forgot — without opening a single job.
Every add, edit and delete is stamped with who made it, so a corrected week still says exactly what was changed and by whom.
An hour that’s already been invoiced is frozen. What a client was billed doesn’t quietly change underneath them.
These are the same hours the invoice pulls from, so a do-and-charge job bills the time that was actually worked rather than a figure typed out a second time.
Hours the customer isn’t charged for still cost the business, so they stay on the job’s costing instead of vanishing.
Tax Invoice
INV-0847
Spark & Wire Electrical · ABN 51 824 753 166
BSB
063-502
Account
1084 7291
Lock the week, then export it.
Handing a week in finalises it: the entries lock and the hours are ready for payroll. The export is a CSV with a row per person per day, carrying locked hours only and reconciling to the cent with the grid the office has been reading all week — built to be handed straight to whoever runs the pay run.
The office can hand a week in on someone’s behalf once it’s been corrected, which is how a payroll deadline gets met when a member is away.
Recorded leave comes out on its own rows, and a full day is flagged rather than given a made-up number — the standard day is your award’s business, not ours.
If you want a second person to check a week before it counts, switch sign-off on: a handed-in week then waits for an approver, and those hours stay off an invoice until it’s cleared.
With sign-off on, anyone who logged hours and hasn’t handed the week in is chased on the first morning after the week closes — once, not every day.
Who it’s for.
The same feature reads differently depending on which end of the business you’re standing at.
The crew
Clock on, clock off, hand the week in. Their own week on their phone, day by day, with the total already added up.
The office
One grid for the whole team, a flag on whoever’s missing, and every correction made from that one screen.
Whoever runs payroll
A row per person per day that reconciles with the screen the hours were read on, with leave carried on its own rows.
Next door.
The parts of the system this one hands off to.
Run one week through it.
Fourteen days and your own crew’s hours. The first payroll export makes the argument.