Patterns
intermediateonboarding Featured

Employee Onboarding Orchestration

Coordinate the multi-department new-hire onboarding process — from IT provisioning and HR paperwork to manager introductions and training enrollment. Ensure nothing falls through the cracks.

Views28
BPMN 2.0
On this page

Visual Flow

Rendering diagram…

When to Use This Pattern

Use employee onboarding orchestration when:

  • New hires require tasks from 4+ departments (IT, HR, Facilities, Training, Finance, Security)
  • Onboarding is inconsistent — some new hires get everything, others are missing equipment on day one
  • Managers complain that onboarding takes too long or requires too much manual coordination
  • You want to measure onboarding quality and identify bottlenecks

How It Works

Rendering diagram…

Implementation Guide

Step 1: Define the Onboarding Checklist

Build a comprehensive checklist organised by department and timing:

DepartmentTaskDue BeforePriority
HRGenerate offer letter-14 daysCritical
HRSend employment contract for e-sign-10 daysCritical
ITCreate email account-5 daysCritical
ITOrder and configure laptop-7 daysCritical
ITGrant system access (based on role)-3 daysCritical
FacilitiesAssign desk/workspace-5 daysHigh
FacilitiesOrder building badge-5 daysHigh
SecurityInitiate background check-14 daysCritical
SecuritySend NDA for e-sign-10 daysCritical
FinanceSet up payroll-5 daysCritical
TrainingEnroll in orientation program-3 daysHigh
ManagerPrepare first-week schedule-3 daysHigh
ManagerAssign buddy/mentor-3 daysMedium
Step 2: Trigger the Workflow

The onboarding workflow starts when:

  • HR creates a new hire record in the HR system
  • A hiring manager completes a "New Hire Request" form
  • The offer letter is signed by the candidate

Include all the data downstream tasks need:

  • Employee name, email, start date
  • Department, role, manager
  • Office location
  • Role-specific requirements (special software, certifications)
Step 3: Fan Out to Departments

Use the Fan-Out / Fan-In pattern to assign all tasks simultaneously:

  1. Create one task per department with the specific items for that team
  2. Set due dates based on the start date (work backwards)
  3. Include role-specific variations — a developer needs different IT setup than a sales rep
  4. Allow task delegation — if the IT point person is OOO, use Delegation on Absence
Step 4: Track Progress

Build a dashboard showing onboarding status:

New HireStart DateITHRFacilitiesTrainingFinanceSecurityOverall
Jane SmithMar 1586%
Bob JonesMar 2233%
Step 5: Day-1 Readiness Check

The day before the start date:

  1. Check if all critical tasks are complete
  2. If any critical task is incomplete → escalate to the department manager
  3. Send a day-1 package to the new hire: where to go, who to ask for, what to bring
  4. Send a reminder to the manager with the new hire's schedule
Step 6: Post-Onboarding Follow-Up

Schedule automated check-ins:

TimingAction
Day 7Survey: "Do you have everything you need?"
Day 30Manager check-in: "How is the new hire settling in?"
Day 60Training progress review
Day 90Probation review reminder to manager

Tips & Best Practices

Important

Start onboarding before the start date, not on it. If IT orders a laptop on day one, the employee sits idle for 3 days waiting. The best onboarding workflows start 2-3 weeks before the start date.

  • Create role-based templates. A "Developer Onboarding" template has different tasks than "Sales Rep Onboarding". Maintain separate checklists per role.
  • Measure time-to-productivity. Track how long it takes from start date to "fully set up" (all tasks complete). Aim for <3 days.
  • Automate what you can. IT account creation, group membership, license assignment — these can often be fully automated via Microsoft Graph, Azure AD, or RPA.
  • Collect feedback. At day 30, ask the new hire to rate their onboarding experience. Use this to continuously improve.

Related patterns