Belarusian IT Terminations: Why Your Home Playbook Doesn’t Translate
Every foreign employer who’s ever ended a Belarusian employment contract has started at roughly the same place. They take the…
Every foreign employer who’s ever ended a Belarusian employment contract has started at roughly the same place. They take the process they know from home. They pull up the template that worked in London or Berlin or Boston. They call their local counsel and ask how to translate it.
That’s the mistake.
You’re not translating a playbook here. You’re switching toolkits. The instruments have different names because they’re different instruments, and some of what you were counting on isn’t in the toolkit at all. Garden leave is the clearest example, and we’ll get to it. But the same shift applies to how “for cause” dismissal works, to what a notice period actually means, and to what a “clean exit” is even structurally capable of looking like. This piece walks through what shifted, what to reach for instead, and where foreign HR templates most often break under the weight of that shift. If you haven’t yet decided whether to hire in Belarus at all, the first-employee decision tree is here. Everything below assumes you already have people on payroll.
The thing that isn’t in the toolkit
Start with garden leave, because it’s the sharpest example.
In common-law jurisdictions, garden leave is a single coherent instrument. You put an employee on it after their resignation or your dismissal notice. Employment continues, loyalty duties hold, salary keeps flowing. But the person isn’t in the office, doesn’t have access to systems, and can’t start work for the competitor until the clock runs down. It’s not one right combined with another. It’s one recognised legal category.
Belarus doesn’t have that category. There is no statutory analogue in the Labor Code, and no combination of other provisions reliably produces the same effect.
The clearest published confirmation of this comes from Grata International’s Belarus employment law summary, which states it directly. Garden leave belongs to English legal systems. Belarusian legislation doesn’t provide for it. Full stop.
As a result, during any notice period, the employment connection is completely active. Your engineer has the right to get tasks, to have sufficient system access to complete them, and to be compensated.
What happens if you add a garden leave clause to a Belarusian contract? There are two possible readings. If the court interprets it as unpaid leave imposed without authorization, it is unenforceable and results in a pay claim for the entire term, plus damages. If it says compensated enforced idle time, the employee might still seek actual work, and you may still owe it. In neither reading does the clause accomplish what you want it to do. And, in both readings, the clause is now apparent proof that the employer signed contracts under a framework it never fully comprehended, influencing how a judge interprets everything else the employer did.
This is the archetype of the toolkit shift. What you brought from home doesn’t exist here, and what does exist here doesn’t reassemble into the same shape.

