ZUS Just Got More Power. Here’s What Remote Workers and IT Professionals on L4 Sick Leave in Poland Actually Need to Know

Starting Monday, April 13, ZUS – the Polish Social Insurance Institution – expanded the powers of its inspectors to check whether sick leave is being used appropriately. A lot of people misread what changed on April 13, 2026. It wasn’t a ban on leaving your home. It wasn’t a crackdown on everyone who’s ever taken a sick day. And it definitely wasn’t designed with remote workers in mind, which is exactly why L4 sick leave remote workers in Poland need to read this carefully, because the rules that seem simple on paper get complicated fast when your office is your living room.

What Changed on April 13 and Why It Matters

From April 13, 2026, ZUS, the Polish Social Insurance Institution, expanded the powers of its inspectors to verify how employees on medical leave, known in Poland as L4, are actually spending their time off.

This isn’t a procedural tweak. It’s a more assertive approach to catching genuine abuse of the sick leave system, which has been a growing concern for both employers and the state. The changes were introduced in direct response to cases where workers on certified sick leave were found doing things clearly incompatible with recovery, like performing paid work for another employer, or engaging in physical activity they were supposedly unable to do.

What the rules do not do is ban employees from stepping outside their door entirely. Leaving home is permitted, but the reason matters. A short walk for health reasons or a visit to a pharmacy is a very different situation from going to work a second job.

The Ministry of Family, Labour and Social Policy was explicit: the goal is to prevent abuse, not to turn sick leave into house arrest.

Can You Go Outside While on L4 Sick Leave in Poland?

Yes, and this is probably the most misunderstood point in the whole debate.

Leaving home during L4 sick leave in Poland is not automatically forbidden. The key question inspectors ask is whether the activity is consistent with the medical reason for the leave. If a doctor has certified that someone needs rest due to a back injury, that person going for a light walk is very different from them carrying boxes at a second job.

What gets people into trouble is engaging in activities that contradict their medical condition, especially performing work for another employer, or doing things that clearly show the leave was obtained under false pretences. Inspectors can now act more decisively when they observe such inconsistencies, and the consequences can include losing the sick pay benefit entirely, for the full duration of the leave.

The Expanded ZUS Powers Do Not Change the Definition of Sick Leave

The single most important conclusion here is this: the April 13 changes expand enforcement capabilities, not the legal definition of what sick leave permits or prohibits.

ZUS inspectors can now conduct checks with a wider scope of investigative tools, but the underlying rules about what constitutes legitimate sick leave behaviour remain the same as before. This change does not affect the medical criteria for obtaining L4, does not alter the role of treating physicians, and does not introduce new restrictions on employee movement.

Employees who genuinely need sick leave and use it appropriately have no new obligations. The scope of this reform is limited to abuse prevention and inspector authority, not to redefining the rights of workers who are legitimately ill.

What Remote Workers and IT Professionals Must Understand About L4 in 2026

This is where it gets genuinely complicated, and where most articles on this topic fall short.

For people working in tech, developers, QA engineers, DevOps specialists, data analysts, the remote nature of the job creates a specific grey area that the new rules make significantly more important to understand.

Being physically at home doesn’t mean you’re compliant with L4 sick leave rules in Poland if you’re also actively working.

Let’s be specific about what that looks like in practice:

Logging into your company’s systems and completing tasks – even from your sofa, even for 20 minutes, is considered performing work. It doesn’t matter that you never left the building.

Responding to substantive Slack or Teams messages – not “I’m on sick leave, speak to X” but actual problem-solving, decisions, or deliverables, sits in a grey area that inspectors are increasingly aware of.

Pushing commits to GitHub, reviewing pull requests, or joining technical calls – these are all traceable, timestamped activities that could be used as evidence that you were performing work during a period you claimed to be incapacitated.

Being on call is a separate and particularly complex situation. If your contract requires it, this is worth clarifying explicitly with your employer before you go on L4, not after.

The line between “resting at a computer” and “working at a computer” isn’t obvious. But ZUS inspectors are no longer limited to knocking on doors. The reform gives them broader investigative tools, and digital activity is increasingly part of what compliance in remote-first environments looks like.

For IT professionals on B2B contracts specifically, the situation is even more nuanced. B2B contractors operate under different legal frameworks than employees on employment contracts, and the rules around L4 entitlement, sick pay, and permissible activity during illness vary depending on how the contract is structured and whether voluntary sickness insurance has been taken out through ZUS. If you’re on B2B and you’re unsure whether you’re even covered, check before you need it, not during.

One More Change Coming in 2027 – Worth Knowing Now

The April 2026 changes are not the end of this reform.

From January 1, 2027, the rules around combining sick leave with work for a second employer will shift significantly. Under the new framework, a doctor, at the employee’s request, will not be required to issue sick leave for every insurance title, provided the nature of one of the jobs allows it to be performed. In practice, this means that being on L4 for one employer will not automatically prohibit working for another, if the illness doesn’t prevent that specific type of work.

This is a meaningful change for anyone holding multiple contracts, a situation that’s increasingly common in the Polish IT market. It’s worth tracking, and worth discussing with a legal adviser as 2027 approaches.

The Practical Takeaway for Anyone on L4 Remote Work in Poland

The new rules don’t punish people who are genuinely ill and using sick leave appropriately. They create more tools to identify people who aren’t. If you’re a remote worker or IT professional, the relevant questions to ask yourself are: Have I clearly communicated to my employer that I’m on L4 and unavailable? Is there any ambiguity in my contract about what’s expected of me during illness? Am I doing anything digitally that could be interpreted as performing work?

If the answer to any of those isn’t immediately clear – that’s the gap worth closing now, before an inspection makes it urgent.

This article is for informational purposes only and does not constitute legal advice. For guidance specific to your contract type and situation, consult a qualified legal professional in Poland.

Navigating B2B contracts and employment compliance in Polish IT?

At Itentio IT Recruitment, we work exclusively in tech – and questions around contract structure, sick leave coverage, and employment terms come up in many placements we make. If you’re a professional figuring out your options or a company hiring in Poland, we’re happy to point you in the right direction. Get in touch via the contact form or e-mail [email protected]