Соглашение о неконкуренции в Беларуси: что иностранный работодатель действительно может применить, помимо NDA

Here’s the phone call. A senior engineer on your Belarusian team has just handed in notice — and next Monday they start at your closest competitor. You pull up the employment contract. There it is: a two-year non-compete, signed on the first day. You forward it to your lawyer. Your lawyer sighs.

This piece is about what that sigh means, and what to do about it. The honest answer is more useful than the reassuring one: the standard Western-style non-compete you pasted into your Belarusian contract almost certainly won’t hold up. But that isn’t the end of the story — it’s the beginning of it. You actually have more tools than you think. They’re just not the ones you were reaching for.

The general rule: outside the High-Tech Park, non-competes barely work

Start with the honest headline. In most of Belarus, a post-employment non-compete clause is close to unenforceable. This isn’t a technicality — it’s a constitutional principle. The Belarusian Constitution guarantees the right to work, the Labor Code doesn’t provide a framework for employer-imposed post-employment restrictions, and courts have historically been reluctant to bar a former employee from earning a living in their profession.

That doesn’t make the clause illegal to include — it just makes it inert. Third-party HR guides put it bluntly: outside the Hi-Tech Park regime, non-compete agreements are legally unenforceable in Belarus. Where courts do consider such restrictions, they weigh them strictly against factors like duration, geographic and functional scope, compensation, and whether they unduly restrict the employee’s right to work — and most standard Western drafts fail at least one of those tests.

The trap to watch for: many foreign employers assume that because the pen touched paper, the restriction is real. It isn’t. If your protection strategy rests entirely on the words «non-compete» in a signed contract, you’re protected on paper and exposed in reality. The good news is that the actual protection you need is available — just built differently.

The Hi-Tech Park exception: where non-competes actually work

Residents of the High-Tech Park regime operate under a different set of rules — introduced under Presidential Decree No. 8 in 2017 — which unlocks a legal toolkit that isn’t available to employers elsewhere in the country. This includes proper post-employment non-compete agreements, non-poaching agreements between employers, and a range of corporate instruments familiar to any founder who has raised money in London or Delaware.

The specifics on non-competes matter, because they’re what turns the clause from theatre into a real restriction. Inside the HTP, a non-compete is enforceable for up to one year after employment ends, and the employer must pay the former employee compensation for each month of compliance — at a minimum, one-third of that employee’s average monthly salary from their final year of work. Skip the compensation and the clause reverts to decorative. Get the compensation right, and you have a restriction that Belarusian courts will actually enforce.

This changes the calculus of HTP residency in an interesting way. The tax benefits are the headline reason companies structure through the Park, but the enforcement toolkit is a quieter, and for some businesses more valuable, second reason. If you’re protecting genuinely differentiated IP or client relationships, the difference between «we can enforce» and «we can’t» is worth more than a few percentage points on the corporate tax rate.

What actually works — inside and outside HTP

Here’s where most articles on this topic stop. Ours doesn’t, because the more useful question isn’t «does the non-compete work?» but «what does?» The answer, in Belarus, is a stack of complementary tools, most of which are enforceable regardless of HTP status.

Confidentiality and NDA obligations

The workhorse of any protection stack. Confidentiality clauses are generally enforceable in Belarus, provided the scope of protected information and the duration of the obligation (during and after employment) are clearly defined. A well-drafted NDA is a stronger practical protection than a shaky non-compete: it doesn’t stop the person moving to a competitor, but it puts a defined leash on what they can take with them.

The commercial-secret regime

Sitting alongside general confidentiality is a separate statutory regime for commercial secrets — information the employer has formally designated as such and protected through restricted access and documented handling. This is often a stronger basis for legal action than an NDA alone, because it comes with its own cause of action and remedies. The practical requirement: you have to have actually treated the information as a secret, not just called it one in a contract.

IP assignment

The default rule catches out most foreign employers: without explicit contractual assignment, code an employee writes belongs to the employee, not to you. This is such a common trap that it’s worth its own article — which is exactly what our piece on IP ownership in Belarus covers in detail. For the purposes of the protection stack, treat proper IP assignment as the non-negotiable baseline every other layer sits on top of.

Duty of loyalty during employment

