Skip to Content
Side Jobs and Freelancing by Your EOR Employees: What You Can Restrict
Home • Blog • Side Jobs and Freelancing by Your EOR Employees: What You Can Restrict
17 November   John D.  

Side Jobs and Freelancing by Your EOR Employees: What You Can Restrict

Every so often a client sends us a link to a freelance platform. On it is a profile of one…

Article navigation

Every so often a client sends us a link to a freelance platform. On it is a profile of one of their developers in Minsk, with a portfolio and a few recent five-star reviews. The message that comes with the link is usually short: can you make this stop?

The honest answer is that in Belarus you usually can’t forbid side work as such. You can, however, make sure it stays away from your working hours, your data, your code, your equipment and your competitors, which is what clients are actually worried about in most cases.

Below we look at what Belarusian law says about second jobs and freelancing, which activities you can restrict or control, and how to deal with the situation if you discover one.

What Belarusian Law Says About Second Jobs

The starting point is generous to employees. Under Article 343 of the Labour Code of the Republic of Belarus, a person may work for another employer in their free time, and as a general rule they don’t need the main employer’s consent. The second job has to be done outside the hours of the main one.

The Code does restrict secondary employment, but mostly for specific groups: managers in state organisations, people under 18, those doing harmful work with reduced hours, and some public officials under anti-corruption rules. A developer employed by a private EOR provider rarely falls into any of these categories.

Freelancing is a separate case. Someone can take on projects under civil-law contracts, register as a sole proprietor or, in some cases, pay professional income tax as a self-employed person. Each option has its own tax rules. For the clients on the other side of those contracts, tax authorities look at how the relationship actually works, as explained in this overview of how businesses engage freelancers in Belarus. None of these options requires permission from the person’s employer.

So a clause in the employment contract that bans any outside work would be hard to enforce. It can also backfire: people tend to hide side projects they think are forbidden, and then you learn about them only when something goes wrong. In practice, the useful question is which parts of your business side work might affect, and how to protect them.

Can Ban, Can Control, Can’t Touch

Here’s how common situations usually play out:

Side activityGenerallyWhat you can do
A second job at a non-competing company, outside working hoursCan’t banRequire the agreed hours, availability and results
Freelance projects for unrelated clients at weekendsCan’t banEnforce confidentiality, IP and equipment rules
Working for a direct competitorHard to ban unless the employer is an HTP residentNon-compete agreement (HTP only), trade secret regime, conflict-of-interest disclosure
Using your laptop, accounts or code for side workCan controlIT and equipment rules, disciplinary procedure for breaches
Doing side work during paid hoursCan controlWorking-time rules, disciplinary procedure
Their own startup in a different marketCan’t banDisclosure, clear IP boundaries
Open source, teaching, conference talks, bloggingCan’t banConfidentiality; agreement in advance only for content about your product

One point to keep in mind throughout: the EOR is the legal employer, so it runs any formal procedure. Your role is to notice a problem, document it and raise it. We explain how that division works in our article on which company policies apply to EOR employees.

Your Main Tools

Confidentiality and Trade Secrets

In Belarus, information is protected as a commercial secret only if the employer has formally set up a regime for it: a local act that defines what’s confidential, restricted access, and staff who have signed to confirm they know the rules. An NDA on its own helps, but without the regime behind it you’ll find it much harder to rely on in a dispute.

Beyond the paperwork, the practical side matters. The steps recommended in international guidance on protecting trade secrets, such as marking sensitive material, limiting access and training staff, are the same ones that make a Belarusian regime work in practice.

Intellectual Property: Whose Code Is It?

Work an employee creates as part of their job generally belongs to the employer, which with an EOR means the provider. The service agreement then transfers those rights to your company.

A side project written in the employee’s own time, on their own laptop and outside their job duties, generally belongs to them. The grey areas are code copied from your repositories, a side project in the same domain as your product, or work done partly during paid hours. People often mix up who wrote something and who owns it, and this fact sheet on authorship and ownership explains the difference in plain terms.

To keep things clear, describe job duties properly in the employment documents, prohibit reusing your code or internal tools outside the job, and ask employees to tell you about side projects that touch your business area.

Working Hours and Availability

An employee has to work the agreed hours and be reachable when the contract says they should be. What they do in the evenings is their own business, as long as their work for you doesn’t suffer.

If you’d rather have someone openly work fewer hours for you, it’s often better to formalise that than to fight it. Our guide to part-time and fractional hires through EOR explains how reduced-hours contracts work in Belarus.

Equipment, Accounts and Data

This is where you have the most control. You can prohibit using company laptops, accounts, licences and repositories for anything other than your work, and treat breaches as a disciplinary matter.

Write those rules down and get them signed during onboarding. If you provide hardware, our article on laptops and home-office equipment for EOR employees covers how to set up ownership and usage terms.

Be careful with monitoring, though. Tracking employees’ activity involves personal data and has to be disclosed in advance. Checking an employee’s freelance profiles or contacting their other clients behind their back can create more problems than it solves.

Conflict-of-Interest Disclosure

A reasonable middle ground is to ask employees to disclose side work that could compete with your business or overlap with their duties. This can be set out in a local act or a policy the employee signs. The aim is a conversation and an agreement, not a permission slip for every small gig.

For team leads and people with access to commercial information, stricter expectations are fair. A lead who quietly works for a competitor is a different risk from a QA engineer building websites for local cafés at the weekend.

Non-Competes: HTP Residents Only

