Two onboardings, one word
When software vendors say employee onboarding, they usually mean the administrative kind: offer letters, right-to-work checks, payroll enrolment, policy acknowledgements. That work matters and it belongs in HR systems. This guide is not about it, and any tool honest about this category should say so as plainly.
Site onboarding is the second kind, and for anyone whose workplace is a construction project, a factory floor, a warehouse or an industrial facility, it is the kind that decides whether day one is productive or wasted. It answers physical questions: has this person been inducted for this site? Do we hold their emergency contact? Are they a first aider we should know about? Do they have a credential that opens the gates and doors their job requires, and only those?
The two onboardings fail differently. When HR onboarding is late, someone's first payslip is wrong. When site onboarding is late, a new starter stands at a gatehouse while someone phones around for the induction laptop, or worse, gets waved through uninducted because the queue was building. One is an annoyance. The other is a liability with a name and a start date.
Why day one goes wrong on working sites
The failure pattern is remarkably consistent across industries. A new employee arrives at eight. The induction is a classroom session that runs on Tuesdays, or a supervisor reading from a binder when they get a spare half hour. The credential request went to an office that prints them in batches. The emergency contact form is in a pigeonhole. By the time all of it converges, half a day is gone, and every gap was covered by an improvisation nobody would defend in writing.
Improvisation is the real cost. Sites do not plan to let uninducted people work; they let the queue decide. A starter borrows a colleague's credential for the morning. A supervisor signs an induction record for a session that was a five-minute chat. Each shortcut is small, and each one is exactly the finding an investigator writes up after an incident.
The fix is not more paperwork, it is removing the waiting. Everything a starter needs on day one, the record, the induction, the certificate, the credential, the access, can happen at the site, on the morning they arrive, in one sequence that does not depend on a particular person being free.
The day-one sequence that works
Picture the version of day one worth buying. The new starter arrives with a personnel record already created: name, company, department, employee type, emergency contact, any safety flags such as first aid training carried over from their last role. What remains is the site-specific part, and it runs as a sequence at the gatehouse rather than a tour of departments.
Induction at a walk-up kiosk. The starter takes the site induction self-service at a kiosk: text, images, video and narrated audio built by your own team, ending in an assessment. No trainer to schedule, no Tuesday classroom, no binder.
Certificate printed on the spot. A pass prints a certificate there and then, and the completion lands in the certificate register with its expiry date tracked from day one. The evidence exists before the first task does.
Credential issued and assigned. A credential is created at the desk with a tap, assigned to the starter through a guided flow, and tested against a reader before they walk away. No batch printing, no waiting on another office.
Access set from the record. Zone permissions follow the personnel record: the areas their role needs, and not the high-risk or restricted zones it does not. The first time they present the credential, the site already knows the rules.
The measure of site onboarding is simple: a new employee arrives at eight and is working, inducted, credentialed and correctly restricted, before the first break. Anything longer is queue, not process.
The personnel record is the spine
Every step in that sequence hangs off one thing: a single, trustworthy personnel record. Not a row in the HR system, a row in the induction spreadsheet and a row in the access database, loosely agreeing with each other, but one record that the induction, the credential and the access rules all read from.
The contents are unglamorous and vital. Emergency contact details, captured before they are needed rather than after. Safety flags, so the live register and the roll call screen can highlight that the new starter is a trained first aider, which is information a site wants on day one, not at the next audit of the noticeboard. Department and personnel type, so reports slice the way the organisation actually thinks. Custom fields for whatever your operation tracks: fork lift tickets, medical notes, locker numbers.
A single record also fixes the quiet rot that multi-system onboarding creates. When access lives in one database and training in another, the systems drift, and the drift is always discovered at the worst moment: a leaver whose credential still works, a certificate that expired while the access system slept. When one record drives all of it, expiry enforcement is automatic, revocation is one action, and the plain-English audit log shows every change with a name attached.
Onboarding does not end at day one
Site inductions expire, refresher requirements come round, and roles change. A starter who joins the stores team and moves to maintenance eighteen months later is, from the site's point of view, being partially onboarded again: new zones, possibly a new induction, a change to the record. Software that only handles the first morning misses most of the lifecycle.
The mechanism that keeps this honest is the enforcement loop. Certificates sit in a register with expiry tracking, and entry checks them: when an induction lapses, the person is stopped at sign-in with a clear reason and pointed back to the kiosk, where they retake the course and print a fresh certificate. Nobody has to notice the expiry, chase the individual or quietly extend a date in a spreadsheet, and the assessment pass mark is enforced consistently, with a default threshold of 80% that you can configure per course.
It is worth saying once more what this category of software is not. It does not issue contracts, run payroll, manage probation reviews or book benefits. If a vendor implies one system does all of that and the gate, press hard on which half is real. Site Commander does the site half completely, and hands HR the thing HR systems cannot produce: proof of who was inducted, credentialed and on site, from the first morning onward.
