Reference Periods, Working Hours & Holiday Pay: A Practical UK Rota Guide

What Is a Working-Time Reference Period?

A reference period is the period of time used to calculate an average. For the UK 48-hour weekly working-time limit, the standard reference period is normally 17 weeks. That means one busy week does not automatically create a breach. What matters is the average across the relevant period.

For example, an employee might work 52 hours during a stocktake week, then 40, 42 and 38 hours in later weeks. The single 52-hour week matters, but it needs to be viewed as part of the wider average. This is why rota records should not only show the next seven days. Managers need visibility across several weeks, especially where overtime and cover shifts are common.

GOV.UK explains that workers cannot usually work more than 48 hours a week on average, normally averaged over 17 weeks. It also notes that the averaging period can be extended up to 52 weeks in some agreed circumstances. See the official GOV.UK guidance on calculating working hours .

Why This Matters for Rota-Based Teams

Reference periods become harder to manage when staff do not work the same pattern every week. That is common in hospitality, retail, healthcare support, leisure, cleaning, events and any business that relies on part-time, flexible, zero-hours or seasonal workers.

The problem is not usually one dramatic rota mistake. It is the quiet build-up: someone covers sickness twice, picks up an extra Sunday, swaps into a late shift, then stays longer because the close-down took more time than expected. If those changes are handled through texts, spreadsheets and memory, the average can drift before anyone spots it.

• Managers need the full picture: scheduled hours, worked hours, overtime, unpaid breaks and last-minute changes should not live in separate places.
• Payroll needs clean records: the person paying staff needs to know what was actually worked, not just what the original rota said.
• Employees need confidence: workers are more likely to trust the process when hours, holiday and changes are visible rather than guessed.

Do Overtime Hours Count?

In practical terms, managers should assume overtime needs to be visible in working-time records. The 48-hour average is about working time, not just contracted hours. If someone is contracted for 30 hours but regularly works 45 to 50 hours because of cover shifts, those extra hours are part of the picture.

This is where rota software can help. It is not enough to know that a shift existed. You need to know whether it was worked, whether it ran over, whether a break was unpaid, and whether the person picked up more work elsewhere in the same period. Without that, managers end up trying to reconstruct working-time averages after the fact.

ACAS also explains that the 48-hour weekly maximum is normally averaged over 17 weeks under the Working Time Regulations. Read the ACAS guide to the 48-hour weekly maximum .

A Simple Reference Period Example

Imagine a café supervisor works the following pattern over four busy weeks while two team members are away:

• Week 1: 50 hours
• Week 2: 46 hours
• Week 3: 42 hours
• Week 4: 38 hours

The total is 176 hours. Divided by four weeks, the average is 44 hours. In that simplified example, the employee has worked more than 48 hours in one week, but the average over the four-week period is below 48. For the actual legal check, the relevant reference period is normally longer, which is why managers need ongoing visibility rather than a one-week snapshot.

The operational lesson is simple: do not wait until payroll day to find out whether someone has been carrying too many shifts. Review the trend while the rota is still being built.

Holiday Pay: Why the 52-Week Look-Back Matters

Holiday pay is a separate issue from the 48-hour working-time average, but both rely on good records. For workers whose pay varies, UK guidance commonly uses a 52-week reference period to calculate average weekly pay. Weeks where the worker received no pay are normally skipped, and the employer looks back further, up to the relevant limit, to find paid weeks.

This is especially important for staff whose earnings vary due to extra shifts, overtime, seasonal peaks, different day rates or changing weekly hours. If holiday pay is based only on a quiet week, the worker may be underpaid. If it is calculated from an incomplete spreadsheet, the business may struggle to explain the decision later.

GOV.UK explains how workers with varied pay can calculate average weekly pay using a 52-week approach, and ACAS states that holiday pay for irregular-hours and part-year workers is based on average pay over the previous 52 weeks. Read the GOV.UK guide to holiday pay where pay varies .

Irregular-Hours and Part-Year Workers

Since changes introduced from 2024, there are specific holiday rules for irregular-hours and part-year workers. This matters for businesses that use seasonal staff, term-time staff, casual staff, zero-hours workers or employees whose hours genuinely vary from pay period to pay period.

One area that often causes confusion is rolled-up holiday pay. ACAS describes rolled-up holiday pay as holiday pay spread throughout the year by adding an amount to normal pay, rather than paying the worker when holiday is taken. Employers do not have to use this approach, and it is only suitable in particular circumstances, so it needs to be handled carefully. See the ACAS guidance on rolled-up holiday pay .

