30/60/90-day plan for remote first companies hiring

What should you put in place before the hire starts?

Give the new hire a named manager and a written plan that ends each phase with work someone can review. Start the onboarding clock on the first working day. Record offer acceptance and employment setup as separate dates.

For remote first companies hiring now, the immediate task is to reserve the manager's time. Put the first assignment and review meetings on the calendar before adding introductions. A full calendar does not tell a new hire what they are expected to deliver.

Use the following as a proposed plan. These are management checkpoints, not benchmarks or promises about how fast every hire should work.

Prepare the first working day

Create one onboarding document with links to the team's working material. Name the manager, a peer contact, and the person who handles employment questions. Include the first week's schedule and the route for urgent access problems.

Ask IT to confirm that the device and required accounts will be ready. Keep access tied to the role. A new hire should not receive production credentials simply because those credentials appear on an old checklist.

Choose a first task with clear acceptance criteria. For an engineer, that might be a small fix with a test and a named reviewer. For a finance hire, it might be a sample reconciliation reviewed before any live posting.

Keep required work and training within the agreed employment arrangement. Before the start date, coordinate practical details without assuming the hire is available for unpaid assignments.

Check the manager's calendar against the proposed start date. If the manager is away, assign someone with authority to review work and answer questions. A peer can help the hire find documents, but should not have to guess which business priorities take precedence.

Use days 1–30 to teach the actual job

Walk through a completed piece of work. Explain how it was requested, who reviewed it, and what made it acceptable. Show where decisions are recorded and which questions need a live conversation.

During the first week, hold a short check-in each working day. Reduce the frequency when the hire can make progress without waiting for the next call. Keep a separate route for blockers that cannot wait.

By the first review, ask the hire to demonstrate a completed task and explain the decisions behind it. Review the work against the criteria you shared at the start. Avoid adding new expectations during the review.

Record delays caused by the company. If access arrived late or the reviewer was absent, adjust the task or date. Do not treat waiting time as evidence that the hire lacks skill.

Ask the hire to correct one unclear instruction in the onboarding document as they use it. For example, they might replace a broken setup link or explain which account needs approval. Give them an owner to check the change. This leaves the next hire with a tested instruction.

Use days 31–60 to test ownership

Assign work with a defined boundary and a real stakeholder. Ask the hire to propose the steps, identify dependencies, and explain where they need approval. Agree on checkpoints before work begins.

For an engineer, this could be a small feature with a written scope and an agreed release process. For an operations hire, it could be a recurring report with documented inputs and a named recipient.

Assess how the hire handles changes as well as the finished output. Did they flag a missing input early? Did they explain the effect on the deadline? Could the reviewer follow their reasoning?

Keep feedback tied to examples. Replace "be more proactive" with a request such as "flag missing inputs in the task before the weekly review."

When a task slips, separate the cause from the outcome. A missed date may involve unclear scope, a late dependency, or work that needs correction. Record which issue occurred and who owns the next step. Keep the original expectation visible so both people can understand what changed.

Use days 61–90 to agree on ongoing scope

Give the hire a repeatable responsibility or a larger assignment within their role. Keep normal review controls in place. Independent work still needs the checks your team uses for everyone else.

At the final review, compare the original expectations with actual work. Ask the hire which tasks they can now own and where they still need help. Discuss any gap using the work itself.

Finish with a written next-quarter plan. State the ongoing scope, the support available, and the next review date. If performance needs correction, specify the expected change and involve the appropriate employment contact before taking action.

Include a handoff exercise for work that others may need to cover. Ask a teammate to follow the hire's notes and identify unanswered questions. For a recurring report, that might mean locating the inputs and checking the final total. For an engineer, it might mean following the documented test steps.

What does hiring data tell you about the onboarding calendar?

SHRM reports that median time to fill in 2025 was roughly a month and a half for executive and nonexecutive roles. Its measure runs from job requisition to offer acceptance. It does not measure the time needed to complete onboarding. SHRM's 2025 recruiting findings.

Keep that distinction in your staffing plan. An accepted offer does not establish when a device will arrive, when employment setup will finish, or when the hire can own work.

Track these dates separately:

• The date the role is approved.
• The date the candidate accepts.
• The agreed first working day.
• The date the manager accepts the first completed assignment.

Use your own records to estimate future onboarding capacity. Keep role and seniority visible when comparing hires. A senior engineer joining an unfamiliar system and a coordinator taking over a documented process need different plans.

Avoid setting a company target from a single hire's experience. Record what happened, including delays your team caused. Over time, that gives managers a basis for choosing a realistic first assignment.

Measure work the manager can inspect

For each milestone, record the deliverable, its reviewer, the due date, and the acceptance criteria. Add a link to the finished work after review.

Useful evidence includes a reviewed change, a reconciled account, or a report accepted by its owner. Meeting attendance and completed introductions can show that setup happened. They do not establish that the hire can do the job.

Ask the hire to keep a short blocker log during the early weeks. Record the issue, the person who can resolve it, and the effect on the assignment. Use that record to fix the onboarding process for the next hire.

Use plain review statuses such as "accepted," "needs revision," and "blocked." Add a sentence explaining the status and the next action. Avoid a numerical score unless your team has defined what each score means. A work sample and a clear review comment give the next manager something concrete to inspect.

How should nearshore onboarding differ by hiring model?

