Reconcile earlier agency assignments, disputed dates and breaks before treating a new placement as a fresh qualifying clock.
A worker joins your agency on Monday. Your system shows a new start, but the worker says they have already spent eight weeks doing the same job for this hirer through another supplier. The new agency record and the worker’s qualifying history are not necessarily the same thing.
Quick answer: build one evidence-backed history for the worker, hirer and role—not one isolated count for each supplying agency. Ask about earlier assignments, resolve conflicting periods, obtain a reviewed qualifying-period decision, and hand the result to the people responsible for the applicable terms. An unanswered history question is not evidence of zero service.
This guide is for staffing operations in England, Scotland and Wales, within the scope of the Agency Workers Regulations 2010 (AWR). Northern Ireland needs separate guidance. The process sits between engagement and readiness, and reopens during an active assignment when new evidence arrives. It is an administrative review method, not a legal calculator or a complete statement of agency-worker rights.
Separate the agency start date from the qualifying history
The GOV.UK recruiter guidance on AWR explains that qualifying service in the same role with the same hirer can accumulate across more than one temporary work agency. It recommends asking for up-to-date work history. A worker may therefore arrive at a new supplier with qualifying service already accrued.
The same guidance distinguishes this from working for different hirers, where separate qualifying periods can run alongside each other. It also identifies the hirer’s role in providing information about the terms that would apply to a directly recruited worker. Those are two connected jobs: establishing history and establishing the correct terms. Completing one does not complete the other.
Do not substitute a company’s maximum-assignment policy for this review. A contractor tenure policy governs internal review and continuation decisions; it does not, by itself, decide AWR qualifying service.
Open a history case when a placement is proposed
Name an agency operations owner and a reviewer competent to resolve AWR questions. The coordinator gathers facts; the reviewer decides their treatment. Keep the proposed assignment ID, stable worker identity and current agency start date, but add a separate history-case reference.
Ask the worker whether they have performed this or another role for the hirer through any agency. Request the periods, supplying agency, site, duties and known gaps. Record “worker reports no previous assignment” differently from “history question unanswered.” Preserve the date and wording of the response rather than converting either answer silently into a calculated start date.
Then seek proportionate corroboration through permitted channels: earlier assignment confirmations, dated work records, and hirer or agency confirmation where available. Note what each source actually establishes. A payment covering several weeks may not identify the work dates; a booking confirms intended work, not necessarily attendance. Avoid collecting unrelated financial or personal information just because it appears on an available document.
Use a period-level evidence sheet
Use one row per work period or gap. Keep source references beside the interpretation, so another reviewer can reconstruct the decision without relying on a profile’s unexplained total. The following fields are recommended operating controls, not a statutory form.
| Record | Evidence and question | Owner and next state |
|---|---|---|
| Worker and hirer identity | Stable worker reference; hirer legal identity, trading name and site. Are two client records actually the same hirer? | Account owner verifies the identity or routes uncertainty to the reviewer. Do not merge solely on a similar name. |
| Role history | Dated duties and assignment descriptions, including any reported change. Is this the same role, or does a change require substantive review? | Hirer contact supplies facts; reviewer records the conclusion and basis. |
| Work period | Start/end dates, agency, work-date evidence, relevant seven-day period and source reference. | Coordinator marks verified, reported only, or disputed. Keep overlapping sources linked to one period. |
| Gap or absence | Dates, relevant reason category, source and any uncertainty. Do not infer the reason from an empty timesheet. | Reviewer determines pause, reset, continued accrual or further review under current guidance. |
| Conflict | Both versions, affected period, evidence requested and decision deadline. | Named owner resolves it; status remains disputed until a recorded decision, not until somebody overwrites a date. |
| Approved handoff | Reviewed history version, qualifying conclusion, applicable effective date, terms-information reference and recipients. | Agency reviewer authorizes the handoff; terms/pay owners acknowledge receipt and resulting action. |
Retain separate fields for the factual period, evidence status and legal treatment. “Verified dates” does not mean “qualifying week approved.” Conversely, a disputed source does not automatically mean the worker did no qualifying work. A reviewer must identify what remains uncertain and how the potential entitlement will be handled.
Count qualifying weeks, not invoices or agency records
Acas explains the 12-week qualifying period using seven-day weeks anchored to the assignment’s start. Working part of a qualifying week can count; this is not a requirement to accumulate 12 full-time working weeks or a fixed number of hours.
Acas also distinguishes breaks that pause the period, circumstances that restart it, and absences that may continue to count. An ordinary break of no more than six weeks is treated differently from a reset; leave and other exceptions need their own review. Its current guidance flags particular parental-leave circumstances as legally complex. Do not make “no hours this week” a universal reset instruction.
For administration, maintain a unique period reference within the reviewed worker–hirer–role history. Two agencies’ records describing the same qualifying week are two pieces of evidence, not two weeks. Likewise, a correction to the number of hours in an already-counted week is not automatically an additional week. Send any question about week boundaries, changing roles or consecutive absence categories to the reviewer before finalizing the clock.
Resolve identity before adding periods
A site code, payroll client code or agency branch is useful for locating records, but it should not make the legal decision. Where two sites may belong to one hirer, obtain the necessary entity facts. Where the same job title hides different duties, obtain descriptions rather than assuming continuity. Record the reviewer’s resolution and the sources it relied on.
Do not solve uncertainty by restarting the clock
If a previous agency has not replied, leave a named follow-up action and escalate the potential impact before the relevant terms or payroll decision. Do not treat a response deadline as permission to deny rights, delay required pay or invent a zero balance. The authorized reviewer should determine the lawful handling while evidence is outstanding.
Worked example: a disputed week changes the handoff
Illustrative case, not a customer story: a worker reports eight qualifying weeks in one role with the same hirer through Agency A, followed by a two-week ordinary gap and four more weeks through Agency B. Assume the reviewer has confirmed the hirer, role, week boundaries and gap treatment, with no other relevant exception.
On those assumptions, the two-week gap pauses the count rather than adding qualifying service. Eight earlier qualifying weeks plus four later weeks produce 12—not 14, and not Agency B’s isolated four.
Now suppose the sources confirm only seven of the earlier eight weeks. The eighth is disputed: the worker reports a shift, but a booking was marked cancelled. The sheet should show 11 verified qualifying weeks, one disputed potential week, and an unresolved entitlement decision. Neither “12 confirmed” nor “four weeks since joining us” describes the evidence honestly.
The case owner asks for the actual work-date evidence and alerts the reviewer and terms/pay owner immediately. If the disputed week is confirmed, the reviewer records the revised history and the applicable effective date. If it is not established, the reviewer records the supported conclusion and how the outstanding issue was handled. The team must assess whether earlier terms or processing need correction; simply changing next month’s profile total is not a completed recovery.
Close the evidence review only after its decision is received
The reviewer’s handoff should identify the worker, hirer, role, history version, conclusion, relevant effective date, outstanding questions and approved next actions. Attach the terms-information reference separately. Do not infer every pay element or working condition from an existing colleague’s salary alone.
Ask each downstream owner to acknowledge the version received and record the resulting action or unresolved issue. An emailed attachment is evidence of sending, not of implementation. When new history changes a conclusion, preserve the earlier version, explain the correction, and reopen affected handoffs rather than deleting the original decision.
The ordinary temporary worker onboarding checklist still handles site readiness, contacts and practical start conditions. This history review supplies a specific input to that wider process; it does not replace it.
Where Workhint fits
Workhint’s Workflow Engine describes configurable request steps, role-based approval routing and required details, files or notes before work advances. Those capabilities are relevant to a proposed process in which a coordinator collects history, a reviewer resolves exceptions and a terms owner receives the approved decision.
The Staffing Managers solution describes worker profiles, documents, availability, assignments and manager review. That provides the staffing context for linking a review case to the worker and assignment.
For this use case, define the evidence fields, responsible roles and states—history requested, evidence under review, decision approved, downstream action confirmed—before discussing configuration. These are proposed workflow requirements, not a claim that Workhint includes an AWR calculation engine, automatically retrieves other agencies’ records, determines legal entitlement or corrects payroll. Those decisions and any required specialist systems remain separate.
FAQ
Does changing agency automatically restart the 12-week period?
No. The relevant history can continue across supplying agencies for the same role with the same hirer. Reconcile that history rather than relying only on the latest agency registration date.
Can we use a worker’s total paid hours as the clock?
No. Hours can help evidence work, but the qualifying-period review concerns weeks and continuity. An hours total alone does not establish the relevant hirer, role, periods or treatment of gaps.
What if the worker and hirer provide different dates?
Retain both reports, identify the disputed period, request the evidence that could resolve it and assign a reviewer. Escalate any potential entitlement impact promptly; silence does not prove no earlier service.
Is this a complete guide to AWR rights?
No. It is a method for gathering and reconciling history. Check current official guidance and obtain appropriate review for scope, legal interpretation, complex absences and applicable terms. Do not export this Great Britain process unchanged to another jurisdiction.

Leave a Reply