Weekly payroll for shift workers is hard for a simple reason: nothing stays the same from one week to the next. Hours change, rates change with the day of the week, and holiday and sickness depend on a rota that may repeat only every few months. In transport and logistics, warehouses, care homes, hospitality and manufacturing, that is normal. When HR and payroll sit in separate systems, every one of those changes is entered twice.
In short:
- Weekly payroll for shift workers takes long because hours, rates and allowances change every week and are often re-keyed from spreadsheets.
- The real problem is usually HR and payroll that do not speak to one another, so starters, leavers, holiday and sickness are entered twice.
- Get working patterns right first: holiday entitlement, holiday pay and absence all depend on them.
- Check weekly pay against approved hours and pay rules, not against last week’s pay.
- When you have outgrown your payroll software, look for weekly and monthly payrolls, rotas, time and attendance, leave and HR on one platform.
A common picture in shift-based businesses: a small HR and payroll team runs weekly and monthly payrolls for several companies in one group, for hundreds of employees who work days, nights, weekends and rotating rosters. The payroll software is not ticking the boxes any more, and the HR system does not speak to it. The goal is a one-touch approach: enter something once, and have HR and payroll both see it.
This guide covers where weekly payroll for shift workers goes wrong, what to fix first, and a checklist for when you have outgrown your payroll software.
Why weekly payroll for shift workers takes so long
For salaried staff, payroll is mostly the same as last month plus a few changes. For hourly shift workers paid weekly, every pay run starts from scratch.
A typical week looks like this:
- Hours arrive on spreadsheets. Each site or depot sends its own spreadsheet of hours, sometimes with paper timesheets as well. Someone combines them into one master spreadsheet.
- Hours are typed in one by one. Each person’s hours are keyed into payroll by hand, against the right pay element.
- There are many pay elements. Weekday and weekend rates, overtime, nights, and allowances such as meal and overnight allowances. In businesses that run several kinds of work, each with its own rates, pay elements can run into the hundreds.
- Pay runs a week in arrears. The pay week runs, for example, Saturday to Friday, and payroll processes it the following Monday and Tuesday for that week’s pay day.
- Starters and leavers never stop. Shift-based businesses often have high staff turnover, so new starters, leavers and contract changes (dropping hours, moving to a 4-on-4-off pattern) arrive every week.
Put together, preparing the weekly payroll can take a day or two of every week before anyone has checked a single payslip.
A worked example: one week paid in arrears
Take a warehouse operative paid weekly, one week in arrears:
- Pay week: Saturday 7 to Friday 13 November 2026.
- Hours approved: Monday 16 November.
- Paid: Friday 20 November.
That week they worked 32 weekday hours at £12.50 an hour and 8 weekend hours at a weekend rate of £15 an hour, plus two meal allowances of £5:
| Pay element | Calculation | Amount |
|---|---|---|
| Weekday hours | 32 × £12.50 | £400.00 |
| Weekend hours | 8 × £15.00 | £120.00 |
| Meal allowances | 2 × £5.00 | £10.00 |
| Gross pay | £530.00 |
Next week the same person might work only weekdays, or pick up nights. Every line changes, which is why weekly payroll cannot simply copy last week.
The real problem: HR and payroll that do not speak to one another
Most teams in this position do not have a payroll problem or an HR problem. They have a gap between the two.
When HR and payroll are separate systems, the same information is entered twice:
- New starters. HR collects the starter checklist, P45, bank details and right-to-work documents, adds the person to the HR system, then passes paperwork to payroll, which enters it all again.
- Leavers and changes. Every leaving date, change of hours, bank details change and contract variation is entered in both systems.
- Holidays. Holiday is booked in the HR system but paid from a separate spreadsheet, because the HR system’s working patterns are not accurate enough to feed payroll.
- Sickness. Employees tell their manager, sick notes are passed to HR and payroll, and both record the absence separately.
Every duplicate entry is a chance for the two systems to disagree. Over time, people lose faith in the HR system, stop updating it and go back to doing everything manually in payroll. That is the opposite of what the HR system was bought for.
Employees feel it too. It is common for shift workers to have one app to book holiday, another to see their payslips, and another for their pension, each with its own username and password.
Get the working patterns right first
If there is one lesson from teams that have been through this, it is that working patterns come first. Without them, nothing else will work.
Shift-based businesses rarely have one pattern. The same company can have:
- Monday to Friday office staff
- Full-time contracts of 40 hours a week
- Zero-hours contracts
- Fixed rotas, such as 4 on, 4 off
- Rolling rosters that repeat over many weeks
- Contracts with very precise hours and minutes
If the system holding these patterns cannot represent them accurately, holiday entitlement will not add up, absence cannot be valued correctly, and holiday cannot feed payroll. Teams then fall back on a holiday spreadsheet, and the HR system becomes a record of which days someone had off, nothing more.
Before you choose a new system, write down every working pattern you have, with a real example of each, and test that the new system can hold all of them. For the holiday side, see our guide to holiday entitlement for shift workers on 4-on-4-off and 12-hour shifts.
Holiday pay and sickness for shift workers
Getting the pattern right matters because holiday pay and sick pay for shift workers depend on it.
| Type of shift worker | Holiday entitlement | Holiday pay |
|---|---|---|
| Regular hours on a fixed rota, such as 4 on, 4 off | 5.6 weeks a year, turned into shifts or hours (19.6 shifts a year on 4 on, 4 off) | Normal pay when leave is taken. If pay varies, the average over the previous 52 paid weeks |
| Irregular-hours and zero-hours workers | 12.07% of hours worked in each pay period, for leave years from 1 April 2024 | The average over the previous 52 paid weeks when leave is taken, or rolled-up holiday pay of 12.07% |
- Holiday pay is based on an average. For workers whose pay varies, GOV.UK guidance says employers should normally look back over the previous 52 paid weeks. Weeks with no pay are skipped, and the look-back stops at 104 weeks.
- “Normal” pay includes more than the basic rate. For the first four weeks of statutory leave, holiday pay must reflect normal pay, which includes regular overtime and other payments linked to the work. Expenses that are only incurred when working, such as travel between work locations, are excluded.
- Irregular-hours workers follow different rules. Zero-hours and other irregular-hours workers build up leave at 12.07% of hours worked. See holiday entitlement for irregular-hours and zero-hours workers.
- Sick pay depends on qualifying days. For shift workers, statutory sick pay follows the days they would normally work. Since 6 April 2026, SSP is paid from the first full day of sickness, with no waiting days and no lower earnings limit, according to GOV.UK. See statutory sick pay for shift workers.
If weekend rates, nights and allowances are calculated on a spreadsheet outside payroll, the 52-week average has to be rebuilt from that spreadsheet too. That is one more reason to get hours and pay rules into one place.
Checking weekly payroll when every week is different
Checking a payroll usually means comparing it with the last one. For salaried staff, a big difference stands out. For shift workers, it does not.
A driver, carer or warehouse operative might work five days one week and three the next. Their pay goes up and down every week, so large variances are normal and “different from last week” tells you very little. Payroll teams end up as detectives, opening last week’s payslip for each person to work out what changed.
Better checks ask a different question: does this pay match the approved hours and the pay rules? Some practical steps:
- Check pay against approved hours, not against last week’s pay.
- Look for missing data first: no hours, no pay rate, no bank details.
- Flag only the variances that the approved hours do not explain.
- Keep a record of who approved the hours and who approved the payroll.
Most employee pay queries in shift-based businesses come from hours that were wrong at source, for example a manager sending the wrong hours, not from tax or calculation errors. Fixing the input fixes most of the queries.
A checklist for when you have outgrown your payroll software
If your payroll software is no longer ticking the boxes, it is tempting to replace it like for like. Changing payroll is also the best moment to look at HR, rotas and time and attendance at the same time, so that everything lives on one platform.
Questions to ask any supplier:
- Pay frequencies and companies. Can it run weekly and monthly payrolls side by side, for several companies and PAYE schemes in one account?
- Working patterns. Can it hold every pattern you have, including rolling rosters, 4 on 4 off and zero hours? Ask to test it with your real examples.
- Pay rules. Can weekday and weekend rates, nights, overtime and allowances be set up once and applied to approved hours, instead of typed in each week?
- Timesheets. How do hours get in? Clocking in from a phone, a shared device or a site location removes the spreadsheet and the paper timesheet.
- Holiday and sickness. Do approved holiday and sickness go straight to payroll, and are entitlements calculated from the actual working pattern?
- New starters. Can new starters fill in their own details, bank details and starter checklist online before their first shift?
- Permissions. Can you give HR and payroll full access, and line managers and senior managers only what they need?
- Pensions and accounts. Can it produce your pension provider’s file and your accounting journals?
- Employees. Do employees get one app for rotas, holiday, payslips and their details?
- Implementation. Who moves your data, how are discrepancies between your HR and payroll data found, and can you go live in phases?
On that last point: if your data has been entered by hand by different people over several years, expect a clean-up. The same role with four different job titles, start dates that differ between HR and payroll, and old pay elements nobody uses are all common. Clean data before moving it, or the new system will inherit the old problems. Going live in phases, for example one company or HR first, is safer than switching everything on one day. Our guide to switching payroll providers mid-year covers the payroll side of the move.
How Givver handles weekly payroll for shift workers
Givver is UK HR, rota, time and attendance and payroll software for shift-based businesses, including warehouse and logistics, care homes, hospitality and manufacturing. HR, rotas, time and attendance and payroll share one employee record, so approved changes are already there when payroll runs.
- Rotas and working patterns. Rota templates cover each pattern, including rotating patterns such as 4 on, 4 off. See complex working patterns.
- Clock-in and approved hours. Employees clock in from their phone, a shared site device or a QR code, and managers fix exceptions and approve hours. See time and attendance.
- Pay rules. Nights, weekends and overtime are set up once and applied to approved hours. See overtime and shift premiums.
- Leave that feeds payroll. Employees request leave, managers approve it, and payroll and rotas see the result. See leave and absence.
- Several companies. Several entities and PAYE schemes run in one account. See multi-entity payroll.
- Checks before approval. Large changes and missing data are flagged before your team approves the payroll. See payroll accuracy.
FAQs
What should payroll software for shift workers do?
It should run weekly and monthly payrolls side by side, hold every working pattern you use, take approved hours from rotas and clocking straight into payroll, apply weekend, night and overtime rates automatically, and send approved holiday and sickness to payroll without re-keying. Givver brings rotas, time and attendance, HR and HMRC-recognised payroll together on one employee record. See complex working patterns.
What does paying a week in arrears mean?
It means employees are paid for the week that has just finished, not the current week. For example, hours worked from Saturday to Friday are processed the following week and paid on that week’s pay day. It gives payroll time to collect and approve the hours.
How is holiday pay calculated for shift workers?
For workers whose pay varies from week to week, a week’s holiday pay is normally the average weekly pay over the previous 52 paid weeks, skipping weeks with no pay. For the first four weeks of leave, that average should include regular overtime and other payments linked to the work.
Can weekly and monthly payrolls run in the same system?
Yes, in most modern payroll software, but check that it can run them side by side, for every company and PAYE scheme you have, with separate pay dates.
Why do HR and payroll systems need to be connected?
So that starters, leavers, changes, holiday and sickness are entered once. When they are separate, every change is entered twice, the two systems drift apart, and errors are often found by the employee on their payslip.
This guide is general information, not legal or tax advice. For a specific situation, speak to Acas or a payroll adviser.
Weekly payroll for shift workers will never be as simple as a monthly salaried payroll, but it does not have to take two days of re-keying every week. Get the working patterns right, capture hours once, and let HR and payroll share the same data. See how Givver handles it.