The key point for rota managers is that worker type matters. A fixed-hours employee, a variable-hours employee, an irregular-hours worker and a part-year worker may not all be handled in exactly the same way. Your rota records should make it easy to identify the pattern, not hide it.

Common Mistakes Managers Make

Most reference-period and holiday-pay problems start with weak records rather than bad intentions. These are the mistakes that cause trouble later:

• Only keeping the planned rota: the original schedule is useful, but payroll and working-time checks need the hours actually worked.
• Forgetting overtime: extra cover shifts can become normal very quickly in a small team.
• Not recording breaks clearly: paid and unpaid breaks affect the records differently and should not be guessed later.
• Using one quiet week for holiday pay: variable-hours holiday pay needs a proper look-back, not a convenient snapshot.
• Letting swaps bypass management: informal swaps can create fairness, rest and average-hours problems if no one reviews the impact.
• Mixing up entitlement and pay: holiday entitlement is about how much leave is built up; holiday pay is about what the worker should be paid when leave is taken or paid out.

What Good Rota Records Should Show

If a manager, employee, accountant or adviser needed to review a rota decision six months later, the record should answer basic questions without relying on memory.

• Who was scheduled to work?
• Who actually worked?
• What time did the shift start and finish?
• Were breaks paid or unpaid?
• Was the shift changed, swapped, cancelled or extended?
• Who approved the change?
• How many hours has the worker averaged over the period?
• Which weeks should be included for holiday pay averaging?

This is where spreadsheets often become fragile. A spreadsheet can show numbers, but it may not show the story behind the numbers: who changed the rota, when the employee was notified, whether a shift was approved, or whether the final hours differ from the original plan.

How FlowRota Helps Managers Stay on Top of It

FlowRota is built for shift-based teams where rotas, worked hours, leave and changes need to be kept in one place. The goal is not to turn every manager into a payroll specialist. It is to give managers cleaner records before a small rota issue becomes a pay query or compliance headache.

• Track scheduled and worked hours: keep the planned rota and the final working record connected.
• Spot heavy workloads earlier: review hours across a wider period instead of reacting after payroll has closed.
• Keep shift changes visible: swaps, edits and cover shifts are easier to review when they are not buried in WhatsApp messages.
• Support fairer leave and pay records: clearer worked-hours data gives payroll a better starting point for variable-hours calculations.
• Maintain a practical audit trail: managers can see what changed and why, rather than rebuilding the history from memory.

If you are still planning rotas in Excel, it is worth asking one uncomfortable question: could you confidently explain a worker's average hours or holiday pay calculation three months from now? If the answer is no, your rota process is carrying more risk than it needs to.

Internal Checks to Add to Your Rota Process

Even before you change software, managers can improve their process by adding a simple monthly review. Look at who is regularly picking up extra hours, who is close to heavy weekly averages, which shifts are regularly extended, and which workers have variable pay patterns that need careful holiday-pay treatment.

For more on reducing avoidable rota disruption, read our guide to the hidden cost of last-minute rota changes . If you are reviewing your scheduling process more broadly, see how FlowRota helps with staff rota planning for UK shift-based teams.

Quick FAQ

Is the working-time reference period always 17 weeks?

Not always. The normal reference period for the 48-hour average is 17 weeks, but it can be different in certain sectors or where a valid agreement extends the period. Check the official rules for your situation.

Does one week over 48 hours automatically break the rules?

Not necessarily. The limit is normally based on the average over the relevant reference period. A single heavy week can still be acceptable if the wider average remains within the limit, subject to the detailed rules and any opt-out arrangements.

Should regular overtime be visible for holiday pay?

Yes. If overtime affects a worker's normal pay pattern, it can be relevant to holiday pay. The safest operational approach is to keep accurate records of actual hours and earnings rather than trying to decide later from incomplete rota notes.

Can FlowRota replace payroll advice?

No. FlowRota helps managers keep cleaner rota and hours records, but employment-law and payroll decisions should be checked against official guidance or professional advice where needed.

The Bottom Line

Reference periods and holiday pay are not abstract HR topics. They are directly affected by everyday rota decisions: who covers sickness, who works overtime, who swaps shifts, who takes leave, and whether the final worked hours match the original plan.

The businesses that handle this best do not wait for a dispute before checking the numbers. They build rotas with visibility, keep worked-hours records clean, and give payroll reliable data. That is better for managers, better for employees and far less stressful than trying to rebuild months of rota history from a spreadsheet.

Note: This article reflects UK guidance reviewed in May 2026. Employment rules can change, so always check official GOV.UK and ACAS guidance before relying on a calculation.