Cookies on this site

Strictly necessary cookies keep the site working. Our analytics and advertising tags — Microsoft Clarity and Google Tag Manager — stay switched off, and write no cookie, until you accept them. Privacy Policy

HR Software

How do you manage statutory compliance for contract workers?

Treat it as a recurring verification routine, not a clause in the contract. Decide who owns it, fix a short list of evidence the contractor produces each cycle, check that the people on site match the people on the records, and hold your own records rather than only the contractor's. What applies to your arrangement differs by state and by law, so confirm it with a qualified advisor.

Why is a clause in the agreement not enough?

Because a contract allocates cost and recourse between two businesses, and certain duties attach to the organisation where the work is performed regardless of what the two businesses agreed. An indemnity is worth having and does not change who the authority deals with, nor does it help much when the contractor that owes you the indemnity is the one in difficulty. Read the clause as what you can recover afterwards rather than as protection from the duty itself, and establish which duties actually sit with you, in your arrangement and your state, with a qualified advisor rather than inferring it from the agreement.

What should the contractor produce each cycle?

A short list you genuinely check beats a long one you file. Which documents belong on it depends on the regime that applies to your engagement, so build the list with an advisor once and then keep it stable, because stability is what makes an absence visible. The important discipline is the record of receipt: what arrived, for which period, covering which people, and what was missing. A folder of documents proves that somebody collected paperwork. A dated log of what was requested, received and chased proves that somebody was checking, and those are very different things when the question is asked later.

How do you know the records describe the people actually on site?

By comparing them with something the contractor did not produce. Access control logs, the gate register, the site supervisor's own list or induction records all come from a different source, and reconciling any of them against the contractor's deployment record is the check that finds the real problems: people working who are not on any record, people on the record who left, and names that differ between systems. Doing it occasionally and unannounced is more informative than doing it thoroughly and on a schedule everybody knows. The point is not to catch anyone out but to establish whether the paperwork describes the site.

Who owns this internally?

One named person per engagement, with a deputy, and the answer is usually not procurement alone. Procurement owns the commercial relationship and is measured on cost and delivery, so a compliance gap arrives as an obstacle to a payment rather than as its own issue. Human resources understands the obligations but often has no visibility of the supplier relationship or the invoice. Site operations knows who is actually there and is not asked. Whichever function holds it, write down who checks what and who is told when something is missing, because the reliable failure pattern here is an obligation every function believes another one has.

What do you do when a contractor cannot produce something?

Treat it as a live issue with a date on it rather than as chasing. Record what is outstanding, for which period and which workers, tell someone with authority over the relationship, and decide explicitly whether work continues while it is unresolved. Continuing is often the right commercial answer and should be a decision somebody made, not a default that happened. A pattern of missing evidence usually indicates a supplier under financial strain, which is exactly the situation in which the exposure to the principal employer is highest, so a second consecutive gap deserves a different response from the first.

How should this show up in your own systems?

As a population you can see. Workers who are not on payroll are invisible to reports keyed to payroll, so headcount, access reviews and capacity planning all describe a smaller organisation than the one operating. Holding these people as a distinct class, with their contractor, site, engagement dates and evidence status, in the same place as your employee records rather than in a procurement folder is what allows a straightforward question about who works here to have a straightforward answer. Keeping them distinct from employees matters as much as recording them, because merging the two populations creates a different problem.

What changes when you add a site or a state?

Potentially the applicability tests, the registrations, the records and the authority you deal with, so a new location is a fresh question rather than a copy of the last answer. The same is true of changes that feel purely operational: extending a contractor's scope, engaging a second contractor at one site, or a seasonal increase in deployed workers can move an engagement across a line that nothing internal records. Attach the compliance question to the decision that triggers it, so it gets asked by whoever approves the change and answered before the arrangement starts rather than during a review.

Want Pitch N Hire to handle this for your team?

FAQ

Frequently asked questions

Can we make the contractor fully responsible in the agreement? +
You can allocate cost and recourse between the two businesses, and that is worth doing carefully. What an agreement generally cannot do is move a duty the law places on the organisation where the work is performed. Establish which duties sit with you in your specific arrangement with a qualified advisor, then write the commercial terms around that position rather than in place of it.
How often should we verify a contractor? +
Often enough that a lapse surfaces while it is still small, and on a rhythm that survives a busy period. Tying the check to the payment run works for most organisations because that is the one moment the relationship reliably has attention. Onboarding diligence tells you about the day it was done and nothing about the position two periods later.
Which records should we hold ourselves rather than rely on the contractor for? +
Separate what you receive from what you must be able to produce. Copies of a contractor's documents are useful evidence but are not a substitute for the records the applicable rules expect the principal employer to maintain about the engagement. Ask an advisor to draw that line for your arrangement, then store your own records with your statutory files rather than in the procurement folder.
Should contract workers sit in our HR system? +
Somewhere visible, held as their own class rather than mixed into employee records. Tracking contractor, site, engagement dates and evidence status alongside your people is what makes access reviews, safety checks and capacity planning describe the actual population on site. Mixing them into headcount creates reporting problems of its own, so keep the distinction explicit in the data.
How do we work out which rules apply to our arrangement? +
Set out the facts rather than the labels: where the work happens, who directs it, how many people are deployed, for how long, in which state, and under what commercial terms. The tests turn on the substance of the arrangement rather than on the heading of the agreement, and they differ by state and change over time. Take those facts to a qualified advisor and record the answer with its date.
Pitch N Hire ATS

See how this works in a real applicant tracking system

Pitch N Hire is an applicant tracking system built for recruiters and hiring teams. If this answer described something you want to run properly, the ATS is where it lives.

  • One pipeline for every role, applicant, and interview stage
  • Structured scorecards so the panel compares candidates on the same criteria
  • Careers page, job posting, and candidate communication in one place

Free for 1 user Β· No credit card Β· Talk to a real hiring expert

Built for recruiters & hiring teams

See how much faster your team could hire

Get a personalized walkthrough of Pitch N Hire on your own roles and workflow. No slides, no obligation.

Prefer to talk? Book a demo Β· Talk to sales Β· View pricing

Free 1-user plan Β· No credit card Β· Talk to a real hiring expert

One Hiring Infrastructure.
Zero Tool Chaos.

Demos are consultative. We respect privacy and enterprise
governance. No lock-ins.

Start free Book demo