Notice Periods and Garden Leave in Belarus IT Contracts: How to Negotiate a Clean Exit

A developer signs an offer with a company in Warsaw. They tell their new employer, confidently, that they have “a one-month notice period.” Then they walk into their current manager’s office in Minsk, and discover that their contract still has fourteen months to run — and that nobody is obliged to let them out of it.

This happens constantly. Belarusian IT runs on English-language HR vocabulary borrowed from London and San Francisco: notice, garden leave, PIP, non-compete. Belarusian labour law runs on something else entirely. The gap between the two is where offers fall apart, start dates slip, and perfectly good working relationships end badly.

So let’s clear it up. Here’s what the rules actually say, what employers can and can’t do, and how to negotiate an exit that leaves everyone able to work together again. If you’re on the other side of the table and trying to build a team in Belarus, our IT recruitment team deals with these conversations every week.

Key takeaways

• Garden leave, as a legal concept, does not exist in Belarus. What people call “garden leave” here is a negotiated arrangement, not an entitlement.
• Most Belarusian IT specialists work on a fixed-term contract. As a rule, that means you cannot simply hand in your notice and walk after a month.
• The real instrument for a clean exit is termination by mutual agreement. Almost every good exit in Belarus runs through it.
• Non-compete agreements are broadly unenforceable in Belarus — with one big exception for Hi-Tech Park residents, and even then the employer has to pay for it.
• None of this is automatic. It is a negotiation, and how you open it determines how it ends.

First, the uncomfortable part: garden leave isn’t a legal thing here

In the UK and much of the common-law world, garden leave is a recognised arrangement: you’ve resigned, you’re still on the payroll, you’re still bound by your duties of loyalty, but you’re not coming into the office. It buys the employer a cooling-off period and it protects the employee’s income.

Belarusian labour law has no equivalent instrument. There is no statutory mechanism that says “keep paying this person and don’t make them work.” The framework governing employment relationships in Belarus is built around a different set of assumptions, and “paid non-working notice” simply isn’t one of the categories it recognises.

That doesn’t mean the effect is impossible to achieve. It means you have to build it yourself, out of the tools that do exist — accrued annual leave, unpaid leave by agreement, an agreed handover schedule, or simply an earlier release date that both sides sign off on. More on that below.

The two contract types that decide everything

Before you can plan an exit, you need to know which contract you’re actually on. Most people don’t. Check your paperwork, because the answer changes what’s possible.

The fixed-term contract system dates back to 1999 and was folded into the Labour Code in January 2020. It is worth understanding the balance of power it creates: an employer can decline to renew a contract when the term expires without giving a reason, and, at least in principle, can also refuse an employee’s request to leave early — leaving the employee to argue the point in court. The US State Department’s investment climate report on Belarus describes the system in exactly these terms, and notes that the vast majority of Belarusian employees now work on term contracts.

This is the single most misunderstood fact in Belarusian IT hiring, and it catches out foreign employers as often as it catches out candidates. “When can you start?” is not a scheduling question here. It is a legal one.

So what do people actually use instead of garden leave?

In practice, teams improvise something that looks like garden leave out of ordinary components. None of these are rights. All of them are things you ask for.

• Accrued annual leave. Belarusian employees accrue paid holiday, and burning the balance at the end of a contract is the closest thing to a legitimate soft landing. It’s paid, it’s yours, and it doesn’t require anyone’s goodwill — only agreement on timing.
• Unpaid leave by agreement. Useful when you need a gap between roles and your employer would rather not have you in the codebase.
• A reduced handover period. Documentation, knowledge transfer, an offboarding checklist — no new feature work. Most managers will take this deal because it’s the thing they actually need.
• An agreed early release date. The cleanest option, and the one that requires the negotiation we’re about to get into.

If you’re an employer trying to design offboarding that doesn’t leak knowledge or goodwill, this is exactly the kind of thing our HR consulting work covers — building the process before you need it, rather than improvising it in a difficult week.

Termination by mutual agreement: the instrument that actually works

Here is the thing to internalise. Nearly every clean exit in Belarus — the ones where the leaving date is chosen, the handover is orderly, and the two sides still speak afterwards — goes through termination by agreement of the parties.

It works because it is the only route where both sides get something. You get out on a date you can commit to. Your employer gets a controlled handover, no dispute risk, and no surprise about when the seat empties. It can be signed for any date the two of you choose, including tomorrow.

Which means the entire game is making that signature easy to give.

Why employers say yes

• A replacement is lined up, or the search has started.
• The handover plan is already written and credible.
• The relationship is intact and they’d rather keep it that way — Belarusian IT is small, and people come back.
• Holding an unwilling engineer for a year buys them a disengaged year, not a productive one.

