Runbook

Remote Employee Onboarding Checklist

A remote onboarding checklist for distributed teams: ship the laptop early, set up accounts, plan the first week on video and build real team connections.

  • Typical schedule per remote hire
  • The checklist 4 sections, 24 items
  • Variables {{employee_name}} {{start_date}} {{manager}} {{timezone}}
  • Start from CI
Use this template Free, no credit card. Imports the checklist into your Runbook organization.

Auf Deutsch lesen: Remote-Onboarding-Checkliste

Use this checklist when a new hire will work fully or mostly remotely. Remote onboarding has the same goals as in-office onboarding, but the things that happen by accident in an office, like overhearing how decisions are made or asking a quick question at the next desk, have to be planned on purpose.

Who owns it

The hiring manager owns the run. Operations or IT handles the hardware shipment and accounts, and an onboarding buddy covers the informal side. If the new hire is in a different time zone from the manager, agree the overlap hours before the start date.

Common pitfalls

  • The laptop arrives late. Shipping, especially across borders, can take a week or more and get stuck in customs. Ship early and track it.
  • Video calls all day. Back-to-back calls on day one are exhausting. Mix short calls with self-paced reading and a first task.
  • No written context. Remote hires cannot pick up unwritten rules. Point them to where decisions, processes and team norms are written down, and fix the gaps they find.
  • Isolation after week two. The welcome energy fades fast. Keep the buddy and regular 1:1s going for at least the first three months.
  • Ignoring where the person lives. Employing someone in another country brings tax, payroll and labour law questions. Adapt this to your jurisdiction; it is a practical checklist, not legal advice.

Triggering the run when the contract is signed gives you enough time for the shipping step, and the audit trail shows when each account and device was handed over.

The checklist: Remote onboarding for {{employee_name}}

Before the start date

  • Employment set up correctly for the country where {{employee_name}} works

    Direct employment, an employer of record or a contractor agreement have very different obligations.

  • Payroll, tax and insurance registrations completed before {{start_date}}
  • Laptop prepared with disk encryption and device management, then shipped with tracking

    Ship at least a week ahead, longer for international delivery.

  • Delivery of the laptop confirmed by {{employee_name}}
  • Home office budget or equipment (monitor, headset, chair) agreed optional
  • Company email, single sign-on and core tool accounts created
  • Working hours and overlap with the team agreed for time zone {{timezone}}
  • Onboarding buddy chosen and introduced by email before day one

First day

  • Welcome video call with {{manager}} at a time that suits {{timezone}}
  • First login, multi-factor authentication and password manager set up on a call with IT
  • Short team introduction call held, with cameras on where people are comfortable
  • Links shared to the handbook, team norms and where decisions are documented
  • Day-one schedule includes breaks and self-paced time, not only calls

First week

  • 30/60/90 day plan agreed in writing
  • First small task assigned and reviewed together
  • Short one-to-one calls held with key colleagues outside the team
  • Communication norms explained: which channel for what, expected response times
  • Recurring 1:1 with {{manager}} booked inside the overlap hours
  • Security training on remote work done (home Wi-Fi, screen lock, public networks)

First 90 days

  • Buddy check-in held every week for the first month
  • 30-day check-in held and notes recorded
  • 60-day check-in held, plan adjusted if needed
  • In-person meeting with the team arranged optional
  • 90-day review held and onboarding feedback collected
Checklist as Markdown

Start this checklist from your pipeline

When a remote hire is signed in your HR system, POST /api/v1/runs with template "Remote onboarding for {{employee_name}}" and the start date and time zone.

curl -X POST https://runbook.metastic.ch/api/v1/runs \
  -H "Authorization: Bearer $RUNBOOK_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"template": "Remote onboarding for {{employee_name}}", "variables": {"employee_name": "…", "start_date": "…", "manager": "…", "timezone": "…"}}'

See the API and the GitHub Action

Frequently asked questions

How is remote onboarding different from in-office onboarding?

The steps are mostly the same, but remote onboarding needs more lead time for hardware and more deliberate social contact. In an office people learn by watching others. Remotely, that context has to be written down or explained on purpose, and the buddy role becomes more important.

How do you make a remote employee feel part of the team?

Give them a buddy, real work in the first week and regular short conversations with different colleagues. Small, informal calls often matter more than a big welcome meeting. If you can, meet in person once in the first few months.

What equipment should I send to a remote employee?

At minimum a managed, encrypted laptop and a decent headset. Many companies add a monitor or a budget for home office equipment. Agree in writing who owns the equipment and how it is returned if the person leaves.

Updated

Send feedback

Ideas, bugs, questions: we read every message.