Clocking on
From the home screen, without opening anything
In and out from the phone, with breaks, and the timer visible while it runs. It also works straight from the iPhone home screen widget — because the moment you're clocking in is the moment you're least inclined to wait for something to load.
In the office you see who is on the clock right now, and the history behind it.
Home screen widget
04:12:38
On the clock since 07:48
On the clock right now
The shifts that need a human
The exceptions should come to you
All six of these were previously invisible unless a manager scrolled the entire month and happened to notice. That's exactly backwards. Each one carries a severity, so a forgotten clock-out doesn't compete for attention with a four-minute mis-tap.
A timesheet is a ledger, and nobody reads a ledger.
Closing a shift somebody left open
The software doesn't guess at somebody's wages. It asks the person who knows.
When the office closes a forgotten shift, the end time is the time the person actually finished — entered by someone who knows. Not the moment the office noticed. “Now” would be convenient, and would also pay somebody for the eleven hours their phone sat on a worktop.
The only limits are the ones that catch typing: it can't end before it started, and it can't end in the future.
The hours are worked out on the server
The total for a shift is always recalculated from the start time, the end time and the breaks — never taken from what the app sends. A phone that can send its own total is a phone that can send its own hours.
It isn't a statement about your engineers. It's that hours become money, and anything that becomes money should be worked out somewhere the person being paid doesn't control.
Approving the period
Reviewed and approved, rather than silently becoming fact
Work through the period, deal with the exceptions, approve it. What you hand to whoever does your payroll is a set of hours somebody looked at, with the corrections recorded rather than rubbed out.
OnPoint produces the hours. It is not a payroll system: there are no pay rates in it, and it does not calculate wages, overtime, holiday pay or anything you'd file.
Leave
Why holiday belongs on the same page as hours
Leave is requested and approved here too — and it isn't a separate world from the diary or the timesheet.
Approved leave shows in the diary as a reason someone can't be booked — on the same footing as an existing job, so you find out while you're choosing who to send rather than on the morning. Scheduling.
And approved leave is what makes “clocked in on a day they'd booked off” a detectable exception at all. Without it, that shift just looks like any other.
Straight answers
Including where hours stop and payroll starts.
01Can engineers clock in from their phone?
Yes — in and out from the phone, with the timer visible while it runs, and straight from the iPhone home screen widget without opening the app.
02Can they record breaks?
Yes, and breaks come out of the shift total. There are no automatic breaks — a long day with no break recorded is surfaced as something for a person to look at rather than deducted on an assumption.
03What happens if someone forgets to clock out?
It's flagged as a high-severity exception — a shift still running overnight has no total at all until it's closed. The office closes it at the time the person actually finished, not the moment it was noticed. It can't end before it started or in the future, and the correction is recorded.
04Will it tell me about a shift that looks wrong?
Yes — six checks, each with a severity: a shift still running overnight, a sixteen-hour day, a four-minute mis-tap, a ten-hour day with no break, somebody clocked in on a day they'd booked off, and absent when expected in. You don't have to scroll a month to find them.
05Can I see who's working right now?
Yes — who's on the clock, who's on a break, and how long they've been going, with the history behind it.
06Can I correct a shift?
Yes, and the total is recalculated on the server from the start time, end time and breaks — never taken from what the app sent. Hours become money, so they're worked out somewhere the person being paid doesn't control.
07Are timesheets approved before they're final?
Yes. Shifts are reviewed and approved for a period rather than silently becoming fact — you clear the exceptions, then approve, and the corrections stay on the record.
08Does it calculate wages or run payroll?
No. There are no pay rates in OnPoint. It produces hours worked — no wages, overtime or premium rates, no holiday pay, no payslips, nothing filed with HMRC, and no payroll integration. You hand the approved hours to whoever does your payroll.
09Can staff book holiday?
Yes — leave is requested and approved in the same place as the hours.
10Does approved leave stop someone being booked onto a job?
It shows in the diary as a reason they can't be booked, on the same footing as an existing job, so you're told while you're choosing who to send. You can still book them if you need to — it asks first. Scheduling.
11Does it work offline?
A full day's work can be done with no signal and syncs when you're back in coverage — see field mode for exactly what's held on the device.
12What does it cost?
£19 for the first seat and £9 for each seat after. Time, shifts, exceptions and leave are on every plan — there's no higher tier. See pricing.
Run one week and see what it flags.
14 days free, no card. Clock a couple of shifts, leave one running on purpose, and watch the exception come to you instead of waiting for month end.