Why tracking assignment length matters for AWR compliance

The 12-week qualifying period is only meaningful if an agency actually knows, accurately and in real time, where every current assignment sits against it. That sounds straightforward for one placement — it gets genuinely difficult at scale, especially once breaks in assignment and role changes are factored in, both of which can affect the calculation.

The risk of getting this wrong runs in both directions: failing to flag a worker who's crossed the threshold denies them rights they're legally entitled to and exposes the agency to a claim; incorrectly flagging someone who hasn't actually qualified creates unnecessary cost and confusion with the hirer.

Why a spreadsheet stops being reliable

A spreadsheet with a start date and a formula for week 12 works fine for a handful of assignments watched by one person who remembers to update it. It stops working once there are multiple consultants updating the same file, multiple hirers with their own start and end dates, and workers who've had a break, a role change, or a second assignment layered on top of the first. The formula itself might be fine — the problem is that nobody notices when an update was missed, because a spreadsheet doesn't flag its own staleness.

What accurate tracking actually requires

• –A start date per assignment, per hirer, per role — not one date per worker if they're active across several placements
• –A way to record breaks and whether they reset or preserve progress toward the 12 weeks, per the current rules for that type of break
• –A way to flag a genuine role change, distinct from a cosmetic one, and its effect on the qualifying period
• –A rolling view of who's approaching the threshold in the next one to two weeks, not just who's already crossed it

A worked scenario

A worker starts with Hirer A in week one. In week eight, they take a fortnight off for a personal reason, then return to the same role with the same hirer. Whether that break resets the count depends on its length and reason under the current rules — which means the tracking system needs to record not just that a gap happened, but why, in order to calculate the resulting date correctly. A worker record that only stores a start date and an end date can't answer that question later without someone manually reconstructing the timeline from memory or old emails.

Building this into everyday operations

What tends to work is treating the 12-week countdown as a standing, visible figure against every active assignment — not a calculation someone runs manually when a query comes up. That's the same principle behind good operational KPI tracking more broadly: the numbers that matter need to be visible without anyone having to go looking for them. A desk that can see, at a glance, which workers cross the threshold in the next fortnight can get ahead of the pay and terms conversation with the hirer, rather than reacting to it after the fact.

What ownership looks like when things get busy

AWR tracking tends to degrade first during the busiest periods — exactly when a desk is placing the most workers and has the least spare capacity to double-check a spreadsheet formula. This is worth planning for explicitly rather than hoping discipline holds under pressure: decide in advance who's responsible for reviewing approaching thresholds each week, what happens if that person is unexpectedly out, and make sure the answer to who's covering this isn't just whoever remembers. A single point of failure in AWR tracking is a real operational risk, not just a compliance one.

It's also worth accepting that perfect precision to the day isn't always achievable, and shouldn't be the bar — what matters is that the agency has a defensible, consistent method applied the same way every time, with enough buffer built into the flagging point that an occasional imprecise edge case doesn't translate into a missed threshold. A system that's roughly right and consistently checked beats one that's theoretically exact but only reviewed sporadically.

What a good system flags automatically, versus what still needs judgement

A tracking system can reliably flag dates — start dates, elapsed weeks, approaching thresholds. What it generally can't do on its own is judge whether a given break or role change genuinely resets the clock under the current rules; that still requires a person applying the regulation to the specific facts. The useful design is one where the system surfaces every case that needs a judgement call clearly and early, rather than either making the call silently and incorrectly, or burying the decision in a spreadsheet nobody reviews until it's too late to act on it.

It's worth involving whoever actually built or maintains the tracking system in a periodic review of edge cases the desk has encountered — breaks, role changes, disputed dates — so the system's rules stay aligned with how the regulation is actually being interpreted in practice, rather than drifting away from real cases over time as the team that set it up moves on to other things.

Multi-hirer workers and the tracking challenge they create

A worker taking concurrent or sequential assignments with different hirers through the same agency needs the 12-week clock tracked separately for each hirer relationship — time accrued with Hirer A doesn't count toward a qualifying period with Hirer B, because the comparison and the obligation are both specific to that hirer. A tracking system built around "time since this worker started with us" rather than "time in this specific role with this specific hirer" will get this wrong, understating or overstating the position depending on how the worker's history happens to be structured. This is a common source of error precisely because it looks like it should be simple and isn't.