A remote onboarding checklist, from before day one to day 90.
Starting a new job remotely is lonely in a way an office isn't: no one to sit next to, no sense of who's around, and every question feels like an interruption. A good checklist fixes most of that. Here's what to do before day one, on the first day, and through the first three months, and who should own each step.
By Jitto Joseph3 min read
Who owns what
Onboarding goes wrong when everyone assumes someone else is doing it. Name an owner for each part.
| Who | Owns |
|---|---|
| Manager | The plan, goals for the first 90 days, weekly one-to-ones |
| Buddy | Everyday questions, introductions, how things really work |
| Operations or IT | Equipment, accounts, access and paperwork |
| The new hire | Asking questions, writing down what was confusing, a first small piece of work |
Before day one
- 1.
Send the equipment
Laptop and anything else they need, timed to arrive a few days early.
- 2.
Create every account
Email, chat, docs, the task board and anything role-specific, tested before they log in.
- 3.
Pick a buddy
A teammate who isn't their manager, with time set aside for the first two weeks.
- 4.
Write the first-week plan
Who they'll meet, what they'll read and a first small task, shared before they start.
- 5.
Tell the team
A short introduction in the team channel, so people say hello on day one.
- 6.
Send a welcome message
Start time, first meeting and who to contact if anything doesn't work.
Day one
- 7.
Start with a call with the manager
Welcome, the plan for the week and what good looks like in the first month.
- 8.
Check every login works
Nothing kills a first day like an afternoon waiting on access.
- 9.
Meet the buddy
A first chat, and an agreement to talk at least once a day for the first week.
- 10.
A team welcome
A short, informal call or gathering. A light icebreaker question helps everyone say something.
- 11.
Point them to the handbook
How the team works, where to ask what, and where decisions live.
- 12.
End the day with a check-in
Five minutes: how was it, and what's still unclear?
The first week
- 13.
One-to-one intros
Fifteen minutes with each person they'll work with most.
- 14.
Shadow real work
Sit in on calls, reviews and planning, with the buddy explaining what's going on.
- 15.
Ship something small
A first task they can finish this week. Finishing something early builds confidence.
- 16.
Agree on working hours
When they're online, the team's overlap hours and how fast people usually reply.
- 17.
First weekly one-to-one
What's going well, what's confusing, and what they need.
The first 30, 60 and 90 days
- 18.
30 days: settled in
Knows the tools, the people and how work flows. Owns small pieces of work on their own.
- 19.
60 days: contributing
Takes on bigger work with less guidance and starts to spot what could be better.
- 20.
90 days: fully part of the team
Works independently, helps others, and has had a proper review of how onboarding went.
- 21.
Ask what to fix
At 30 and 90 days, ask what was confusing or missing, and update the checklist for the next person.
Remote onboarding mistakes to avoid
- A week of reading. Documents matter, but people learn faster by doing real work with someone beside them.
- No one to ask. Without a buddy, new people sit on questions for hours rather than interrupt.
- Invisible teammates. When you can't see who's around, it's hard to know when it's fine to ask. Make presence visible.
- Too many meetings at once. Spread the introductions over the first two weeks rather than ten calls on day one.
- Onboarding stops after week one. The first three months shape whether people stay. Keep the one-to-ones and the check-ins going.