Employee onboarding process
From signed offer to confirmed hire in 90 days.
Most onboarding "processes" are a checklist in someone's head, which is why new hires still show up to a missing laptop and a calendar full of nothing. This template draws onboarding as the 90-day process it really is: accounts and hardware prepared between offer and start date, a structured day one and week one, a buddy assignment with an explicit catch for when it was skipped, and check-ins at 30, 60, and 90 days — including the support-plan branch for hires who are not on track at the first checkpoint.
The decision diamonds are the point. "Buddy assigned?" and "On track?" are the two questions that separate teams that onboard well from teams that merely hire well.
When to use this template
- HR process design — align IT, HR, and hiring managers on who does what and when, from offer signature to confirmed hire.
- Manager enablement — give first-time managers a concrete map of their responsibilities in the first 90 days, not just a welcome-email template.
- Onboarding audits — walk recent hires through the diagram and mark which steps actually happened; the gaps you find are your retention risks.
How to adapt it
Rename the milestones to match your company's cadence, then extend:
- Add a pre-boarding track — welcome email, paperwork sent early, team announcement — between offer signed and day one.
- Branch by role type: engineering setup (repos, environments) differs from sales onboarding (CRM, shadowing calls), so give each a lane.
- Append a probation decision after the 90-day review if your jurisdiction or policy requires a formal confirm-or-extend outcome.
Visual edits regenerate clean Mermaid code, so the adapted flow pastes directly into your handbook, Notion space, or new-manager training deck.
Mermaid code
Copy it anywhere Mermaid is supported — GitHub, Notion, or your docs.
flowchart TD
A[Offer signed] --> B[Create accounts + order hardware]
B --> C[Day 1: welcome + paperwork]
C --> D[Week 1: team intros + setup]
D --> E{Buddy assigned?}
E -->|No| F[Assign onboarding buddy]
F --> G[30-day check-in]
E -->|Yes| G
G --> H{On track?}
H -->|No| I[Create support plan]
I --> J[60-day check-in]
H -->|Yes| J
J --> K[90-day review + confirm]
Frequently asked questions
- What should an employee onboarding process include?
- Pre-boarding (accounts and hardware ready before day one), a structured first day and first week, an assigned onboarding buddy, and scheduled check-ins at 30, 60, and 90 days ending in a confirmation review. This template covers each stage, plus the support-plan branch for hires who are off track at 30 days.
- Why are the 30-60-90 day check-ins drawn as part of the flow?
- Because onboarding does not end after week one — most attrition risk and most ramp-up problems surface in the first three months. Drawing the check-ins as required steps with an explicit "on track?" decision makes them accountable milestones rather than optional calendar invites that quietly get skipped.
- Who owns each step in an onboarding flowchart?
- Typically IT owns account creation and hardware, HR owns day-one paperwork, the hiring manager owns team intros and the check-ins, and the buddy owns informal support. When you adapt this template, color-code or label nodes by owner — most onboarding failures are handoff failures between exactly these four parties.
- How do I customize this template for remote or hybrid teams?
- Add a hardware-shipping lead time before day one, replace in-person intros with scheduled video pairings, and make the buddy assignment mandatory rather than conditional — remote hires have no hallway to absorb context from. Edit the nodes visually and the editor regenerates clean Mermaid code for your HR handbook.