There are two different things called onboarding. One is the human work of helping someone become effective and feel part of a team, which is mostly the manager's job and is covered in [the first 90 days](resources-article.html?slug=onboarding-90-days). The other is the operational process that has to happen around it: paperwork, access, equipment, compliance, and a sequence of things that must occur in order.
This is about the second one, because it is the one that fails, and it fails for a structural reason. It usually exists only as a set of steps somebody has memorised, so it works perfectly until that person is on leave, until two people start in the same week, or until the business grows past the point where one memory is enough.
Start before the first day
The gap between acceptance and start date is the most underused part of the whole process. It is frequently four weeks or more, and in most organisations nothing happens in it at all.
That silence is expensive. It is exactly when counter-offers land and when the enthusiasm that drove the acceptance fades into second thoughts.
What belongs in the pre-start window:
The contract, signed and filed within days of acceptance, not the week before they start.
Equipment ordered. Hardware lead times are the most common cause of a bad first day, and they are entirely predictable.
Accounts and access requested, with a start date on them so they activate on the right morning.
Payroll set up, with the details collected in advance rather than on day one.
A first week that exists. Not a welcome pack. An actual schedule of who they are meeting, what they are being shown and what they will do.
Some human contact. The manager checking in, an introduction to a colleague, something genuinely useful about what they will be working on. It does not need to be much. It needs to be non-zero.
Get the compliance items right, and get them early
These are the items that carry real consequences if missed, and they are the easiest to miss because they are nobody's favourite part.
Right to work. Verified before the start date, with evidence recorded and any expiry diarised. This is one of the few HR failures that can produce a penalty against the business directly.
The employment contract, issued and signed. Most jurisdictions require written particulars within a defined period, and starting someone without a signed contract creates ambiguity that only ever resolves against the employer.
Tax and payroll details, collected on the correct forms for the jurisdiction.
Policy acknowledgements, recorded rather than assumed. A policy nobody has demonstrably received is difficult to enforce later.
Role-specific requirements: licences, certifications, background checks, health and safety induction, and any mandatory training. Record the expiry dates, because certifications that lapse unnoticed are a recurring and avoidable problem.
Data protection. A new employee record is a new set of personal data. Collect what you need, record why you hold it, and apply your retention rules from the start rather than retrofitting them.
Define the sequence, the owner and the trigger
This is the step that converts a memorised routine into a process.
For each task, write three things: what it is, who owns it, and what triggers it. The trigger is the part usually missing, and it is what removes the dependence on memory.
A simple version:
Yours will differ. The structure is the point. Once it is written this way, it can be automated, and an HRMS will fire each task from the trigger rather than relying on anyone to remember.
- Offer accepted: Contract issued: HR
- Contract signed: Equipment ordered: IT
- Contract signed: Payroll record created: Payroll
- Two weeks before start: Accounts provisioned, dated: IT
- One week before start: First-week schedule confirmed: Manager
- Day one: Right to work verified and recorded: HR
- Day one: Policy acknowledgements issued: HR
- Week one: Health and safety induction: Manager
- Week two: First check-in: Manager
- Month one: Probation checkpoint: Manager
- Month three: Probation decision: Manager and HR
Where it usually breaks
Everything lands on day one. Contract, forms, policies, inductions and introductions compressed into a morning. Nobody absorbs any of it, and the person's first experience is of being processed. Spread it: essentials on day one, the rest across the first fortnight.
IT is told too late. The most common single failure, and the most visible one. Bring IT in at acceptance rather than at start.
The manager has not planned anything. The person arrives, the manager is in meetings, and they spend a day reading documentation alone. This is where new starters form the impression that determines whether they stay.
Probation is forgotten. A probation period nobody diarises simply expires, and the opportunity to have a clear conversation while the bar is still explicit is lost.
Nobody checks whether it worked. Ask new starters, at about a month, what was confusing and what was missing. They are the only people who can see the gaps, and the ability to see them disappears within a few weeks as they normalise.
Remote onboarding needs deliberate structure
Remote starters lose everything that happens incidentally: the overheard context, the person at the next desk, the informal introductions.
Compensate explicitly. Ship equipment so it arrives before day one. Schedule the introductions that would otherwise have happened by accident. Name someone as their first point of contact for small questions, because remote starters routinely sit on trivial blockers for days rather than interrupt anyone. Be more explicit about written norms than feels necessary.
Common questions
How long should onboarding last?
The operational process is largely complete within the first month. The human side runs to around ninety days, and probation periods commonly align with that.
What must legally happen when someone starts?
It varies by jurisdiction, but consistently: right-to-work verification, a written employment contract or statement of particulars within a defined period, correct tax and payroll registration, and any role-specific health and safety induction. Record all of it.
What is preboarding?
Everything between offer acceptance and the first day: contract, equipment, accounts, payroll setup and keeping contact. It is the most neglected part of the process and the point at which acceptances are most often lost.
Who owns onboarding?
HR owns the process and the compliance items. The manager owns the person's actual experience. It fails when either assumes the other is handling it.
Write each task with an owner and a trigger so the process fires from events rather than memory, do the compliance items before the start date rather than on day one, spread the paperwork across a fortnight, and ask new starters at one month what was missing.