The Remote Onboarding Checklist We Give Every Employer

Onboarding failure is silent. In an office, a lost new hire looks lost: they wander over, ask a question, get coffee. Remote, they simply go quiet, sit on a half understood task and, in their own head, start re reading your job listing to see what they signed up for. By the time anyone notices, week two is gone and the first impression is set.

The fix is not expensive. It is a checklist, done before the person arrives instead of improvised while they wait. Here is the one we hand out, phase by phase.

Before day one

• Hardware shipped and confirmed. Laptop, monitor, whatever the role needs, arriving at least three days early with tracking shared. A new hire starting without tools is the single most preventable bad omen in remote work.
• Accounts created, passwords ready to rotate. Email, chat, code, docs, the lot. First day logins that fail tell your new teammate exactly how the next month will feel.
• A written first week. One page: what we will cover each day, who they meet, what they will ship by Friday. The deliverable matters less than the existence of the plan.
• A buddy assigned. Not the manager. A peer whose explicit job, for two weeks, is to answer the small questions: which channel for what, how meetings really work here, who to ask about the printer that does not exist.
• Calendar cleared on their side and yours. No surprise sessions on day one. Book the welcome call, the team intro and nothing else.

Day one

One 30 minute welcome call. Camera on, no agenda beyond hello: how the week will go, how to reach people, what time everyone works. Then hand over one small, real task, sized for a couple of hours, and let it ship. A merged pull request, a published doc, a first support reply sent. Day one should end with something that exists because the new person made it exist.

That first shipped thing does more for week two motivation than any welcome deck. It proves the systems work, the permissions work and the team ships.

Week one

• Two or three one to ones with teammates, 25 minutes each, no agenda beyond "what do you do and what annoys you about working with everyone else". The honest answers are the real onboarding documents.
• A tour of the docs, not a lecture. Where decisions live, where the roadmap lives, where the "we tried that and it failed" notes live. Remote teams run on their written memory, and teaching someone to fish in it pays out for years.
• The first real task by Wednesday. Real meaning: production, reviewed by the buddy, not a sandbox exercise nobody looks at twice.
• A Friday retro message in writing. The buddy asks: what was confusing, what was missing, what would you have wanted to know on Monday. Then, this is the part everyone skips: fix one of those things before the next hire arrives.

The first 30 days

Weekly async check in, five lines: shipped, learned, stuck, mood. The mood line sounds soft and predicts resignations earlier than any performance metric.

At day 30, ask three questions in a proper one to one: what surprised you, what still feels unclear, what would you change about how we onboarded you. New hires see the company with fresh eyes for about a month. After that they have normalised your weirdness and the window closes.

Signs your onboarding actually works

• The new hire asks questions in public channels instead of private messages. That is belonging, not ignorance.
• Something real shipped in week one.
• They disagree with something out loud inside the first month.
• They tell you what confused them without being begged.
• Your buddy volunteer list grows with each new hire. People sign up for what they enjoyed.

Quick answers

When should onboarding prep start? The day the offer is signed. Everything on this list is doable in a week, but only if the week exists. Starting on day one is starting too late.

What is the ideal first project for a remote hire? Small, real and visible. It should touch the deploy or publish path so the new person experiences the full cycle, and it should be reviewed by someone patient.

How long until a remote hire is fully productive? Plan on 30 days to useful, 90 days to independent. Companies promising week one productivity are usually just measuring how fast someone learned to hide confusion.

Onboarding is the last mile of hiring. If you are still building the pipeline, start with the interview questions that predict remote performance or post your role on the board and let applicants come to a process this organised.