Why do repeated short agency assignments create legal risk?

Why repeated agency assignments become legally risky

Repeated short assignments are risky because the legal test usually follows substance, not paperwork. If the same worker keeps doing materially the same job, successive short contracts, small gaps, or relabelled engagements can be treated as an attempt to avoid the 12-week threshold. That creates exposure to equal treatment claims, backpay-style liabilities, and anti-avoidance findings.

The key issue is continuity of work, not just continuity of contract language. Tribunals and regulators tend to look at whether the assignment, role, site, reporting line, and core duties stayed effectively the same. If they did, a nominal break may not reset the clock, especially where the pattern suggests a deliberate effort to stay below a legal trigger.

In practice, the risk grows when managers use repeated short bookings as a workaround for workforce planning rather than as genuinely separate placements. If the organisation is relying on artificial breaks, reissued statements of work, or changing labels without changing the underlying work, it creates a weak record and makes it harder to defend the arrangement if challenged.

Risk and Threat Considerations

Repeated assignment cycling can create both compliance exposure and a predictable avoidance pattern. The main legal risk is not the short assignment itself, but the appearance that the organisation is using timing and re-papering to bypass a statutory protection. Once that pattern is visible, the employer or agency may have to justify why the engagements were genuinely separate.

Failure mechanism: The same worker continues in substantially the same role across linked engagements, so the clock is treated as continuous or as not properly reset. Short gaps, cosmetic role changes, or contract relabelling can then fail to defeat the threshold.

Impact: The organisation can face equal treatment obligations, retrospective pay exposure, disputes over agency terms, and enforcement or penalty risk if the arrangement is viewed as avoidance rather than legitimate workforce rotation.

How to assess whether the assignments are truly separate

Start by testing what actually changed between assignments. The most relevant facts are the work content, location, supervisor, team, and whether the worker had a real break from that role. A genuine new placement is easier to defend when the job itself has changed in substance, not just in contract wording or booking dates.

If the same operational need persists, repeated short placements should be treated as a continuity problem, not a scheduling convenience. That means the organisation should keep evidence of why each assignment ended, why any break occurred, and what materially changed before a new assignment began.

Good documentation matters because the legal risk is often evidentiary. If challenged, the organisation needs a coherent record that shows separate placements were planned for legitimate reasons, rather than assembled to stay under a threshold. Where that record is thin, the legal argument is usually harder to sustain.

Practitioner Guidance

What to verify: Confirm whether the role, site, manager, and duties changed enough to support a genuinely new placement. If those elements are stable, assume continuity risk until proved otherwise.

Decision rule: If the same worker is repeatedly placed into the same work pattern, treat the arrangement as threshold-sensitive and get legal review before continuing the cycle. If the work is materially different, retain the evidence that shows why the clock should be treated separately.

What practitioners underestimate: The biggest mistake is assuming a short gap automatically resets legal exposure. In reality, the surrounding facts often matter more than the calendar break.

Practitioner takeaway: The safest approach is to manage repeated agency use as a continuity and documentation problem, not just a contract-renewal issue. If the substance of the role stays the same, the legal risk usually stays with it.

Related resources from NHI Mgmt Group

• When does a short-lived API key still create material risk?
• Why do non-human identities create more audit risk than human accounts?
• Why do non-human identities create audit risk in modern environments?
• Why do non-human identities create compliance risk even when policies exist?