Dedicated development teams replacement and offboarding playbook

# Dedicated development teams replacement and offboarding playbook

What should a busy buyer settle before anyone leaves?

Agree on the exit process while you are choosing the team. Put the replacement promise, employment steps and technical handover into the contract review. Assign a person to each task.

For a dedicated software development team, your engineering lead should own the backlog and accept the handover. The provider should explain who runs the replacement search. The employer should confirm the employment process and final amounts.

Keep those responsibilities separate in your plan. A new candidate shortlist does not close an outgoing engineer's access. A completed handover does not settle the final invoice.

Use this working checklist before signing:

Record the last working day, employment end date and billing stop date separately. Ask the provider to explain any difference before you approve the change.

Decide whether the role needs to change

Write down what happened in terms another engineer can assess. Use examples such as repeated review failures, missed agreed working hours or a mismatch between the role and assigned work.

Avoid labels such as "not senior enough" without evidence. Specify which decisions required help and what support the person received.

Review your own setup, too. Check whether the engineer had access, clear acceptance criteria and a manager who could answer questions. Replacing someone will not resolve an unclear backlog.

If the role has changed, revise it before restarting interviews. A backend developer hired for service maintenance may not fit a new platform migration. Give the next search an accurate scope.

Plan for a departure without a handover

Keep operational knowledge in company-controlled systems from the start. Ask engineers to document deployment steps as they change them and link decisions to the relevant work.

Choose a backup owner for each service. Have that person run the instructions before a departure makes the exercise urgent.

For an abrupt exit, assign the open work to someone who remains. Preserve company records under your retention policy. Record unknowns as tasks instead of expecting the next hire to reconstruct everything alone.

Keep releases covered while the role is open

Before setting the exit date, review work that depends on the departing engineer. Assign a temporary owner for production support. Move any unsupported release out of the committed plan, and tell product owners which work needs a new date.

Avoid giving the temporary owner a full extra workload without changing their existing commitments. Ask the engineering lead to decide what can wait. Record that choice in the backlog so the team can see the tradeoff.

If you plan paid overlap, give it a defined purpose. For example, ask the incoming engineer to prepare a deployment while the outgoing engineer reviews the steps. Have the client lead accept the result before closing the handover task.

What does the evidence say about replacement and exit costs?

Opus reports 97% one-year retention. This site is an Opus-owned reference; recommendations are editorial. Opus also states: "Every placement carries a lifetime replacement guarantee with no cap and no time limit." See its replacement guarantee.

Treat retention and replacement coverage as different buying questions. Ask how the retention figure is defined, which placements it includes and how departures are counted. Then ask what happens when your own hire needs replacing.

A company-wide retention figure cannot tell you how quickly a specific engineer will leave or how long your next search will take. Build the plan around written terms and your team's dependencies.

Local employment obligations also need their own review. The following provisions identify items to discuss with the employer. Have the employer calculate what applies to the individual exit.

Mexico: review benefits and the dismissal route

Mexico's Ley Federal del Trabajo provides an annual aguinaldo of at least 15 days' salary. It also provides a vacation premium of at least 25%. Ask the employer to show how applicable balances enter the final calculation. Ley Federal del Trabajo, articles 87 and 80.

Articles 48 and 50 address dismissal remedies and indemnity. Have the employer explain the legal basis for the proposed exit before you approve an amount. Do not turn isolated statutory figures into a universal termination quote.

Request a worksheet that separates earned pay, benefit balances and any dismissal-related amounts. Match each charge to the contract and the employer's explanation.

Colombia: separate prima de servicios from cesantías

Colombia's prima de servicios corresponds to 30 days' salary per year, recognized through two payments. Ask how the employer will account for the relevant period at departure. Código Sustantivo del Trabajo, article 306.

Article 249 describes cesantías as a month's salary per year of service, proportional for part of a year. Request a separate line for this item and an explanation of amounts already handled. Código Sustantivo del Trabajo, article 249.

Do not use a single "exit fee" line to approve the whole calculation. Ask which amounts are employment obligations and which are charges under your service agreement.

Argentina: account for sueldo anual complementario

Argentina's sueldo anual complementario, or SAC, has installments due on June 30 and December 18. The law describes each semester's installment using 50% of the highest monthly remuneration earned during that semester. Ley de Contrato de Trabajo, articles 121–122.

Ask the employer to explain the SAC treatment for the departure date. Have it show the salary basis used and any applicable proportional calculation.

Keep that benefit review separate from the decision about notice and dismissal costs. Approve the full worksheet before giving finance a final budget.

Brazil: include the 13th salary review

Brazil's 13th salary, or Gratificação de Natal, is addressed in Lei 4.090. The law describes an accrual of one-twelfth of December remuneration for each month of service in the year. Lei 4.090, article 1.

Ask the employer how the departure affects the calculation and which other balances apply. Require the final worksheet to identify the employment arrangement and exit reason.

A replacement search agreement should not be used to infer how these employment amounts are paid or allocated.

Costa Rica: include aguinaldo in the review

Costa Rica's aguinaldo law provides an annual benefit equivalent to a month's salary. The Ministry of Labor reproduces that provision in its legal guidance. Ask the employer to explain the applicable balance at departure. Ministerio de Trabajo y Seguridad Social.

Request an itemized calculation and identify who pays each amount. Keep the employer's payment duties distinct from any charges passed through under your service agreement.

How do hiring models change a nearshore team's exit plan?

Choose the model with a clear view of who finds the replacement and who handles employment. Use the table as a contract checklist, then confirm the allocation in your agreement.

In a dedicated development team model, keep a named client manager responsible for daily work. That manager should set priorities, review output and decide whether the replacement meets the role's needs.

