Hr Onboarding

When to use

Reach for this when a new hire has accepted and you need an onboarding plan spanning before day one through the first 90 days. Balance logistics (access, paperwork) with belonging (people, context) and clear ramp goals.

Not for: writing the offer (use hr-draft-offer), designing the interview loop (use hr-interview-prep), or running the first performance cycle (use hr-performance-review).

Method

1. Pre-boarding (before day 1) — order equipment, provision accounts/access, send I-9/tax/benefits paperwork, a welcome message, and the day-1 agenda in advance.
2. Day 1 — manager 1:1, verify workspace/tools, team intro, security and compliance basics, and a where-to-get-help map.
3. First week — role-expectations conversation, scheduled stakeholder intros, read-in on team goals/docs, one small starter task for momentum, and shadowing where relevant.
4. First 30/60/90 — define ramp milestones: 30 (learn systems + relationships), 60 (own a piece of work), 90 (fully productive, measurable goals). Make each concrete and checkable.
5. Assign owners — name who owns each item (IT, HR, manager, buddy). Decision point: any unowned item is a gap — assign it or drop it before publishing.
6. Build feedback loops — schedule a week-1 and day-30 check-in. Decision point: if the day-30 check-in surfaces blockers, adjust the 60/90 goals rather than letting the hire fall behind silently.

Example

New hire: Data Analyst, remote. Pre-boarding — laptop shipped to arrive day -3, Okta + Snowflake + Looker access filed (owner: IT), benefits enrollment link sent (owner: HR). Day 1 — 9:00 manager 1:1, 10:00 tooling check, 14:00 team standup intro. Week 1 starter task: reproduce last month's retention dashboard. 30-day milestone: independently answer ad-hoc data questions; success signal = ships 3 correct queries unaided. 60: owns the weekly metrics report. 90: proposes one new metric with a documented definition. Buddy check-in on day 3 and day 14; manager check-in week 1 and day 30.

Pitfalls

• Front-loading paperwork and access but never scheduling the human intros — the hire feels isolated.
• 30/60/90 milestones written as activities ("attend meetings") instead of outcomes with a success signal.
• No named owner per item, so equipment or access slips and day 1 stalls.
• Skipping the early check-in, so blockers surface only at review time.

Output format

Pre-boarding checklist: item → owner → due
Day-1 agenda (timed): time → activity → owner
First-week plan: day → focus → activity
30/60/90 ramp: milestone → goal → success signal
Check-in schedule: week-1 + day-30 (owner)

Reference

Pre-boarding checklist (owner in parens)

Fire these the moment the offer is signed; the goal is a hire who logs in on day 1 to a working setup, not a ticket queue.

• Equipment ordered to arrive day −3 with time to set up (IT)
• Accounts/SSO, email, MFA, and role-based access provisioned and tested (IT)
• I-9 / right-to-work, tax, and payroll forms sent and tracked (HR)
• Benefits enrollment link + deadline sent (HR)
• Welcome email: start time, first-day agenda, dress/logistics, point of contact (Manager)
• Buddy/mentor assigned and briefed (Manager)
• Team notified; calendar holds for day-1 1:1s and intros created (Manager)
• Workspace/desk or remote-kit confirmed; first-week reading list compiled (Manager)

Day-1 agenda (timed template)

Keep day 1 light on paperwork (send it pre-boarding) and heavy on people and context. Isolation on day 1 is the #1 avoidable regret driver for new hires.

30 / 60 / 90 plan template — milestones and success signals

Write every milestone as an outcome with an observable success signal, never an activity. "Attend meetings" is not a milestone; "can explain the team's top 3 priorities and how your work maps to them" is.

First 30 days — Learn (systems + relationships)

• Complete all onboarding/compliance training; environment fully working.
• Meet every direct collaborator and key stakeholder (1:1s done).
• Understand the team's mission, current priorities, and where your role fits.
• Ship one small, low-risk starter task end-to-end (the "first win").
• Success signal: completes a scoped task with light supervision; can describe the team's goals unprompted.

First 60 days — Contribute (own a piece of work)

• Take ownership of a recurring responsibility or a defined project component.
• Deliver meaningful work with normal (not heavy) oversight.
• Give and receive feedback in the team's cadence; know the quality bar.
• Success signal: owns a deliverable others depend on; needs help only on genuinely novel problems.

First 90 days — Perform (fully productive)

• Operate at the level's expectations with standard autonomy.
• Have measurable goals set for the next period.
• Contribute an improvement, idea, or process suggestion.
• Success signal: fully ramped; manager and peers treat them as a self-sufficient team member.

Adjust the curve to level and complexity: senior/complex roles may push "fully productive" toward 120–180 days; simple operational roles may hit it well before 90. State the adjustment as an assumption.

Check-in cadence

If the day-30 check-in surfaces blockers, revise the 60/90 milestones rather than letting the hire quietly fall behind — silent drift is how a good hire becomes a "bad fit" narrative by day 90.

Remote / distributed adjustments

• Ship equipment earlier (day −5) to absorb delivery risk; have a same-day backup plan.
• Over-schedule human contact: a video buddy, virtual team lunch, and explicit "who to ping for what" map compensate for no hallway.
• Document everything the office would convey by osmosis (norms, unwritten rules, comms channels).
• Watch for isolation signals in check-ins; remote hires under-report struggle.

Common ramp roles

• Manager — owns expectations, milestones, feedback, and the ramp curve.
• Buddy/mentor — peer-level "safe" questions, social integration, unwritten norms; distinct from the manager.
• IT — equipment and access, provisioned and tested before day 1.
• HR — paperwork, benefits, policy orientation, compliance.
• Onboarding cohort (if used) — shared sessions build cross-team belonging.

Anti-patterns to catch

• All logistics, no belonging → hire feels like a ticket, not a teammate.
• Milestones as activities, not outcomes → nobody can tell if ramp is working.
• No owner per item → equipment/access slips and day 1 stalls.
• First win never scoped → weeks of reading with no sense of progress.
• No early check-in → blockers surface at review time, far too late.