Employee onboarding BPMN diagram example
Employee onboarding is a great BPMN example because it involves several teams working in parallel. HR, IT and the hiring manager each do their part, often simultaneously, before the new hire is ready on day one.
The process in plain English
HR submits a new-hire request. In parallel, IT provisions accounts and equipment, the manager assigns a buddy and prepares a plan, and HR completes paperwork and payroll setup. Once all three are done, the new hire is marked active. If any task fails or stalls, the HR coordinator is notified.
Steps and their BPMN elements
| Step | BPMN element | Lane |
|---|---|---|
| New-hire request submitted | Message start event | HR |
| Split work | Parallel gateway | — |
| Provision accounts & equipment | Service task | IT |
| Assign buddy & prepare plan | User task | Manager |
| Complete paperwork & payroll | User task | HR |
| Synchronise | Parallel join gateway | — |
| Any step failed? | Error boundary event → notify | HR |
| Mark new hire active | Service task | HR |
| Onboarding complete | End event | — |
Key modelling points
- The parallel gateway is what makes this diagram realistic — the three streams run at once and re-join.
- Error boundary events on each task route problems to the HR coordinator without cluttering the happy path.
- Three lanes (HR, IT, Manager) make responsibilities explicit.
Generate your own onboarding diagram
Describe your onboarding steps and teams to BPMN Studio and get an editable BPMN 2.0 diagram instantly. See more templates or how to create a BPMN diagram.
Frequently asked questions
How do you model employee onboarding in BPMN?
Start with a message start event (new-hire request submitted), then use a parallel gateway to run IT provisioning, manager buddy assignment and HR paperwork at the same time, synchronise them with a parallel join, and end when the new hire is marked active. A failure path notifies the HR coordinator if a step can't complete.