Built for service firms whose founders are making their first 1–5 remote hires.Inspect the brief
Start your hiring brief

A remote onboarding checklist for days 30, 60, and 90

Give a strong hire the access, context, cadence, measures, and feedback needed to take ownership.

Onboarding pathway in three stages built from frosted acrylic blocks, folders, and blue markers
30/60/90 onboarding pathway visual for role handoff.
DECISION SUMMARY

Secure access before the start date

Teach decisions, not only tasks

Measure ownership with observable outcomes

APPLY THIS GUIDE

Choose the issue in front of you and jump to the section that resolves it.

Use the summary choices to reach the most relevant guidance without reading the entire page first.

RELEVANT GUIDANCE

Secure access before the start date

Open the matched section for the complete framework, decision criteria, and next action.

Jump to “Before day one
COMPARISON VIEW

Preview who owns the onboarding handoff at each stage.

Use this matrix to identify which model matches the work, access, judgment, and management capacity involved.

Swipe or use Shift + scroll to compare every column.

StageEmployer or manager ownsNew hire owns
Before day oneApprove relationship, equipment, accounts, minimum necessary access, manager, and calendar for the first weekConfirm start logistics and surface missing access or context
First 30 daysTeach business context, decision rules, measures, and escalation; review work frequentlyLearn the system and close supervised loops with visible updates
By day 60Transfer the agreed recurring cadence and coach exceptionsOwn core work, report risks early, and improve one recurring handoff
By day 90Review evidence against the scorecard and reset scope or support where neededOperate against agreed measures with less prompting and a clear growth plan
01

Before day one

Finalize the employment or contractor relationship, payroll or payment method, equipment, manager, working hours, time off process, confidentiality terms, calendar for the first week, and emergency contact path. Create accounts with minimum necessary access, test required hardware and authentication, prepare the role scorecard, and assign an owner for every onboarding dependency.

  • Send a written plan for the first week
  • Confirm access without sharing personal credentials
  • Schedule manager and stakeholder introductions
02

Days 1–30: teach context and close supervised loops

Explain customers, services, vocabulary, stakeholders, priorities, communication norms, quality standards, and the reasons behind recurring work. Demonstrate tasks, observe the hire completing them, review the output quickly, and update documentation where the process and reality differ. Use short weekly reviews tied to the approved outcomes for the first 30 days.

  • Practice the escalation path
  • Review written and live communication
  • Track questions that reveal missing context
03

Days 31–60: transfer the operating cadence

Move the core recurring workflow from supervised execution to visible ownership. The hire should manage deadlines, send structured updates, surface dependencies early, and maintain the relevant documentation. Review error patterns and decision quality, then select one contained workflow improvement rather than expanding the role in every direction.

  • Measure outcomes, not online presence
  • Clarify new decision rights in writing
  • Keep security access proportional to ownership
04

Days 61–90: confirm autonomy and role shape

Evaluate the agreed outcomes, reliability, judgment, communication, stakeholder trust, documentation, and management load using evidence from the work. Decide which responsibilities are stable, which need more support, and whether the scope or measures should change. Write the development plan for the next quarter and access review instead of treating day 90 as the end of onboarding.

  • Review permissions and unused accounts
  • Record mutual feedback
  • Set the outcomes for the next 90 days
05

If onboarding is not working

Separate a knowledge gap, unclear process, insufficient access, weak management, role design error, and performance concern before choosing a response. State the expected behavior, show the evidence, agree on support and a review date, and document the outcome. Do not leave a new remote hire guessing through silence or vague dissatisfaction.

SOURCE STANDARD

Use guidance in the context of the actual role and jurisdiction.

First Hire’s framework is operational guidance, not legal, tax, employment, or security advice. These primary sources support the specific selection, classification, or access topics discussed on this page.

NIST: small business cybersecurityCISA: require multifactor authentication
A CLEARER NEXT STEP

Bring us the bottleneck. We’ll help name the role.

Start with the work that keeps interrupting your week, plus the timeline and schedule overlap you need.

Start your hiring brief

EVIDENCE BEFORE INTERVIEWS · YOU MAKE THE FINAL CALL