A homeowner in Washington, DC rented her property through Airbnb for a 32-day stay. Standard booking, standard platform, standard expectations.
When the period ended, the guest refused to leave. She stopped paying. And she claimed she had acquired tenant rights — not through any written agreement, not through anything the host had signed, but solely from the length of her stay.
She lived in the home rent-free for months while the legal dispute worked through the courts.
The case became a widely-cited cautionary tale in DC property circles, and it exposes something most mid-term operators have not fully internalised: at some point in a stay, the legal status of the occupant changes, and almost no property management software tracks that transition.
What actually happened, legally
There is no statute in DC that says "an Airbnb stay becomes a tenancy at day 30." The conversion happens through the interaction of the DC Rental Housing Act with how DC courts evaluate the facts of occupancy: length of stay, exchange of payment, exclusivity, and control of the unit.
The threshold that emerged from the case is uncomfortably simple. Paying for roughly 30 days or more is sufficient for DC courts to treat someone as a tenant under the Rental Housing Act — with no written lease, and with the booking made through a short-term rental platform.
Once tenant status attaches, several things become true simultaneously:
Self-help eviction is illegal. No lock changes. No utility shutoffs. No removing belongings. These are not merely inadvisable; they expose the operator to liability.
The formal process is the only process. A written Notice to Vacate must be served. A case must be filed in DC Superior Court's Landlord and Tenant Branch. A judicial order must be obtained. US Marshals enforce it.
Expiration of the stay is not, by itself, grounds for eviction without that notice and judicial process.
The guest's claim was never adverse possession — DC requires fifteen years of continuous, open occupation for that. It was a pure tenant-rights claim based on nothing but how long she had been in the unit.
Why this hits mid-term operators specifically
Short-term rental operators running two-to-five night stays never approach the threshold. Long-term landlords are inside the framework from day one and structure accordingly.
Mid-term operators — 30 to 180 days, furnished — sit precisely in the zone where the conversion happens, and frequently without recognising it.
The DC Landlord Association's analysis identified four operator profiles at highest exposure:
- Operators listing on Airbnb with stays of 30+ days, where Airbnb's own monthly discount is the explicit trigger for longer bookings
- Operators treating an extended stay as "still a guest" without executing a formal lease
- Operators relying on platform terms of service for protection — the Association states directly: don't rely solely on platform terms
- Operators who delay filing once a guest overstays, because delay allows the occupant to entrench
The recommended mitigations are revealing:
Cap stays at 29 days or less if no formal lease is in place. Draft written agreements for anything longer, stating occupancy limits and obligations explicitly. Document everything — payments, communications, extensions, side agreements. Serve a Notice to Vacate immediately on overstay. File promptly.
Read that first recommendation again. The advice from a landlord association to operators in a growing category is, effectively: avoid the category, unless your paperwork is airtight.
That's not a legal problem. It's a tooling problem.
The five capabilities that would prevent this
A booking that crosses the 30-day boundary in a jurisdiction like DC requires the management system to do five things automatically:
1. Generate a compliant written lease at the 30-day mark. Not a template in a folder — a jurisdiction-appropriate document, executed and stored against the booking record.
2. Notify the occupant of their changed status, with the rights disclosure the jurisdiction requires.
3. Alert the operator at day 25 to file a Notice to Vacate if the stay is not being renewed — before the entrenchment window opens.
4. Lock the channel manager from auto-extending past 30 days without explicit operator re-approval. Platform auto-extension is how many operators cross the line without deciding to.
5. Maintain audit-grade documentation — timestamped payments, communications, occupancy records — that survives an evidentiary challenge in court.
No property management system on the market does all five. The closest available implementation is a tenant-transition feature in one platform, and the operators appearing in DC case law were not using it.
This is the structural condition of the mid-term category: it inherited software built for nightly stays or annual leases, and the legal boundary between those two models runs straight through the middle of it.
The wider pattern
DC is not unique, it is simply well-documented. The 30-day threshold appears in tenant-rights frameworks across numerous US jurisdictions, with variations in how it's triggered and what protections attach.
California's AB 1482 has its own exemption framework that mid-term operators must navigate — and notably, it applies to properties held in LLCs even when the operator owns a single house, a fact that surprises operators regularly.
New York's enforcement environment has produced its own case law, including a $1.2 million default judgment against a corporate housing operator.
Each jurisdiction draws the line slightly differently. What's consistent is that the line exists, that crossing it changes the operator's legal position materially, and that the software running the booking generally has no awareness of it.
What this means operationally
For an operator running ten units across two states, the compliance surface is already beyond what a spreadsheet can track: different conversion thresholds, different notice requirements, different documentation standards, different filing procedures.
For an operator running fifty units across five states, it is beyond what any individual can hold in their head.
The operators who scale in this category are the ones whose systems know where the boundaries are. Not because compliance is interesting, but because a single conversion event — one guest, one entrenched occupancy, one multi-month court process — can erase a year of margin on a unit.
RentOS is built for the 30-day-plus category specifically: lease generation tied to booking events, jurisdiction-aware documentation, audit-grade records, and the boundary alerts that keep operators on the right side of the line.
FAQ
When does a short-term rental guest become a legal tenant? It varies by jurisdiction, but roughly 30 days of paid occupancy is a common threshold. In Washington DC there is no specific statute; courts evaluate length of stay, payment exchange, exclusivity and control of the unit under the DC Rental Housing Act, and paying for approximately 30 days or more has been sufficient for tenant status to attach — with no written lease and even when the booking was made through Airbnb.
Can a host evict a guest who overstays a 30+ day booking? Not through self-help. Once tenant status attaches, lock changes, utility shutoffs and removal of belongings are illegal. The operator must serve a written Notice to Vacate, file in the appropriate landlord-tenant court, obtain a judicial order, and have it enforced by marshals. Expiration of the booking is not by itself grounds for eviction without that process.
Do Airbnb's terms of service protect operators from tenant conversion? No. The DC Landlord Association explicitly advises operators not to rely solely on platform terms. Platform terms govern the relationship between the host and the platform; they do not override local landlord-tenant law, which determines occupant status independently.
How can mid-term operators avoid tenant conversion risk? Common guidance is to cap stays at 29 days where no formal lease exists, execute written agreements for anything longer with explicit occupancy terms, document all payments and communications, serve a Notice to Vacate immediately on overstay, and file promptly rather than allowing an occupant to entrench. Systematically, this requires software that generates leases at the boundary, alerts before it, and prevents platform auto-extension past it.
Does the 30-day rule apply outside Washington DC? Similar thresholds appear across many US jurisdictions with local variations in triggers and protections. California's AB 1482 has its own exemption framework that applies to LLC-held properties even for single-house operators. Operators running units across multiple states face different conversion rules in each, which is why jurisdiction-aware lease automation matters more as portfolios grow.