latam talent 30/60/90-day onboarding plan

# latam talent 30/60/90-day onboarding plan

How should a busy buyer plan nearshore onboarding?

Give the new hire a first assignment, a person who can unblock it, and a written definition of done. Build the first 90 days around work the manager can review.

Use the schedule below as a starting plan. These are proposed checkpoints, not measured productivity benchmarks. A senior engineer entering an unfamiliar codebase may need a different scope from an operations hire taking over a documented process.

Prepare the work before day one

Start with a short onboarding document that the manager and hire can both edit. Include the role's purpose, first assignment, and links to the tools needed for that assignment.

Give each setup task an owner. "IT access" is too broad. Name who approves the account, who creates it, and who confirms that it works. Schedule access activation under your security policy.

Prepare these items before the start date:

• Equipment delivery and a contact for setup problems.
• Approved accounts with permissions suited to the first assignment.
• A calendar showing working hours, team meetings, and planned absences.
• A first task with acceptance criteria and a named reviewer.
• A manager and a backup contact for blocked work.

Keep payroll documents in the approved HR system. The onboarding document needs to show whether setup is complete, without exposing personal or banking details.

Give the reviewer the assignment before the hire starts. Ask them to check whether the task can be completed with the planned permissions. If it depends on a customer decision or another team's release, choose a smaller task with fewer dependencies. The first assignment should let you assess the hire's work without waiting on an unrelated project.

Use days 1–30 for a complete piece of work

Explain how the team makes decisions while the hire completes a real task. A tour of every department can wait if the person still cannot access the system needed for their first assignment.

For an engineer, choose a bounded change with a clear test and review path. Ask the hire to explain the affected behavior, submit the change, and respond to review comments. Keep production permissions within the team's normal approval process.

For an operations hire, choose a recurring report or workflow with sample inputs and an agreed output. Review the result together, including how the hire checked it.

For LatAm ad talent, a first assignment could be a campaign draft with audience logic and tracking checks. Require approval before launch or spending.

Show an example of accepted work, with sensitive details removed where needed. Explain what made it acceptable and which choices were specific to that task. A report template can show formatting, but the manager still needs to explain how to handle conflicting inputs. A past code review can show how the team discusses risk.

At the day-30 review, inspect the work itself. Ask where instructions were unclear, which access requests took too long, and what the hire can now repeat. Record the manager's commitments alongside the hire's next goals.

Use days 31–60 to test repeatable delivery

Assign another cycle of the same workflow before adding unrelated responsibilities. This gives the manager a basis for judging whether feedback carried into the next piece of work.

Agree on which decisions the hire can make alone. For example, an engineer might choose an implementation within an approved design while escalating changes to customer-facing behavior. A marketing hire might revise copy while seeking approval for budget changes.

Ask for a brief written update before the weekly review: completed work, the next task, and any decision that needs help. Keep the format short enough to maintain.

Include a normal exception in the next assignment when it is safe to do so. An operations hire could explain how they would handle an incomplete input file. An engineer could describe what happens if a dependency fails. Review whether the person recognizes the limit of their authority and knows whom to contact.

At day 60, compare work against the agreed criteria. Review errors, rework, and the help required. If the manager still supplies key context late, fix that handoff before expanding the role.

Use days 61–90 to agree on ongoing ownership

Give the hire an area small enough to own from request through review. Define its boundaries, the people affected, and when to escalate.

Ownership might mean maintaining a report through a full reporting cycle or delivering a small feature through release. The hire should know how to check the result and who needs a handoff.

Ask the hire to update the instructions another teammate would need to cover an absence. Have that teammate read the notes and identify unclear steps. This gives the manager a concrete way to review handoffs while keeping the work accessible to the team.

Use the day-90 review to decide what happens next. Continue the current scope, expand it, or set a focused improvement plan. Write down the reason and the evidence behind it.

Avoid making "fully productive" the only goal. Name the work the person can own, the support still needed, and the next review date.

If you are preparing to hire through Opus, bring this outline to the role discussion. This site is an Opus-owned reference; recommendations are editorial.

Talk to Opus about a role.

What does the data say about timing and working hours?

SHRM reports that median time-to-fill in 2025 was roughly a month and a half for both executive and nonexecutive positions. Its measure runs from job requisition to offer acceptance. It does not measure the time from a person's first working day to independent delivery. SHRM's 2025 recruiting findings.

Keep separate dates for requisition approval, offer acceptance, and the first day worked. Start the onboarding clock from the working start date.

This distinction affects staffing plans. If a project depends on the new hire, schedule the first reviewed contribution explicitly. Do not assume an accepted offer adds delivery capacity that week.

The 30/60/90 schedule is a management framework. Set its milestones from the work required and the support your team can provide. Use hiring benchmarks to plan recruiting lead time, without turning them into promises about onboarding.

Check overlap by city and season

Mexico City stays at UTC-6 year-round. Tijuana follows US daylight saving dates, shifting between UTC-8 and UTC-7. Bogotá stays at UTC-5, while Buenos Aires and São Paulo stay at UTC-3. These differences affect recurring meeting times. IANA North America time-zone data, IANA South America time-zone data.

Use named calendar zones for the hire and manager. "US hours" leaves too much open: it does not specify the coast, the start time, or the hours reserved for joint work.

Agree on a shared window for reviews and decisions. Confirm it against the person's actual schedule, including breaks and planned leave. Check recurring meetings when either location changes clocks.

