The AWR 12-week rule, explained

The Agency Workers Regulations (AWR) 2010 give temporary workers certain rights from the very start of an assignment, with further, more substantial rights kicking in once they complete 12 weeks in the same role with the same hirer.

The 12-week figure gets quoted constantly in the sector, usually correctly as a headline and much less reliably once you get into the detail of how it's actually calculated. That gap between the headline and the mechanics is where most AWR problems start.

What changes at 12 weeks

Once the qualifying period is met, an agency worker becomes entitled to equal treatment with a comparable directly-recruited employee on pay and certain core working conditions — including working time, night work, rest periods and breaks, and annual leave. Before that point, entitlements are narrower. See our breakdown of what applies before and after the 12-week mark.

How the 12 weeks is actually counted

The qualifying period runs on calendar weeks in the same role with the same hirer, not weeks actually worked — a week where the worker did fewer hours than usual, or none at all for a permitted reason, can still count toward the total depending on the circumstances. This is one of the more counterintuitive parts of AWR, and it's exactly the kind of detail worth checking against current gov.uk guidance for a specific situation rather than assuming a simple headcount of hours worked.

Same role, same hirer — what actually breaks the chain

A worker who moves to a genuinely different role with the same hirer may restart the clock, but a role change used specifically to avoid triggering equal treatment — moving someone sideways into a nominally different job that's substantially the same work — is exactly the kind of pattern regulation is designed to catch, and treating it as a workaround is a real risk, not a clever solution. A short break in an assignment doesn't necessarily reset the count either; certain breaks, including sickness, holiday, and some short gaps between assignments with the same hirer, can still count toward or preserve progress toward the 12 weeks. The rules here are specific enough that they deserve checking against the current regulations for a given scenario rather than being assumed from a general sense of how it usually works.

Why the qualifying period itself needs careful tracking

The 12 weeks is calculated on time in the same role with the same hirer — which means a break in assignment, or a genuine change of role, can affect the calculation, and getting this wrong in either direction is a real risk: understating it denies a worker rights they're entitled to, and miscounting it the other way can create confusion with a hirer about when equal-treatment obligations actually apply. This is exactly why assignment length needs to be tracked deliberately, not estimated.

What this looks like in practice

• –A worker on a single ongoing assignment with one hirer — the most straightforward case, but still needs the countdown tracked, not assumed.
• –A worker who takes a two-week break for another commitment then returns to the same role and hirer — whether the break resets the clock depends on the reason and length of the gap.
• –A worker moved to a materially different role with the same hirer partway through — a genuine change may restart the count, but the change needs to be real, not cosmetic.
• –A worker supplied to the same hirer through two different agencies at different points — this can still count toward the same qualifying period from the hirer's perspective.

How this affects the charge rate to the hirer

Equal treatment on pay past week 12 usually has a knock-on effect on what the agency needs to charge the hirer, since the agency's own costs rise to cover the comparator-level pay. This is worth flagging to a hirer well before the 12-week point arrives, rather than as a surprise on an invoice — a hirer caught off guard by a rate change right at the qualifying threshold is far more likely to push back than one who was told from the outset that this was coming, and roughly when.

What the agency actually needs to do once the threshold is met

Reaching 12 weeks isn't just a status change to note internally — it requires the agency to actively identify the correct hirer-side comparator's pay and core conditions and apply them from that point forward. That means a conversation with the hirer, in good time, about what a comparable directly-recruited employee in that role actually receives, not an assumption based on what the agency has always paid for similar roles elsewhere. Leaving this until after the threshold has passed, rather than preparing for it in the run-up, is one of the more common ways agencies end up retroactively correcting pay — which is a far harder conversation than getting it right from week 13 onward the first time.

Why this is worth taking seriously even for a small number of long-running placements

It's easy to treat AWR tracking as only worth the effort for agencies running large volumes of temporary placements. In practice, a single long-running assignment that quietly crosses 12 weeks without anyone noticing is just as real a compliance gap as a systemic failure across hundreds of workers — the exposure is proportional to the individual claim, not diluted by how many other placements the agency is managing correctly. A smaller agency with fewer long assignments has less volume risk, but no less obligation to track each one accurately.