staff augmentation services replacement and offboarding playbook

# Staff augmentation services replacement and offboarding playbook

What should a busy buyer agree before signing?

Ask for a written exit plan alongside the hiring proposal. It should tell your manager what to do when a hire resigns, misses agreed requirements, or leaves after a project ends.

Separate the replacement request from the employment exit. A new search needs a role owner and acceptance criteria. The departure needs an authorized employer contact, a payment calculation, and a controlled handover. Track both in the same plan, with separate approvals.

Before signing, complete this table with the provider. Replace each role with a person's name once the hire starts.

These are proposed assignments. Confirm them against the actual contract and employing arrangement.

Define the trigger before a performance dispute

Write down what successful work looks like at the start. For an engineer, that might mean completing an agreed task, responding during agreed hours, and following review rules. Use criteria the person can understand and the manager can check.

When performance slips, record the expected result and what happened. Include the task, date, feedback, and support given. Avoid vague labels such as "poor fit" when the issue is a missed requirement.

Check whether your own setup caused the failure. A person waiting for repository access cannot complete a code change. A manager who changes priorities without updating the task has not set a stable target.

If a replacement is still needed, give the provider the corrected role requirements. Otherwise, the next search may repeat the same mismatch.

Keep delivery moving during the search

Assign an internal owner to each open task before the person leaves. Decide what can pause and what needs coverage. Tell affected teams which deadlines need a new estimate.

For example, if the departing engineer owns a release, name someone who can review and deploy it. Have that person walk through the release steps while questions can still be answered. A document alone does not prove the handover worked.

Keep the replacement start date separate from the date the team expects normal output. Plan for access setup and review time after the new person arrives.

Prepare for a departure without overlap

Build a fallback plan for an exit that leaves no time for live training. Ask the internal owner to gather current tickets and locate the last working build. Review upcoming deadlines before assigning new work.

Start with tasks that could stop the team: a release awaiting approval, a customer issue, or an automated job with a single owner. For each, record who can take over and what they need.

Do not leave the departed person's account active so someone else can use it. Have IT transfer approved access and ownership to named users. If a task cannot continue safely, pause it and tell the affected team why.

What do the rules say about exit costs?

Build the exit estimate from the employment arrangement and the person's circumstances. Ask the employing entity to show earned pay, benefits, notice obligations, and any termination payment as separate lines.

The country examples below identify items to check. They are not complete settlement formulas. Have the employer confirm which provisions apply before anyone promises an amount or a departure date.

Mexico: check the dismissal basis and earned benefits

Mexico's annual aguinaldo is at least 15 days of salary, payable before December 20. The labor law also sets a vacation premium of at least 25%. Ask the employer how the relevant accrued amounts enter the final settlement. Ley Federal del Trabajo, Articles 80 and 87.

For dismissal exposure, Article 48 includes a three-month salary indemnity remedy. Article 50 II specifies 20 days of salary per year of service for indefinite employment in its applicable indemnity framework. Have the employer explain the legal basis before combining amounts in a budget. Ley Federal del Trabajo, Articles 48 and 50.

Ask for the calculation and approval before issuing an exit instruction. A provider's replacement promise does not tell you which employment obligations apply.

Colombia: separate prima de servicios and cesantías

Colombia's prima de servicios corresponds to 30 days of salary per year, recognized in two payments. The statutory schedule places half by June 30 and the other half within the first 20 days of December. Código Sustantivo del Trabajo, Article 306.

Article 249 describes cesantías as one month's salary per year of service, proportionally for a fraction of a year. Ask for a reconciliation of amounts already paid or deposited and any balance due. Código Sustantivo del Trabajo, Article 249.

Keep these entries distinct from any separate dismissal payment. Request a written explanation for each line rather than accepting a single unexplained exit fee.

Argentina: reconcile sueldo anual complementario

Argentina's sueldo anual complementario, or SAC, has installments due June 30 and December 18. Article 122 bases each semester's payment on 50% of the highest monthly remuneration earned during that semester. Ley de Contrato de Trabajo, Articles 121–122.

Ask the employer to show the applicable SAC treatment in the exit calculation. Have it identify the pay records used and reconcile prior payments. Review notice and termination obligations separately.

Brazil: include the 13th salary review

Brazil's 13th salary, the gratificação de Natal, is addressed in Lei 4.090. The law provides for one-twelfth of December remuneration per month of service in the corresponding year. A fraction of at least 15 days counts as a full month under that provision. Lei 4.090, Article 1.

Ask the employer to explain how the departure date and reason affect the settlement. Request the remaining payroll and termination items separately. Do not treat the annual bonus calculation as the entire exit bill.

Costa Rica: account for aguinaldo

Costa Rica's aguinaldo includes an annual benefit equivalent to one month's salary, as described in the labor ministry's discussion of Ley 2412. Ask the employer to show the applicable earnings and prior payments when preparing the final account. Ministerio de Trabajo y Seguridad Social.

For every country, ask who funds each amount and when. Your commercial invoice and the worker's final payment should have separate approvals and records.

Review the estimate before approving a date

Give finance an estimate that identifies the currency, payment recipient, and due date for each charge. Ask the employer to distinguish confirmed amounts from amounts that depend on the departure date.

If the date changes, request an updated calculation. Record who approved the change and whether it affects the service invoice. Keep the original estimate so finance can explain the difference when the final bill arrives.

How do nearshore hiring models change the exit plan?

Compare models by who employs the person, who directs the work, and who must provide the replacement. Put those answers in the contract rather than relying on the model's label.

Use the table as a contract review agenda. A label does not establish the terms of a particular agreement.

The managed service vs staff augmentation question becomes concrete when someone leaves. Ask whether you bought an individual's time under your direction or a supplier-owned delivery commitment. Then identify who must cover unfinished work.