Most employers in Belarus can’t use non-compete agreements at all. Hi-Tech Park residents are the exception: they can agree with employees not to work for competitors for an agreed period, which can last up to a year after dismissal, with compensation of at least a third of average monthly earnings for each month after employment ends. If competitor risk is a real concern, check whether your EOR provider is an HTP resident. Our guide to what foreign employers can enforce beyond an NDA goes through the details.

When Someone Seems to Have Two Full-Time Jobs

Overemployment, holding two full-time remote jobs at once, gets a lot of attention in tech. The warning signs are usually practical: slower responses during core hours, missed meetings, a drop in output, and cameras that are always off.

Most HR advice says the same thing. Confirm the facts first, talk to the employee before assuming the worst, and focus on whether the work is being done. Guidance for employers on staff working two full-time jobs also suggests looking at whether financial pressure is behind it, since a pay review or more flexible hours can sometimes solve the problem.

In Belarus, the legal question is whether the employee is meeting their obligations under the employment contract. If they’re absent during working hours or not doing the job, that’s a matter of labour discipline, and the EOR can deal with it through the normal procedure.

Special Cases

Foreign employees. People working in Belarus with a special work permit are subject to migration rules that may limit work for other employers. Check with your provider before agreeing to anything. Our article on hiring foreign nationals through a Belarusian EOR covers the wider rules.

Employees who want to freelance openly. Some people are upfront about it. Agreeing clear boundaries is usually better than pretending it isn’t happening. In some cases, reduced hours or a contractor arrangement for part of their work may suit both sides.

What to Do When You Find Out

  1. Check the facts. Is there any actual harm to working hours, data, code or competition?
  2. Have an informal conversation through the employee’s manager first. Many cases end here.
  3. If there’s a real breach, document it and pass it to the EOR.
  4. The EOR follows the Labour Code procedure: it asks for a written explanation and, if justified, applies a remark, a reprimand or, in serious cases, dismissal.
  5. Update your policies so the expectations are clear to everyone.

What to avoid: secret surveillance, deducting money from pay (fines aren’t allowed in Belarus), or trying to end the employment outside the legal procedure.

Focus on the main business tasks while we find trusted IT specialists.
Try

Checklist for Clients

  1. Make sure the EOR has a trade secret regime in place and that employees have signed NDAs.
  2. Check that your service agreement assigns IP created on the job to your company.
  3. Set clear rules on using company equipment, accounts and repositories.
  4. Define working hours and availability in the employment documents.
  5. Introduce a conflict-of-interest disclosure for side work that overlaps with your business.
  6. Find out whether your EOR is an HTP resident if non-competes matter to you.
  7. Explain all of this during onboarding, not after a problem appears.
  8. Review the setup once a year.

How EOR.by Helps

We help clients set up confidentiality, IP and conflict-of-interest provisions in local acts and employment documents through our HR consulting services, and we brief employees on them during onboarding.

If a problem does come up, we handle it through the proper procedure, so that any measure we apply holds up under Belarusian law.

FAQ

Can I forbid my Belarus EOR employee from having a second job?

Generally no. Belarusian law allows secondary employment outside working hours without the main employer’s consent, except for certain categories that rarely apply to private IT companies. You can protect your hours, data, code and equipment.

Can an EOR employee freelance at weekends?

Yes, as long as it doesn’t involve your confidential information, code or equipment and doesn’t affect their work for you.

Who owns code an employee writes for a side project?

Usually the employee, if it was created in their own time, on their own equipment and outside their job duties. Code created as part of the job belongs to the employer and passes to you under the service agreement.

Can I stop an employee from working for a competitor?

Only an HTP-resident employer can sign a non-compete agreement. Otherwise, rely on a trade secret regime, NDAs and a conflict-of-interest disclosure.

What if I suspect an employee has two full-time jobs?

Focus on results and availability. Talk to the employee first, and if they aren’t meeting their obligations, ask the EOR to deal with it through the normal disciplinary procedure.

Does a foreign employee need a separate permit for a second job?

Migration rules may limit this for people working under a special permit. Check the specific case with your provider before agreeing to it.

Summing Up

A ban on side work won’t hold up for most EOR employees in Belarus, and trying to impose one tends to damage trust. What does work is protecting your working hours, data, code and competitive position with clear rules, signed at the start and explained to the team.

Concerned about side work in your Belarus team? Get in touch, and we’ll review your NDA, IP and policy setup and tell you what’s enforceable.

About the author

John D.

Content Marketing Manager

John D. is the content Marketing Manager at EOR.by. He has a passion for simplifying complex topics. With experience creating content and developing strategies in the local market and abroad, John shares his rich experience to make easier processes in companies striving for their development and scaling.



Our Blog

The latest news in our blog

Reference and Background Checks in Belarus: What’s Legal and What’s Customary

19 November • by John D.

We’ve watched this happen more than once. A US client’s HR team sends a candidate in Minsk a link to…

Learn More

Side Jobs and Freelancing by Your EOR Employees: What You Can Restrict

17 November • by John D.

Every so often a client sends us a link to a freelance platform. On it is a profile of one…

Learn More

English Proficiency in Belarusian Tech Teams: How to Assess It and What to Expect by Role

12 November • by John D.

We hear a version of the same story from new clients every few months. The Minsk team’s pull requests are…

Learn More

Contact

We’re available for the new projects

Call Us
+375 29 366 44 77
Address
Novovilenskaya str, building 38, office 21, Minsk, 220053, Belarus
Email
info@eor.by

    All the fields are required