A quieter but useful protection: while employed, a worker has a duty of loyalty to their employer that operates by default under Belarusian law. They can’t simultaneously work for a direct competitor, and they can’t use their position to divert business or opportunities to themselves. This doesn’t restrict them after they leave — but it does mean that «moonlighting» or preparing to compete while still on the payroll is a live cause of action.

Non-solicitation of clients

Different from a full non-compete, and treated differently by courts. A well-drafted clause preventing a departing employee from actively soliciting your customers for a defined period sits on firmer ground than a blanket bar on working in the industry — because it protects a specific business relationship rather than restricting the employee’s trade generally. Precision in drafting matters: define «client,» define «solicit,» keep the duration reasonable.

Non-poaching of colleagues

Outside HTP, weak. Inside HTP, expressly available. If your concern is a departing team lead who might take three of their reports with them, this is a real HTP-only advantage worth structuring for.

Contractual penalties for breach

Belarusian contracts can include a penalty (liquidated damages) for breach of the protective provisions. This is often more practical than proving actual damages in an IP or trade-secret case, which is notoriously hard. The catch: penalties have to be proportionate to the breach. As is standard across many European jurisdictions, a court will reduce a disproportionate penalty. Design them as recovery mechanisms, not punishment.

The reference table

If you remember anything from this article, make it this table. It’s a quick overview of the entire toolbox.

Post-employment non-compete	Effectively unenforceable	Yes, up to 1 year	Explicit compensation — at least a third of monthly salary, per month of restriction
Non-solicitation of employees (non-poaching)	Weak; treated with scepticism	Yes, expressly permitted	Clear scope, defined period, and mutual agreement between employers where applicable
Non-solicitation of clients	Partial — courts more open than for full non-compete	Same	Precise definition of «client,» reasonable duration, no blanket bar on the employee’s trade
Confidentiality / NDA	Yes — works well	Yes	Defined scope of confidential information, clear post-employment duration, protected commercial-secret regime where applicable
Commercial-secret protection	Yes — statutory regime	Yes	Formal designation of information as commercial secret, restricted access, documented handling
IP assignment	Yes — with explicit clauses	Yes	Explicit written assignment; without it, the code stays with the author
Duty of loyalty during employment	Yes — default rule	Yes	Applies by operation of law; explicit contract wording strengthens the case
Contractual penalty for breach	Possible if reasonable	Yes	Amount proportionate to the breach; disproportionate penalties will be reduced by the court

«Enforceability» is a working shorthand. Every clause depends on precise drafting and the specific facts of the case; the notes in the last column are the minimum conditions for a serious chance of enforcement, not a guarantee.

The layered strategy that actually protects your business

Any one of these tools taken on its own leaves gaps. Stacked together, they close most of the real-world scenarios that keep founders up at night — an engineer walking to a competitor with your codebase in their head, a salesperson taking their client relationships with them, a technical lead leaving with half the team in tow.

The protection stack — what to actually build into your contracts

• IP assignment. Explicit clauses in every employment and contractor agreement. Without this, nothing else matters.
• NDA and commercial-secret regime. Defined scope, defined duration (typically 3–5 years post-employment for commercial secrets), formal designation of what qualifies as a secret.
• Non-solicitation of clients and, where applicable, employees. Precise definitions, reasonable period (typically 6–12 months).
• Duty of loyalty during employment. Applies by default, but state it in the contract to strengthen the record.
• If you’re an HTP resident: full non-compete with proper compensation. Realistic scope (6 months is often more defensible than 12), and monthly compensation of at least one-third of average salary during the restriction.
• Proportionate contractual penalties. Attach them to specific, defined breaches. Reasonable amounts survive judicial review; disproportionate ones get cut down.

Executives are a different game

Everything above is the standard-employee stack. For directors, deputies, chief accountants, and other senior roles, the calculation shifts. Executive contracts routinely carry enhanced restrictions, and courts approach them with less scepticism about the balance of bargaining power — a departing CTO is not the same as a departing junior developer, and the case law reflects that. A common practical structure: part of the executive’s severance is paid explicitly as compensation for observing post-employment restrictions, which both funds and justifies the restriction. Don’t work from a standard-employee template for senior roles; the drafting is genuinely different.

What actually happens when someone breaches

This is where the theory meets reality, and where a properly structured stack pays for itself.

Injunctions — court orders stopping the ex-employee from doing something — are rare and hard to secure quickly enough to matter. If your protection strategy assumes you’ll walk into court next week and get an order to stop them starting the new job on Monday, adjust your expectations.

