Onboarding plan for remote employees: the first 30 days, day by day where it matters
On this page
An onboarding plan for remote employees schedules everything a new hire would otherwise pick up by being in the same building: meeting colleagues, learning how decisions get made, knowing who to ask, and getting working equipment and access on day one. It starts two weeks before the start date, because shipping hardware and verifying employment eligibility at a distance take time, and it runs through the first 30 days with a check-in cadence that is denser than in an office.
The general manager's checklist is in the new hire onboarding checklist, and goals beyond the first month belong in a 30-60-90 day plan. This page covers what changes when the person is not in the room.
Two weeks before day one
| Task | Owner | Why it cannot wait |
|---|---|---|
| Order and ship the laptop and peripherals, with tracking; confirm delivery 3 business days before the start | IT | Shipping delays are the most common cause of a lost first day |
| Create accounts: email, chat, video, core systems; send login steps for day one | IT | Multi-factor setup often needs a phone and a working laptop together |
| Arrange Form I-9 document examination (see below) | HR | Section 2 is due within three business days of the start |
| Confirm payroll set-up for the employee's work state | HR or payroll | A new state can mean new withholding and unemployment registrations |
| Send the welcome message: first-day schedule with times in their time zone, who they meet first, what to have ready | Manager | Removes first-day uncertainty |
| Pick an onboarding buddy with overlapping working hours | Manager | Someone to ask the small questions |
| Book the first two weeks of meetings in the new hire's calendar | Manager | A blank calendar feels like being forgotten |
Form I-9 at a distance
The employee completes Section 1 by the first day of employment, and the employer completes Section 2 within three business days (USCIS, Form I-9). For a remote hire there are two lawful ways to examine the documents: the DHS alternative procedure by live video, available to employers enrolled in E-Verify and in good standing, or an authorized representative who examines the documents in person on the employer's behalf. I-9 remote verification explains both, including the consistency rules for choosing between them.
Equipment and expenses
Decide before the offer what the company provides (laptop, monitor, headset, chair, internet stipend) and what it reimburses. Some states require it: California's Labor Code requires an employer to indemnify employees for "all necessary expenditures or losses incurred by the employee in direct consequence of the discharge of his or her duties" (Labor Code § 2802, as of September 2026). Put the policy in writing and send it with the welcome message.
The first week, day by day
| Day | Morning (their time) | Afternoon |
|---|---|---|
| 1 | 30-minute video call with the manager, camera on, personal before practical; IT check that everything works | Buddy call; I-9 Section 2; read the team's working agreements; end-of-day check-in |
| 2 | Team meeting with introductions; 1:1 with the closest collaborator | First small task, with the buddy available; check-in |
| 3 | Walk-through of the main tools and where decisions are written down | Focus time; 1:1 with a second collaborator; check-in |
| 4 | Shadow a real meeting or customer call | Continue first task; short written questions sent to the buddy |
| 5 | Present the first task's result to the manager | Week-one review: what was confusing, what is missing, plan for week two |
Keep live meetings to roughly half of each day in the first week. Remote new hires tire faster on video than in person, and they need uninterrupted time to set up, read and try things.
Weeks two to four
- Week 2: own a piece of ongoing work with support close by. One-to-ones with people outside the team they will depend on. Check-ins three times a week.
- Week 3: first piece of work shipped or delivered end to end. Join a cross-team meeting and contribute. Check-ins twice a week.
- Week 4: 30-day review: goals met, gaps, what the company's onboarding missed. Move to the normal one-to-one cadence and agree the 60- and 90-day goals.
What remote onboarding has to make explicit
| In an office it happens by itself | Remotely, write it down or schedule it |
|---|---|
| Seeing who is busy and who is free | Status norms: how people show focus time, how quickly messages are answered |
| Overhearing how decisions are made | Where decisions are recorded, and an invitation to read them |
| Asking a quick question across the desk | A named buddy and a channel where beginner questions are welcome |
| Meeting people at lunch | Scheduled 1:1s, including a few purely social ones |
| Watching colleagues work | Shadowing sessions and recorded walk-throughs |
| Knowing when the day ends | Stated working hours and expectations for after-hours messages |
Time zones
If the new hire works several hours away from the team, plan around the overlap. Put onboarding meetings inside shared hours and state every time in the new hire's zone. Pick a buddy who shares the most hours with them. For work outside the overlap, give written tasks with a clear definition of done, so the new hire is not blocked waiting for an answer until the next morning.
The manager's time, budgeted
Remote onboarding costs the manager more time in the first month than office onboarding does, because nothing happens in passing. Plan for roughly an hour a day in week one (the day-one call, daily check-ins, reviewing the first task) and a few hours a week after that. If the manager cannot give that time in the new hire's first month, move the start date or hand specific pieces to the buddy and a named senior colleague, in writing, before day one. A new remote hire who waits a day for every answer loses the first month without anyone noticing.
The template
REMOTE ONBOARDING PLAN — [name], [role]
Start date: [ ] Time zone: [ ] Team overlap: [hours]
Manager: [ ] Buddy: [ ] HR: [ ] IT: [ ]
BEFORE DAY ONE
[ ] Equipment shipped [date], delivered [date]
[ ] Accounts created; day-one login steps sent
[ ] I-9 route: [alternative procedure / authorized rep: name]
[ ] Payroll set up for work state: [state]
[ ] Expense and equipment policy sent
[ ] Welcome message with day-one schedule sent [date]
[ ] Weeks 1–2 meetings booked
WEEK 1
Day 1: [manager call, IT check, buddy, I-9 Section 2]
Day 2: [team intro, collaborator 1:1, first task]
Day 3: [tools walk-through, 1:1]
Day 4: [shadowing]
Day 5: [first task presented, week-one review]
Check-ins: daily, [time]
WEEKS 2–4
Week 2 ownership: [ ]
Week 3 delivery: [ ]
People to meet: [names, by week]
Check-ins: [3x, then 2x per week]
30-DAY REVIEW [date]
What is working: [ ] What is confusing: [ ]
What onboarding missed: [ ] 60/90-day goals: [ ]A filled example
New hire: Tomás Reyes, customer support specialist (invented), works from Arizona; the team is mostly on Eastern time.
Before day one: laptop and headset delivered the Wednesday before. The company is enrolled in E-Verify and in good standing, so HR booked a live video document examination for day one. Payroll confirmed the company was already registered in Arizona. Buddy: a specialist in Colorado, whose working day overlaps with his more than the Eastern team's does.
Week 1: meetings between 11 AM and 2 PM Arizona time. Day 1 laptop worked but the ticketing system login failed; fixed by noon because IT was on the day-one call. First task: answer five closed tickets as practice, reviewed by the buddy.
Week 2: took live tickets in one product area with the buddy reviewing replies before sending.
Week 3: answered tickets independently; joined the weekly product feedback meeting.
30-day review: ahead on product knowledge; unsure when to escalate to engineering. Added a session with the escalation lead and a written escalation guide, which the team did not have and now uses for every new hire.
Checking that it worked
At 30 and 90 days, ask directly: what was the most confusing part of joining, who do you still not know how to reach, and what did you expect to have by now that you do not. Keep the answers across hires; patterns show where the plan needs work. When remote employees leave, the questions in exit interview questions for remote employees often point back to the first month, which is the cheapest place to fix them.
Questions people ask
How is onboarding a remote employee different from onboarding in the office?
Everything that happens by chance in an office has to be scheduled: meeting people, overhearing how decisions get made, asking a quick question. Remote onboarding also has lead times an office does not, such as shipping equipment and verifying Form I-9 documents at a distance, so more of the plan has to happen before day one.
How do you complete Form I-9 for a remote employee?
There are two lawful routes. An employer enrolled in E-Verify and in good standing can use the DHS alternative procedure, examining documents over a live video call after the employee sends copies. Any employer can instead designate an authorized representative, such as a notary or a colleague, to examine the documents in person on its behalf.
How often should a manager check in with a new remote employee?
Daily in the first week, even for ten minutes, then two or three times a week in weeks two to four, then the regular one-to-one cadence. Short, frequent contact catches confusion early, which matters more remotely because a new hire cannot see whether colleagues are busy or approachable.
Do employers have to pay for a remote employee's home office costs?
It depends on the state. California, for example, requires employers to reimburse employees for necessary expenditures incurred in direct consequence of doing their job, which can include some home office costs. Check the law of the state where the employee works and set a written reimbursement policy before the start date.