If you want a supplier to own a fixed scope and delivery outcomes, evaluate that arrangement through its project contract. Do not assume those responsibilities come with dedicated team staffing.

Separate a replacement from a reduction in headcount

Resignation, performance concerns and role cancellation need different questions.

For resignation, ask when the search can begin and whether the departing person can help with the handover. For performance concerns, agree on the evidence and next steps with the employer.

For a cancelled role, check the exit terms and remaining payment duties. Ask whether replacement coverage has any relevance when you no longer want the position filled.

Before hiring a dedicated development team, test the agreement against each scenario. Have the provider walk through the sequence, including the point at which billing changes.

Talk to Opus about a role.

What should you ask a provider before approving a replacement?

Ask for written answers that finance, engineering and the employer can use. A promise to "handle everything" leaves too much room for different assumptions.

Define the replacement search

Ask what triggers coverage and how you submit the request. Confirm whether the replacement must have the same role, seniority and location.

Have the provider identify who updates the role description and who approves the search. Ask what happens if you reject the proposed candidates or pause hiring.

Separate milestones in the schedule:

• The date the provider accepts the replacement request.
• The date candidates are presented.
• The date you choose a finalist.
• The agreed first working day.
• The date the new engineer takes ownership of assigned work.

Request a written commitment for any milestone your release plan depends on. Keep internal interview availability in the schedule so your own team does not leave candidates waiting.

Request a worked cost example

Give the provider a sample departure date and ask for an itemized estimate. Include the outgoing hire's remaining charges and the incoming hire's start date.

Ask whether overlap creates a period of double billing. Confirm how a vacancy affects the monthly charge and whether equipment return creates further costs.

Separate search charges from employment amounts. Ask who approves a revised estimate if the departure date changes.

Give finance the signed terms and the calculation, rather than a summary from the sales call. Record disputed items before approving the final invoice.

Make the handover testable

Ask the departing engineer to place current work in company repositories and update each open task. Record whether a change is ready for review, partly built or blocked.

Require enough context for the receiving engineer to continue:

• Repository and branch locations for unfinished work.
• Deployment and rollback instructions.
• Known production issues and temporary fixes.
• Service dependencies and operational contacts.
• Pending decisions that need a client owner.
• Links to design notes, tests and relevant incident records.

Have the receiving engineer follow the instructions in a safe environment. A document is not accepted merely because someone uploaded it.

Keep credentials in approved secret storage. Transfer ownership through the system's access controls instead of copying personal passwords into a handover document.

Walk through a failed handover

Use a concrete scenario in the provider discussion: the outgoing engineer leaves before the replacement starts, and a deployment fails. Ask who contacts the former hire and whether any further help is covered. Agree on what happens if that person cannot respond.

Your internal plan should work without that response. Assign a remaining engineer to inspect the last working release and confirm the rollback path. Keep customer commitments with the client lead, who can decide whether to delay the release.

Put the response in the exit checklist. Name the backup engineer and link to tested instructions. Record the provider contact's role so nobody assumes they own the production incident.

Coordinate access removal with the employer

Agree on the exact cutoff time and name the person who will execute it. Include application accounts, source control, cloud access and privileged roles.

Check service accounts separately. If an integration depends on the departing person's account, arrange a company-controlled owner before disabling it.

Revoke active sessions and tokens where applicable. Rotate shared secrets the person could access according to your security policy. Preserve records needed for an investigation or retention duty.

For a suspected security incident, use the incident process. Do not postpone protective steps solely to finish a routine handover.

Track equipment by asset identifier and record return instructions. Keep any unresolved return open under its own owner.

Confirm ownership beyond the code repository

Check who controls package publishing, domain administration, monitoring alerts and signing keys. A departing engineer may have created an account while solving an urgent problem. Ask them to list those accounts and transfer approved company assets before the cutoff.

Review scheduled jobs and deployment workflows for credentials tied to the person. Test the new owner or service identity before removing the old access. Keep any secret out of the closure ticket itself.

For devices, agree on the return address and shipping process before the last working day. Ask who confirms receipt and handles any company data that remains on the device. Follow the approved retention process before wiping anything.

Close the departure with evidence

Use a closure record that finance and engineering can both read. List completed tasks, exceptions and the person responsible for each remaining item.

Have the engineering lead accept the handover. Have security confirm the access changes. Have finance reconcile the final invoice against the agreed dates and amounts.

Review the replacement's progress against the revised role expectations. Give the new hire a named reviewer and a first task small enough to expose setup problems early.

Where does Opus fit in a client-run dedicated team?

Opus finds, vets and installs the whole team. The client keeps operational control, with the team working inside the client's process, tools and backlog.

"The client chooses the finalist and manages day-to-day work." Use that division when assigning replacement responsibilities: your engineering lead defines the work and evaluates fit.

Opus states: "Every placement carries a lifetime replacement guarantee with no cap and no time limit." Ask how a request moves from the initial report to a new search and your approval of the next hire. Opus replacement guarantee.

For pricing, 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." Dollar rates: Not published. Opus pricing.

Ask for a written quote that explains how the monthly charge changes during an exit and replacement. Have it address the outgoing hire's end date, any overlap and the incoming hire's start date.

Bring the role description and a sample departure scenario to the discussion. Include who will cover the work during a vacancy and which systems need a handover.

Before you approve the team, leave with named contacts for the search and employment process. Keep your engineering lead responsible for access approvals, backlog changes and handover acceptance.

Talk to Opus about a role.

<!-- File not saved: workspace is read-only. Individual exit obligations were not assessed; have the employer confirm applicable amounts before acting. -->