AI for Employee Onboarding in Construction
Ten to seven on a Monday, a minibus pulls up at the gate. Inside are people nobody on your staff has met, sent by the groundworks subcontractor who won the package in spring, supplied in practice by a labour agency that subcontractor uses when the programme tightens. The site manager has their cards as photographs on a phone, taken in the van on the way over, one with a thumb across the expiry. The excavation is booked. The lift is booked. The only person who can stop any of it is the site manager, and that will not happen.
None of those people are your employees. Their contracts, their training records and their payroll sit with companies you do not control. It is your gate, your site and your duty, and when somebody asks months later who let them in, the answer is you.
Most of the queue at the barrier works for somebody else
Onboarding elsewhere means an offer letter, a laptop and a buddy. On a project it means a stranger arriving on the morning the works start, employed by a firm that is itself employed by a firm you contracted with. So it is not a welcome flow. It is access control plus competency evidence, carried out under a legal duty by the principal contractor, on people whose employment records belong to somebody else.
The record is yours, the paperwork belongs to other firms
Accountability sits with whoever's gate the operative walks through. The evidence sits with the subcontractor, the agency behind them, the training providers who issued the cards and the insurer who wrote the policy.
What reaches you is not a file. It is a scan of a scan, a certificate as a screenshot, and an email from a site manager under pressure to start, usually with the words "cards attached, all in date". The gap between where the duty sits and where the documents sit is the whole problem, and it is a reconciliation problem before it is a safety one.
Everything an operative must have before lifting a tool
The intake pack for one operative on one site runs to this: verification of their right to work; a competency and training card for their occupation; tickets for the plant, machinery and tools they will actually operate; task certification where the task demands it, which covers asbestos awareness, working at height, confined space entry, hot works, lifting duties and any temporary works role; an induction specific to this site; a briefing on the method statement and risk assessment for the task, signed; proof their own employer holds current insurance; and the declaration of who employs them, to the bottom of the chain.
The declarations only some tasks require
Occupational health and medical declarations apply to few workers and get forgotten because they are rare. Hearing, vision, respiratory fitness, night working, vibration exposure. They attach to the task rather than the trade, so the same operative needs one on this package and not the next. Where the contractual position is genuinely ambiguous there are payroll and status questions too, which belong in the pack even though nothing automated should answer them.
Proving someone is allowed to work at all
Right to work is the check with the least room for improvisation. There is a prescribed process, specified documents, and a defence that exists only if the process was followed in order and recorded as specified.
An agent is useful either side of it: flagging that the check is outstanding, holding the record once made, noticing that a time limited permission expires before the package finishes, and queuing the recheck. It should not perform the check. Build it as scaffolding around a named person doing the statutory steps.
A current card is not a licence for that telehandler
Here is the check almost nobody runs. A plant operator's card carries categories, and each covers specific equipment. The operative has a card. The card is current. Nobody compares its categories to the machine they are given on Tuesday afternoon when the first telehandler goes down and a bigger one arrives off a hire contract.
A system that reads the card, extracts holder, scheme, category, issue date and expiry, and then compares the category against the task allocation and the plant register, is doing something a clerk never had time to do. The same holds for lifting, where appointed person, slinger and operator each need their own evidence against one lift plan.
A ticket per hazard, not one ticket for the site
The second failure of the single card mindset is treating entry as the only gate. Entry is one permission. Each hazardous task is another. Scaffolding inspection, hot works, confined space, breaking into live services, asbestos, working over water, temporary works coordination: each carries its own certification, its own refresher interval and often its own named role in a plan. An operative perfectly entitled to be on site can be wholly unqualified for the task they are sent to mid morning.
An induction that could only have been given on this site
Generic induction is theatre. An inspector can tell inside a minute, because the operative cannot describe the traffic route they walked in on.
The induction that counts covers this site: the hazards that exist here now, the pedestrian and vehicle routes as they currently run, exclusion zones under the crane, the muster point, the fire and rescue arrangements, and the restrictions from last week's changes. All of that already exists in your own documents. Assembling an induction pack for the works about to start, from the current revision of this site's drawings and arrangements, is work an agent does well and a site manager does badly at ten to seven.
The signature that says the task was explained
The briefing against the method statement and risk assessment is a separate event from induction, and the one that collapses into a tick. The operative needs the actual sequence for the actual task explained, and the register needs their name against the revision they were briefed on. When the method statement is revised mid package, everyone briefed on the old one needs rebriefing, and knowing who that is should not require reading a folder.
The tier nobody declared on the subcontract
You contracted with a subcontractor. They named their own labour supplier, or did not. By the time anyone looks there are people on site employed through an undeclared tier, whose insurance you have never seen and whose training records nobody has asked for.
Reconciling the names at the gate against the subcontract, the declared supply chain and the insurance certificates on file is routine work nobody has capacity for. The output is narrow and awkward: these operatives work for a company named in no subcontract document, and this insurance certificate expired a fortnight ago.
Qualified in spring, expired by the autumn
Onboarding is treated as an event. Validity is not an event. Cards and tickets expire, refresher intervals lapse, insurance renews annually, and a long package outlasts most of them.
So an operative properly qualified when the works started is, on paper, unqualified by the back end of the job, and a one off intake check cannot see it. What is needed is a live per person, per task validity register with a recall clock, surfacing expiry weeks before it bites and telling the site manager who needs what before the week starts.
The card that was renewed and never collected
The failure that catches good contractors is dull. An operative renews their card. The new one arrives at their employer's office, or at an address they left, and nobody collects it. They keep working, genuinely competent and genuinely certified, while the evidence on your file expired in March.
In an investigation that is indistinguishable from unqualified, and nobody will accept that the real card existed somewhere. It is a reconciliation failure wearing the costume of a safety failure, and exactly the shape of work an agent is good at: noticing that a thing has not come back, and saying so while it still costs a phone call.
One person, one day, one task, asked months later
The audit question is never whether you have an onboarding process. It is whether you can show that for this named operative, on this date, on this task, evidence of competence existed, was current and had been briefed.
That question arrives from an inspector, an insurer or a solicitor, long afterwards and always after something has happened. The deliverable is an evidence bundle for one named person on one named day: identity check, cards with categories and expiry, task certification, induction record, the briefing signature against the correct revision, the employer's insurance and the chain of employment. Assembled on request, from records kept honest while the work was happening. If it takes a week of searching, you have a filing problem that will read as a competence problem.
Where AI fails here
Right to work has a prescribed statutory process, and the defence depends on having followed it. An agent assists and reminds. A named person completes it and owns it.
A forged or altered card defeats extraction entirely. A model reading a fake confidently leaves you worse off than a suspicious clerk, because it creates a record saying the evidence was checked. Authenticity needs verification against the issuing scheme, or a human holding the physical card.
Competence is not the card. An experienced supervisor who refuses to let somebody near a task despite valid paperwork is making the correct call, and any system that overrides that judgement with a green tick is dangerous. The paperwork is a floor, never a verdict.
Employment status determinations carry tax and legal consequences and are not an automation target. Prepare the facts, flag the ambiguity, stop there.
The practical failure is speed. A site manager with a crew waiting at the barrier will route around anything slow. Add minutes at the barrier and you will be bypassed, and the register will quietly become fiction. Everything heavy has to happen before the minibus arrives.
Nothing here fixes a subcontractor who submits poor documents. It makes that visible early, which is the most an agent can honestly claim.
Where to start
Take the plant and lifting population on one live project. Read the cards you already hold, extract category and expiry, and compare them against the plant on site and the tasks allocated this month. You will find expired evidence for competent people, categories that do not cover the machine, and at least one tier of labour nobody declared.
That is a contained build with an unambiguous result, and it earns the right to the rest: the validity register, the recall clock, the site specific induction pack and the evidence bundle. If it would help to talk it through against your own project, Adopt AI Partners can be reached at hello@adoptaipartners.com.