VisitsTracker › Timesheets
Timesheet software for field teams
Hours come from the day as it happened — clock-ins matched to the site, offline entries kept at their real time, and a week you can lock before it reaches payroll.
No card needed. Set up in an afternoon.
Approving locks the week. A late punch aimed at it is refused, not absorbed.
The hours
Hours that came from the day, not from memory
A timesheet is assembled out of the readings the phone already sent. Nobody types a start time on Friday for a Tuesday they half remember.
- Every line traces back to the stay that produced it, openable from the row.
- Untrusted readings are excluded from the total rather than quietly averaged in.
- The gap between paid hours and hours on a site is shown, not buried.
Thursday is not an error. It is time the worker was moving but not on any site you have mapped, and it is named rather than folded in.
Corrections
An edit is a new fact, not a replacement
Somebody will always need to fix a forgotten clock-out. The question is whether the fix is visible afterwards. Here the original stays.
- The old value, the new value, who changed it and when, kept on the line.
- The worker sees their own corrections without having to ask for them.
- Approving a week locks it, so a late punch aimed at it is refused.
Both numbers survive. A timesheet that silently overwrites itself is not evidence of anything.
Payroll
Out in the shape your payroll already wants
The week leaves as a file your bureau can read, with the flagged lines marked rather than dropped, so nothing disappears on the way out.
- CSV and PDF, per worker or per site, for any range you choose.
- Overtime split out against the rule you set, not one we assumed.
- Exports are reproducible: the same week exported twice matches.
Also in the box
From clock-in to payroll, without retyping
Clock in and out, matched to the site
A clock-in records where it happened relative to the site. “At the site” and “three miles away” are different rows, not the same tick.
Offline entries keep their real time
No signal on site is normal. Entries wait on the phone and upload with the time they actually happened, in the order they happened.
Rotas that know about leave
Build a shift pattern with a grace window. Someone on approved leave shows as on leave, not as a no-show.
Forgotten clock-outs
If someone forgets to clock out, the session is closed automatically and marked as an estimate — it is never presented as a real reading. You can see which rows are estimates before you approve the week.
Straight answers
Questions people ask
How do hours get into payroll?
Clock-ins become a weekly timesheet. You approve the week, which locks it, then export for Xero, Sage, QuickBooks or plain CSV. Your rounding and overtime rules are applied at export.
What if someone forgets to clock out?
The session is closed for them and flagged as an estimate. It shows as an estimate on the timesheet and in the export, so you can correct it before you approve.
Can I stop a timesheet changing after I approve it?
Yes. Approving a week locks it. A late clock-in aimed at an approved week is refused outright rather than absorbed, so an approved total cannot move underneath you.
Does it handle overtime and rounding?
Yes, applied at export rather than to the stored record. That means you can change the rule and re-export without losing what actually happened.
What if there is no signal on site?
Entries queue on the phone and upload when signal returns, carrying their real time. They upload in order, so a late upload cannot reshuffle the day.
Also part of VisitsTracker
The rest of the product
Try it on one van for a week.
Put it on one phone, run a normal week, and see what comes out the other end.