Before You Hire Dedicated Engineers, Ask for a Replacement SLA

Key takeaways

• A replacement SLA should put notice, replacement timing, handoff, approval rights, and cost in writing.
• If replacement terms are vague, continuity risk stays with the client.
• A resume swap is not enough when an engineer owns production code or active feature work.
• Client approval rights should survive any replacement.
• The vendor should carry the cost of fixing its own staffing miss.

Yes. Before you hire dedicated engineers, require a replacement SLA in writing. It should cover notice, a defined replacement window, handoff, client approval rights, and vendor-paid replacement costs.

If those terms are missing, continuity risk stays with you. The US Bureau of Labor Statistics lists median pay for software developers at $133,080 per year, so replacement terms should be settled before work starts.

Put the replacement SLA in the contract

A replacement SLA should say what happens if the assigned engineer leaves, misses the agreed bar, or needs to be removed from the account. Keep it specific. Do not accept vague wording such as "commercially reasonable efforts" without defined obligations.

The clause should cover:

• written notice when a change is known
• a defined window for presenting replacement candidates
• overlap or another handoff requirement
• client interview and approval rights before substitution
• vendor-paid sourcing and replacement ramp costs

Define notice before the problem happens

Written notice should be required for planned rolloffs and sudden departures. You need time to protect active work, reassign ownership, and start a handoff.

The contract should also require the vendor to tell you when it already knows fit is breaking down. Do not leave disclosure to the vendor's discretion.

Define what counts as a replacement candidate

A replacement window matters only if the candidate still matches the original role. Put the role definition back into the clause so the replacement does not drift on stack, seniority, working hours, or communication.

Put these points in writing:

• the clock starts when you request a replacement
• the job scope does not change unless you approve it
• you can interview the candidate before the swap
• sourcing continues until you approve a match

Require handoff, not just a resume swap

A replacement should include overlap or a handoff package when the engineer owns production code or active feature work. Without context transfer, your team still absorbs the disruption.

The handoff should cover:

• open pull requests and branch status
• service boundaries and recent decisions
• deployment steps and runbooks
• ticket notes and near-term priorities
• test gaps or known issues

If overlap is not possible, require current documentation and a recorded walkthrough.

Keep approval rights with the client

Client approval should be explicit before any substitution. If the vendor can swap people without your signoff, the contract leaves too much control on the wrong side.

The clause should state that billing starts only after you approve the replacement. It should also state that rejecting a mismatch does not trigger a fee.

Keep replacement cost with the vendor

Replacement cost should stay with the vendor when the first match fails. Do not pay again for the same seat.

Ask for language that blocks:

• a new placement fee for the replacement
• double billing during vendor-required overlap
• charges for sourcing replacement candidates
• billing for an empty seat while the vendor is backfilling

Use one paragraph that assigns responsibility

One paragraph is enough if it assigns notice, replacement timing, handoff, approval, and cost. The goal is not legal volume. The goal is a clear operating rule when the assigned engineer changes.

Boltout is a software agency.

If you want a second set of eyes on one role, Boltout can review the replacement language with you on a short call.

Sources

• https://www.bls.gov/ooh/computer-and-information-technology/software-developers.htm
• https://www.boltout.co/