staff augmentation replacement and offboarding playbook

# staff augmentation replacement and offboarding playbook

What should a busy buyer agree before a hire leaves?

Agree who can request a replacement, who handles the worker's employment, and when your bill stops. Then assign the handover and access removal to people on your team. A search can restart while those tasks remain unfinished.

Use a practical staff augmentation definition: an outside professional joins your team and works under your day-to-day direction. That describes how work gets done. Check the contract separately to establish who employs the person and who handles an exit.

Start the playbook before the hire receives production access. Record the provider's escalation contact and the manager who can approve a change. Give IT and finance access to the parts they must act on.

Decide whether you need a replacement

Write down why the assignment may end. A resignation, an unmet role requirement, a budget cut, and a security incident need different responses.

For a performance concern, collect examples of expected work and actual results. Include the feedback given and any blockers the team owns. A missed release caused by withheld credentials calls for a different response than repeated errors after clear feedback.

Give the provider a factual account. Link to the agreed task, explain what happened, and describe the effect on delivery. Avoid labels such as "poor fit" without examples. Ask the employer how feedback and any proposed improvement period should be handled.

If the work has disappeared, ask about ending the assignment. Do not open a replacement search simply because the contract includes one. If the role has changed, send a revised role description before anyone starts screening.

For a suspected security incident, involve your incident lead immediately. Let that person direct containment and evidence preservation while the employer handles the employment process.

Give each exit task an owner

Use a shared record with an owner, deadline, and completion evidence for each task.

Do not make the incoming hire the only person who can receive the handover. Their start date may fall after the outgoing person's last day. Your internal owner should be able to keep the work moving.

Record separate dates for the last day on the assignment, access cutoff, employment end, and billing stop. Ask the employer and provider to confirm each date. Avoid a single field labeled "end date" that leaves everyone to interpret it.

Prepare the team for a gap

Decide which work can wait if the replacement starts later than planned. Assign someone to watch alerts, answer customer questions, and approve urgent changes where those duties apply.

Tell stakeholders which commitments have changed. Keep the message focused on coverage and ownership. Limit personal employment details to the people who need them.

If nobody can safely maintain an unfinished system, pause that work and record its current state. A named owner should decide when it can resume.

What do the numbers tell you about nearshore exit costs?

A replacement promise and a final-pay calculation answer different questions. Use the promise to assess the search remedy. Use the employment terms and country rules to review the departure costs.

Opus reports 97% one-year retention. This site is an Opus-owned reference; recommendations are editorial. Treat that figure as a company-reported measure when reviewing the replacement guarantee. Ask for the cohort, measurement dates, and treatment of client-requested exits before comparing it with another measure.

For your own team, track the time between a replacement request and an accepted candidate. Track the first working day separately. A signed offer does not put someone in the next sprint.

Also record why each assignment ended. Separate resignations from performance changes and canceled roles. Otherwise, a change in hiring plans can look like a failed placement in your own reporting.

Check the country-specific payment items

Ask the legal employer for an itemized exit estimate before approving the departure schedule. The following benefit rules identify items to review. They are not a formula for every worker's final payment.

Colombia also has cesantías. Article 249 describes a month's salary for each year of service, with a proportional amount for a partial year. Ask the employer to reconcile the worker's position under that provision, including amounts already handled through payroll or deposits.

For Mexico, have the employer explain whether the dismissal provisions apply to the specific case. The LFT contains distinct provisions in articles 48 and 50. Do not add figures from separate articles into a standard exit charge without a case-specific calculation.

Ask payroll to show the service dates and pay basis used for each item. Confirm which benefits have already been paid or funded. Have the employer explain adjustments before finance treats the estimate as an approved invoice.

Separate invoices from delivery costs

Build the exit estimate from named items: service charges through the agreed stop date, employment costs, equipment return, and any approved overlap. Ask finance to identify deposits or credits that should reduce the final balance.

Keep internal delivery costs separate. These include your engineer's handover time and the work postponed while the role is vacant. They belong in the hiring decision even when they never appear on a provider invoice.

Ask for a written estimate with assumptions. If the departure date changes, request an updated estimate before approving the final bill.

For each charge, record who owes it under the agreement and who will pay it first. A provider's payroll duty and your company's reimbursement duty may be separate contract questions. Resolve both before authorizing the exit.

How do the hiring models change replacement and offboarding?

Compare models by responsibility. The label on a proposal does not tell you who must find the next person or recover a laptop.

For a direct placement, read the replacement clause alongside the employment agreement. A recruiting fee remedy does not tell your managers how to conduct the employee's exit.

For staff augmentation, define the provider's search duties and your team's operating duties. Your engineering manager should own acceptance of the handover. Ask the provider to identify the person who owns employment steps.

For an EOR arrangement, confirm whether a replacement search is included at all. Assign it explicitly if your talent team or a separate recruiting agency must do it. Do not discover the gap after the worker leaves.

For outsourced work, review the delivery agreement before requesting a named replacement. Your practical need may be a qualified person maintaining the service, with agreed documentation and acceptance criteria.

Check whether ending one assignment also changes the wider agreement. Ask about minimum commitments, remaining team members, and access to shared work. Keep the scope of your written request precise so that removing one person does not leave the service end date ambiguous.

Test the model against a departure scenario