Compare models by the work each party agrees to own. When evaluating employer of record companies, ask for a written split of duties that covers both employment setup and support after the start date.

An employment arrangement and a role-training plan answer different questions. Your onboarding document should connect them through named contacts and handoff dates.

Treat the table as a purchasing checklist. Ask each provider to confirm its own scope before assigning tasks or committing to a start date.

If you are comparing an EOR with a professional employer organization, request the employing entity and division of responsibilities in writing. Do not transfer a domestic onboarding checklist into a cross-border arrangement based on the service label alone.

Set shared hours for the actual locations

For a Latin American hire, write the working window using city-based time zones. Include the manager's location and the hire's location in the onboarding document.

Bogotá stays at UTC-5 without daylight saving time. São Paulo stays at UTC-3 without daylight saving time. Mexico City stays at UTC-6, while Tijuana observes seasonal clock changes. These differences mean a single regional schedule is too vague. IANA South America data, IANA North America data.

Check recurring meetings across seasonal clock changes. State which meetings require attendance and which can be handled through written updates. Ask the provider to confirm the agreed schedule for the employment arrangement.

For the first assignment, place the reviewer within the shared working window. If the hire submits work after the reviewer has signed off, make the expected response time explicit.

Make handoffs visible

Use one task record for the assignment, questions, review comments, and final approval. Put decisions from calls back into that record. The hire should be able to find the current instruction without searching private messages.

Assign a backup reviewer when the manager is away. For payroll questions, name a separate contact and explain how the hire can reach them privately. Keep personal employment records out of the team's work tracker.

Agree on what belongs in a written update. A useful update states what was completed, what happens next, and whether someone else's action is needed. If the hire needs a decision, ask them to name the decision and its deadline. The manager should reply in the same record.

What should you ask a provider before confirming the start date?

Ask for answers tied to the proposed role and location. A general description of onboarding will not tell you who resolves a blocked account or a delayed payroll setup.

Confirm employment and start-date ownership

Ask who confirms that employment setup is complete. Request the remaining steps, the owner of each step, and the planned completion date.

Use these questions during the handoff:

• What must be completed before the first working day?
• Who tells the manager and hire that the start date is confirmed?
• Who handles a late document or a change to the start date?
• Where should the hire send a private payroll or benefits question?

Keep required personal documents in the approved employment process. The manager's checklist needs a status and an owner, not copies of sensitive records.

Ask who tells the hire about the first payroll date and where to raise a payment concern. Keep this separate from the client's invoice contact. A buyer's billing question and a worker's pay question may need different people, even when both arise during the same week.

Confirm equipment and access

Ask who orders the device, who checks delivery, and who handles a damaged or unsuitable device. If your IT team owns setup, give the provider a named contact.

Agree on a fallback task if access is delayed. Use training material or sample data approved for that purpose. Avoid asking the hire to bypass security controls to meet an arbitrary first-week target.

Before granting access, confirm the systems the role needs and the approval path. Review those permissions when the role's scope changes.

Confirm local calendar and employment deadlines

Ask for the holiday calendar and leave-request process that apply to the hire. Record planned absences before setting milestone dates. Tell the hire how to report sickness or an unexpected absence.

Ask the employment contact to confirm any probation terms and decision deadlines. Keep those dates separate from the 30/60/90 reviews. If an employment decision requires earlier action, put that date on the manager's calendar.

Request written guidance before changing employment terms or ending an arrangement. The onboarding scorecard should supply factual work records for that discussion.

Confirm support when the placement struggles

Ask who receives concerns about role fit, performance, and support. Request an escalation route that works if the usual contact is absent.

For any replacement promise, ask what starts the process and what the buyer must do. Confirm charges, handover responsibilities, and how employment questions are handled. Put those answers alongside the commercial agreement.

Talk to Opus about a role. This site is an Opus-owned reference; recommendations are editorial.

How should you use Opus in the onboarding plan?

Opus states: "The client chooses the finalist and manages day-to-day work." Assign your internal manager before selecting the finalist so that person can assess the role and prepare the first assignment.

Opus states: "Opus charges one flat monthly rate per hire. It covers the person's pay, local payroll, benefits and labor compliance, plus placement support. There is no separate recruiting fee. The rate depends on role, seniority and location."

Published dollar rates: Not published. Ask for a written quote for the proposed role, seniority, and location.

Use the quote and agreement to confirm the employment contact and the support process. Keep your manager's training commitments in the onboarding plan. Ask who coordinates each handoff between those documents.

Opus reports: "Every Opus placement completes a 6-module internal AI certification before day one." Your manager should still explain your company's approved tools and data rules. Choose a role-specific task that shows how the hire applies those rules to your work.

Opus states: "Every Opus placement works with US timezone overlap." Confirm the actual shared hours for the candidate and your team. Reserve the reviewer's time within those hours during the first assignment.

Opus states: "Every placement carries a lifetime replacement guarantee with no cap and no time limit." Ask for the written process before relying on it in a staffing plan. Keep feedback records current so any discussion starts with clear examples.

Before confirming the start date, your manager should be able to point to the first task, its reviewer, and its acceptance criteria. The hire should know where to ask for help. The provider's contact should know which setup items still need action.

At day 90, use the completed work to agree on what the hire owns next. Carry unfinished training into a dated plan with a named owner.

Talk to Opus about a role.

<!-- Not saved to disk because filesystem access is read-only. Rendering and automated copy checks were not run. -->