Airbnb Squatter: When a Guest Won't Leave and the 30-Day Tenancy Trap

The word hosts use is squatter. The word the law uses, once a stay passes a certain length, is tenant. That single reclassification is the difference between a guest you can ask to leave and an occupant you can only remove through a court process that takes weeks and costs more than the booking ever earned. The threshold is usually counted in nights, and it arrives quietly.

The count is what matters, not the label

Tenancy is created by facts on the ground, not by the words in a booking confirmation. The relevant facts are usually how long the person has occupied the property, whether they treat it as a residence, and in some places whether they have received mail there. A 34-night reservation and a 27-night reservation extended twice can end up in the same legal category even though only one of them was ever described as long term.

Because the threshold varies by country, state and city, the number you need is your local one, and it is worth knowing it before you accept a long booking rather than after. What is consistent everywhere is the direction of travel: the longer someone has been in place, the more procedure is required to remove them. Long-term and monthly Airbnb stays covers how the risk profile of a 28-plus-night booking differs from a weekend, and AirCover for long stays covers what changes on the damage side over the same period.

Extensions are how most hosts get there by accident

Very few hosts knowingly accept a 45-night stay from an unvetted guest. What happens instead is a 21-night booking, a polite request to add a week, another request to add ten days, and a host who says yes each time because the guest has been quiet and the calendar was empty anyway. Nobody is counting cumulatively, and then the count is past the line.

Treat every extension request on a stay that is already long as a new decision with the total in view, not as a small favour. Before you accept, add the nights up, compare the total against your local threshold, and decide whether you would have taken that booking as a single reservation from the start. If the answer is no, decline the extension while the guest still has a checkout date to plan around.

A useful discipline: keep long stays deliberately short of the threshold, then require a genuine gap before a rebooking rather than a seamless extension. A guest who leaves and returns has interrupted the occupancy; a guest who never leaves has not.

What to do in the first 24 hours of an overstay

Speed matters more here than in almost any other hosting problem, because every day of occupancy strengthens the other side. The steps immediately after a missed checkout are set out in full in what to do when an Airbnb guest will not leave. In short: message on the platform, state the agreed checkout time and that the reservation has ended, ask for a specific departure time in writing, and open a case with Airbnb the same day so the platform record starts before the situation hardens.

Keep every exchange inside the platform. The messages are timestamped, they are visible to a case manager, and they become the record of what was agreed. A phone call that resolves nothing and leaves no trace is worse than a blunt written message that documents the ask.

Do not escalate in the physical world. Locks, utilities, belongings and entry are the four things that turn a civil inconvenience into liability that follows you. The occupant who was merely overstaying becomes a claimant with a documented grievance, and any damage claim you later file gets read in that light.

What Airbnb can and cannot do

The point of the table is the third row. Hosts lose weeks waiting for the platform to solve a problem the platform has no authority over. Recognising which row you are in on day one is the whole game.

Damage found after an overstay is its own claim

An overstay and the damage discovered afterwards are separate matters, and the damage claim still has its own deadline. Filing is required within 14 days of the checkout that appears on the booking, or before the next guest arrives, whichever comes first, and a contested departure does not pause that clock. See the 14-day filing window for the mechanics.

This is where an overstay quietly costs twice. Documentation gets deferred while you deal with the human problem, the property is finally free, and by then the window has closed on evidence you could have gathered on the original checkout date. If an overstay is developing, photograph what you can access legally and safely, and file on time on the strength of what you have rather than waiting for a clean finish.

The screening signals that predict a long-stay problem

• A long booking with no clear reason for being in the area, or a reason that changes between messages.
• A request to extend within the first days of a stay that was already long.
• Pressure to move the conversation or the payment off-platform.
• A local booking for an extended period, which fits relocation more often than travel.
• Vagueness about who will actually occupy the property, or a booking made for someone else.
• A newly created account with no reviews requesting the longest stay you have ever taken.

None of these are grounds for refusing a person; they are grounds for asking a straightforward question and reading the answer. The behavioural, discrimination-free version of that routine is in how to screen an Airbnb booking before you approve it, and local booking explains why proximity changes the risk profile. The third-party booking pattern has its own article in third-party bookings and fake IDs.

For a structured pass on a specific request, the free Guest Risk Pre-Screener walks through the behavioural facts in order and flags the combinations that historically precede trouble, without touching any protected characteristic. Comparison of the paid screening services sits in guest-screening tools compared.

Set the rules before the booking, not during it

Two policy choices remove most of this risk. First, cap the maximum stay length in your listing settings below your local tenancy threshold, so the platform enforces the limit instead of your judgement in the moment. Second, write the checkout expectation and the extension policy into your house rules, so a refused extension is a policy rather than a personal decision. House rules that prevent damage includes the language and the reasoning.

Neither choice costs anything, and together they mean the count never gets close to the line. That is the only version of this problem that ends cheaply.

The honest summary

Once occupancy has run long enough to look like tenancy, there is no fast fix, no platform escalation that resolves it, and no self-help step that does not make it worse. Get local legal advice early, keep every exchange written and on-platform, and protect the damage claim separately so the filing window does not close while you are focused on the departure.

Then fix the intake. A maximum-stay cap, a stated extension policy, and a five-minute screening routine on long requests will prevent nearly every case that reaches the point where a lawyer is the only option.