nearshore vs offshore replacement and offboarding playbook

What should a busy buyer decide before replacing a hire?

Assign separate owners to the replacement search and the employment exit. A provider may agree to find another person while your team still needs to approve final costs and recover equipment. Put those tasks on the same schedule, with separate signoffs.

Start with the reason for the change. A resignation, missed performance standard, changed role, and suspected security incident need different responses. Record the facts and have the legal employer review the proposed exit before anyone promises a final date.

For performance concerns, compare the work with the agreed role. Write down the missed requirement and the feedback already given. Check whether the person had the tools and authority to finish the task. A replacement will inherit an unclear job unless you fix it.

Use a shared exit record with these fields:

Treat these as assigned tasks. "HR will handle it" is too vague when the provider's HR team and your own team both expect the other to act.

Prepare for an exit without a handover

Keep work in company-controlled accounts throughout the engagement. Assign a backup owner to production services and billing accounts. Store deployment steps where another engineer can find them.

For a planned departure, ask the outgoing person to document open work and demonstrate the tasks someone else must take over. Have the recipient try the steps before the last working day.

For an abrupt departure, name an interim owner immediately. Review upcoming releases and customer promises against the work your remaining team can support. Do not make delivery depend on a replacement who has not accepted an offer.

A replacement search should begin with a corrected role description. Reusing the old description without reviewing the failure can send the next candidate into the same problem.

Decide what work can wait

Ask the manager to sort open work by the consequence of delay. Keep payroll approvals, production support, and customer deadlines with named owners. Move work that can wait out of the interim owner's queue.

For example, if the departing engineer owns a release, appoint someone to decide whether it should proceed. Record the release status and rollback plan. The replacement candidate should not become the assumed release owner before accepting the job.

Tell affected colleagues where to send requests during the gap. Keep that message about work coverage. Share employment details only with people who need them to carry out the exit.

What do the rules and working hours mean for Latin American exits?

Plan employment costs and handover hours separately. Local rules shape the exit calculation. Shared working hours shape when people can meet, transfer work, and resolve questions.

Review accrued benefits before approving the exit bill

Ask the legal employer for an itemized calculation tied to the employee's circumstances. The following statutory benefits belong in that review. They are not a complete termination formula.

Mexico's Federal Labor Law sets an annual aguinaldo minimum of 15 days of salary. It also sets a vacation premium of at least 25%. Keep these benefit lines separate from any dismissal payment in the employer's calculation. Mexico Federal Labor Law, articles 80 and 87.

Colombia's prima de servicios equals 30 days of salary per year, paid in two installments. The labor code also describes cesantías as one month's salary per year of service, proportional for part of a year. Ask the employer to reconcile amounts already paid or deposited before approving the final balance. Article 306, article 249.

Argentina's SAC has installments due on June 30 and December 18. Ask the employer to explain the treatment of the employee's departure date and pay history. Do not use the next scheduled installment date as your assumed exit payment date. Argentina employment contract law, articles 121–122.

Brazil's thirteenth salary law sets an accrual basis of one twelfth of December remuneration per month of service. Have the employer apply the relevant exit rules to the actual employment record. Brazil Lei 4.090.

Costa Rica's labor ministry describes the annual aguinaldo benefit as equivalent to a month's salary. Request the employer's calculation rather than treating the last ordinary paycheck as the entire balance. Costa Rica Ministry of Labor.

Give the employer the actual start date, pay history, and proposed departure date. Ask it to identify the assumptions behind each amount. If the date changes, request an updated calculation before finance approves payment.

Keep the employee payment calculation separate from the provider's closing invoice. Ask how any deposit, prepaid service charge, or credit will be reconciled. This lets finance check what the worker receives and what the supplier charges without mixing the two.

Schedule handovers by city and working hours

Mexico City and San José, Costa Rica, use UTC-6 without daylight saving time. Bogotá uses UTC-5 year-round. Buenos Aires and São Paulo use UTC-3 without seasonal clock changes. Tijuana follows a different schedule from Mexico City and observes daylight saving time. IANA North America data, IANA South America data.

Use the worker's city and agreed schedule in the handover plan. "US overlap" does not tell you whether the outgoing person can join your afternoon deployment review.

Check the calendar dates of each session. A US clock change can shift the meeting time for a Latin American colleague whose local clock stays fixed. Send invitations with named time zones and confirm attendance before relying on a live walkthrough.

How do hiring models change replacement and offboarding duties?

Nearshore and offshore describe location relative to the buyer. They do not tell you who employs the person, owns the search, or pays an exit charge.

For a US team comparing offshore vs nearshore outsourcing, start with the contract model. Then test the working hours against the handover you need.

Use this table to mark up the proposed agreement. Put a person's name beside each task after choosing a model.

Separate a search promise from a start date

A shortlist, accepted offer, and first day worked are different milestones. Ask the provider to define the event that starts each clock.

For example, a search might begin when you submit a replacement request or after the provider approves it. Those terms can produce different schedules. Confirm what happens while the request is under review and whether you must keep paying service fees.

Ask whether a changed role still qualifies for replacement support. Moving from maintenance work to system design changes the candidate profile. Record the revised scope and any price change before interviews begin.

Set an internal decision deadline for candidate feedback. Name a backup interviewer when the hiring manager is away. Otherwise, your own approval process can leave a qualified candidate waiting while the interim team carries the vacancy.

Compare the actual handover method