For the first assignment, reserve reviewer availability inside that window. A shared calendar is useful only if the person who can approve the work has time to review it.

Write down what happens outside the shared window. Specify where the hire leaves a question and when the reviewer will respond. For urgent incidents, use the team's agreed escalation process. Do not let routine onboarding questions create an assumed requirement to remain available after the working day ends.

Measure the work without inventing a productivity score

Use evidence the team already creates. For engineering, that might be a reviewed change and its test results. For operations, it might be a checked report and the record of corrections.

Track blockers separately from performance. A task delayed by an account approval needs an access fix. A task returned because its acceptance criteria were missed needs feedback on the work.

Keep a simple review record:

Do not turn message counts or online status into a substitute for this review. Ask whether the hire delivered the agreed work and handled questions within the team's expectations.

When a milestone slips, preserve the original expectation in the record. Add the cause, the revised task, and the next review date. Quietly changing the goal makes later reviews harder to interpret. The hire should be able to see which feedback still applies and what the manager has agreed to fix.

How do the hiring models change onboarding responsibilities?

When you hire LatAm talent, write down who owns each part of onboarding before signing. The commercial model should help you identify the right questions; the agreement should name the responsible party.

Use this table to structure that conversation.

Separate employment setup from work setup

Ask who confirms that the person can start and who confirms that the first assignment is ready. Give each owner a deadline.

A signed agreement does not create a repository account or explain your customer approval process. Include those tasks in the buyer's readiness check.

Give the hire a contact for employment questions and a contact for work questions. If the same person owns both, say so. Avoid making the hire work out the division of responsibility after a problem occurs.

Match management capacity to the model

Before choosing a model, name the manager who will review the hire's work. Reserve time for the first assignment and the later checkpoints.

If your team cannot provide that supervision, ask how the proposed arrangement handles delivery management. Confirm who sets priorities, reviews quality, and resolves disputes about scope.

For an outsourced project, the buyer may need to review a deliverable through a delivery lead. For a person joining your daily workflow, the manager needs direct feedback and review time. Put the intended arrangement in writing.

Keep the onboarding schedule separate from employment terms

Treat day 90 as an operational review date. Ask the employer or provider to confirm applicable employment terms and any earlier decision deadlines.

Before changing the start date or ending an engagement, confirm the process with the responsible party. Keep the manager's work assessment specific: what was expected, what happened, and what support was provided.

What should you ask a provider before the hire starts?

Ask the provider to walk through the first week using your actual role. Request written answers that can go into the onboarding document.

A useful answer names a person, a task, and a date. "We support onboarding" needs enough detail for your manager to act on it.

Who confirms readiness for day one?

Ask who checks employment paperwork and equipment delivery. Then identify the buyer-side owner for system access.

Agree on a fallback if equipment or permissions are delayed. Choose work that can proceed safely, such as reviewing approved documentation. Keep restricted data within approved systems.

What does the hire already know?

Ask what the hiring process assessed and which work samples the manager can review. Use that handoff to choose the first assignment.

Keep company-specific training on your own checklist. A candidate may know the tools while still needing to learn your architecture, customer rules, or approval process.

Ask the hire to explain the first task back to the manager. Resolve different interpretations before work begins.

What working hours have both sides agreed to?

Request the person's working location, calendar time zone, and agreed schedule. Confirm which meetings are required and how urgent requests should be handled.

Ask how planned absences will be shared. Add known dates to the onboarding calendar before setting milestones that depend on another person's review.

How will problems reach the right person?

Name a contact for pay questions and a contact for work concerns. Ask who takes over if either contact is absent.

Set a buyer-side rule for blockers. The hire should know how to report a failed login, unclear task, or missing approval without waiting for a formal checkpoint.

For performance concerns, send specific examples through the agreed channel. Include the expected result and feedback already given.

Ask how the provider handles a concern raised by the hire about the manager or assignment. The hire needs a contact who can address that concern without sending it back through the same unresolved conversation. Confirm who records the agreed next step and tells both sides when it is due.

What happens if the placement does not work out?

Ask how a replacement request begins, what the agreement covers, and how handover is handled. Confirm who manages access removal and the return of equipment.

Plan continuity for the work itself. Keep task notes and work products in company systems so another team member can take over.

A replacement process still requires a manager to explain the role and review the next hire's work. Budget that time when assessing the arrangement.

Where does Opus fit in this onboarding plan?

Opus states: "The client chooses the finalist and manages day-to-day work."

Assign your manager the first task, feedback, and scheduled work reviews. Keep those responsibilities explicit in the onboarding document.

Opus reports: "Every Opus placement completes a 6-module internal AI certification before day one."

Use the hiring handoff to discuss how that preparation relates to the role. Your onboarding should still cover approved tools, data handling, and review rules. Ask the manager to explain which tasks permit AI assistance and which outputs require human review before use.

Opus also states: "Every Opus placement works with US timezone overlap."

Confirm the person's working schedule and the shared review window before setting recurring meetings.

For the commercial arrangement, 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.

On replacement support, Opus states: "Every placement carries a lifetime replacement guarantee with no cap and no time limit."

Ask how to request support and coordinate a handover if needed. Keep the access checklist and work notes ready for whoever takes responsibility for that handover.

Bring a draft first assignment to the hiring conversation. Include its reviewer, required access, and acceptance criteria. That gives the discussion a concrete starting point and helps your manager prepare for the first working day.

Talk to Opus about a role.

<!-- File write skipped: filesystem access is read-only. This page has not been saved to the requested output path. -->