Employee onboarding process flowchart
A cross-functional employee onboarding process template covering pre-boarding checks, IT provisioning, day one, first week and the day-90 probation review.
How it works
Rename the lanes to match your org
Replace HR, Hiring manager, IT and Facilities with the teams that genuinely do the work. If Payroll, Security or a shared services desk owns a step in your company, give it its own lane rather than burying the handoff inside HR.
Set the real lead times
Change 'Equipment ready before start date?' to the lead time your IT team actually quotes, and note that threshold on the node. If your hardware takes three weeks, the check has to happen at contract signature, not the week before.
Rewrite the screening branch to your policy
Swap 'Background check clear?' and the exception decision for the checks you are legally allowed and required to run in your jurisdiction, and name who signs off an exception. Delete the branch entirely if you do not run background checks.
Name your systems explicitly
Split 'Create accounts and grant access' into the systems a new hire needs on day one. Listing them by name is what turns the diagram into something IT can execute without asking a follow-up question.
Add an owner and a due offset per step
Use the comment field on each node to record who is accountable and when it is due relative to the start date (start minus 10 days, day one, day 30). The diagram then doubles as the timeline.
Review it after the next few hires
Ask each new hire what was missing on day one and update the chart. Onboarding maps go stale quickly because tooling and access requirements change faster than the document does.
Frequently asked questions
What are the main stages of an employee onboarding process?
Most onboarding processes have five: pre-boarding (contract, screening, equipment order, account provisioning), day one (welcome, workspace, systems access, policy sign-off), the first week (team introductions, role expectations, training plan), the first 30 to 60 days (structured check-ins), and a probation or 90-day review that formally confirms the hire. The chart above splits pre-boarding into two phases, Offer and contract and Screening, because the screening outcome is what unblocks IT and Facilities.
What is the difference between pre-boarding and onboarding?
Pre-boarding is everything between offer acceptance and the start date: contract, background and reference checks, hardware ordering, account creation, desk and building access. Onboarding starts on day one. The distinction matters operationally because pre-boarding is where all the lead times sit. A laptop ordered on day one arrives in week three, so any onboarding process that begins on the start date is already late.
Who owns the employee onboarding process, HR or the hiring manager?
HR usually owns the process and the compliance steps (contract, screening, policy acknowledgements, payroll), while the hiring manager owns the outcome: role expectations, training, check-ins and the probation decision. IT and Facilities own their provisioning steps but are rarely accountable for the timeline. That split is why the process needs a named end-to-end owner, most often HR, who can chase the other lanes when a start date moves.
How do I show what happens when a step fails?
Draw the failure route rather than describing it in a footnote. In this template, a flagged background check goes to a hiring manager exception decision that either rejoins the main flow or terminates in a withdrawn offer, and equipment that will not arrive on time routes to a temporary loaner kit that rejoins at day one. Every branch either rejoins the flow or ends in an explicit terminator, so there is no path where the process just stops.