Damages claims require you to prove actual loss, which in an IP or trade-secret context is difficult even when the breach is obvious. This is why the commercial-secret regime and contractual penalties are so important: they provide you with causes of action that do not rely only on quantifying loss.

Contractual penalties are the workhorse enforcement tool — predictable, contractually agreed, and (if reasonably sized) upheld by courts. This is what a well-drafted stack tilts the balance towards: a departing employee who breaches faces a defined, non-negotiable financial consequence, which is often enough to change their behaviour before litigation is needed.

And in the honest majority of cases, the fight never happens. Most departures are resolved by the balance of leverage set by the contract itself. If your protection stack is credible — real IP assignment, real commercial-secret protection, real penalties for specific breaches — you rarely need to enforce it in court. If it isn’t credible, you’ll find that out the hard way.

Why this is hard to get right from abroad

The overarching problem for a foreign employer: none of the above is intuitive from the outside. The right stack depends on Belarusian statutory nuance, HTP-specific carve-outs, drafting conventions that hold up in local courts, and formal steps (like designating information as commercial secret) that have to be done properly to have effect. A template dropped in from your US or UK counsel will miss most of this. A template drawn up by a local lawyer who’s never seen how these clauses litigate will miss some of it.

This is one of the quiet-but-large values of hiring through a proper local partner. An Employer of Record who works in Belarus every day drafts the whole protection stack by default: HTP-compliant where applicable, commercial-secret protocols wired in, IP assignment done correctly, penalties calibrated to survive judicial review. It’s the sort of thing that’s invisible when it’s working and very expensive when it isn’t.

The bottom line

The Western reflex — «put a two-year non-compete in the contract and we’re covered» — doesn’t translate to Belarus. Outside the High-Tech Park, that clause is close to inert. Inside the Park, it works, but only with proper compensation and realistic scope. Either way, it’s never the whole story.

The real protection is a layered stack: IP assignment, confidentiality with a defined commercial-secret regime, non-solicitation, duty of loyalty, and — where the HTP regime allows — a properly compensated non-compete. When combined, they mitigate significantly more risk than any single provision. They withstand testing since they were built together and formulated for how Belarusian courts actually work.

That’s the version worth building. Talk to the team at EOR.by if you’d like help putting together an employment framework that protects what actually matters in your business — or read more about how we structure Belarusian employment before you commit.

Frequently asked questions

Are non-compete agreements enforceable in Belarus?

Not generally, outside the High-Tech Park. Belarus’s Constitution protects the right to work, and courts are reluctant to enforce broad post-employment restrictions on an employer’s initiative. Inside the HTP regime, non-competes are enforceable — up to one year, and only if the employer pays the former employee monthly compensation of at least one-third of their average salary during the restriction.

What makes the High-Tech Park different?

HTP residents operate under a special legal regime that unlocks contract tools not available elsewhere in the country: non-competes, non-poaching agreements between employers, option agreements, convertible loans, and other instruments familiar to international founders. For businesses that need to protect genuinely differentiated IP or team stability, this changes the calculus of where and how to structure.

Can I use my US or UK non-compete template on a Belarusian employee?

You can put it in the contract, but you shouldn’t rely on it. Outside the HTP, it’s functionally decorative; inside the HTP, it will likely fail because it won’t meet the specific compensation and scope requirements that make the local version enforceable. Use a locally drafted version — the wording is genuinely different.

How long can a non-compete last in Belarus, and does it require payment?

Inside the HTP, up to one year, and yes — monthly compensation of at least one-third of the employee’s average monthly salary from their last year of work is a condition of enforceability. Skip the compensation and the clause reverts to unenforceable in practice.

What actually protects trade secrets if a Belarusian employee leaves?

The commercial-secret statutory regime, combined with a properly drafted confidentiality clause. Both work regardless of HTP status. The practical requirement is that you have actually treated the information as a secret — formal designation, restricted access, documented handling — not just called it one in a contract.

What’s the difference between an NDA and a non-compete for enforcement purposes?

An NDA restricts what a former employee can do with your confidential information; a non-compete restricts where and for whom they can work. In Belarus, the NDA is far more reliably enforceable than the non-compete outside HTP. If your goal is to protect information rather than block employment, the NDA plus commercial-secret regime is your workhorse.