Nearshore working hours can make live pairing easier when the schedules overlap. For a team with little shared time, plan written handovers and recorded demonstrations, subject to company policy.

Have the recipient test the handover in either model. Watching a deployment does not show that the next engineer can run it. Ask them to perform the task in a suitable environment and record any blockers.

For an asynchronous handover, use a question log with links to the relevant task or system. Agree on when the outgoing worker will review it during paid working hours. Assign any unanswered item to the interim owner before the departure.

When comparing offshore and nearshore arrangements, review the hours available for this work. Geographic labels alone do not establish a workable transition.

Compare hiring models with Opus. This site is an Opus-owned reference; recommendations are editorial.

What should you ask a provider before signing or requesting a replacement?

Ask for written answers that can become tasks in your exit record. A sales call can explain the process, but your team needs terms it can use when the account manager is away.

Confirm what triggers replacement support

Ask which departures qualify. Cover resignation, performance concerns, and a role you no longer need. Ask whether a change in scope creates a new search.

Confirm any request deadline and the documents needed to open the case. Ask who decides eligibility and how you escalate a disagreement. Keep the approved role description and signed guarantee together.

Request a definition of a completed replacement. Does the obligation end when candidates arrive, when you choose someone, or when that person starts? Ask what happens if your chosen candidate withdraws.

Ask what happens if you pause hiring or decide to close the role. Confirm whether you can resume the search later and which cancellation terms apply. Have the provider distinguish replacement support from any refund or account credit.

Get the full cost picture

Request a sample closing statement with separate lines for:

• Pay through the approved end date.
• Applicable notice or termination payments.
• Accrued benefits and approved expenses.
• Provider fees through the contract's billing end date.
• Equipment shipping or recovery.
• Any period when outgoing and incoming hires are both paid.

Ask which amounts are estimates and which are fixed. Have finance record the currency, payment date, and person authorized to approve changes.

Keep search fees separate from employment costs. A waived recruiting charge does not answer whether you will pay for a handover period or an accrued benefit.

Also ask when billing stops if you decline every proposed replacement. Your hiring decision and the service agreement's cancellation terms need to work together.

Agree on the exit meeting and access cutoff

Have the legal employer approve who delivers the employment message and what they say. Coordinate the meeting with your security owner.

Record the access cutoff as a timestamp with a time zone. Include company email, code repositories, cloud accounts, customer systems, and personal tokens used for company work.

Check access outside single sign-on. Review shared credentials and integrations that run under the departing person's account. Transfer ownership and rotate secrets where appropriate. Do not place passwords in a handover document.

Preserve required records before deleting accounts or wiping devices. Have HR and security agree on retention, evidence handling, and permitted device actions. Record who completed each step.

For equipment, record the asset identifier and who owns it. Agree on a return method, shipping payer, and receipt process. Keep device recovery separate from account access so an overdue shipment does not leave an account active.

Give the departing worker a contact for return questions. Ask the employer to review any proposed deduction or payment condition before anyone communicates it.

Require a usable handover

Ask for links to open tickets, pull requests, and decisions that have not yet been documented. Assign each unfinished item to a named recipient.

For engineering work, include deployment and rollback steps, known faults, and production responsibilities. For finance or operations, include approval queues, deadlines, and recurring tasks.

Keep the acceptance check practical. The recipient should be able to locate the work, access the required system, and complete the next task. Record unresolved questions with an owner.

If the outgoing worker cannot participate, build the handover from company records. Do not leave the vacancy idle while waiting for a response that may never arrive.

Close the case with evidence

Ask the provider for the agreed employment documents and payment confirmation through an approved channel. Have your own team confirm access removal and equipment status.

Reconcile the final invoice against the approved estimate. Resolve differences while the case owner still has the details.

Close the replacement search separately. The manager should confirm that the incoming hire has the right access and understands the revised role. Keep any remaining payroll or equipment issue open under its own owner.

Set a review with the manager after the replacement has completed a real assignment. Check the specific issue that prompted the change. If unclear ownership caused missed work before, confirm that the new hire knows who approves decisions and where to raise blockers.

Where does Opus fit in this plan?

Opus states: "Every placement carries a lifetime replacement guarantee with no cap and no time limit." The guarantee is relevant when comparing how long replacement support remains available. Opus replacement guarantee.

Opus reports 97% one-year retention. Treat that as a company-reported figure when assessing the service. Ask how the cohort is defined and how departures are counted before using it in your own staffing forecast. Opus replacement guarantee.

A lifetime guarantee answers the duration question. Your agreement should also answer who handles the exit, what costs apply, and how the replacement search proceeds. Ask for those details before the first hire starts.

Keep the provider discussion tied to your role:

• Share the work the person must own and the hours needed for handover.
• Ask how to submit a replacement request and who will manage it.
• Request an itemized explanation of any exit costs.
• Confirm the milestones for candidates, offer acceptance, and the first day worked.

The client chooses the finalist and manages day-to-day work. Keep that responsibility visible during a replacement. The hiring manager should update the role and assess candidates against the work that caused trouble.

Before approving the next hire, review the old handover gaps. If production access depended on one person, assign a backup owner. If the role changed without a written update, fix the scope. Give the incoming hire a usable starting point.

Compare hiring models with Opus.

<!-- Not saved to disk: this session permits read-only filesystem access. Individual exit calculations and contract terms require review by the legal employer. -->