Why employers say no

• You’re mid-release, and your leaving blows up a client commitment.
• There’s no backfill and no budget for one.
• They think holding you gives them leverage on a counter-offer.
• It’s personal. This happens more than anyone likes to admit.

The fixable ones are the first two. Which is why timing matters more than eloquence — and why, if you’re the employer facing a wave of departures, the fastest way to unblock everyone is to close the backfill. That’s where outstaffing or a fast targeted search can turn a hard “no” into an easy “yes.”

The six-move playbook for a clean exit

1. Open the conversation before you sign, not after. Once you’ve signed elsewhere, you’ve handed your current employer all the leverage and none of the choice. Sound out the release date first, then commit to a start date you can actually keep.
2. Lead with the handover, not the resignation. Walk in with a written plan — what you’ll document, what you’ll transfer, to whom, by when. You are not asking for a favour; you are offering to solve their problem.
3. Don’t name the new employer unless you have to. It rarely helps you and occasionally hurts you, especially if the new company is a competitor.
4. Get it in writing, and get it signed. A Telegram message from your team lead saying “sure, no problem” is worth exactly nothing on your last day. An agreement signed by whoever is authorised to sign is worth everything.
5. Time the ask to the contract’s expiry window. Non-renewal is dramatically cleaner than early release, for both sides. If your term ends in four months, four months of patience may cost you far less than four months of conflict.
6. Know what you’re owed on the last day. Final settlement, unused leave compensation, any bonus terms. Read the contract before the conversation, not after it.

Non-competes and the Hi-Tech Park exception

Ask a Belarusian lawyer whether a non-compete clause in an ordinary employment contract is enforceable and you will generally get a short answer: no. The right to work is constitutionally protected, and a clause telling an ex-employee where they may not work runs into that head-on.

Then there is the exception, and it matters, because it covers most of the IT sector. Decree No. 8 “On the Development of the Digital Economy”, signed in 2017, imported a set of English-law instruments into Belarusian practice specifically for residents of the Hi-Tech Park — among them convertible loans, option agreements, and, crucially, non-competition and non-solicitation agreements with employees.

Two details do most of the work here:

• The restriction is capped at one year.
• It has to be paid for. For each month the former employee complies, the employer owes compensation of at least one third of that person’s average monthly salary over their final year. An unpaid non-compete is not a non-compete; it’s a piece of paper.

So if you’re leaving an IT company, three questions. Is the company an HTP resident? Did you sign a separate non-compete agreement — not a clause buried in the contract, but its own document? And does it specify compensation? If you’re an employer weighing up whether the regime is worth it in the first place, the Ministry of Economy’s overview of the HTP is a reasonable starting point, and we walk companies through HTP residency from application to certificate.

One more group: contractors and the self-employed

A meaningful slice of Belarusian IT never signed an employment contract at all. If you work as an individual entrepreneur or self-employed specialist on a services agreement, the Labour Code is not your rulebook — civil law is, and your contract is.

That cuts both ways. There is no statutory notice period protecting you, and no obligation on the client to keep paying you through a transition. But equally, there is no contract term trapping you, and the termination clause you negotiated is the whole story. Read it. It is usually two paragraphs long and almost nobody does.

For companies, this is also where classification risk lives. Getting the employment model right — direct hire, EOR and payroll, or a PEO arrangement — is a decision worth making deliberately, before the first offer letter goes out rather than after the first exit goes wrong.

If you’re the employer, read this bit

You can, in many cases, refuse to release someone before their contract expires. The question is whether you should.

An engineer who has mentally left and legally can’t is not an engineer you are getting value from. You get a year of quiet disengagement, a handover done badly on purpose, and a story that travels — because Belarusian IT is a small market with long memories and busy Telegram chats. The people you most want to hire next year are the people who hear that story.

The employers who come out of this well do three things: they backfill early, they treat the exit conversation as a scheduling problem rather than a betrayal, and they keep the door open. The ones who come out of it badly discover that a reputation for holding people hostage is a very expensive form of retention. If you’re hiring inside the Park and want the process to run cleanly from offer to onboarding, our HTP recruitment team can help.

The short version

You cannot rely on the vocabulary you learned from Western job ads. Garden leave isn’t here. Notice periods aren’t what you think they are. And on a fixed-term contract, leaving well is not a right you exercise — it is a deal you close.

Open the conversation early, bring the handover plan, get the agreement signed, and check whether a paid non-compete is sitting in your file. Do that, and the exit is clean. Skip it, and you find out the hard way.

Hiring in Belarus, restructuring a team, or trying to work out which employment model fits? Talk to our team — we answer within two hours on any working day.