Four months into a senior backend hire, the engineer resigns. The offer letter is somewhere in your onboarding folder. The signing bonus has been paid. The recruitment agency invoice cleared in month one. Now you are opening the recruitment contract for the first time since you signed it — trying to figure out whether you are owed a replacement, a refund, or nothing at all.
A well-drafted clause means that a replacement candidate is on the shortlist within 60 days of the departure. In practice the language often works out less favourably than the companies remember agreeing to. Common problems are a guarantee period starting from the date of the offer instead of the first working day, a definition of “cause” that does not include ordinary resignations, and a refund provision that covers only 50% of the fee and is contingent on a 90-day unsuccessful search. For a candidate leaving within a quarter, vendor exposure can be as high as €4,500 on a €18,000 placement fee.
This pattern is consistent across the market. The replacement clause is the most heavily negotiated provision in an IT recruitment contract and the one most rarely re-examined after execution. Contracts are signed on the basis that the wording reflects standard terms, then set aside until a placement fails and the language becomes material in a way it was not at signing.
This piece breaks down what a workable replacement guarantee actually says, where the standard vendor templates leak value, and what to put in writing when you are hiring engineers or executive-level tech talent — in Belarus and in every other market where recruitment is a meaningful line item.
A replacement guarantee is a contractual undertaking that if a placed candidate leaves the role within a defined period, the recruitment agency will source a replacement at no additional fee.
It is not a refund. It is not a warranty on the candidate’s future performance. It is a promise to run a second search on the same commercial terms if the first one does not stick.
The refund is a separate thing. Some contracts pair the two — replacement first, refund only if the replacement search fails. Some contracts offer a straight refund with no replacement obligation. A minority offer both in parallel and let the client choose. These are different products, and treating them as interchangeable is where the first misunderstanding usually enters.
The difference is important for a practical reason: replacement takes time you may not have. If your Q3 delivery plan is dependent on the person you just lost, an eight-to-12-week search for a replacement doesn’t fix the delivery plan. Sometimes it is better for the business to refund (credit against another hire or the outstanding invoice on a live search) than to replace like for like.
Good contracts spell out which lever the client can pull, when, and on what conditions.
Cut through the vendor marketing language and every replacement guarantee reduces to five variables. Read the clause for these, and you will know exactly what you are buying.
Duration. How long the guarantee runs. Market standard sits between 60 and 90 calendar days for mid-level IT roles, 90 to 180 days for senior engineers and engineering managers, and up to 12 months for C-level and executive search. Anything under 30 days is not a guarantee — it is decoration.
Start of the counter. The date the clock starts. Three common options: the offer signing date, the candidate’s first working day, or the end of the statutory probation period. The first is aggressive for the vendor. The third is aggressive for the client. The first working day is the fair midpoint. Vendors sometimes leave this ambiguous on purpose.
Trigger events. What counts as an event that activates the guarantee. Voluntary resignation by the candidate almost always qualifies. Termination by the client is where the language gets carefully drafted — usually only termination for cause (poor performance, misconduct) activates the guarantee, not redundancy, role elimination, or a mutual parting of ways. This is the most contested piece of the clause.
Replacement scope. The parameters the second candidate has to meet. Job title, seniority, salary range, technology stack, years of relevant experience — each of these needs to be named in the clause, or the vendor retains room to interpret them downward. Under a loosely drafted scope, the agency can present a mid-level engineer against a senior brief, argue that the role has been filled, and treat the guarantee as discharged. Under a tightly drafted scope, the replacement candidate has to sit within the same seniority and compensation band as the original placement, with the agency continuing the search if the profile falls short.
Refund fallback. The mechanism that determines the financial outcome when a replacement cannot be sourced or is no longer required by the client. The preferred structure is a pro-rata refund, calculated by reference to the portion of the guarantee period that had elapsed at the point of departure. A binary refund — full recovery of the fee upon the failure of a replacement search running for a defined period — is a defensible secondary option. A clause worded as an obligation to use “best efforts” to identify a replacement, with no refund provision in the alternative, offers no protection in the event the search does not conclude, and is the version most frequently found in unamended vendor templates.
Any recruitment contract that leaves more than one of these five variables ambiguous is a contract that will be re-litigated the moment something goes wrong.
Here is where the standard templates leak value, based on what we see reviewing agency contracts for foreign IT clients hiring into Belarus and adjacent markets.
The counter starts too early. Contracts that start the guarantee period on the offer signing date are betting on the pre-start window. If the candidate accepts a counter-offer from their current employer in that window — a common failure mode across the Belarusian senior IT market — the vendor argues the guarantee has already elapsed even though the person never showed up. Push the start to first working day.
“Cause” is left undefined. “The guarantee applies unless the candidate is terminated for cause” reads reasonable until you try to enforce it. Whose definition of cause? Documented under what procedure? The Belarusian Labour Code has its own list of grounds for termination for cause, and the international agency template usually does not reconcile with it. Reference the applicable code explicitly or define the grounds in the contract itself.
Redundancy loopholes. A clause that voids the guarantee where the role has been “eliminated, restructured, or materially changed” gives the vendor a defensible position on almost every internal reorganisation. Team restructures, reporting-line adjustments, and title revisions are ordinary events in a growing company, and none of them should extinguish the guarantee on a placement made three months earlier. The exclusion should be narrowed to circumstances of genuine business necessity — closure of the local office, discontinuation of the practice area, or wind-down of the entity — with routine internal reorganisation carved out.
No replacement timeline. “The agency shall use best efforts to source a suitable replacement” without a stated deadline is not a delivery commitment. State the timeline: shortlist within 15 business days, placement within 60 business days, and the refund kicks in automatically if the placement does not close. Put a number on it.
Sole-remedy language. Some contracts state that the replacement guarantee is the client’s “sole and exclusive remedy” for a candidate departure. That language should be pushed back on. If the departure resulted from misrepresentation by the agency — a fabricated CV, a candidate placed on false pretences — the client should retain broader remedies. International HR bodies such as the Society for Human Resource Management publish reference guidance on this, and the pattern is consistent: carve out fraud, negligence, and gross misconduct explicitly.
Payment tied to the wrong milestone. The classic bad structure: full fee due on offer acceptance, not on the candidate’s start date. This misaligns incentives — the vendor’s job is done at signature, not at the point where the client has actually received the value paid for. Push for payment on start date, or a two-stage payment (part on acceptance, balance on start) at minimum. For high-value senior placements, structure part of the fee against the guarantee period.
Silence on candidate re-approach. After a placement, does the agency remain free to approach that candidate for other clients? Most standard contracts say nothing. Add an off-limits clause — 12 to 24 months on the specific candidate, and a broader non-solicitation covering all placed hires for the duration of the agency relationship plus 12 months.
Currency and jurisdiction mismatch. For cross-border engagements — a UK holding company using a Belarusian recruiter to hire in Minsk — the contract often names one currency for the fee and another for the refund, or names an inappropriate governing law. Reconcile these at signing, not at dispute.
If you are hiring in Belarus specifically, the local statutory framework interacts with the guarantee clause in ways that international templates do not always account for.
The standard probation period under the Belarusian Labour Code runs up to three months. The primary source of record for employment legislation is the official pravo.by portal, which publishes the codified text and regulatory clarifications. During probation, either side can terminate the contract with three days’ written notice — a much shorter runway than the two-to-four weeks common in Western European jurisdictions.
The interaction with the guarantee: a 90-day guarantee that starts on the first working day maps almost exactly onto the probation window. That is deliberate. It gives you the ability to make a probation call — keep or release the hire — inside the vendor’s own exposure period. A shorter guarantee (60 days or less) leaves you carrying probation risk that the vendor has already priced out.
For senior IT hires, the calculation is different. Senior engineers, engineering managers, and country leads often have probation terms shortened or waived at offer. In those cases, the guarantee should extend beyond the statutory probation — 120 to 180 days is the range we recommend for senior placements — because the failure mode for senior hires is usually visible in months two through five, not months one to three.
For C-level and executive search, the guarantee frame is different again. Executive placements should carry a 12-month guarantee tied to the fiscal-year cycle of the hiring company, not the individual’s probation. Reference guidance from the Association of Executive Search Consultants sets 12 months as the industry standard on retained executive assignments — a benchmark worth citing when a vendor pushes back on longer terms.
Before you sign, walk the contract against this list.
A clean contract fits these on two pages of substantive clauses. Anything longer than that is usually hiding something in the paragraphs nobody reads.
Some contract features tell you the vendor is not one you should be signing with in the first place.
“Best efforts” language without any measurable delivery commitment. “Guarantee void at agency’s sole discretion.” A guarantee that shortens or disappears if you use any other recruiter in parallel. Refund calculated on “net fee” without defining what net means. Any clause that requires the client to waive rights they hold under the applicable Labour Code — those clauses are usually unenforceable, but the fact that a vendor is trying to insert them tells you what to expect on the rest of the relationship.
Reference-check the agency before signing. Ask two or three previous clients how the guarantee held up when it was actually triggered. Vendors who deliver on their guarantees are happy to provide those references.
For senior and executive hires specifically, top management recruitment works on guarantee terms structured against the fiscal-year cycle and calibrated to the seniority of the placement — the kind of clause language that matters most when a bad hire at that level costs six figures.
Then the reason for the termination is what matters. Performance issues, misconduct, breach of contract — those are “for cause,” and a well-drafted guarantee will cover them. Redundancy is different. Role elimination is different. A quiet mutual exit where nobody wants to say the hire didn’t work is different again, and in most contracts those situations are on you. Nail down which framework governs, or list the grounds out. General language creates general problems.
Only if the contract provides for it. A pro-rata refund structure — a percentage of the fee proportional to the remaining guarantee period — is the cleanest option. Push for this if the contract is silent, especially for senior hires where a replacement search may not fit the business timeline.
A shortlist within 15 business days of the request and a placement within 60 business days is a reasonable commitment. Beyond 60 business days, the refund alternative should kick in automatically.
Only where termination is for cause under the Labour Code. Ending probation for other reasons — including “the fit is not right” without documented cause — usually voids the guarantee under standard agency terms. Structure your probation review process so any decision to release the hire is documented against cause criteria the contract recognises.
No. Structure payment around the start date, not the offer signing. A two-stage payment — a smaller portion on acceptance, the balance on start — is a fair compromise if the vendor pushes back on full payment on start.
A replacement guarantee is only as strong as the words on the page. Vendor templates are drafted to protect the vendor. Your redlines are what turn the clause into something that actually holds up when a placement doesn’t stick.
If you are negotiating an IT recruitment contract in Belarus or building the first version of a preferred-vendor framework for your Belarus operation, the clauses that matter most are the ones nobody reads until something breaks. Get them right in advance, and the second-hire scenario becomes a straightforward process instead of a commercial fight.
For teams hiring engineers, tech leads, or executive-level talent in the local market, Spex Advisers runs IT recruitment with guarantee terms drafted around the Belarusian Labour Code and calibrated to the seniority of the placement. Send us the shortlist and we will walk you through what the contract should say before you sign it.
Dear Clients! We are pleased to announce the completion of a project of recruitment of 13 (thirteen) developers for a Lithuanian IT company with an office in Belarus. Due to the existence of a confidentiality agreement, we cannot write the name of the brand under which our Client operates. However, as before, we can tell […]
Most foreign IT companies looking at Belarus stop reading after three letters: HTP. It’s understandable. The High-Tech Park has the best marketing, the cleanest English-language materials, and a tax profile that makes the math easy to model. For a lot of software companies, it’s genuinely the right answer. But not for all of them. We […]
Nobody accidentally under-invests in document legalization. They under-schedule it. Every failed Belarusian setup we see loses two to six weeks in the same three or four places — and none of them are legal complexity. They’re order-of-operations mistakes: notarizing after the apostille instead of before, translating in the wrong country, issuing a Certificate of Good […]
