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

What should you put in place before day one?

Give the new hire a manager, a first assignment, and a written definition of success before they start. Build the calendar around work the person can show at each review.

For remote first companies hiring now, the immediate task is to name who will prepare that first week. A signed offer leaves practical decisions open: who approves access, who explains the product, and who answers questions when the manager is busy.

Use the plan below as a starting template. These are proposed milestones, not industry benchmarks or promises about how quickly every hire will become independent.

Prepare the workspace and the first week

Create a single onboarding document that the hire can reach on day one. Include the role's purpose, the team directory, working hours, and links to the systems they need.

Assign an owner to each access request. Give each owner a due date and a way to confirm that access works. An invitation sent to the wrong email address does not complete the task.

For an engineering role, prepare development environment instructions and choose a starter ticket. Confirm who can approve repository access and who will review the first change. Give the hire a fallback task if an approval is delayed.

Keep access tied to the work. Start with the permissions needed for the initial assignment, then expand them through the normal approval process. Show the hire how to report a security concern and where sensitive information may be stored.

Book introductions around the first assignment. A developer fixing a billing issue needs to meet someone who understands that workflow. They do not need every department presentation before they can begin.

Name a backup contact for the manager's absence. Put that person's working hours beside their contact details so the hire knows when to expect help.

Use days 1–30 for supported delivery

Choose a small task with a clear finish. For a developer, that might be a bug fix with a test and a reviewed pull request. For an operations hire, it might be a recurring report with checked inputs and a documented handoff.

Explain what good work looks like before the person starts. Share a completed example and the acceptance criteria. Name the reviewer and explain how to request feedback.

Schedule a short daily check-in during the first week. Reduce the frequency as the hire learns where to get help. Keep a separate private conversation for feedback that does not belong in a team meeting.

At day 30, review actual work. Ask the hire to explain a decision, describe a blocker, and identify a document that needs correction. Check whether they know when to proceed and when to ask.

Record unresolved setup problems separately. Waiting for a test account is a manager's follow-up task. It should not become evidence that the hire works slowly.

Use days 31–60 for routine ownership

Give the hire an assignment that includes planning and handoff. Keep the scope small enough that a reviewer can assess the result without guessing what happened along the way.

Ask for a written plan before work begins. It should identify the expected result, dependencies, and decisions that need approval. The manager should resolve conflicting priorities before judging delivery.

For engineering work, review tests, code review responses, and release notes where relevant. For other roles, inspect the finished report, completed workflow, or customer handoff. Count completed outputs only when they meet the agreed standard.

At day 60, discuss the support still required. Some help may be normal for the role. Repeated confusion about the same process may call for a better explanation or a narrower assignment.

Ask the hire to hand work to a colleague using the team's usual process. Review whether that colleague can continue without reconstructing decisions from private messages.

Use days 61–90 to agree on ongoing scope

Define an area the hire can own with normal team support. Write down which decisions they can make and which require review.

Have the person take that work through the full cycle. Include the follow-up after delivery: checking the result, answering questions, and updating the relevant documentation.

Use the day-90 meeting to agree on the next quarter. Record the work they will own, the support they still need, and the next skill to develop. Give the hire room to describe what the team could change.

Avoid treating the calendar as proof of readiness. If the work supports a narrower scope, set that scope explicitly and choose a new review date.

What does the data say about hiring and the start date?

SHRM describes median time-to-fill in 2025 as roughly a month and a half for executive and nonexecutive positions. Its measure runs from job requisition to offer acceptance. It does not measure how long a new employee needs to learn your systems. SHRM's recruiting overview.

Keep these dates in the hiring plan:

• The date the role is approved.
• The date the candidate accepts.
• The agreed first working day.
• The date the hire takes ongoing responsibility for a defined area.

Recruiting can finish while equipment, employment setup, or access approvals still need work.

Ask each provider which event starts and stops its hiring clock. Then put the proposed start date beside the manager's capacity to train the person. A fast search has limited value if the reviewer is away during the first week.

Use the onboarding plan to assess your own setup as well. At each review, record whether the hire had the access and feedback promised. This helps the next manager see which delays the team can prevent.

When reporting progress to leadership, distinguish completed training from accepted work. A person may finish every introductory session while still waiting for the access needed to deliver their first assignment.

How should you plan Latin American working hours and remote handoffs?

Agree on a shared work window using named time zones. Write the hours in both the hire's location and the manager's location.

Mexico City stays at UTC-6, while Tijuana follows US daylight saving changes. A country-level label is too broad for scheduling. IANA time-zone rules for North America.

Bogotá stays at UTC-5. Buenos Aires and São Paulo stay at UTC-3 without seasonal clock changes. The relative difference from a US office can still change when that office changes its clocks. IANA time-zone rules for South America.

Put the agreed review window in the onboarding document. Check it again when clocks change. Make sure the person who reviews work is available within that window.

Also agree on holiday coverage before assigning deadlines. Ask the provider and the hire to confirm the applicable calendar. Record who handles urgent work when either side is away.

Explain how work moves outside meetings

Show the hire where to post progress and how to ask for a decision. Give them an example update that links to the work, identifies the blocker, and names the requested action.