Use the same hypothetical case with each provider: the engineer resigns while an unfinished migration is due for release.

Ask who receives notice and who confirms the last working day. Then ask who takes ownership of the migration, who searches for the next engineer, and what you pay during the gap.

Request the answer in writing. Include what happens if you reject the proposed candidates or pause hiring. Those details make the comparison useful to procurement and the engineering lead.

Repeat the exercise with a client-requested departure. Ask whether the process changes when the person has met the role requirements but your budget has changed. Record any difference in eligibility or charges beside the resignation case.

Talk to Opus about a role.

What should you ask a provider before signing?

Ask for terms your team can use without reconstructing a sales call. Put the replacement clause, exit process, and billing rules in the agreement or an attached schedule.

Confirm the replacement remedy

Ask these questions together so the answers describe a complete process:

• What events qualify for a replacement?
• How do we submit a request, and when must we submit it?
• Does coverage change if the worker resigns or we end the assignment?
• What happens if the replacement also leaves?
• Can we revise the role, location, or seniority?
• What costs continue while the position is vacant?
• What happens if no candidate meets the agreed requirements?

Ask for a named escalation contact and a response commitment. Separate the date the provider acknowledges a request from the date it expects to present candidates.

Set candidate acceptance criteria before the search begins. For an engineering role, specify the work the person must own and the evidence you want from interviews. Avoid repeating a vague requirement such as "strong senior engineer."

Confirm who can approve candidates while the usual hiring manager is away. Reserve interview time and give feedback against the agreed criteria. Record provider delays separately from time spent waiting for your team's decision.

Agree the handover before access changes

Require the outgoing person to put working documents in company-controlled locations. Assign an internal reviewer to check them while questions can still be answered.

For engineering work, request:

• Open tickets and code branches, with the next step for each.
• Local setup instructions and a tested path to run the application.
• Release and rollback procedures.
• Known defects, operational risks, and pending decisions.
• Service ownership, including scheduled jobs and integration accounts.
• Links to design notes and relevant approvals.

Have the receiving engineer use the instructions. A document marked complete is weaker evidence than a colleague successfully running the project.

Ask the reviewer to record any failed step and its owner. If the departing person cannot finish a task, capture the last known state and remaining work. Avoid marking an incomplete migration as transferred simply because its repository link was shared.

For customer-facing work, transfer open commitments and meeting ownership. For finance work, transfer reconciliation status and approval responsibilities. Tailor the checklist to what the worker actually controls.

If overlap is possible, agree its scope and cost before scheduling it. Use the overlap for specific demonstrations and unresolved questions. Avoid paying for two people to attend meetings without a handover plan.

Set an exact access cutoff

Write the cutoff with a date, time, and time zone. Coordinate it with the employer's communication plan and your security owner's decision.

Inventory the worker's access before the final day. Include company login accounts, code repositories, cloud consoles, customer tools, shared vaults, and devices. Check service accounts or jobs the person administers.

Transfer ownership before disabling an account that runs scheduled work. Revoke active sessions and individual tokens where needed. Rotate shared credentials the person could access, using a sequence that preserves required services.

Check tools with direct logins as well as those behind your company sign-in system. Ask application owners to confirm removal of guest invitations and external sharing permissions where applicable.

Give the replacement a separate account with approved permissions. Do not transfer the former worker's login to preserve convenience or history.

Preserve records required by your retention rules or legal hold. Ask IT to confirm what was disabled, what was transferred, and what remains open. Keep that evidence with the exit record.

Close equipment and billing separately

Ask who owns the laptop, who arranges shipping, and where the return receipt will be stored. Agree how personal information and company data will be handled before any device wipe.

Record the asset identifier and expected return date. If shipping is delayed, assign someone to track it. Keep the asset task open until receipt or another approved resolution is documented.

Request the final invoice by line item. Reconcile the billed period against the agreed stop date, then check overlap charges and credits. Route disputed charges to a named owner instead of leaving the whole exit case untracked.

Review the replacement's onboarding plan before calling the staffing gap resolved. Confirm the first working day, manager availability, access requests, and initial work. A new hire needs a usable starting point even when the search was urgent.

After the handover, review which knowledge existed only in the departing person's head. Turn those gaps into specific documentation tasks. Assign them to the team that owns the work so the next exit does not repeat the same scramble.

How does Opus fit this playbook?

Opus states: "Every placement carries a lifetime replacement guarantee with no cap and no time limit." Review the guarantee alongside the agreement you will sign.

Use that promise to start a concrete discussion about your role. Ask how to submit a replacement request, who owns the search, and how a changed role affects the process. Request the milestones in writing.

Opus describes its pricing this way: "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." See Opus pricing.

Published dollar rates: Not published. Request a written quote for the role and a separate explanation of charges during notice, vacancy, and any overlap.

The client chooses the finalist and manages day-to-day work. Build your own handover acceptance into that management role. Name the engineer or functional lead who will check the departing person's work and prepare the replacement's first assignment.

Before signing, bring the role description and your departure scenario to the discussion. Ask Opus to walk through the search request, employment coordination, and billing stop date. Have procurement record the agreed terms where finance and the hiring manager can find them.

Talk to Opus about a role.

<!-- Not saved to disk: filesystem access is read-only. Individual exit calculations require review by the legal employer. -->