The legal ground under your feet<\/strong><\/h2>\n\nBelarusian intellectual property law is based on two key pillars for employers: the Civil Code and the Law on Copyright and Related Rights of May 17, 2011. When you combine different legislation for patents, industrial designs, trademarks, and utility models, you have a complete picture of software, creative work, and inventions.<\/p>\n\n
The core concept you need to understand is the service work<\/strong>. When an employee creates something within the scope of their job duties, exclusive rights default to the employer. That is the good news. The details are where it gets sharp.<\/p>\n\n\n- Personal non-property rights<\/strong> \u2014 authorship and the right to a name \u2014 always stay with the individual who created the work. You cannot buy them, sign them away, or reassign them.<\/li>\n\n\n\n
- Exclusive (economic) rights<\/strong> transfer to the employer by default for service works, provided the work genuinely falls within the employee’s documented job duties.<\/li>\n\n\n\n
- The five-year rule<\/strong> \u2014 if the employer does not use the service work (or transfer it) within five years of its creation, exclusive rights can revert to the author. Sitting on a codebase or a design without commercial use is a real risk, not a theoretical one.<\/li>\n\n\n\n
- Inventions, industrial designs, and utility models<\/strong> are governed by patent law rather than copyright, and the process for claiming employer rights is different. Miss the deadline, lose the patent.<\/li>\n<\/ul>\n\n
For the source texts, WIPO Lex publishes the Civil Code of the Republic of Belarus<\/a> and the 2023 amendments to Belarusian IP legislation<\/a> in English. Neither is a fun read, but they are the ground truth.<\/p>\n\nCode: where software IP leaks in Belarus<\/strong><\/h2>\n\nSoftware is the asset most employers assume they own automatically. In Belarus, they usually do \u2014 until they don’t.<\/p>\n\n
The default assignment of exclusive rights to the employer only works if the employment contract and job description clearly define software development as part of the employee’s duties<\/strong>. A vague job title like «Specialist» or a job description that reads «performs tasks assigned by management» is not enough. If a court cannot tell from the contract whether writing code was the person’s job, the presumption in the employer’s favor gets shaky.<\/p>\n\nThe other common leak is off-hours work. An engineer writes an internal tool on a weekend, on their own laptop, in a language nobody at the company uses. Is it a service work? The answer depends on whether the contract defines «service work» broadly enough to cover work created using company resources, company data, or in connection with the company’s business \u2014 not just the narrow set of tasks written into a job description.<\/p>\n\n
A third pattern we see: contributions to open source. Without a clear policy, employers and employees can end up in a mess over whether contributions made on company time to an external project belong to the company, to the employee, or to the project. If your engineers are contributing upstream, address this explicitly, especially for roles that generate significant IP such as AI\/ML engineers<\/a> or backend leads.<\/p>\n\nDesigns: the freelancer trap and other pitfalls<\/strong><\/h2>\n\nUI\/UX, branding, product illustration, industrial design \u2014 creative work follows the same service-work logic as code, with one important twist that catches a lot of companies out.<\/p>\n\n
The twist is contractor work. If you hire a designer as an independent contractor rather than an employee, none of the employment-based intellectual property presumptions apply. Contractor IP has to be assigned to your company through a separate agreement, in writing, with the scope of assignment clearly spelled out. «We paid for it, therefore we own it» is not a legal principle in Belarus.<\/p>\n\n
This is most important for organizations that want to swiftly scale design work: an in-house lead designer and a revolving bench of freelance contributors. The full-timer’s work is covered by the employment contract. The freelancers’ work is only yours if each contract says so, ideally naming specific deliverables and confirming the assignment of exclusive rights.<\/p>\n\n
Derivative work is a separate design flaw. If your designer builds on an existing framework, template, or asset collection, the IP rights you receive are only as clean as the upstream inputs. Ask about licenses for assets brought into the company, and document where they came from.<\/p>\n\n![\"\"](\"https:\/\/recruiting.by\/wp-content\/uploads\/2026\/07\/20944989-1024x683.jpg\")
<\/figure>\n\nInventions and patents: the disclosure clock<\/strong><\/h2>\n\nFor patentable inventions, utility models, and industrial designs, Belarusian law adds a step that copyright does not have: the employee must notify the employer of the invention, and the employer has a fixed window to decide whether to claim rights and file. Miss the window and the right to file can pass to the inventor. The Belarusian government portal on intellectual property<\/a> gives a plain-language overview of how the national system fits together, including membership in the Eurasian Patent Organization, which lets you protect an invention in eight countries with a single filing.<\/p>\n\nThere is also a compensation obligation. When an employer takes a service invention and files for a patent, the inventor is entitled to remuneration on top of their regular salary. The amount is not fixed by statute, which sounds employer-friendly and is often the opposite: unclear remuneration terms are one of the most common sources of dispute. If the number is vague and the invention becomes commercially significant, expect the conversation to get expensive.<\/p>\n\n
For companies without a Belarusian entity, this whole area is a strong argument for using a compliant local employer of record. The IP assignment, disclosure workflow, and remuneration framework are all contained within a contract that is already properly handled.<\/p>\n\n
Seven clauses every Belarusian employment contract should have<\/strong><\/h2>\n\nIf you take one thing from this article, take this checklist. Every contract you send in Belarus should cover the following seven points. If any are missing or vague, you have a gap to close.<\/p>\n\n
\n- Explicit scope of duties. <\/strong>The job description names the type of work that generates IP \u2014 software development, design, research, product engineering \u2014 in enough detail that a reader can tell what the person is paid to create.<\/li>\n\n\n\n
- Assignment of exclusive rights. <\/strong>A clean clause assigning all exclusive rights to service works to the employer, covering both existing and future works created during employment.<\/li>\n\n\n\n
- Definition of «in connection with duties». <\/strong>Language that covers work created using company time, company resources, company data, or company confidential information \u2014 not just tasks assigned by name.<\/li>\n\n\n\n
- Disclosure obligation for inventions. <\/strong>The employee agrees to notify the employer promptly of any patentable result, and to cooperate in the filing process.<\/li>\n\n\n\n
- Remuneration for patentable inventions. <\/strong>A concrete formula or a clear procedure for setting the amount. Do not leave this open.<\/li>\n\n\n\n
- Post-termination obligations. <\/strong>Confidentiality that is maintained even after termination, material return, and a clear declaration that all previously created service works remain the company’s property. Non-compete and non-solicitation are separate topics with their own limits.<\/li>\n\n\n\n
- Moral rights acknowledgment. <\/strong>A clause acknowledging that authorship rights stay with the creator, and agreeing on how attribution and publication will be handled.<\/li>\n<\/ol>\n\n
Taken collectively, these regulations establish a consistent framework for protecting intellectual property throughout the employment relationship, from onboarding to termination. Reviewing them as a whole, rather than as individual provisions, is one of the most effective strategies to decrease legal risk and avoid future ownership conflicts.<\/p>\n\n
Five mistakes we see most often<\/strong><\/h2>\n\n\n- Copy-pasting a Russian or generic template. <\/strong>Belarusian law overlaps with Russian in many places and diverges sharply in others. Templates from a Moscow-based firm are a starting point, not a finished contract.<\/li>\n\n\n\n
- A job description that does not match the actual work. <\/strong>Your senior engineer’s title says «Consultant» because that was the visa route. Their day job is architecting a payments platform. If it goes to a dispute, the contract, not the reality, is what the court reads.<\/li>\n\n\n\n
- No handling of pre-employment IP. <\/strong>A new hire brings a personal library, framework, or design system into your product. Without a written arrangement, that upstream IP is not yours, and it is now entangled with what you ship.<\/li>\n\n\n\n
- Treating contractors like employees. <\/strong>You onboard them, give them a laptop, put them on Slack. But their contract does not include an IP assignment. Six months later, half your product is legally theirs.<\/li>\n\n\n\n
- Sitting on the five-year clock. <\/strong>A prototype gets shelved, a design library is never adopted, an internal tool is quietly abandoned. Five years later, the creator can reclaim rights to work you assumed was yours.<\/li>\n<\/ul>\n\n
What to do before the offer letter goes out<\/strong><\/h2>\n\nIP protection is easiest at the top of the funnel, hardest at termination. The practical playbook for a hiring lead in Belarus looks like this:<\/p>\n\n
\n- Review your employment contract template with a Belarusian IP specialist at least once a year, and any time the law changes.<\/li>\n\n\n\n
- Brief recruiting managers on the importance of the job description. Vague descriptions are cheap to write and expensive to defend.<\/li>\n\n\n\n
- Include an IP disclosure phase in onboarding: a brief discussion of pre-existing IP, open-source contributions, and side projects, followed by written acknowledgment.<\/li>\n\n\n\n
- Keep a live register of service works and inventions, with dates, contributors, and current status. This makes the five-year rule manageable and helps in any due-diligence or acquisition process.<\/li>\n\n\n\n
- Coordinate with whoever runs your global equity plans. Stock options interact with IP in ways that are easy to miss \u2014 see our note on equity for Belarusian IT employees for the practical constraints.<\/li>\n<\/ul>\n\n
For companies that do not want to run this themselves, our Employer of Record service<\/a> handles compliant employment contracts, IP assignment, and payroll under a Belarusian entity, so you can hire without setting up a legal presence. If you are further along and want template review, workflow design, or an audit of existing contracts, HR consulting<\/a> is the right door.<\/p>\n\n \n \n \n\t\t\t\t \n FAQ<\/h2>\n <\/div>\n\t\t\t\t \n - Does the employer automatically own everything an employee creates in Belarus?<\/a><\/dt>\n
No. The employer owns exclusive rights to service works \u2014 work created within the scope of the employee’s documented job duties. Personal non-property rights, like authorship, always stay with the individual. Work created outside the scope of duties, on personal time and without company resources, is typically the employee’s.<\/p>\n<\/dd>\n
- What is a «service work» under Belarusian law?<\/a><\/dt>\n
A service work is intellectual property created by an employee as part of their job. It covers software, designs, documentation, business process descriptions, and other outputs produced in connection with the employee’s documented duties. The exact scope depends on how well the employment contract and job description define what the person is hired to do.<\/p>\n<\/dd>\n
- What happens if we do not use a piece of employee-created IP for five years?<\/a><\/dt>\n
Under Belarusian copyright law, if the employer does not use the service work or transfer rights to a third party within five years of its creation, the exclusive rights can revert to the author. This is why maintaining a register of created works and their commercial status matters, especially for research-heavy or design-heavy teams.<\/p>\n<\/dd>\n
- Do contractor agreements need a separate IP clause?<\/a><\/dt>\n
Yes, and this is one of the most common mistakes we see. The employment-law presumptions in favor of the employer do not apply to contractors. Every contractor agreement needs an explicit written assignment of exclusive rights covering the specific deliverables, or you may not own what you paid for.<\/p>\n<\/dd>\n
- How does Belarusian IP law treat inventions and patents differently from software?<\/a><\/dt>\n
Patents follow a different process. The employee has an obligation to disclose the invention to the employer. The employer has a fixed window to decide whether to claim rights and file. If the employer files, the inventor is entitled to remuneration on top of their regular salary. Missing the deadline can transfer the right to file back to the employee.<\/p>\n<\/dd>\n
- Can we use an English-language employment contract in Belarus?<\/a><\/dt>\n
Employment contracts in Belarus should be in Russian or Belarusian, the official languages. You can maintain a bilingual version for internal clarity, but the enforceable text will be the local-language one. This matters for IP clauses because precise legal language does not always translate cleanly.<\/p>\n<\/dd>\n
- What if we hire through an Employer of Record instead of setting up a Belarusian entity?<\/a><\/dt>\n
An EOR employs the person on your behalf under Belarusian law, which means the EOR’s employment contract is what governs IP. A well-run EOR includes IP assignment terms that pass exclusive rights through to your company. Ask any potential EOR to walk you through their standard IP language before signing.<\/p>\n<\/dd>\n <\/dl>\n <\/div>\n <\/div>\n <\/div>\n<\/section>\n\n
The takeaway<\/strong><\/h2>\n\nIP ownership in Belarus is not exotic law. The system is well established, the concepts are familiar, and the rules are workable. What trips employers up is not the law itself \u2014 it is contracts that were written for a different jurisdiction, or drafted quickly, or never updated as the business grew.<\/p>\n\n
- \n
- Personal non-property rights<\/strong> \u2014 authorship and the right to a name \u2014 always stay with the individual who created the work. You cannot buy them, sign them away, or reassign them.<\/li>\n\n\n\n
- Exclusive (economic) rights<\/strong> transfer to the employer by default for service works, provided the work genuinely falls within the employee’s documented job duties.<\/li>\n\n\n\n
- The five-year rule<\/strong> \u2014 if the employer does not use the service work (or transfer it) within five years of its creation, exclusive rights can revert to the author. Sitting on a codebase or a design without commercial use is a real risk, not a theoretical one.<\/li>\n\n\n\n
- Inventions, industrial designs, and utility models<\/strong> are governed by patent law rather than copyright, and the process for claiming employer rights is different. Miss the deadline, lose the patent.<\/li>\n<\/ul>\n\n
For the source texts, WIPO Lex publishes the Civil Code of the Republic of Belarus<\/a> and the 2023 amendments to Belarusian IP legislation<\/a> in English. Neither is a fun read, but they are the ground truth.<\/p>\n\n
Code: where software IP leaks in Belarus<\/strong><\/h2>\n\n
Software is the asset most employers assume they own automatically. In Belarus, they usually do \u2014 until they don’t.<\/p>\n\n
The default assignment of exclusive rights to the employer only works if the employment contract and job description clearly define software development as part of the employee’s duties<\/strong>. A vague job title like «Specialist» or a job description that reads «performs tasks assigned by management» is not enough. If a court cannot tell from the contract whether writing code was the person’s job, the presumption in the employer’s favor gets shaky.<\/p>\n\n
The other common leak is off-hours work. An engineer writes an internal tool on a weekend, on their own laptop, in a language nobody at the company uses. Is it a service work? The answer depends on whether the contract defines «service work» broadly enough to cover work created using company resources, company data, or in connection with the company’s business \u2014 not just the narrow set of tasks written into a job description.<\/p>\n\n
A third pattern we see: contributions to open source. Without a clear policy, employers and employees can end up in a mess over whether contributions made on company time to an external project belong to the company, to the employee, or to the project. If your engineers are contributing upstream, address this explicitly, especially for roles that generate significant IP such as AI\/ML engineers<\/a> or backend leads.<\/p>\n\n
Designs: the freelancer trap and other pitfalls<\/strong><\/h2>\n\n
UI\/UX, branding, product illustration, industrial design \u2014 creative work follows the same service-work logic as code, with one important twist that catches a lot of companies out.<\/p>\n\n
The twist is contractor work. If you hire a designer as an independent contractor rather than an employee, none of the employment-based intellectual property presumptions apply. Contractor IP has to be assigned to your company through a separate agreement, in writing, with the scope of assignment clearly spelled out. «We paid for it, therefore we own it» is not a legal principle in Belarus.<\/p>\n\n
This is most important for organizations that want to swiftly scale design work: an in-house lead designer and a revolving bench of freelance contributors. The full-timer’s work is covered by the employment contract. The freelancers’ work is only yours if each contract says so, ideally naming specific deliverables and confirming the assignment of exclusive rights.<\/p>\n\n
Derivative work is a separate design flaw. If your designer builds on an existing framework, template, or asset collection, the IP rights you receive are only as clean as the upstream inputs. Ask about licenses for assets brought into the company, and document where they came from.<\/p>\n\n
<\/figure>\n\nInventions and patents: the disclosure clock<\/strong><\/h2>\n\n
For patentable inventions, utility models, and industrial designs, Belarusian law adds a step that copyright does not have: the employee must notify the employer of the invention, and the employer has a fixed window to decide whether to claim rights and file. Miss the window and the right to file can pass to the inventor. The Belarusian government portal on intellectual property<\/a> gives a plain-language overview of how the national system fits together, including membership in the Eurasian Patent Organization, which lets you protect an invention in eight countries with a single filing.<\/p>\n\n
There is also a compensation obligation. When an employer takes a service invention and files for a patent, the inventor is entitled to remuneration on top of their regular salary. The amount is not fixed by statute, which sounds employer-friendly and is often the opposite: unclear remuneration terms are one of the most common sources of dispute. If the number is vague and the invention becomes commercially significant, expect the conversation to get expensive.<\/p>\n\n
For companies without a Belarusian entity, this whole area is a strong argument for using a compliant local employer of record. The IP assignment, disclosure workflow, and remuneration framework are all contained within a contract that is already properly handled.<\/p>\n\n
Seven clauses every Belarusian employment contract should have<\/strong><\/h2>\n\n
If you take one thing from this article, take this checklist. Every contract you send in Belarus should cover the following seven points. If any are missing or vague, you have a gap to close.<\/p>\n\n
- \n
- Explicit scope of duties. <\/strong>The job description names the type of work that generates IP \u2014 software development, design, research, product engineering \u2014 in enough detail that a reader can tell what the person is paid to create.<\/li>\n\n\n\n
- Assignment of exclusive rights. <\/strong>A clean clause assigning all exclusive rights to service works to the employer, covering both existing and future works created during employment.<\/li>\n\n\n\n
- Definition of «in connection with duties». <\/strong>Language that covers work created using company time, company resources, company data, or company confidential information \u2014 not just tasks assigned by name.<\/li>\n\n\n\n
- Disclosure obligation for inventions. <\/strong>The employee agrees to notify the employer promptly of any patentable result, and to cooperate in the filing process.<\/li>\n\n\n\n
- Remuneration for patentable inventions. <\/strong>A concrete formula or a clear procedure for setting the amount. Do not leave this open.<\/li>\n\n\n\n
- Post-termination obligations. <\/strong>Confidentiality that is maintained even after termination, material return, and a clear declaration that all previously created service works remain the company’s property. Non-compete and non-solicitation are separate topics with their own limits.<\/li>\n\n\n\n
- Moral rights acknowledgment. <\/strong>A clause acknowledging that authorship rights stay with the creator, and agreeing on how attribution and publication will be handled.<\/li>\n<\/ol>\n\n
Taken collectively, these regulations establish a consistent framework for protecting intellectual property throughout the employment relationship, from onboarding to termination. Reviewing them as a whole, rather than as individual provisions, is one of the most effective strategies to decrease legal risk and avoid future ownership conflicts.<\/p>\n\n
Five mistakes we see most often<\/strong><\/h2>\n\n
- \n
- Copy-pasting a Russian or generic template. <\/strong>Belarusian law overlaps with Russian in many places and diverges sharply in others. Templates from a Moscow-based firm are a starting point, not a finished contract.<\/li>\n\n\n\n
- A job description that does not match the actual work. <\/strong>Your senior engineer’s title says «Consultant» because that was the visa route. Their day job is architecting a payments platform. If it goes to a dispute, the contract, not the reality, is what the court reads.<\/li>\n\n\n\n
- No handling of pre-employment IP. <\/strong>A new hire brings a personal library, framework, or design system into your product. Without a written arrangement, that upstream IP is not yours, and it is now entangled with what you ship.<\/li>\n\n\n\n
- Treating contractors like employees. <\/strong>You onboard them, give them a laptop, put them on Slack. But their contract does not include an IP assignment. Six months later, half your product is legally theirs.<\/li>\n\n\n\n
- Sitting on the five-year clock. <\/strong>A prototype gets shelved, a design library is never adopted, an internal tool is quietly abandoned. Five years later, the creator can reclaim rights to work you assumed was yours.<\/li>\n<\/ul>\n\n
What to do before the offer letter goes out<\/strong><\/h2>\n\n
IP protection is easiest at the top of the funnel, hardest at termination. The practical playbook for a hiring lead in Belarus looks like this:<\/p>\n\n
- \n
- Review your employment contract template with a Belarusian IP specialist at least once a year, and any time the law changes.<\/li>\n\n\n\n
- Brief recruiting managers on the importance of the job description. Vague descriptions are cheap to write and expensive to defend.<\/li>\n\n\n\n
- Include an IP disclosure phase in onboarding: a brief discussion of pre-existing IP, open-source contributions, and side projects, followed by written acknowledgment.<\/li>\n\n\n\n
- Keep a live register of service works and inventions, with dates, contributors, and current status. This makes the five-year rule manageable and helps in any due-diligence or acquisition process.<\/li>\n\n\n\n
- Coordinate with whoever runs your global equity plans. Stock options interact with IP in ways that are easy to miss \u2014 see our note on equity for Belarusian IT employees for the practical constraints.<\/li>\n<\/ul>\n\n
For companies that do not want to run this themselves, our Employer of Record service<\/a> handles compliant employment contracts, IP assignment, and payroll under a Belarusian entity, so you can hire without setting up a legal presence. If you are further along and want template review, workflow design, or an audit of existing contracts, HR consulting<\/a> is the right door.<\/p>\n
\n \n\n\n\t\t\t\t\nFAQ<\/h2>\n <\/div>\n\t\t\t\t
- \n
- Does the employer automatically own everything an employee creates in Belarus?<\/a><\/dt>\n
No. The employer owns exclusive rights to service works \u2014 work created within the scope of the employee’s documented job duties. Personal non-property rights, like authorship, always stay with the individual. Work created outside the scope of duties, on personal time and without company resources, is typically the employee’s.<\/p>\n<\/dd>\n
- What is a «service work» under Belarusian law?<\/a><\/dt>\n
A service work is intellectual property created by an employee as part of their job. It covers software, designs, documentation, business process descriptions, and other outputs produced in connection with the employee’s documented duties. The exact scope depends on how well the employment contract and job description define what the person is hired to do.<\/p>\n<\/dd>\n
- What happens if we do not use a piece of employee-created IP for five years?<\/a><\/dt>\n
Under Belarusian copyright law, if the employer does not use the service work or transfer rights to a third party within five years of its creation, the exclusive rights can revert to the author. This is why maintaining a register of created works and their commercial status matters, especially for research-heavy or design-heavy teams.<\/p>\n<\/dd>\n
- Do contractor agreements need a separate IP clause?<\/a><\/dt>\n
Yes, and this is one of the most common mistakes we see. The employment-law presumptions in favor of the employer do not apply to contractors. Every contractor agreement needs an explicit written assignment of exclusive rights covering the specific deliverables, or you may not own what you paid for.<\/p>\n<\/dd>\n
- How does Belarusian IP law treat inventions and patents differently from software?<\/a><\/dt>\n
Patents follow a different process. The employee has an obligation to disclose the invention to the employer. The employer has a fixed window to decide whether to claim rights and file. If the employer files, the inventor is entitled to remuneration on top of their regular salary. Missing the deadline can transfer the right to file back to the employee.<\/p>\n<\/dd>\n
- Can we use an English-language employment contract in Belarus?<\/a><\/dt>\n
Employment contracts in Belarus should be in Russian or Belarusian, the official languages. You can maintain a bilingual version for internal clarity, but the enforceable text will be the local-language one. This matters for IP clauses because precise legal language does not always translate cleanly.<\/p>\n<\/dd>\n
- What if we hire through an Employer of Record instead of setting up a Belarusian entity?<\/a><\/dt>\n
An EOR employs the person on your behalf under Belarusian law, which means the EOR’s employment contract is what governs IP. A well-run EOR includes IP assignment terms that pass exclusive rights through to your company. Ask any potential EOR to walk you through their standard IP language before signing.<\/p>\n<\/dd>\n <\/dl>\n <\/div>\n <\/div>\n <\/div>\n<\/section>\n\n
The takeaway<\/strong><\/h2>\n\n
IP ownership in Belarus is not exotic law. The system is well established, the concepts are familiar, and the rules are workable. What trips employers up is not the law itself \u2014 it is contracts that were written for a different jurisdiction, or drafted quickly, or never updated as the business grew.<\/p>\n\n
- Does the employer automatically own everything an employee creates in Belarus?<\/a><\/dt>\n
- A job description that does not match the actual work. <\/strong>Your senior engineer’s title says «Consultant» because that was the visa route. Their day job is architecting a payments platform. If it goes to a dispute, the contract, not the reality, is what the court reads.<\/li>\n\n\n\n
- Assignment of exclusive rights. <\/strong>A clean clause assigning all exclusive rights to service works to the employer, covering both existing and future works created during employment.<\/li>\n\n\n\n
- Exclusive (economic) rights<\/strong> transfer to the employer by default for service works, provided the work genuinely falls within the employee’s documented job duties.<\/li>\n\n\n\n