Distinguish an urgent incident from a question that can wait until the next shared work window. Name the channel for each and explain who monitors it.

After a meeting changes the assignment, update the written task. A new hire should not have to compare a meeting recording with an outdated ticket to discover the current deadline.

Ask for a handoff note before planned leave. Include unfinished work, pending approvals, and the colleague covering each item. Use the same practice for the manager's leave.

How do the hiring models change onboarding ownership?

Choose the model based on who will manage the person and accept the work. A buyer seeking an individual contributor needs a different onboarding agreement from a buyer purchasing a project outcome.

Use this table to assign responsibilities during provider discussions. Confirm each allocation in the agreement.

Decide whether you are onboarding a person or a project

If you are comparing a nearshore software development company with an individual staffing arrangement, ask who assigns daily work. Then ask who is accountable when the result fails acceptance.

For an individual hire, the onboarding plan should describe the role and the manager's expectations. For a delivery team, define project governance, dependencies, and how scope changes are approved.

Keep those responsibilities explicit. A provider contact who resolves payroll questions may have no authority to settle a product decision. A technical lead may be unable to resolve an employment issue.

Opus states: "The client chooses the finalist and manages day-to-day work." This site is an Opus-owned reference; recommendations are editorial.

If you are considering that arrangement, bring the role's first assignment and proposed review dates to the discussion. Talk to Opus about a role.

Name the handoff owners

Before the start date, put the hiring manager and provider contact in the same handoff thread. Include the agreed role scope, schedule, and open setup tasks.

Give each unresolved item an owner. If a laptop is late, the hire should know who is tracking it. If a payment question comes up, the manager should know where to route it.

Keep performance feedback with the person who observes the work. Share concerns with the provider through the agreed process, using specific examples and the support already given.

What should a buyer know about "sign in to save company job alert"?

Treat that wording as an account prompt. Use the actual vacancy and hiring discussion to establish the role's terms.

Before onboarding, check that the accepted role matches what the candidate understood when applying. Confirm permitted work locations, required overlap, reporting line, and any travel requirement. Resolve differences before setting the first assignment.

If a candidate expected flexible hours but the team needs a fixed support shift, settle that before the start date. The onboarding document should reflect the arrangement both sides accepted.

What should you ask a provider before accepting the plan?

Ask for documents your manager can use. A general promise of onboarding support leaves room for different expectations.

Ask what must be ready for the first working day

Request a readiness list with owners and due dates. It should cover the agreed start date, equipment arrangements, and setup tasks each party controls.

Ask these questions before committing to a start:

• Who confirms that employment setup is complete?
• Who arranges equipment and resolves delivery problems?
• Who tells the hire where to go on the first morning?
• Which tasks depend on approvals from our team?
• What happens if a required item is delayed?

Give your access owner the same deadline. Provider readiness cannot compensate for an application account your team has not approved.

Ask what support continues after placement

Request the name of the ongoing contact and the process for raising an issue. Ask who responds if that person is away.

Separate administrative support from work coaching. Confirm who handles pay questions, who discusses attendance, and who helps with a concern about role fit.

Ask whether provider check-ins are included and what they cover. Keep your internal reviews on the calendar regardless. The manager still needs direct evidence of the person's work.

Ask how performance concerns will be handled

Share a sample scorecard before the hire starts. Use descriptions tied to work:

Avoid scoring the person on vague labels such as attitude or culture fit. If communication needs work, show the missed update and explain what the team needed.

When a milestone slips, identify the cause before changing the plan. A missing permission needs an access owner. A skill gap needs a smaller assignment, instruction, or a decision about role fit.

Write down the next step and review date. Do not let an unresolved concern wait until day 90 because that meeting is already booked.

Give the hire a copy of the review and space to correct factual errors. Record any changed expectations beside the original assignment.

Ask what happens if a replacement is needed

Request the terms that apply to your agreement. Ask how to start a replacement request and who owns the handover.

Cover access removal, equipment return, documentation, and unfinished work. Ask separately about cost and timing.

Keep the replacement process separate from the performance record. That record should explain the role expectations, work reviewed, and help given. It gives everyone a concrete basis for deciding what happens next.

Where does Opus fit in this onboarding plan?

Consider Opus if you want to choose an individual hire and manage that person's daily work. Assign your internal manager before agreeing on the start date.

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 role, seniority, and location you are considering.

Confirm the first working day separately from candidate selection. Before booking training, check the outstanding setup tasks and the availability of the manager and reviewer.

Opus states: "Every Opus placement works with US timezone overlap." Turn that into named working hours for your team. Include the reviewer's availability and any seasonal changes to the shared window.

Your manager should also explain which tools the hire may use, what data may enter those tools, and how work receives approval. Include those rules in the first assignment.

Opus states: "Every placement carries a lifetime replacement guarantee with no cap and no time limit." Ask how the guarantee applies to your agreement and how a handover would work.

Bring a short role plan to the conversation. Include the first assignment, internal manager, and evidence you want to review at each milestone. Add working hours and the systems your team must prepare.

Talk to Opus about a role.

<!-- Not saved to disk: the workspace is read-only. Live pages were not checked. -->