Remote Onboarding: The First Thirty Days

In an office a new starter absorbs an enormous amount without anyone planning it: who talks to whom, what the unwritten rules are, how decisions really get made, who to ask. Remotely, none of that transmits. Whatever you do not deliberately provide, they do not get.

This is the single largest difference between remote and on-site onboarding, and it explains most early departures.

Before day one

Equipment arrives early, tested and working. A first day spent troubleshooting a laptop is a first day spent learning that things do not work here.

Accounts exist. Every access request that lands on day one costs the new person a day and teaches them that they are an interruption.

Send the reading in advance — not a policy dump, but the three or four documents that explain what the team does and why.

Name a buddy who is not their manager, and tell that person it is a real responsibility with time attached.

Week one: context, not tasks

The instinct is to give a new person work immediately so they feel useful. Useful work without context produces the wrong work.

Explain the shape of things. What the team is for, what it owns, who depends on it, what the current priorities are and why. This is obvious to everyone who has been there and invisible to someone who has not.

Introduce people with a reason. "This is Maria, she runs X, you will work with her on Y" is worth ten introductions without context.

Show them how the team actually communicates. Which channel is for what. Where decisions are recorded. What response time is expected. In an office they would learn this by watching; remotely, tell them.

Give one small, real task by the end of the week. Something that ships. It matters more for confidence than for output.

Weeks two to four: real work with support

Pair on something real. The most efficient transfer of tacit knowledge available remotely, and the closest substitute for sitting next to someone.

Frequent, short check-ins. Daily for the first fortnight, brief. Not status — a chance to ask the questions they are accumulating.

Explicit permission to interrupt. New remote employees systematically under-ask, because they cannot see whether someone is busy and every question feels like a disruption. Say directly that asking is expected and name who to ask about what.

Watch for silence. A new remote hire who has asked nothing in a week is not settling in well. They are stuck and embarrassed.

Write down the unwritten rules

Every team has them. Whether people work in the evening. Whether a same-day reply is expected. What "urgent" means. Whether disagreement in a channel is normal or a problem. Which meetings can be declined.

In an office these are learned by observation over weeks. Remotely they are learned by breaking one.

Write them down. Half a page. New people describe it as the most useful document they receive, and almost no organisation has it.

Thirty, sixty, ninety

Set expectations for each point and review against them. Not performance management — clarity. A new person who does not know whether they are on track will assume they are not.

The signals that it is failing

They have not asked for help. Almost certainly stuck.

Their questions go only to their manager. The network has not formed.

They are producing without checking. Context did not land.

Camera off, short answers, no small talk. Isolation, and it accelerates.

Any of these in the first month is worth an immediate conversation. Onboarding problems compound quickly and are cheap to fix early.