Three Breaches in Six Months: Poland's Delisting Maths

Delisting is arithmetic, not discretion. Three recorded breaches inside the window is the threshold that removes a listing.

Last updated: October 24, 2026

Poland's delisting rule isn't a judgement about how bad a host you are. It's a count. Three breaches recorded inside a six-month window and the listing comes off, as published in the Polish rules. That reframes the job: the thing you manage isn't the incident, it's the record. And a record is something you can keep, date and read.

Key Takeaways

• A breach exists once it's recorded. An incident that was settled at the door and never entered may not be a breach; one that was entered is a breach whatever happened next.
• Each finding is logged on its own. The rule counts entries, not episodes, so one bad inspection can produce more than one.
• The window runs from the first entry. It isn't the calendar year, and it isn't a fixed quarter.
• Two is a different posture from zero. Distance from three is the number worth knowing, not the severity of any single incident.
• Your log is the only version you control. Dated entries, the fix and the evidence are what you can produce when someone asks.

How a breach gets recorded

Nothing starts as a breach. Something happens — an inspection, a complaint that gets followed up, a check at the property — and then a finding is written down, dated and attached to a unit. From that moment the count has moved, whether or not you agree with it.

The record is not a narrative. It carries what was found, when, at which property, and what was required in response. That's why the date matters more than the description: the date is what the window is measured against, and it's the part you can't reconstruct later from memory.

Two practical consequences follow. First, the paperwork you keep is the only way to contest an entry, and a contest needs dates, photographs and a record of what you did. Second, a finding you never received a copy of still exists somewhere, so it's worth asking, at the start of each season, what currently sits on your units.

Small operations are exposed here in a way they don't expect. A host with one unit and a cleaner who holds the keys has no one whose job is to keep the file, so the file is whatever survived in a message thread. The threshold doesn't care about the size of the business, and a single apartment can reach three entries as easily as a portfolio of forty.

The six-month window

The window is measured back from the most recent entry, not forward from January. Three findings spread across eighteen months can still be three, if the first and the last sit inside a six-month span. That's the part hosts get wrong when they think in calendar years.

Read it as a sliding interval. An entry in the first week of the month starts a clock, and the sixth month after it ends the period in which two more entries would be decisive. Two findings in the first month and a third in the seventh don't add to three, because the first has already fallen out.

Which is why the useful number isn't the total on the file. It's the entries inside the current window. localsbnb.com keeps Airbnb, Booking.com, Agoda and Trip.com in one calendar with each channel's source rate and status beside the dates. The operational history of a unit — when it was available, what it sold, what changed — sits in one place, while the compliance file sits in another. Two records, one property, and they have to agree.

A simple way to keep the interval readable is to write the entry and the expiry of its window on the same line. Then a glance tells you which findings still count, and a finding that has dropped out stops shaping your decisions. Without that line, old entries keep feeling like current risk, and hosts over-correct for problems that are already out of scope.

What counts as one breach

Each finding is logged on its own, as published in the Polish rules. A single visit that turns up two separate problems can therefore move the count by two, and that's the mechanism that turns a bad week into a delisting.

That changes how you prepare for an inspection. If a visit covers safety equipment, capacity and the register display, then a missing extinguisher certificate and an overcrowded unit are two findings, not one incident with a bad afternoon attached. The count is per problem found, so the cost of a messy file is higher than the cost of one broken item.

The categories that recur are unglamorous. Safety equipment that's present but out of date. Capacity that was quietly exceeded on a busy weekend. A register entry that no longer matches who's responsible for the unit. None of these is dramatic, and each is easy to record.

Whether a record follows the property or the operator is a question worth putting to the competent authority in writing, because it decides what a new co-host or a new owner inherits. Plan as though it follows the property, and the answer will only ever make your file better.

Staying under the threshold

Treat the record as an asset with a maintenance schedule. One page per unit: the address the register uses, the responsible person, every dated finding, what was required, what was done, and where the evidence lives. Update it the week something happens, not at year end.

Fix forward, and document the fix. A resolved finding still counts toward the total — resolution changes what happens next, not the arithmetic. But a file that shows a dated response to each entry is a different file from one that shows the entries alone. It's also the one you'd want in front of you in a conversation about whether a unit should stay listed.

Then remove the easy entries before they happen. Date every safety check and keep the certificate in the folder. Count guests against the capacity on the register, not against what the sofa can sleep. Check once a quarter that the responsible person on the file is still the person answering the phone at eleven at night.

For a portfolio, the same logic scales into a budget you can read. Count the entries inside the window across all units, and you have a measure of how much attention the portfolio needs this quarter — not a legal figure, just an honest one. A month where the count rises across three properties is a month where the routines slipped somewhere shared, and that's usually cheaper to fix than the entries themselves.

FAQ

Does a fixed problem still count as a breach?

If it was recorded, it counts, as published in the Polish rules. Fixing it changes what an inspector finds next time and what you can show in response; it doesn't remove the entry that already exists.

What happens after the third entry?

Removal follows, and re-registration isn't available immediately — the rules set a waiting period, as published in the Polish rules. The practical point is that the penalty isn't the fine, it's the time off the market. Confirm the current position with the competent authority.

Do findings on one unit affect the others?

Entries are recorded against a property, so a clean unit isn't dragged down by a messy one. But shared habits travel: the same missing certificate or the same capacity shortcut usually turns up on every unit run by the same team.

The maths is simple enough to keep on one line, which is exactly why it's easy to ignore until the third entry lands. localsbnb.com holds the letting side of the same property — channels, dates and source rates — so the operational record and the compliance file can be checked against each other rather than argued about.

---

This article is general guidance for hosts and isn't legal, tax or insurance advice. What counts as a breach, how a record is kept and what follows removal are set by the Polish rules and applied by the competent authority. Confirm the current threshold and window with the competent authority before you rely on them.