Remote Onboarding Checklist: Before Day One to Day 90
A remote onboarding checklist for managers: what to prepare before day one, how to run week one, and how to cover offshore hires across time zones.
By Ramp RemoteUpdated

A remote hire cannot absorb the office by osmosis, so everything the office teaches informally has to be prepared, written down and scheduled. The checklist below runs in four stages: before day one, day one, week one, and days 30 to 90. A fifth section covers what changes when your new hire is offshore. If that hire is a Philippines-based team member, we handle the employment, payroll, compliance and equipment parts of this list, which leaves you with the manager’s work: goals, introductions and feedback.
TL;DR
- Most remote onboarding failures start before day one: equipment that arrives late, accounts that are not ready and no written plan.
- Spread the first two weeks out. One university toolkit suggests 3 to 4 meetings a day rather than a few days packed with 7 to 8.
- Give every hire a 30-60-90 day plan, a named go-to colleague and a weekly one-on-one.
- For offshore hires, agree on core hours, record training and keep handoffs written, so nothing stalls overnight.
- With Ramp Remote, employment, payroll, compliance and equipment are included in one monthly fee per hire.
What a remote onboarding checklist has to cover
Remote onboarding is the same job as in-person onboarding with the hallway removed. Slack’s guide describes it as using digital tools, asynchronous communication and structured touchpoints to replace the in-person cues a new hire would otherwise pick up. Its checklist items are equipment delivery before day one, account setup, security training, paperwork, introductions, role-specific training, policies, performance expectations and scheduled check-ins.
That is a long list, but it sorts into four needs: the new hire can work (tools and access), knows what good looks like (goals and expectations), knows people (introductions), and is legally set up (paperwork and pay). The stages below put each need where it belongs in time.

Before day one: the preboarding checklist
The days between offer acceptance and the start date decide how the first week feels. Baylor University’s remote new-hire preparation checklist is a good model. It covers these tasks:
- Define 30-60-90 day goals and success metrics. Write them before the hire arrives, even as a draft.
- Announce the hire to the team once the offer is accepted and the background check is complete.
- Assign a go-to colleague. This is a peer who answers the small questions a manager should not have to.
- Order technology and request system access. MIT’s HR guidance says to order hardware well ahead of the start date and to allow up to two hours for remote set-up.
- Collect the reference material. That means org charts, standard operating procedures (the written how-tos for recurring tasks) and guides.
- Schedule introductions across the teams the hire will work with, plus a few informal ones such as a virtual coffee chat.
- Send a personal welcome message that includes the first-day schedule.
- Run a final readiness check the day before: calendar invites, system access and equipment delivery all confirmed.
The Indeed checklist adds two small items that pay off: a first-week agenda sent in advance and a welcome kit.
The most common failure is the equipment item. If the laptop is late, the hire spends the first days waiting, and no welcome call makes up for it. Treat delivery as a deadline with an owner, not a task someone will get to.
Day one: keep it short and human
The first day should answer three questions: can I log in, who are these people, and what am I doing this week? ADP’s timeline puts virtual team introductions, a tour of where policies and directories live, and paperwork on the first day.
A workable day-one run sheet:
- Welcome call with the manager. Cover the week’s agenda and how you prefer to communicate.
- Tool check. Confirm email, calendar, chat, project tools and password manager all work, before anything else.
- Team introduction in the main channel, with a one-line note on what the hire will own.
- Paperwork. Finish the required forms and have the hire read the key policies.
- A first small task that can be finished by the end of the day. A win on day one matters more than it sounds.
Resist filling the day with video. Atlassian’s onboarding lead has said that Zoom fatigue is real and advised capping video time early, delivering critical information live and filling gaps in writing in chat.
Week one and the first two weeks
The week-one goal is a hire who can do one real piece of work independently. UC Berkeley’s onboarding toolkit tells supervisors to build a two-week orientation calendar with 3 to 4 meetings a day. Packing a few days with 7 to 8 meetings, it warns, can overwhelm a remote hire.
A sensible first-week pattern:
| Day | Focus | Output |
|---|---|---|
| Mon | Welcome, tools, introductions | Logged in everywhere, first small task done |
| Tue | Role walkthrough with the manager | Written list of the hire’s recurring responsibilities |
| Wed | Shadow or review recorded training | Notes and questions captured |
| Thu | First real task with a review | Feedback in writing and a short call |
| Fri | One-on-one: what worked, what was unclear | Adjustments to next week’s plan |
Two habits do most of the work. The first is a weekly one-on-one that never gets cancelled. GitLab’s all-remote handbook recommends weekly 1-1s to field questions and build trust, plus informal coffee chats with no work agenda. The second is a written communication agreement: which messages need an immediate reply, which can wait, and when the hire is expected to be online. MIT’s guidance recommends exactly this kind of agreement along with clear availability blocks.
Days 30 to 90: from learning to owning
This is where most checklists stop and most problems start. ADP’s timeline schedules a supervisor follow-up at 15 days, projects and an onboarding survey at 30 days, a comfort check at 45 days, and a request for improvement suggestions at 90 days.
Use those checkpoints to answer concrete questions:
- Day 15: Is the hire blocked on access, information or a person? Fix it this week.
- Day 30: Has the hire completed the first goals from the 30-60-90 plan? Hand over one recurring task completely.
- Day 45: Does the hire know how their work is judged? Show them the metrics.
- Day 60: Has the hire improved a process or caught an error you had not seen? That is a good sign of ownership.
- Day 90: Hold a formal review against the plan and ask what the onboarding got wrong.
To tell whether onboarding is working, compare the hire’s output with the 30-60-90 plan and ask the same short survey at each checkpoint. The most useful warning signs are quiet ones: questions that stop, camera-off habits and tasks that return unfinished with no explanation. Raise them in the one-on-one before they harden.
Onboarding an offshore team member across time zones
An offshore hire follows the same checklist with three additions: a schedule that works across time zones, communication that does not depend on being in the same room, and a clear employment arrangement.
Time zones. Agree on core hours when both of you are online, and keep everything else asynchronous. TechClass recommends recorded training for self-paced completion, explicit core hours, a buddy in the new hire’s own time zone and documented handoffs so onboarding does not stall overnight. It also suggests rotating live-session times so the same people are not always taking calls at 5 a.m. For a Philippines-based hire working with a US team, that fairness point is worth taking seriously: decide which overlap window you will protect, and agree on it before the start date.
Documentation. Offshore onboarding fails when knowledge lives in someone’s head. Record your screen while you do the task, write the steps below the video, and keep it in a shared folder. Our guides on managing staff in the Philippines through the first 90 days and offshore team management go deeper on routines, and a time tracking setup for offshore teams helps you see workload from week one.
Employment and pay. The paperwork depends on the country the hire lives in, not yours. In the Philippines, for example, the labor department’s advisory says rank-and-file private-sector employees are entitled to 13th month pay if they worked at least one month in the calendar year. Rules like that are the reason employers tend to want a local employment arrangement behind an offshore hire. When we place someone, employment, payroll, compliance, equipment and onboarding sit inside one monthly fee, so the contract, the payslip and the laptop are not items on your list. Our offshore payroll officer and HR and recruitment coordinator roles are examples of the back-office hires some clients bring in to support a growing team.
Security. Add a short security block to week one: password manager, multi-factor authentication, which data stays in which system and what is never stored on a personal device. MIT’s list of tools new hires should know covers file sharing and cloud backup, computer security, and password management and data encryption.

