How to create an employee onboarding process
How to design an employee onboarding process: work backwards from day one, put the lead times where they belong, name the owner of each provisioning step, and end at a probation decision.
A worked example, stage by stage
The date that drives everything
Contract issued and start date confirmed. Every downstream offset — order equipment, create accounts, prepare a desk — is measured from this, so the step that communicates it to IT and facilities is the highest-leverage one in the process.
Screening gates provisioning
A background check with an exception route to the hiring manager. The dependency matters: IT often cannot provision before screening clears, so a slow check silently consumes the hardware lead time and nobody notices until day one.
Three teams, one morning
Order hardware, create accounts and grant access, prepare desk and building access, with an equipment-readiness decision that issues a loaner kit. Design the fallback deliberately: without one, the answer to "not ready" is an apology.
Day one and the first week
Orientation, equipment handover with access verified live, policy sign-off, buddy and expectations. Verifying access in front of the new hire rather than assuming it is what turns a checklist into a control.
Finish at the probation decision
Check-ins at 30 and 60 days, then a day-90 decision that confirms employment or extends probation with a support plan. Onboarding processes that end on day one have no way of telling whether they worked.
How it works
Name one end-to-end owner
Four teams each own their steps and none owns the date. Appoint a single owner — usually HR — accountable for the new hire being productive on day one, with the authority to chase the other lanes. Without that role, a moved start date is communicated by whoever remembers.
Work backwards from the start date
Write each pre-boarding step as an offset: contract at minus 14 days, hardware ordered at minus 10, accounts created at minus 2. Use the lead times your suppliers actually quote, not the ones in the policy, and put the offset in the step's comment so the diagram doubles as the timeline.
Draw the screening dependency explicitly
If provisioning cannot start until checks clear, that is a serial dependency consuming your lead time. Decide whether anything can start in parallel — ordering hardware often can — and draw the exception route for a flagged check with a named decision-maker.
List the systems by name
"Create accounts and grant access" is not executable. Split it into the systems a new hire needs on day one, in the order they are needed, and record who requests and who grants each. This single change removes most of the day-one follow-up questions.
Design the fallback for late equipment
Hardware will occasionally be late, so decide in advance what happens: a loaner kit, a shared machine, a delayed start. A drawn fallback is a decision made once; an undrawn one is a decision made under pressure on the morning.
Extend to the probation decision and review it
Add the 30, 60 and 90-day checkpoints and a real decision at the end. Then ask each new hire what was missing on their first week and update the chart — onboarding decays faster than most processes because tooling and access requirements change constantly.
Frequently asked questions
What are the stages of an employee onboarding process?
Five in most organisations: pre-boarding (contract, screening, equipment ordering, account creation), day one (welcome, workspace, access, policy sign-off), the first week (team introductions, expectations, training plan), the first 30 to 60 days (structured check-ins), and a probation review that formally confirms the hire. The example above splits pre-boarding into offer-and-contract and screening, because the screening outcome is what unblocks IT and facilities.
How far in advance should onboarding start?
As soon as the offer is accepted, and the specific lead time is set by your slowest dependency — usually hardware, sometimes background screening or building access. Ask IT what they actually quote rather than what the policy says, and set the ordering step that far before the start date. Organisations that measure this are routinely surprised: the gap between the policy lead time and the real one is where most first-day failures live.
Who owns the employee onboarding process?
HR usually owns the process and the compliance steps, while the hiring manager owns the outcome — expectations, training and the probation decision. IT and facilities own their provisioning steps but are rarely accountable for the overall date. That split is exactly why a single named end-to-end owner matters: someone has to notice when a start date moves and re-drive the four workstreams that depend on it.
How do I measure whether onboarding is working?
Three measures cover most of it: the proportion of new hires who have full access on day one, time to first meaningful contribution as judged by the manager, and retention through probation. Collect the first from IT rather than from the new hire, and ask the new hire in week two what was missing — they will tell you accurately then, and diplomatically six months later.