36.7 hours was the average actual weekly hours worked for full-time UK workers in April to June 2026. That figure sits below the old 40-hour assumption, and it changes how HR directors should think about contracts, payroll models, and capacity planning.
For anyone running time and attendance in a Microsoft-centric HR stack, that gap matters. If your policies still treat full-time work as a neat round number, your approvals, overtime logic, and reporting will drift away from how people work.
Table of Contents
- What Full-Time Work Actually Means in the UK Today
- Working Time Regulations Every HR Team Must Know
- The Hidden Cost of Unpaid Overtime and Under-Recording
- Full-Time Versus Part-Time Workforce Patterns
- Flexible Working and the Time-Tracking Gap
- Configuring Time and Attendance in a Microsoft HR Platform
- Building a Compliant Record-Keeping Practice
What Full-Time Work Actually Means in the UK Today
The modern UK benchmark for full-time work is practical, not symbolic. The Office for National Statistics reported 36.7 hours as the average actual weekly hours worked for full-time workers in April to June 2026, which is a useful baseline for workforce planning in Microsoft-based HR systems, especially where managers still assume a standard 40-hour week. ONS Labour Market Release
That matters because the difference between policy language and actual practice shows up everywhere. It affects shift patterns, salary modelling, overtime approval, and how accurately line managers judge capacity when they promise deadlines or approve absences.
The baseline is a planning tool, not a slogan
Practical rule: set your internal standard from real UK working patterns, then build exceptions around the contract, not around a legacy assumption.
In operational terms, that means using the observed hours baseline to test whether your contracts, rota rules, and overtime thresholds make sense together. If payroll assumes one thing and time capture records another, the result is usually messy reconciliation rather than better control.
The official statistics also help HR teams avoid overpromising in recruitment. A role can still be full-time without fitting the mythical 40-hour mould, and candidates increasingly notice when the job advert, the contract, and the actual schedule don't line up.
Full-time labour still drives workforce design
The wider UK labour market picture reinforces why this benchmark matters. In February to April 2025, there were 25.48 million full-time workers and 8.53 million part-time workers, so full-time workers outnumbered part-time workers by nearly 3 to 1. House of Commons Library briefing
That dominance means full-time patterns shape the default structure of HR reporting, headcount planning, and payroll control. If your Microsoft-based system handles time capture well only for simple Monday to Friday schedules, you'll feel the strain first in the largest part of the workforce.
Working Time Regulations Every HR Team Must Know
The legal framework is tighter than many managers realise. Under the UK Working Time Regulations, employees generally must not work more than an average of 48 hours per week over a 17-week reference period, unless they have opted out, and employers must keep records of working hours. GOV.UK maximum weekly working hours
That record-keeping duty is not a box-ticking exercise. It is what lets HR prove compliance when hours rise, schedules change, or a manager asks for a retrospective explanation after a grievance or inspection.
The rules that need to live in your system
For HR operations, the practical job is to turn legal limits into system rules. That means your time-and-attendance setup should be able to recognise opt-outs, identify people who are close to the weekly cap, and retain auditable history of what was worked and when.
- Weekly limit: the 48-hour average must be monitored over the 17-week reference period.
- Opt-out tracking: if a worker has opted out, the agreement needs to be visible and traceable.
- Time records: the employer has to keep records of working hours, not just payroll summaries.
- Retention: Acas says these records must be kept for 2 years from the date they were made. Acas working time rules
The same framework also defines rest requirements. UK working time rules set a minimum 20-minute rest break when the working day exceeds 6 hours, a minimum daily rest period of 11 consecutive hours in each 24-hour period, and a weekly rest period of at least 24 hours. Some jobs have separate rules that provide a 30-minute break after more than 4.5 hours and a 12-hour daily rest period. PKC working time regulations overview
Night work needs its own controls
Night work is not just a scheduling label. Acas states that night time is the period between 11pm and 6am, and night workers must not work more than an average of 8 hours in any 24-hour period. If the work involves special hazards or heavy physical or mental strain, they must never work more than 8 hours in any 24-hour period. Acas night workers guidance
Employers that rely on spreadsheets for all of this usually end up with evidence scattered across inboxes, calendars, and payroll notes. A configurable HR platform gives you one place to test, approve, and audit the whole pattern.
The Hidden Cost of Unpaid Overtime and Under-Recording
A common compliance gap is assuming salaried staff are covered because payroll runs on time. Unpaid overtime and under-recording still happen when hours are worked but never reach the record that HR and payroll rely on.
The TUC reported that UK workers lost £28.5bn to unpaid overtime, with 3.5 million people regularly working extra hours and averaging 6.8 unpaid hours per week. People Management on TUC unpaid overtime findings That is not a fringe issue. It is a working pattern that should change how HR directors set up time capture.
What to look for in the data
Under-recording usually starts small. A missed lunch break, a late laptop login, or a final call after the scheduled finish time can each look harmless on its own.
Watch for these signals:
- Off-the-clock work: messages, approvals, and project updates happening outside recorded shifts.
- Missed breaks: repeated gaps between work blocks that no one is logging properly.
- Salaried overtime drift: teams treating extra work as invisible because the salary feels fixed.
- Manual corrections: recurring edits to timesheets after payroll checks expose the underlying pattern.
Weak records also create pay risk. Advisory reporting has linked poor time capture to National Minimum Wage underpayment cases, including named employers, underpayments, and affected workers. The compliance lesson is straightforward, if the record is thin, the financial exposure grows.
For HR directors using Microsoft-based systems, the practical question is simple. Can the platform prove what happened if a timesheet is challenged six months later, or does the business have to reconstruct the week from memory, inboxes, and payroll notes?
Full-Time Versus Part-Time Workforce Patterns
Part-time working now accounts for about a third of the workforce, so HR teams cannot treat it as a side case. The operational difference is not just headcount. It is how you handle pro-rata pay, variable coverage, holiday accrual, and approvals without distorting the record. House of Commons Library briefing
That has practical consequences inside payroll and reporting. Full-time workers usually need time capture that can cope with overtime, rest breaks, and exceptions to the standard day. Part-time workers need cleaner pro-rata logic and tighter controls, so absence, holiday, and pay stay aligned with the contracted hours.
Why the difference matters inside payroll and reporting
The risk sits in the gap between contract design and live scheduling. A full-time pattern can absorb a small amount of variance, but a part-time pattern exposes weak setup quickly if the system does not apply hours, leave, and pay rules consistently.
For HR directors using Microsoft-based systems, configuration discipline matters. If the platform cannot separate a standard day from a reduced-hours contract, or a manager-approved change from an informal swap, your reports may look clean while the controls underneath stay weak.
A useful internal reference is this overview of workplace arrangements. The point is not classification for its own sake. It is matching time rules to the actual contract so payroll, absence, and reporting speak the same language.
What good configuration looks like
A workable setup does three things well. It keeps the contract model clear, routes exceptions to the right approver, and preserves the audit trail so payroll does not have to reconstruct the week later.
That sounds basic, but many HR teams still fall into manual workarounds. They design the contract, then let every variation become an exception, which turns reporting into a patchwork and makes it harder to spot where part-time and full-time patterns are drifting away from policy.
Flexible Working and the Time-Tracking Gap
Flexible working is now common, but common policy language doesn't guarantee clean time capture. CIPD reported in 2025 that 91% of employers offer some kind of flexible working, yet employees still most often use homeworking in normal hours (50%) and flexi-time (38%), while unmet demand remains strong for a 4-day week (45%), compressed hours (25%), and flexi-time (20%). CIPD flexible and hybrid working report
That gap is where time-and-attendance systems either help or fail. Policy can say “flexible”, but the software still has to know when the day started, when it paused, who approved the variation, and whether the recorded hours are fair to the employee and the business.
Fragmented work needs different controls
The issue isn't whether flexibility exists. It's whether HR has enough structure to measure it without forcing everything back into a fixed shift.
A separate UK study reported 67% of workers are interested in microshifting and 44% would reject a job without flexible hours, which tells you the demand is now embedded in hiring and retention conversations. CIPD flexible and hybrid working report
This is also where many managers struggle. They want trust and autonomy, but they still need time data that can survive payroll checks, absence reviews, and complaints about unfair treatment. That means fragmented hours, split shifts, and varied start times need proper approvals, not just a free-text note.
The uncertainty HR still has to manage
HMRC backed away from plans to require employers to report hours worked through PAYE RTI from April 2026, which leaves employers to decide what internal hours data they still need for compliance, payroll accuracy, and planning. CIPD flexible and hybrid working report
The practical answer is to keep enough detail to prove decisions, not so much that the process becomes burdensome. If people work in short bursts across the day, the platform needs a reliable way to consolidate those fragments into one auditable record.
Configuring Time and Attendance in a Microsoft HR Platform
A Microsoft-based HR platform works best when it treats time capture as a controlled workflow, not as a passive timesheet dump. In HRManagement365.com, for example, time and attendance can be set up for time capture, review, and approval using start/stop, grid entry, mobile, browser, Microsoft environment, or a clocking terminal, with approved records feeding reporting and downstream HR, ERP, project, or payroll processes.
That kind of setup matters because it lets HR separate raw entry from approved fact. The employee records the time, the manager reviews the exception, and payroll only receives data that has already passed the agreed rules.
HR Management 365 time and attendance
Start with the contract rules
The contract should drive the workflow. Set the normal hours, define where overtime begins, and make sure the platform can distinguish between standard work, approved extra work, and work that needs escalation.
Then configure the checks that sit around the contract. Opt-out tracking should be visible, night worker limits should be enforced by rule, and breaks should be captured in a way that lets HR prove the rest pattern later.
Make approvals do the heavy lifting
The approval chain should be lean, but not casual. Managers need a clear place to confirm exceptions, and HR needs an audit trail that shows who approved what, when, and under which rule set.
Practical rule: if an exception can be changed after payroll without a trace, the control is too weak.
That is where Microsoft Power Platform helps. Modular design lets organisations start with core time tracking and then extend into leave, reporting, and wider HR processes without rebuilding the whole setup. It also keeps employee access inside familiar tools such as Teams, Outlook, browser, and mobile, which reduces the amount of training needed for everyday use.
Building a Compliant Record-Keeping Practice
A compliant record-keeping practice is a protection layer, not just an audit chore. Under the Working Time Regulations, employers must keep adequate records, make them available for inspection by the Health and Safety Executive, and retain them for 2 years. Those records should include workers who exceed the 48-hour limit with their opt-out agreements, plus night workers and the hours they work. PKC record keeping requirements
The same principle applies operationally. If records are complete, HR can answer questions quickly, support payroll with confidence, and spot patterns before they become a dispute.
What should be retained
- Working hours: enough detail to show what was worked.
- Opt-out agreements: proof of who has agreed to the 48-hour exception.
- Night work data: the hours worked by night workers.
- Retention control: a process that keeps records for 2 years and then reviews them.
The cleanest process is usually digital, searchable, and attached to the employee record rather than scattered across email folders. That keeps the administrative burden down and makes inspection response far easier.
If your team needs a central document trail, the HR document centre pattern is useful because it puts evidence and policy material in one controlled place rather than across multiple shared drives.
If you want a Microsoft-based approach that ties time capture, approvals, compliance evidence, and reporting into one HR workflow, speak to HR Management 365. Their platform is built to support UK working-time controls inside the Microsoft ecosystem, and it's a sensible place to start if your current process still relies on spreadsheets and inbox chasing. Visit HR Management 365 to discuss your time and attendance setup, then call +441522508096 today or send a message at https://www.hrmanagement365.com/contact/
