Remote Onboarding Checklist

Equipment and access before day one, because a remote starter cannot borrow a login, then the social half that an office supplied for free.

The interactive tool loads here when JavaScript runs.

About this tool

What is the Remote Onboarding Checklist?

Remote onboarding fails in two ways. The equipment and access arrive late, so the first week is wasted and a remote starter cannot borrow a colleague's login the way an office starter could. And nobody replaces the incidental contact an office provided, so the new person is isolated without anyone noticing.

The strongest single item is also the least technical: telling them explicitly who to ask about what. In an office they would work that out by overhearing. Remotely, nobody does.

  • Treats access and equipment as blocking, because remote starters cannot borrow
  • Covers home workstation duties, which many employers do not realise apply
  • A section specifically on replacing the office's incidental contact
  • Daily short buddy calls in week one rather than a weekly check-in
  • Editable and exportable as PDF, CSV, Markdown or a Google Form
Read the guide: Why Checklists Work, and How to Use One Properly

Updated

How to use the Remote Onboarding Checklist

  1. Ship equipment early and request every account with the start date, then verify each one works.
  2. Provide a workstation assessment, the home working policy and the expenses rules.
  3. Fill the first week's calendar, assign a buddy and schedule short daily calls for week one.
  4. On day one, walk through tools and security together, and say which documentation is current.
  5. Name who to ask about what, say questions are expected, and ask at the end of week one what is unclear.

Worked examples

A fortnight before start

Input

Before day one

Output

Kit shipped, access verified, workstation assessed, calendar filled

A laptop arriving on day three costs a week.

First week

Input

Day one and social sections

Output

Tools walked through, introductions booked, who-to-ask list given

In an office they would overhear this.

End of week one

Input

First weeks section

Output

Asked what is unclear, small task finished, expectations written

Remote problems are invisible unless asked about.

Background and insight

Access gaps are total rather than inconvenient when the person is remote, which is why requesting every account with the start date attached and verifying each one works matters more than it does for an office hire.

Employers have duties for home workstations in many jurisdictions, not only office ones, which makes a workstation assessment and whatever it identifies, chair, screen height, keyboard, lighting, an obligation rather than a perk. Sending the home working policy and expenses rules at the same time prevents a month of uncertainty about what can be claimed.

A buddy with short daily calls in week one works better remotely than a weekly check-in, because remote starters cannot ask small questions in passing and the questions accumulate instead.

Day one needs more structure than an office day one. Walking through the tools together rather than sending links, saying which documentation is current and which is stale, and covering security explicitly all matter more because there is nobody to turn to. New starters are the most phished people in any organisation and a remote one cannot check with the person next to them.

The social section is the part that gets cut and should not. Short one-to-one introductions with a stated purpose, a named list of who to ask about what, and saying out loud that questions are expected all address the same pattern: remote starters systematically under-ask, which turns small confusions into month-three problems.

Finally, expectations. Writing down what good looks like at thirty, sixty and ninety days matters more remotely because there are fewer signals to read, and asking at the end of week one what is unclear is the only reliable way to find out, since remote problems are invisible unless asked about directly.

Common use cases

  • A first remote hire

    The equipment, access and duties that differ from an office start.

  • Distributed teams

    Time zones, norms and protecting the new person from the worst hours.

  • Hybrid onboarding

    What still has to be deliberate when some days are in an office.

  • Improving an existing process

    The social half most remote onboarding leaves out.

Tips and limitations

  • Verify every account works with them watching, rather than assuming provisioning succeeded.
  • Walk through the tools together instead of sending a list of links.
  • Say which wiki pages are stale. Everyone else already knows; the new person does not.
  • Give a named list of who to ask about what. Nobody overhears anything remotely.
  • If the team spans time zones, protect the new starter from always taking the awkward hour.

Sources and further reading

  1. Planning an induction programme, Acas. What an induction should cover and how to plan it
  2. Home working, Health and Safety Executive. Employer duties for people working at home
  3. Working safely with display screen equipment, Health and Safety Executive. Workstation assessments and what they must cover

Frequently asked questions

What should be ready before a remote starter's first day?

Equipment delivered and tested, every account requested with the start date and verified as working, a workstation assessment, the home working and expenses policies sent, the first week's calendar filled, and a buddy assigned.

Do employers have duties for home workstations?

In many jurisdictions yes, and the same duties that apply in an office. That typically means providing a workstation assessment and acting on what it identifies, which can include a chair, screen height, keyboard, or lighting.

How do I stop a remote new starter feeling isolated?

Short one-to-one introductions with a stated purpose rather than vague chats, a named list of who to ask about what, saying out loud that asking questions is expected, daily short buddy calls in week one, and one recurring optional informal slot.

What should a remote first week look like?

A video call from the manager on time, the tools walked through together, security covered explicitly, the practical basics explained, short introductions spread across the week, one small task they can finish, and a fifteen-minute review of how it went.

How often should a remote new starter have one-to-ones?

Weekly from the start, recurring, and short. Frequent and short beats monthly and long while everything is new, and remotely there are fewer incidental opportunities for the conversation to happen another way.

Is there an in-depth guide to the Remote Onboarding Checklist?

Yes. “Why Checklists Work, and How to Use One Properly” covers the background, how it works, common pitfalls and worked examples. Read the full guide.