A reusable checklist
Copy this into your project tool and assign an owner and a date to each line.
Before day one
- 30-60-90 plan drafted
- Equipment ordered, shipped and tracked
- Accounts and system access requested
- Go-to colleague assigned
- Welcome message and first-week agenda sent
- Readiness check completed the day before
Day one
- Manager welcome call
- All tools tested
- Team introduced in the main channel
- Paperwork and policies completed
- First small task assigned
Week one to two
- 3 to 4 meetings per day, not more
- Weekly one-on-one booked
- Communication agreement written
- Recorded training and written procedures shared
- First real task reviewed with feedback
Days 30 to 90
- Check-ins at 15, 30, 45, 60 and 90 days
- Survey at 30 days
- Formal review against the plan at 90 days
- Onboarding feedback fed back into the next hire’s plan
Where we fit
A checklist this long is manageable for one hire and heavy for a team that is hiring several. Ramp Remote recruits, vets, employs and manages skilled professionals based in the Philippines for finance, operations, administration, IT, marketing and support roles. You meet and select vetted candidates, and the monthly fee covers salary, compliance, equipment, support and onboarding. Published rates start from $1,400 per month for a Virtual Assistant, $1,500 for an Operations Coordinator and $1,600 for a Bookkeeper or Executive Assistant. See the full list on our roles page, or read how your first offshore hire works.

For a founder making a first offshore hire, our page for founder-led businesses explains the process step by step.
Our view on remote onboarding
Most onboarding advice is written as if the hard part is the welcome email. In our experience of structuring offshore hires, the hard part is the first fortnight after it: who answers a question at 9 a.m. in Manila when your team is asleep?
That is why we think the checklist should be built around handoffs rather than meetings. Write the task down, record it once and name the person who reviews the result. A new hire who can see what good looks like works faster and asks better questions.
It is also why we put employment, payroll, compliance and equipment into one monthly price. Those items are the ones that go wrong quietly, and they should not be competing with your attention in week one. Your time belongs to the plan, the one-on-one and the feedback.
Josh
FAQ
How long should remote onboarding take?
Plan for 90 days, with the most structure in the first two weeks. Common models, such as ADP’s, schedule check-ins at 15, 30, 45 and 90 days. The new hire should be doing real work by the end of week one.
What are the best practices for virtual onboarding?
Send equipment early, assign a go-to colleague, hold a weekly one-on-one and write down your communication norms. Limit live video in the first days, and keep recorded training and written procedures where the hire can find them without asking.
What should I do on a remote employee’s first day?
Hold a welcome call, confirm every tool works, introduce the hire to the team, finish the paperwork and assign one small task. Keep meetings short. A successful first day ends with the hire logged in everywhere and knowing what the next day looks like.
How is offshore onboarding different from domestic remote onboarding?
The steps are the same, but you also need agreed core hours across time zones, recorded training for asynchronous learning and an employment arrangement that follows local labor rules. With Ramp Remote, employment, payroll, compliance and equipment are included in the monthly fee for each hire.
Sources
- Remote Onboarding: A Complete Guide for Managers, Slack
- Onboarding Remote Employees, Indeed
- Remote new-hire preparation checklist, Baylor University HR
- Onboarding in Remote/Hybrid Work Environments, MIT Human Resources
- Online Onboarding Process, ADP
- Onboarding Timeline and Toolkit, UC Berkeley People & Culture
- Virtual onboarding checklist, Atlassian
- Complete guide to remote onboarding, GitLab Handbook
- Global Onboarding: Overcome Time Zones & Culture, TechClass
- DOLE clarifies 13th month pay rules, Department of Labor and Employment