Employee onboarding process map
A swimlane map of onboarding from an accepted offer to the end of probation, with HR, the hiring manager, IT and Facilities each in their own lane. The lanes are the point: they show the three or four moments where a new starter's first day depends on someone in a different department having acted days earlier.
Opens a copy in the editor and saves it in this browser. No account, nothing sent anywhere.
What is in this map
20 steps across 4 swimlanes and 6 phases, with 4 decision points.
- Swimlanes (who does the work)
- HR, Hiring manager, IT and Facilities
- Phases (left to right)
- Offer and contract, Screening, Provisioning, Day one, First week and Probation
Why map this process
Onboarding almost never fails on the HR steps. It fails on the handovers: the laptop nobody ordered because the start date was confirmed in an email thread IT was not on, the building pass that needs three days' notice, the manager who finds out on Monday morning that someone is joining their team. Each of those is one department waiting on a signal from another, and a numbered checklist cannot show a wait.
Mapping it in lanes makes the dependencies literal. When Provisioning sits in the IT lane but is fed by a step in the HR lane two phases earlier, the lead time is visible on the page, and so is the fact that everything downstream of it slips when it is late. That is the conversation the map is for; the individual steps are the easy part.
Every step in the map
This is the spreadsheet behind the diagram. The numbers in “Goes to” are row numbers, which is exactly what the editor’s “Line to” column holds — so you can read the flow here and retype any part of it.
| # | Step | Shape | Swimlane | Phase | Goes to |
|---|---|---|---|---|---|
| 1 | Offer accepted by candidate | Start | HR | Offer and contract | 2 |
| 2 | Issue contract and confirm **start date** | Process | HR | Offer and contract | 3 |
| 3 | Run background and reference checks | Process | HR | Screening | 4 |
| 4 | Background check **clear**? | Decision | HR | Screening | 7 (Yes), 5 (No) |
| 5 | **Exception** approved by hiring manager? | Decision | Hiring manager | Screening | 7 (Approved), 6 (Declined) |
| 6 | **Withdraw offer** and notify candidate | Reject | HR | Screening | End |
| 7 | Order laptop and phone | Process | IT | Provisioning | 8 |
| 8 | Create accounts and grant access | Process | IT | Provisioning | 9 |
| 9 | Prepare desk and building access | Process | Facilities | Provisioning | 10 |
| 10 | Equipment ready before start date? | Decision | IT | Provisioning | 12 (Yes), 11 (No) |
| 11 | Issue temporary loaner kit | Process | IT | Provisioning | 12 |
| 12 | Run welcome and orientation | Process | HR | Day one | 13 |
| 13 | Hand over equipment and verify access | Process | IT | Day one | 14 |
| 14 | Sign policies and acceptable use | Document | HR | Day one | 15 |
| 15 | Introduce team and assign buddy | Process | Hiring manager | First week | 16 |
| 16 | Agree role expectations and training plan | Process | Hiring manager | First week | 17 |
| 17 | Hold 30 and 60-day check-ins | Process | Hiring manager | Probation | 18 |
| 18 | Meets expectations at day 90? | Decision | Hiring manager | Probation | 19 (Yes), 20 (No) |
| 19 | Confirm employment and close onboarding | Success | HR | Probation | End |
| 20 | **Extend probation** with support plan | Reject | Hiring manager | Probation | End |
The decision points
Every branch in the map, with the label on each outgoing line. These are the questions the process has to be able to answer.
-
4. Background check **clear**?
Owned by HR · Screening
- Yes → step 7
- No → step 5
-
5. **Exception** approved by hiring manager?
Owned by Hiring manager · Screening
- Approved → step 7
- Declined → step 6
-
10. Equipment ready before start date?
Owned by IT · Provisioning
- Yes → step 12
- No → step 11
-
18. Meets expectations at day 90?
Owned by Hiring manager · Probation
- Yes → step 19
- No → step 20
Notes on specific steps
These notes travel with the map. In the editor they live in the Notes column and appear when you open a box.
- 2. Issue contract and confirm **start date**
- The confirmed start date drives every downstream deadline. Send it to IT and Facilities the same day it is agreed.
- 5. **Exception** approved by hiring manager?
- Use this route for employment gaps, spent convictions or an unreachable referee. Record the reasoning, not just the outcome.
- 10. Equipment ready before start date?
- Check **five working days out**, not the day before. That is the last point at which a loaner can still be arranged.
- 14. Sign policies and acceptable use
- Signed acknowledgements belong in the employee record. This is the artefact an auditor or a tribunal actually asks to see.
Making it yours
The phases run left to right (offer and contract, screening, provisioning, day one, first week, probation) and the lanes run top to bottom. When you adapt it, start by editing the Vertical lane column: if provisioning in your company is split between IT and a separate identity team, that is a new lane, not a new step. Keep the background-check decision and its exception branch even if you rarely use them; the exception path is the one people improvise, and improvised paths are the ones that go unrecorded.
What to watch out for
- Do not collapse the two screening decisions into one. The first asks whether the check came back clear; the second asks whether the hiring manager will accept a specific exception. They have different owners and different records, and merging them removes the only step where someone signs their name to a judgement call.
- Probation is a phase, not a footnote. Teams routinely trim the last three steps because they happen months later, and then have no mapped route for a probation that is failed or extended, which is the case that actually needs a documented process.
- If your equipment lead time is longer than your notice period, the map will show provisioning starting after day one. Resist the urge to redraw it tidily. That crossing line is the finding.
Frequently asked questions
What should each swimlane be: a person, a role, or a department?
A role. Person names go stale the moment someone changes job, and department names are usually too coarse to show a handover (HR handing to HR is not a handover). This map uses HR, hiring manager, IT and Facilities because those are the four roles that have to act; if two of them are the same person in your company, keep both lanes anyway: the map should survive the day you hire a second person.
How do I show that IT provisioning and Facilities setup happen at the same time?
Put them in adjacent rows in different lanes and give them the same predecessor in the Line to column. Anything that shares an incoming step and does not connect to the other renders side by side, which is what parallel work looks like on a swimlane map. There is also a Parallel with column for pinning two adjacent same-lane steps level with each other.
Can I use this for contractors and interns too?
Yes, and it is usually better than a second map. Add a decision early in the screening phase that branches on worker type, then let the branches rejoin before day one. Most of the steps are shared; what differs is the checks and the access level, which is two or three extra rows rather than a parallel document that will drift out of date.
Open the map and start editing
The editor loads this chart with the spreadsheet underneath it. Change a cell and the diagram redraws — no drawing, no signup.