Agency Staff and Contractors
Two organisations, one worker, and a safety duty that both assume the other is carrying.
Sectors · Analysis
Agency workers, subcontractors and self-employed people working alone fall into a gap that neither party designed and both rely on.
When agency staff and contractors also depends on reliable work records, the official website can support time, attendance and workload review without being treated as the emergency response itself. Compare any workflow with CCOHS working-alone guidance and keep alarm ownership, escalation and dispatch responsibilities explicit.
The gap
The agency employs them and has duties as an employer.
The client controls the site, the schedule and the hazards.
Neither holds the whole picture: the agency does not know the address risks, and the client does not hold the worker's details or their next of kin.
And the worker frequently has neither a device nor a place in anyone's escalation tree.
What each side usually assumes
The client assumes the agency has a lone worker system.
The agency assumes the client's site arrangements cover anyone on site.
Both are reasonable and both can be wrong at once, which is exactly what happens on a first shift at an unfamiliar site.
What to agree, in the contract
Who provides the device, and who monitors the alerts.
Who holds the escalation tree, and whose numbers are on it.
Who passes address and site risk information, and by when — before the visit, not after.
Who is told when the worker arrives and leaves.
And who investigates an incident, and who reports it to a regulator.
Fifteen minutes of drafting that prevents the whole category.
Information that must travel
Address flags reach whoever is attending, regardless of which organisation employs them.
This is the single most common failure in contracted care and housing, and it appears repeatedly in serious case reviews.
Where the flag cannot travel for data protection reasons, that is a design problem to solve rather than a reason to send someone uninformed.
The self-employed worker
Frequently outside everyone's system entirely.
Still working alone on your site, with your hazards.
A client has duties toward people affected by its undertaking in most jurisdictions, which includes contractors on its premises.
At minimum: they are in the check-in arrangement, somebody knows they are there, and somebody notices when they do not leave.
First shifts
The highest-risk visit is the first one to an unfamiliar address by someone who does not know the service.
Which is precisely the visit an agency worker is sent on.
Do not put agency staff on flagged addresses, and give them the site briefing that permanent staff received at induction.
The measure
Are agency and contractor workers in the check-in arrangement, counted?
Do address flags reach them, tested by asking one?
And when did anyone last confirm who is on site after hours, which is the question that finds the people nobody is watching.
The induction that does not happen
Permanent staff get a briefing. Agency staff get a location and a start time.
Which means the person least familiar with the work receives the least information about its hazards.
A ten-minute site or service briefing closes most of this gap: where the exits are, what to do if something goes wrong, who to call, and the withdrawal policy.
Delivered by the client, because the client holds the hazard information, whatever the contract says about employment.
Devices for people who are not your employees
Who provides it, who charges it, who recovers it when the placement ends?
A device issued to an agency worker and never returned is both a cost and an alarm source nobody will recognise.
Track them against the placement rather than against a permanent register, which is a small administrative change and prevents the estate drifting.
Checking in across organisations
An agency worker checking in to their agency, who then has to contact the client, adds a step at the worst moment.
Where the client controls the site, the check-in should go to whoever can actually respond, which is usually the client.
With the agency informed, not in the path.
Agree it explicitly, because the default is whichever system the worker was given a login for.
Incident reporting and who reports to the regulator
Duties differ by jurisdiction and by the nature of the relationship.
Frequently both parties have a duty, and both assume the other has discharged it.
Which results in an under-reported incident and a second failure on top of the first.
Agree who reports what, in the contract, and confirm it at the point of an incident rather than assuming.
Self-employed and sole traders on your site
A contractor working alone in your building is somebody your undertaking affects, in most jurisdictions.
Which does not make you their employer, and does create duties.
The practical minimum: they are on the check-in arrangement for the period they are there, somebody knows they arrived, and somebody notices if they do not leave.
Most sites have a signing-in book that does the first half and nothing that does the second, which is the gap worth closing because it costs one look at a list at the end of the day.