Guide

Clock in app for small UK businesses: a buyer’s guide

By the SafetyEvo team · · 7 min read

A clock in app records when each person starts and ends work, and their breaks, on the phone they already carry, and turns that into timesheets and a payroll export. For a small UK business the right one is the one that produces the records the law expects, resists the obvious abuses without biometrics, lets you correct mistakes without destroying the evidence, and does not take a day to set up. This guide lists what to look for, what the law actually says, and why a clock in and a lone worker safety app belong on the same button.

What the law expects you to record

Two sets of rules drive the records. The National Minimum Wage rules require every employer to keep records sufficient to show that workers are paid at least the minimum wage, kept for six years, and HMRC can inspect them. The Working Time Regulations 1998 limit average weekly hours to 48 unless the worker has opted out, entitle workers to rest breaks and daily and weekly rest, and limit night work; you must keep records that show you comply with the weekly limit and the night work rules. Neither says how to keep the records. A paper sheet is lawful. An app is simply more accurate, harder to lose and easier to produce when asked.

The questions to ask

  • How does a worker clock in? One tap on their own phone should be enough. Every extra step is a missed clock-in you will correct later.
  • What stops someone clocking in from home for a friend? Location recorded at clock-in and out, and the app tied to a named phone, answer this without fingerprints or face scans.
  • Can a clock-in be corrected? It must be, with a reason, by someone with permission, and with the original kept. Ask to see the edit history.
  • Are breaks recorded, and are staff reminded to take them?
  • Can a pay period be locked after approval, so a timesheet cannot change after it has been paid?
  • Does it flag working time problems: missed rest breaks, long weeks, night work limits?
  • Can managers see who is clocked in now, and who was planned to be but is not?
  • What does the payroll export look like? Ask for a sample CSV and open it in your payroll software before you sign.
  • Where is the data held, for how long, and who can see it? UK hosting and a clear retention period are reasonable asks.
  • What happens with no signal? The clock-in should be recorded on the phone and sent when signal returns, with the phone’s time preserved.

Why no biometrics

Fingerprint and facial recognition clock-in feels secure, but biometric data is special category personal data under UK GDPR. Using it for attendance needs a specific lawful basis, a data protection impact assessment, and a genuine alternative for staff who do not consent, and the ICO has ordered employers to stop using facial recognition and fingerprint scanning for attendance where it was not necessary. For a small business the cost and risk are out of proportion to the problem. A clock-in from a named phone with location recorded stops almost all buddy punching, and a manager who knows the team stops the rest.

Why clock-in and lone worker safety belong on one button

If your staff work alone, you already need them to tell a system when they start and finish, so that protection is on while they work and off when they go home. That is exactly what a clock-in is. Running attendance in one app and safety in another means two systems with two ideas of who is at work, and the one that is wrong is the one you find out about after an incident. In SafetyEvo the button that starts a shift switches on location sharing and the check-in and welfare controls, and writes the timesheet row; ending the shift stops tracking and closes the row. One tap, one record, and the attendance calendar and the live map agree.

A quick rollout plan

  • Week 1: set up sites, teams and pay periods; invite the staff; have them install the app and clock in once from the office.
  • Week 2: run the app alongside your old sheets. Compare the two at the end of the week and correct the differences, with reasons.
  • Week 3: switch. Approve the first period in the app, export the CSV, run payroll from it, and keep the old sheets for that period only.
  • Every period: approve, lock, export. Review the working time flags and the corrections list once a month.

Frequently asked questions

Does UK law require a clocking in system?

No law names one. You must keep records sufficient to show you pay at least the National Minimum Wage and comply with the Working Time Regulations, and for most small businesses an app is the simplest way to produce them. HMRC can ask to see minimum wage records.

How long must I keep time records?

National Minimum Wage records must be kept for six years. Working time records that show you comply with the weekly limit must be kept for two years. Keep the longer period for everything to be safe.

Can I use fingerprint or face recognition to clock in?

You can, but biometric data is special category data under UK GDPR, which means a stricter lawful basis, a data protection impact assessment and a real alternative for staff who refuse. The ICO has acted against employers using facial recognition for attendance. Most small businesses do not need it; a phone app with location at clock-in stops buddy punching without biometrics. SafetyEvo does not use biometrics.

Should staff be able to correct a clock-in?

Yes, with a reason, with approval, and with the original kept. A record you can silently rewrite is worthless in a dispute. Look for an edit history, not an edit button.

What about breaks?

The app should record breaks, because unpaid breaks come off the hours and the Working Time Regulations entitle workers to a 20 minute rest break on a shift over six hours. A one tap break with a reminder is enough.

Can one app do clocking in and lone worker safety?

Yes, and it is the natural pairing: a shift has a start and an end, and both attendance and protection hang off the same two moments. SafetyEvo starts tracking and the timesheet from the same tap.

How this guide was written

Written by the SafetyEvo team, who build lone worker safety software and use it in their own field business. Every legal point is checked against the primary source listed below, the guide carries the date it was published and the date it was last reviewed, and it is corrected when the law or the guidance changes. It is general guidance, not legal advice for your situation.

Sources

This article is general guidance, not legal advice. For your own situation, speak to a health and safety or legal adviser.

Put this into practice.

See how SafetyEvo covers the keep in touch and raise the alarm parts of your lone working policy.