Ask a group of UK employers what time tracking means and you will hear three different answers. Some mean the hours that feed payroll. Some mean evidence of when people worked. Others mean absence records. Buyers often use time tracking, timesheets and attendance interchangeably, then purchase a tool that solves the wrong problem. That mistake is expensive, and as practitioners often find, tools bought for the wrong record rarely survive a second audit cycle. Many employers find they need two of the three: hours for pay, working-time evidence for holiday pay, and absence data for planning.

This tutorial separates the three records by the questions they answer. Time tracking measures working time as the Working Time Regulations define it. Timesheets capture the hours-for-pay record. Attendance tracking reveals absence patterns for planning. You will learn why UK employers keep mixing them up, what each record is actually for, what UK law requires you to evidence, and which records your business needs. We then show how to specify requirements before you compare time tracking software, where one platform fits, and where it does not. By the end, you will know which of the three records to ask for first.

Why UK employers keep mixing up time tracking, timesheets and attendance

All three terms describe the same workforce, so they get spoken about as if they were one thing. They are not. Time tracking measures when work happens. A timesheet turns hours into pay. Attendance records presence, absence and pattern. Different questions, different data.

The confusion surfaces at the point of buying. A buyer searches for time tracking, lands on a tool built for another purpose, buys it anyway, then finds the record they actually needed is missing or half-built. Tools are rarely abandoned over features. They are abandoned when the record cannot serve the obligation or decision behind it: a pay run needing approved hours, or a rolling 17-week working time picture that a daily clock-in log cannot produce. The 48-hour weekly limit is normally averaged over 17 weeks, not measured day by day.

The practical fix is vocabulary, not technology. Name the record you need, the period it covers and who approves it before any demo. That is why a single search so often ends in the wrong purchase.

Time tracking: what are you actually measuring?

Time tracking is the raw measurement layer: when work starts and stops, when breaks are taken, which shift someone worked and how long it lasted. It is capture, not judgement, so it holds no opinion about whether an hour is payable.

Under the Working Time Regulations 1998, working time is time when the worker is at the employer’s disposal and carrying out work activities, duties or training, as Acas sets out. That is narrower than being clocked in. Routine commuting to a fixed workplace usually does not count, and neither do rest breaks where no work is done. A system that treats every clock-in as payable time will misread both.

Design choices matter more than the label on the box: kiosk, phone or terminal capture; automatic break deduction or break by exception; whether site-based staff need location confirmation; and whether salaried staff are tracked at all. When employers ask for time tracking employees can use without friction, the real requirement is usually a weekly total per worker that can be approved and exported, not a minute-by-minute daily log. That weekly total is also where time tracking stops and the timesheet begins.

Timesheets: the hours-for-pay record

A timesheet is a payroll instrument. It converts tracked or claimed time into a payable figure: basic hours, overtime, shift premiums, allowances and adjustments, normally after a manager approves it. That approval is the boundary between the two records. Time tracking measures; a timesheet is a pay decision with a name attached to it. Most systems show them side by side, which is exactly how they get blurred.

Because it exists to pay people, a timesheet is governed by two qualities only: accuracy to the agreed terms and a clear approval trail. Granularity beyond that is optional, and paying for it is a common buying mistake. Shift allowance is not statutory, but once it is contractual or established by custom and practice it becomes enforceable, and failing to pay it may amount to an unlawful deduction of wages, as Davidson Morris sets out on shift allowance.

Period is the quiet variable. A weekly or monthly cut-off decides which hours land in which pay run, so settle timesheet period and pay frequency together rather than accepting software defaults.

This is where this article’s sources stop. Holiday pay calculation and its supporting records, payroll record retention periods and National Minimum Wage record-keeping are governed elsewhere and were not available here. Raise them with your payroll provider or adviser.

Attendance tracking: absence patterns, not hours

Timesheets settle what is owed. Attendance tracking answers a different question: who was present, who was absent, why, and whether that absence is forming a pattern a manager needs to act on.

Its data is usually categorical rather than numerical: absence type (sickness, holiday, unpaid leave), duration, return-to-work date, and a frequency measure that distinguishes repeated short absences from one long period. The pattern matters more than the total.

This is the least independently evidenced of the three records. Absence benchmarks, and the claim that absence data improves planning, are operational arguments rather than regulatory requirements. Treat them as management rationale, not legal obligation.

Attendance feeds capacity decisions: rota gaps, shift cover, and whether a vacancy is a headcount problem or a scheduling problem. That is planning, not pay, and it rarely belongs in the same report as a pay run.

