Employee onboarding BPMN diagram example

By Emilis Mikalajūnas · Published July 8, 2026 · Last updated October 3, 2026

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.

Employee onboarding BPMN 2.0 diagram across HR, IT and Manager lanes: a message start event splits at a parallel gateway into provision accounts and equipment, assign buddy and prepare plan, and complete paperwork and payroll, which synchronise at a parallel join before a service task marks the new hire active; error boundary events route failed steps to notify the HR coordinator. — Employee onboarding in BPMN 2.0 — HR, IT and the manager work in parallel and re-join at a synchronising gateway. Generated with BPMN Studio. How it was made: the description, steps table and decision points below were sent unedited through BPMN Studio's production generation prompt (GPT-4.1), then laid out by the app's own layout engine.

Take this diagram with you. The BPMN 2.0 XML below is the exact source behind the diagram above — open it in Camunda Modeler, Flowable, Activiti, bpmn.io, or any BPMN 2.0 tool.

↓ Download Employee onboarding .bpmn Open in BPMN Studio

Free, no sign-up, no attribution required.

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

The middle column names each BPMN element; the BPMN symbols and shapes reference shows what each one looks like.

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

Why use a parallel gateway for onboarding instead of an exclusive one?

IT provisioning, buddy assignment and HR paperwork all have to happen, and none waits for the others. A parallel gateway starts all three at once, and the matching parallel join waits for every branch before the new hire is marked active. An exclusive gateway would pick only one of them.