Pool and Shared-Facility Liability: What Hosts Underestimate

The pool is not yours, the corridor is not yours and the lift is not yours, and a guest injured there will still be your problem first.

Last updated: September 27, 2026

The pool belongs to the building. So does the corridor, the lift and the gym. None of that changes what happens when a guest slips on wet tiles beside it, because the first message goes to whoever took the booking. The distance between who controls a space and who answers for it is where hosts get caught out.

Key Takeaways

• Control and liability aren't the same. You can control none of a facility and still be the first person a guest contacts.
• Write down the overlap. Record who controls each shared space and where your own cover stops.
• Rules can move the risk onto you. Building rules and lease clauses sometimes make the host responsible for shared areas.
• Disclose what you don't control. A guest who knows the pool closes at eight complains far less than one who doesn't.
• Every rule below carries a place and a date. The examples are local, and they aren't a universal standard.

Who controls each shared space, and who carries the risk

Run through the shared facilities the way a guest will meet them. The pool and its changing area. The corridor that leads to the unit door. The lift, if there is one. The gym, the laundry, the roof terrace, the garden, the parking bay. For each one, two separate questions matter, and they have different answers.

The first is control: who decides what happens there, who maintains it, who can close it. That's usually the freeholder, a body corporate or a management company, and it isn't you. The second is exposure: whose phone rings after an incident. That's usually you, because the booking was made with you and the guest has no relationship at all with the building manager.

The gap runs in both directions. There's control without exposure — the building decides the pool's opening hours and never hears about it. And there's exposure without control — you've never held a key to the plant room, and you're still explaining the incident to a guest, a channel and possibly an insurer.

Registration rules make the paperwork side more visible than it used to be. The European Union is a current example. Regulation (EU) 2024/1028 is described as applying in full from 20 May 2026, with platforms required to verify a registration number before a listing is published (public-report level). Portugal's national short-let register is a worked example. Reporting describes roughly 119,147 valid registrations nationally, and around 6,765 cancelled in Lisbon this year — about 40% of the city's total. Most were cancelled because civil liability insurance documents were missing (public-report level, dated 26 September 2026). Those are one country's figures on one country's date, not a benchmark elsewhere, but the theme travels: the insurance paper is often the thing that fails first.

What your insurance actually reaches in shared areas

Most hosts can name their insurer and can't say what the policy covers. That's the second gap, and it's the one that decides what an incident actually costs you.

Start with the distinction that catches people out. A home or contents policy is written for a household. A short-let liability policy is written for a business. The first may treat paying guests as something between a visitor and an unlisted risk. The second is built around the fact that people you've never met will be sleeping in the unit.

Then check where the boundary falls. Shared areas are often handled through the building's policy rather than yours. That sounds like cover until you ask two questions. Does the building's policy actually respond to an incident involving a paying guest? And would it pursue you afterwards to recover what it paid? An indemnity that comes back to you isn't protection. It's a delay.

The third check is the register and the paper. Places that require registration for short letting increasingly tie it to a minimum level of civil liability cover. Portugal's AL regime, for instance, is described as requiring cover of not less than €75,000 per incident, with fines of up to €40,000 for operating without a valid registration (public-report level, dated 26 September 2026). That number belongs to Portugal on that date. What belongs to you is the question it implies: what does your own jurisdiction require, and does your policy actually meet it?

Write the answers down. Policy name, the cover it provides, the limit, the exclusions, the date you last checked, and the building's policy details with a contact for whoever manages it. Then keep it with the listing file, because the moment you need it is the moment you can't research it.

The building rules that quietly move responsibility onto you

Shared facilities come with rules, and some do more than set opening hours. Read them for clauses that transfer risk; they're usually written in the same calm tone as the bin collection schedule.

Three patterns show up often. A rule that makes the unit owner responsible for the conduct of their guests in common areas. An indemnity clause requiring the host to cover the body corporate for claims arising from the letting. And a prohibition on short letting in the lease or the building rules, which matters more than everything else on this list, because a building that doesn't permit it makes the rest of the question moot.

The prohibition is also the one people miss. A host can be registered, insured and compliant with a local scheme and still be letting in breach of the building's own rules. That's a fast route to an enforcement letter, and a slow route to arguing with an insurer. Check the lease and the building rules before the listing goes live, not after a complaint.

Then get the answers in writing. A verbal "that's fine" from a neighbour on the committee proves nothing. Ask whoever manages the building to confirm in writing which shared facilities guests may use, and keep the reply.

This is also where a tidy record pays off, because platform rules now hinge on documents. Under the EU regime described above, the platform verifies a registration number before publishing, which means the paper has to exist and match the listing. Your own listings across Airbnb, Booking.com, Agoda and Trip.com sit on one calendar at localsbnb.com, which is the easiest place to keep the versions of a unit consistent when one of them changes.

Disclosures that manage a guest's expectations

A disclosure won't transfer a legal duty. It does something more practical: it stops a misunderstanding from becoming an incident, which is what turns a shared facility into a claim.

Say plainly what you don't control. The pool is managed by the building and closes in the evening. The lift doesn't reach the top floor. The shared laundry takes coins and there's no card reader. Works in the corridor are running until a date you name. None of that is a legal shield. All of it is what a guest needs to hear before they arrive rather than after.

Put the same words in two places: the listing description, and the pre-arrival message. Keep them in step with what the building actually permits, so a guest who asks about the pool gets the same answer twice. A disclosure friendlier than the rules turns a small gap into a dispute.

Add a line for what a guest should do if something goes wrong in a shared area. Who to tell, and how to reach you. It costs one sentence and turns a corridor problem into a message, not a complaint. When a guest does report something, treat it as information about the building, not just a complaint to close.

FAQ

The pool is managed by the building. Why would a claim reach me?

Because the guest booked with you. The building may control the facility and the platform may handle the payment, but the guest's relationship is with the host, and that's where the first message and the first request for a resolution arrive. Sorting out who ultimately pays is a separate process you'll be inside whether or not you caused anything.

Is the building's insurance enough to cover my guests?

Don't assume it. It may respond, it may exclude paying guests, and it may pay first and then seek to recover from you. Ask whoever manages the building for the policy details in writing, then check with your own insurer whether your policy expects the building to be primary. Two policies with an unclear boundary is a worse position than one clear one.

Do I need to register if I only let one unit in a managed building?

That's set where the unit sits, and registration requirements increasingly attach to the act of letting rather than the size of the operation. The EU regime noted above is one current example, with platforms verifying registration before publishing. Check your own local scheme and the building's rules, and keep both answers with the listing file.

Shared facilities are the part of hosting you can't fix by being careful inside the unit. Record who controls what, find out where your cover stops, read the rules for clauses that move the risk, and tell guests what they're actually getting. The channels your bookings arrive through — Airbnb, Booking.com, Agoda and Trip.com — already sit on one calendar at localsbnb.com, which is where the documents and the listing can be kept in step.

---

This article is general guidance for hosts and isn't legal, insurance or platform policy advice. Requirements differ by country, region and building type and change over time; the figures here are dated examples from the places named, and your local authority's current requirements and your insurer's current terms prevail.