It is also the record employers most often assume comes free inside a time tracking tool, then discover it does not. Ask specifically whether absence is recorded as its own event, separate from hours.

What UK law actually requires you to evidence

That absence picture matters for planning, but it is not the same as your working time evidence. Acas says employers do not need records of every daily hour. Unless a worker has opted out, you must be able to show the 48-hour weekly maximum is respected, a 17-week average, not a daily ceiling. Opt-outs should be agreed and kept as a separate record, because they change what you must evidence. Workers under 18 cannot exceed 8 hours a day or 40 hours a week.

The duty also covers night work. You need records showing night-work limits are not breached and that regular health assessments are offered to night workers. A daily clock-in export generally will not demonstrate either point.

The Working Time Regulations cover holiday entitlement and apply to agency, casual, seasonal and zero-hours workers, so a flexible workforce is not an exemption. Normal rules have exceptions, including 24-hour staffing, the armed forces, emergency services, security, and unmeasured roles where workers control their own decisions. Confirm which apply before designing the report.

Which records does your business actually need?

With those obligations clear, the practical question is which records your business must produce as routine evidence.

Question one: how do I pay people? Where pay depends on hours worked, shifts taken or overtime, you need a timesheet, possibly fed by time tracking. If everyone is salaried on fixed pay, a timesheet adds overhead rather than value.

Question two: can I prove we respect the 48-hour average? Working time records must support a 17-week average (covered above); a daily presence log will not suffice.

Question three: do I plan staffing around absence? If shift cover, rota gaps or repeated sickness consume management time, attendance must be its own record, with absence types and a frequency view.

Map the answers onto the three record types. Many employers find they need two: a salaried office with occasional overtime may need working time evidence only; a shift-based hourly operation typically needs timesheets plus attendance.

Write this as a one-page requirement list: record type, period covered, approver and retention period. That document, not a feature checklist, makes the buying conversation productive.

Specifying requirements before you compare software time tracking

Ask in three parts: which record do I need, over what period, and who signs it off. Vendors tend to answer the period honestly and the record type enthusiastically, so be specific.

Put four questions to every provider:

• How is a break recorded and deducted?
• Can you show a rolling 17-week average per worker?
• How is absence stored as a separate event from hours?
• What exactly is handed to payroll, and when?

The pay handoff is where implementations fail. Ask for the timesheet cut-off, the approval step, the correction or dispute route, and whether the export reconciles against a pay run.

Watch for three red flags: tools that only report daily clock-ins, tools that treat any clock-in as payable time by default, and tools with no absence record distinct from hours. Each is a mismatch with one of the three records, not a missing feature.

Budget by record type rather than by seat where possible. Buyers who do this often find they need one or two records and can drop a licence line they were about to pay for out of habit.

Where one platform fits, and where it does not

Treat that requirement list as the test any platform has to pass. Staffly describes its product as a single platform combining scheduling, time tracking, HR and compliance, shift cover and payroll readiness, without the complexity of traditional workforce software. That is Staffly’s own description of its offer, not independent evidence.

Held against the framework above, the description maps onto two branches: attendance planning through scheduling and shift cover, and the pay branch through time tracking and payroll readiness.

A single platform is genuinely useful once you have named the records you need and want them captured in one place under one approval flow, with one place for staff to see their own hours. It is not a shortcut past the taxonomy. Bundling records into one product does not make them the same record; the purpose of each still decides what has to be captured, approved and exportable.

If your requirement list turns out to be a single record type, say working time evidence only, then one platform is more than you specified. It is fair to say so.

Three records, three questions: what to do next

Start with the one-page list from the previous section, not a software shortlist.

Match the period to the purpose. Timesheets follow the pay run. The 48-hour average needs a rolling 17-week window. Absence planning needs a rolling absence view. A tool that only reports daily will fail two of those.

Ask for exports, not dashboards, these are documents, not charts.

Then compare software time tracking against that one-page list. Getting the taxonomy right first is what stops the second purchase.

Conclusion

Time tracking, timesheets and attendance are three separate records, not three labels for one thing. Time tracking measures activity or working time; timesheets support pay; attendance reveals absence patterns. UK law may require you to evidence working time, approved timesheets and absence reports, so exports matter more than dashboards. Match each record to its purpose and period, write the one-page requirement list, and ask providers for exportable documents. Do that list first. It is the simplest way to avoid a second purchase and choose a tool that actually fits.