Peak season: staying compliant when placements spike and the shifts are short
For a large part of the temporary labour market, the final quarter is the year. Warehousing, logistics, retail, hospitality and food production all surge, and they surge in a particular way: a lot of workers, registered quickly, placed on short assignments, often starting within days of first contact. It is the highest-volume, lowest-margin, fastest-moving period an agency handles.
It is also the period when the compliance controls that work comfortably at normal volume start to bend. Not because anyone decides to cut corners, but because every control in a recruitment agency has a throughput limit, and peak is when you find out what yours is.
Right to work is the one that cannot flex
Everything else on this list is a matter of getting it right. Right to work is a matter of civil penalty exposure, and the exposure is per worker. An agency that places four hundred people in November and gets the process wrong on even a small proportion of them has a materially different problem from one that makes the same error on two placements in a quiet month.
The pressure in peak is specific and predictable. A client needs forty people on Monday. A candidate turns up on Friday without the right documents and says they will bring them in. A branch is three people down and the person doing checks is also doing payroll queries. Every one of those is a situation where a check gets deferred with the best of intentions, and deferral is where the exposure lives. How right to work checks work for agencies, and what a compliant check actually looks like sets out the detail — and as with anything in this area, the current Home Office employer guidance is the authority, not a summary of it.
The practical peak-season control is a hard gate rather than a reminder. A worker cannot be assigned to a shift until the check is complete and recorded, enforced by the system rather than by a person's judgement under pressure. Agencies that rely on "we always check before they start" rather than on something that physically prevents an uncovered assignment tend to discover the exception in January, when someone reconciles the records.
Short assignments do not reset the AWR clock the way people assume
The twelve-week qualifying period for equal treatment is widely understood as a rule about long placements, which makes it easy to assume peak season is irrelevant to it. Short assignments, over by January, nothing to worry about.
That assumption breaks in two places. The first is the worker who did six weeks for the same hirer in the spring and comes back for seven weeks at Christmas — whether those periods connect depends on the rules around breaks between assignments, which are more involved than a simple reset and are covered in our explanation of the twelve-week rule. The second is the worker who is placed with the same hirer through two different roles, or across two sites, where the agency's own records treat them as two separate assignments and the legislation may not.
Peak is when both of these multiply, because it is the time of year when returning workers and multi-site hirers are most common. The control is to track the clock per worker per hirer rather than per assignment, and to be able to see at the point of placement whether someone has prior accrued weeks. Discovering it afterwards is an underpayment to correct and a conversation with a client about charge rates that nobody enjoys having in arrears.
Under-18s turn up in volume at exactly this time of year
Christmas retail and hospitality draw in young workers who are not in the agency's usual candidate pool, and the restrictions that apply to them are a genuinely different set — working time limits, night work restrictions, rest break entitlements, and specific risk assessment duties, with some requirements differing again for those still of compulsory school age.
The failure mode is rarely a deliberate decision. It is a sixteen-year-old being offered an overnight stock shift by a consultant who did not look at the date of birth, in a branch where the booking system does not flag age. What agencies need to check before engaging workers under 18 covers the restrictions themselves; the seasonal action is to make age a visible attribute at the point of booking rather than something buried on a registration record.
Pay accuracy under volume
Two things that are manageable at normal volume become error-prone at peak. The first is national minimum wage compliance, which is less about the headline rate and more about the deductions and unpaid time that can pull an effective rate below it — and peak brings more of exactly those: transport arrangements, kit, induction time, waiting time.
The second is holiday pay accrual on short assignments. A worker who does nine weeks and leaves accrues entitlement, and getting that right across several hundred short assignments is an arithmetic problem that does not forgive a wrong default setting. Both of these are worth checking before the volume arrives rather than after, because at peak the errors are identical and repeated several hundred times rather than isolated.
Onboarding is a throughput problem, and throughput is where quality drops
An onboarding process designed around a consultant walking a candidate through registration does not survive forty registrations in a day. What tends to happen is that the sequence stays nominally the same while the quality of each step degrades: documents photographed badly, references chased and abandoned, the key information document issued late or not at all, and bank details taken by whatever means is fastest.
The useful pre-peak exercise is to time it. Take your onboarding checklist and work out how long a properly completed registration actually takes, then multiply by your expected peak volume and compare against the hours your branch has. If the arithmetic does not work — and it frequently does not — that gap will be closed by someone skipping steps under pressure, and it is better to decide in advance which steps can be restructured than to let the decision be made at four o'clock on a Friday.
The reconciliation that should happen in January
Whatever the controls, peak will produce exceptions. The agencies that handle this well plan a deliberate post-peak reconciliation rather than simply exhaling in the new year.
- Every worker placed in the period, checked against a completed and correctly recorded right to work check.
- Accrued AWR weeks per worker per hirer, including anyone who returned from an earlier assignment.
- Any worker under 18 placed, checked against working time and night work restrictions.
- Effective hourly rates after deductions, spot-checked against the relevant minimum wage rate for each worker's age band.
- Holiday pay accrued and paid for short assignments that have now ended.
- Key information documents issued, and issued at the right point.
Finding a problem in January is unwelcome. Finding it during an audit, or when a worker raises it, is considerably worse — and the difference between the two is usually just whether anybody looked.
Key takeaways
- Make right to work a hard gate that blocks assignment, not a reminder that relies on judgement under pressure.
- Track the AWR clock per worker per hirer, not per assignment — returning and multi-site workers are what peak produces most of.
- Surface date of birth at the point of booking. Under-18 restrictions are a different regime and Q4 is when they arrive in volume.
- Check minimum wage after deductions and unpaid time, and check your holiday accrual defaults before volume multiplies any error.
- Time your onboarding process and multiply by expected volume. If the hours do not exist, decide in advance what changes.
The AgencyOptix team
Written by people who work daily with recruitment agencies on right-to-work checks, AWR compliance and the records that hold up under an EAS inspection.