With an IT staff augmentation service, give your engineering lead ownership of the technical handover. Ask the provider to name the person handling the employment process. Record how those contacts will coordinate without sharing unnecessary employee information.

Set handover hours using actual locations

Book handover sessions in named time zones. Mexico City and San José, Costa Rica, use UTC-6 without daylight saving time. Tijuana follows a different schedule with daylight saving changes. IANA North America time zone data.

Bogotá uses UTC-5 without daylight saving time. Buenos Aires and São Paulo use UTC-3 without seasonal clock changes. IANA South America time zone data.

Write the meeting time and both locations into the plan. Check the calendar conversion for the actual date, especially if the transition crosses a US clock change. Agree paid overlap hours rather than assuming everyone can extend their day.

What should you ask a provider before an exit?

Ask the provider to walk through a resignation and a performance-based replacement. Use the same role and contract in both examples. Require specific answers about who acts, what gets paid, and when.

Get the replacement terms in writing

Use these questions during contract review:

• Which events qualify for a replacement search?
• How must we submit a request, and who confirms receipt?
• Are there claim deadlines or conditions tied to invoice payment?
• What happens if the role requirements change?
• Is there a deadline for presenting candidates or starting the replacement?
• Who pays for overlap between the departing hire and the replacement?
• What remedy applies if no proposed candidate meets the agreed requirements?
• What happens to the guarantee if we end the service agreement?

Keep search milestones distinct. A shortlist date, an accepted offer, and a first working day answer different planning questions. Ask the provider to define each milestone it commits to.

Agree who tells the worker and the team

Have the employing entity confirm who will speak with the worker and when. Give that contact the approved facts and keep performance records within the group handling the decision.

Prepare a separate team message about work ownership. It should identify the new contact, any changed deadline, and where to send questions. Avoid sharing personal details or speculating about the reason for departure.

Coordinate customer notices where the person held an external role. Confirm who will receive replies sent to the former contact, subject to company policy. Test the routing before declaring the handover complete.

Build a handover another person can use

Require links to work in company-controlled systems. The receiving owner should check that the files open and the instructions work.

For an engineering role, the handover should cover:

• Open pull requests and the next decision needed on each.
• Deployment and rollback instructions.
• Known defects, incident follow-ups, and unresolved risks.
• Service accounts and automation owned by the departing person.
• Current tickets, design decisions, and relevant test results.
• External contacts who need a new company contact.

Do not put passwords in the handover document. Transfer ownership through approved tools. Have security review credentials the person could access and decide what to revoke or rotate.

Ask the receiving owner to perform a real task from the notes. That might be running the test suite or deploying to a test environment. Record any failed step while the outgoing person can still clarify it.

Coordinate access removal and equipment return

Create an access inventory before the last working day. Include identity accounts, repositories, cloud consoles, shared documents, customer systems, and direct application logins.

Set a cutoff time with the employer and security owner. For a routine departure, coordinate it with the final handover. If there is suspected misuse, use the incident process to decide immediate restrictions and evidence preservation.

At the cutoff, disable the relevant accounts and revoke active sessions or credentials as required. Confirm that scheduled jobs no longer depend on the departing person's login. Transfer ownership before deleting accounts or files.

For equipment, record the asset identifier, return method, recipient, and shipping responsibility. Track receipt. Ask IT to confirm the approved data-preservation and device-reset steps before a device is wiped.

Close the financial and delivery records

Request a final account that separates employee payments from provider charges. Check the service end date, any notice charge, overlap costs, approved expenses, and credits against the contract.

Keep proof of required payments in the appropriate restricted system. The engineering team needs confirmation that the exit is complete, not access to the person's payroll records.

Close the handover only when the receiving owner accepts it. Close the replacement task after the new hire completes an agreed piece of work. If that task fails, record the cause before requesting another search.

Test the replacement against the revised role

Choose an initial task that uses the skills the role actually needs. For a backend engineer, that could be a small code change with tests and a reviewed pull request. Define the expected result before work starts.

Assign a reviewer who has time to answer questions. Track blocked access separately from work quality so the assessment does not repeat the first hire's setup problems.

At the review, record whether the task met the agreed criteria and what support is still needed. Share specific feedback with the replacement. If the role has changed again, update its requirements before judging the result.

Where does Opus fit in this decision?

Opus states: "Every placement carries a lifetime replacement guarantee with no cap and no time limit." Opus reports 97% one-year retention. Opus lifetime replacement guarantee.

The guarantee gives you a specific term to discuss during contract review. Ask how to submit a replacement request, who owns the search, and how billing works during the transition. Get those operating details into the agreement.

The retention figure describes a company-reported result. It does not predict whether a particular hire will meet your role requirements. Ask how retention is defined and which placements the measure includes before using it in a vendor scorecard.

Talk to Opus about a role.

Bring a concrete exit scenario to the call

Use the role you intend to hire for. Describe the work, the manager, and the systems the person will need. Then ask what happens if the hire resigns during an active release or fails an agreed performance requirement.

Request a written response covering the search trigger, handover contact, and expected milestones. Ask who prepares the employment exit calculation and which costs require your approval.

Keep the replacement promise separate from your own readiness to receive the next hire. Assign an internal reviewer who can assess candidates promptly. Prepare access requests and an initial task before the replacement starts.

If the first hire struggled because the role was poorly scoped, revise it before approving another search. State what changed and why. Give the replacement a task that tests the revised requirement.

Before signing, you should be able to name the person who accepts the handover, the contact who approves the exit, and the reviewer who accepts the replacement's work. Put those names beside the contract terms and keep the plan with the account record.

Talk to Opus about a role.

<!-- Not saved to disk: this workspace is read-only. Individual exit costs still require employer review. -->