“For cause” isn’t what you think either
Most foreign employers assume they can end a Belarusian contract for cause if the reason is good enough. It’s a natural assumption. It’s also wrong in a particular way that matters.
Article 42 of the Belarusian Labor Code gives employers a closed list of grounds. Not “a hard list to meet.” Closed. If your reason for wanting the person out sits outside the list, the route isn’t available to you, no matter how persuasive the business case feels internally. The list, in the current text of the Labor Code, covers a specific set of grounds and doesn’t stretch: insufficient qualifications or health status, absence exceeding four consecutive months for illness, failure to perform duties by an employee already carrying an unspent disciplinary sanction, single gross violations, property damage established by judgment, and the business-side triggers (liquidation, unit closure, workforce reduction).
“Not a culture fit” isn’t on that list. Neither is “we’re restructuring toward our new AI-first strategy.” Neither is “performance concerns that were never documented as disciplinary sanctions.” All three are common reasons a foreign employer wants a termination, and none of them lands anywhere useful under Article 42. The majority of challenged dismissals are due to a mismatch between the foreign idea of “for cause” and Belarus’s limited statutory list. Employers provide a case that is consistent with their home framework and internal HR rationale, but it fails in a Belarusian court since it does not apply to any of the mentioned grounds. Reinstatement gets ordered, or compensation in lieu of up to ten months of average salary. Either result is expensive relative to the alternative that was available all along.
A brief note on protected categories, which are another instance of the same “different toolkit” pattern. Pregnant employees, employees on maternity or parental leave, and parents of young children in defined configurations are simply outside the reach of Article 42 for employer-initiated dismissals. The government’s own summary of Belarusian employment law covers the general framework at a high level, though the operational reality is stricter than the summary suggests. Foreign employers routinely discover protected status during a termination rather than before starting one.
The notice period concept, only louder
Most foreign HR teams come to their first Belarusian termination with a single number in their head. Usually one month, sometimes two. It’s a reasonable summary of exactly one of the five scenarios you might actually encounter.
| Employee resigning from an indefinite contract | One month |
| Employee wanting to leave a fixed-term contract early | Generally cannot, absent statutory grounds |
| Employer terminating on business grounds (redundancy, liquidation) | Two months minimum |
| Employer choosing not to renew a fixed-term contract | One month before expiry |
| Either side, during probation | Three days |
Two of the five deserve a second look because they trip foreign employers up specifically.
The fixed-term contract is the one that catches people. It looks like an English fixed-term contract on the surface. It isn’t. Once signed, it constrains both sides in ways the English version doesn’t. The employee generally can’t resign at will before expiry. The employer cannot terminate on grounds other than those specified in Article 42. The contract is intended to provide predictability to both parties, which it does, but “predictability” applies equally to both. If foreign counsel creates one of these as if it were a standard fixed-term agreement with reasonable notice, the drafting error sits quietly in the file until someone wants to quit quickly, which is exactly when it hurts the most. It’s one of the more common errors we see in foreign-drafted contracts.
Probation is the other one, in the opposite direction. Three days each way is the fastest unilateral lever the employer has. It’s the only fast lever the Labor Code hands the employer at all. And it expires the day probation ends, which for most IT contracts is three months from the start date. Employers who let probation end without a call have quietly given up an option they can’t recover.
What actually is in the toolkit
So here’s the box, honestly. Four instruments. They work well individually, less well when you try to make them do what garden leave was doing.
Termination by mutual consent, as outlined in Article 37 of the Labor Code, is the quickest and most flexible exit. Employer and employee sign a paper stating that the employment will stop on a specified date. The date might be tomorrow. There is no notice time, no grounds required, and no statutory severance other than what the parties agree upon. The cost is negotiated, usually one to three months’ compensation for a senior IT position. That is frequently less expensive than paying for the notice period during which access risk was mismanaged, and it is the way to choose when time is critical and there is a serious chance of dispute later.
Non-renewal of a fixed-term contract at expiry is the least contentious route. Both sides can walk away without cause, provided the one-month written notice is given. It’s only useful when time is on your side.
Termination during probation is the fast unilateral option, but only if probation is still running. It requires probation-end dates to be tracked as management events rather than passive HR admin, and it requires a decision to actually get made at the two-thirds mark. This is the sort of thing that a well-designed onboarding playbook should be surfacing as a decision point, not leaving to chance.
Article 42 dismissal on statutory grounds is the route foreign employers reach for first and should reach for last. The grounds are closed, the procedure is unforgiving, the appeal window runs a month past the dismissal date, and the litigation exposure is meaningful. It has a place, but that place is smaller than most foreign employers assume. The published overviews from international EOR providers cover the mechanics reasonably well as a starting reference, though what they generally don’t tell you is which route you should actually be using in the specific scenario you’re facing, which is usually not this one.
None of the four is garden leave. Combined, they cover most of what garden leave was doing at home. But they only work if the underlying contract was drafted for the exit, and the exit is being run by someone who understands the toolkit rather than the translation.
What this means for your first Belarus termination
If you take one thing from this, it’s that the substitution isn’t clause-for-clause. It’s a different set of instruments used differently.
Reach for mutual agreement earlier than you would at home. Almost every sensitive IT exit in Belarus should end there. The instinct to fight it out on cause because “we have a solid case” is usually the wrong instinct here, not because the case is weak but because the alternative route (Article 42) is procedurally punishing in ways foreign employers underestimate.
Track probation-end dates as management events. They give you a lever nothing else in the system does, and losing them costs an entire category of clean exit.
Take garden leave clauses out of your Belarusian contract templates. They’re net-negative wherever they appear. If IP protection is the concern, the mutual-agreement release plus IP re-confirmation covers most of the ground, and confidentiality clauses cover the rest.
And build the exit into the contract at hire, not at resignation. The final settlement mechanics matter more than most foreign employers realise, because the appeal window runs for a month past the dismissal and small errors in the day-zero payment are one of the more common reasons a former employee bothers to file at all.
If you’ve already got Belarusian staff and you’ve never stress-tested one of your existing employment contracts against a hypothetical exit, that’s a valuable exercise. It’s the sort of review a Belarus-based HR and legal team should be able to turn around inside a week, and it usually saves the client from the more expensive discovery, which is what happens when the contract meets its first real termination and doesn’t hold up.
Frequently asked questions
- Is there any way to enforce garden leave in Belarus?
Not through a garden leave clause itself, because the instrument isn’t recognised. The closest legally supported approximations are termination by mutual agreement under Article 37, employee-agreed use of accrued annual leave during notice, and employee-agreed leave without pay. None of these can be imposed unilaterally, though. The employee has to sign.
- What’s the shortest legal notice period for a Belarusian IT employee?
Three days, but only during the probation period, and only if the results of probation are documented as unsatisfactory. Outside probation, the shortest route to a near-immediate exit is mutual agreement under Article 37, which requires the employee’s written consent and almost always a negotiated payment.
- Can we terminate for “poor performance” like we would at home?
Not directly. Article 42’s closed list of grounds includes failure to perform duties, but only by an employee already carrying an unspent disciplinary sanction, which means the performance issue needs to have been documented and formally addressed before the dismissal. Foreign employers who try to terminate on performance grounds without a paper trail of prior sanctions usually lose in court.
- What happens if we skip the trade union notification step?
Where a collective bargaining agreement requires it, skipping it can unwind an otherwise valid dismissal. Not every dismissal triggers union involvement, but where it does, the step is procedural rather than optional, and defects here are one of the more common reasons Article 42 dismissals get reversed.
- How long does an employee have to challenge the dismissal?
One month from the date the employee receives a copy of the dismissal order, or from the date the employment record book is issued, whichever is later. Missed deadlines can be restored by the court for valid reasons. For the employer, the practical implication is that the case isn’t closed on the dismissal date. It’s closed thirty days later, which affects what communications and settlement mechanics look like inside that window. The current Labor Code is available on the National Legal Internet Portal if you want to check the specifics.
- Does using an EOR make any of this easier?
An EOR runs the termination as the legal employer, which means the dismissal order, notifications, statutory settlement, and appeal-window management are handled by an entity that does this every month rather than every three years. It doesn’t change what the law allows. It changes the frequency with which the paperwork holds up in court, and it changes the odds that mutual agreement is the route actually reached for, rather than Article 42 by default.
- Can we agree a shorter notice period in the employment contract?
Statutory minimums are floors, not defaults. What you can do, once the exit is on the table, is use Article 37 to agree an earlier end date with a settlement that reflects the notice period that would otherwise have applied. It’s the same economic outcome via a different legal route.
If you are planning your first layoffs in Belarus or would like to check in advance whether your employment contracts and internal procedures comply with local legislation, please contact our team. We will help you to audit the documents, assess the risks and prepare the process so that disputes are resolved before they turn into litigation.
Our Blog
The latest news in our blog
Belarusian IT Terminations: Why Your Home Playbook Doesn’t Translate
Every foreign employer who’s ever ended a Belarusian employment contract has started at roughly the same place. They take the…
Overtime, Night Work, and Weekend Pay Multipliers in Belarus IT Contracts
Ask five global EOR companies what overtime looks like for a Belarusian engineer, and you’ll get five different answers. “200%…
The EOR Vendor Due Diligence Checklist: 25 Questions to Ask Before Signing
The sales demo displayed a tidy dashboard. The pricing page seemed acceptable. Two of your colleagues stated they use this…
Contact
We’re available for the new projects
