Remote onboarding blueprint — the synchronous-front-loaded model

60-Second Summary

Remote new hires need MORE synchronous time in week one than office hires — the opposite of how most async-first companies onboard.
GitLab's onboarding handbook shows the canonical remote pattern: 90+ scheduled 1:1s in the first 30 days, a buddy with explicit calendar holds, and asynchronous reading homework between sessions.
The leading indicator of 90-day retention is the new hire's first standalone meaningful contribution — not training completion. Time-to-first-PR or time-to-first-customer-call is the right metric.
Remote regrettable attrition at the 90-day mark is 1.5–2x in-office attrition at most companies — virtually always traceable to insufficient relationship investment in week one.

The standard advice for remote onboarding — 'be async-first, document everything, let them ramp at their own pace' — is exactly backwards for the first two weeks. New hires can't be async-first until they have the relationships and context to know who to ask.

Why sync-first for remote

Office new hires absorb context by osmosis: overheard hallway conversations, lunch-table dynamics, who-asks-whom-for-what. Remote new hires get none of that. The substitute is structured synchronous time — 1:1s with peers, manager, skip-level, and key cross-functional partners — front-loaded into weeks 1–2 and tapering after week 4.

Week one canonical schedule

Day	Synchronous (~4h)	Async (~3h)
Day 1	Welcome + manager 1:1 + IT setup live + buddy intro	Read company handbook, set up tools
Day 2	1:1 with each direct team member (3–6 people)	Read team docs, shadow recordings
Day 3	1:1 with key cross-functional partners (3–5)	Begin first scoped starter task
Day 4	Manager 1:1 + skip-level intro + buddy check-in	Continue starter task
Day 5	Team meeting attendance + retro of week one with manager	Ship starter task, share for review

The 30-day signal

Training-completion and document-read counts measure compliance, not ramp. The metrics that predict 90-day retention are behavioral: time to first PR merged, time to first customer call run solo, time to first decision made without escalation. Track those.

The week-two cliff

Most remote onboarding programs go heavy on week one and collapse to silence in week two. The result: the new hire feels abandoned exactly when they need the most support. Calendar week-two and week-three check-ins before they're needed.

Hardware and access mechanics

Laptop and peripherals shipped to arrive 5+ business days before start date
All system access (email, Slack, source control, design tools, customer systems) provisioned by 9am Day 1
Manager has dry-run-logged-in to each tool to verify access actually works (the #1 Day-1 frustration)
Welcome package: company swag, handwritten note from manager, optional team gift
Backup contact if IT/HR is unreachable on Day 1 — usually buddy's mobile

Frequently asked questions

Should new hires be in-office for week one even at a remote company?

If feasible — yes for some roles. Atlassian, GitLab, and Automattic all bring remote new hires together for in-person onboarding weeks. The friction is travel cost and accessibility; the payoff is measurable retention.

How do we onboard remote hires across time zones from their manager?

Carve a 3–4 hour overlap window for the first 30 days. Beyond that, the manager-relationship goes async with weekly synchronous 1:1s. Without the overlap window, week-one ramp damage is permanent.

What's the right buddy-to-new-hire ratio?

1:1. A buddy with two simultaneous new hires usually delivers less than one good buddy + one orphan. Stagger starts if you have to.