Does your team need a clocking in app?

So the real question isn't "must we clock in?" It's "what's the easiest way to keep the records we're already on the hook for, without the faff?" Here's what actually matters, and what you can safely ignore.

Do you legally have to make staff clock in?

No. There's no UK law that says you must install a clocking in system, put a time clock on the wall, or a clocking in app on everyone's phone. What the law requires is that you keep adequate records, and clocking in is simply the most reliable way to produce them.

Two sets of rules drive this. The Working Time Regulations 1998 require you to keep records showing that workers aren't exceeding the 48-hour average working week (unless they've signed an opt-out) and that night-work limits are met. ACAS is clear that you don't have to log every daily hour for this purpose, and these records must be kept for two years.

The bigger driver is the National Minimum Wage. You have to be able to prove you're paying at least the minimum wage for every pay reference period, and since April 2021 those records must be kept for six years. From April 2026 the National Living Wage is £12.71 an hour for workers aged 21 and over, so the sums have to be right. If they aren't, HMRC can make you repay the arrears, charge a penalty of up to 200% of what's owed, and name you publicly.

Worth knowing: an EU court ruling in 2019 said employers should record all daily working time. The UK never wrote that into law before Brexit, so the lighter record-keeping rules above are what still apply here.

What records does UK law actually require?

Enough to show two things: that your hours stay within working-time limits, and that everyone is paid at or above the minimum wage. That's the whole ask. There's no prescribed format and no duty to record rest breaks.

In practice, for each worker you need to be able to show the hours worked in a given pay period and what you paid for them. Timesheets, a clocking in system, rota records or a spreadsheet all count, as long as they're accurate and you can produce them on demand for the relevant pay reference period. A worker can also ask in writing to see their own minimum-wage records, and you have to hand them over within 14 days.

The weakness of the manual versions is evidence. If a pay dispute or an HMRC check lands and your "records" are a half-finished spreadsheet and a few WhatsApp messages, the burden of proving compliance sits with you. That's the practical case for capturing hours cleanly at the moment they happen, rather than reconstructing them on a Friday afternoon.

How does clocking in and out work day to day?

At its simplest, each person marks the start and end of their shift and the system timestamps it. How they do that depends on your setup.

On a single site, a clocking in machine on the wall handles it: staff tap a card or fob, punch a PIN, or use a fingerprint. In a clocking in app, they open it on their own phone or a shared table by the door, tap clock in, then clock out at the end. For teams out on the road or spread across sites, app-based clock-ins can use GPS or geofencing, so a clock-in only registers when the person is actually at the right place.

Breaks are the part people forget. Decide up front whether unpaid breaks get clocked out and back in, or deducted automatically, then keep it consistent. That's the difference between a timesheet you trust and one you end up arguing over.

Clocking in machine, clocking in app, or neither?

There are three common ways to capture hours. Here's the short version.

Clocking in machines still earn their place at a single fixed site where nobody carries a phone on shift, a factory floor or a warehouse, say. For most small teams, and for anyone with staff across sites or out in the field, an employee time clock built into an app does the same job without the hardware, and the record is digital from the first tap. Which of the two is right for your setup is worth a proper comparison of its own; the short answer is that fewer and fewer teams now need the wall box.

What should a clocking in app do for you?

Turn clock-ins into pay with as little manual work as possible. For a manager, the value isn't the clocking itself, it's what happens to the data afterwards.

Look for three things. First, clock-ins tied to the rota, so the shift and the hours actually worked sit together rather than in two systems you reconcile by hand. Second, timesheets that build themselves and export straight to your payroll software, with overtime visible before it becomes a payslip surprise. Third, something to curb "buddy punching", where one person clocks in a mate who's running late.

On data, don't get sold on GDPR compliance as though it were a feature. Every credible UK tool is GDPR-compliant; that's table stakes. The question worth asking is where your data is actually stored. UK or EU data residency is the real differentiator, so ask the provider directly and get a straight answer.

Closing that gap is what Timetastic's Rota & Time Clock is built for: your team clocks in from a phone, tablet or computer, every clock-in is tied to their shift on the rota you've already built, and the timesheet is ready for payroll at the end of the week. Leave, rotas and attendance in one place, with no separate app for your team to learn.

Common clocking in mistakes to avoid

A few things quietly trip managers up:

• Buddy punching. Mates clocking each other in. A photo prompt or a clock-in tied to a personal device makes it far harder.
• Untracked breaks. Handle breaks inconsistently and your hours drift, and so does what you pay.
• Rounding by hand. Rounding everyone to the nearest 15 minutes feels tidy, but it can quietly push someone under minimum wage. Capture the actual times.
• No payroll export. If someone still retypes the numbers into payroll every week, you've automated the clocking and kept all the faff.

The bottom line

You don't legally need a clocking in machine or a clocking in app. You do need records that hold up: six years of minimum-wage evidence, two years of working-time compliance, produced on demand. Paper can technically manage it. An app manages it without the chasing, the manual sums, or the faff, and it turns hours into pay while you get on with running the place.

Start your free 30-day trial of Timetastic. No credit card required.

FAQ

Can I require staff to use a clocking in app on their own phones?

You can ask staff to clock in from their personal phones, but you shouldn't force it as the only option. Offer an alternative like a shared tablet or wall kiosk for anyone who objects, and be upfront about what the app records and where that data is stored. UK or EU data residency is the question to put to the provider.

Is it legal to use fingerprint or face scans for clocking in?

Yes, but biometric clock-ins count as special category data under UK GDPR, so you need a clear lawful basis, usually explicit consent, and a genuine non-biometric alternative for anyone who declines. In 2024 the ICO ordered Serco Leisure to stop using facial recognition and fingerprint scanning to track staff attendance across 38 sites, because staff were not offered a clear alternative and it was presented as a condition of getting paid. If you go the biometric route, offer fobs or PINs alongside it and let people choose.

Do salaried staff need to clock in too?

You can ask salaried staff to clock in, and you still need records showing everyone stays within the 48-hour average working week, but the minimum-wage record-keeping that drives most clocking in mainly matters for hourly and lower-paid staff. For salaried teams it's usually about working-time compliance and cover, not proving pay.

Do clocking in apps work without an internet connection?

Most decent clocking in apps keep working offline and sync the timestamps once the phone reconnects. That matters for warehouses, basements, rural sites and anywhere the signal drops, so check the app you're considering handles it before you rely on it.

Should I pay staff for the time spent clocking in?

If clocking in happens at work as part of starting the shift, that time generally counts as working time and should be paid. The bigger trap is rounding: rounding everyone to the nearest 15 minutes feels tidy but can quietly push someone under the minimum wage, so capture the actual times and let the system do the sums.

Can staff clock in before their shift starts, and does that time count?

Someone clocking in a few minutes early doesn't automatically mean you owe extra pay, but if they're genuinely working, you have to count it. The clean fix is to set the app to accept clock-ins only within a window around the rota'd shift, so early taps don't quietly inflate the timesheet.

‍