Short Term Rental Lease Agreement: What It Covers and Where It Stops

You listed your property on Airbnb or Vrbo. You wrote out your house rules. You may have even drafted a short term rental lease agreement to send guests before they arrive. That is more than most hosts do.

But when a dispute lands on your desk, the question is never "did you have rules?" It is "can you prove this guest saw them, read them, and acknowledged them before they walked through the door?" Those are different questions, and a lot of documentation setups answer the first one while leaving the second one wide open.

This article walks through what platform terms cover, what a short term rental lease agreement adds, where it stops, and what you need on top of it to make a dispute file hold together.

What Platform Terms Actually Cover (and What They Skip)

When a guest books through Airbnb or Vrbo, they agree to that platform's terms of service. Those terms set rules for how the transaction works: cancellation, payment, basic guest behavior standards, and what happens when something goes wrong through the platform's own resolution process.

What platform terms do not do is document that your specific guest read your specific rules for your specific property. There is no record inside a booking confirmation that says "Guest reviewed the no-smoking policy, the noise curfew, and the $150 unauthorized pet fee, and acknowledged all three." The booking just records that a reservation was made.

That gap matters. When you file a claim through the Airbnb Resolution Center or open an AirCover case, the platform looks at evidence tied to your listing. A platform-level agreement is not a substitute for property-level documentation.

What a Short-Term Rental Lease Agreement Adds

A short term rental lease agreement is a document you create and send to guests separately from the booking. It typically spells out the specific conditions of their stay: check-in and checkout times, occupancy limits, pet policies, smoking rules, noise expectations, fee schedules for violations, and anything else you want acknowledged in writing.

Done well, it adds real value. It names the property and the dates. It lists your rules in detail. It may include fee amounts that the listing page mentions only briefly. It gives you a document you wrote, not one the platform wrote on your behalf.

For specific rule language and fee structures worth including, the guide on itemizing STR fees that hold up covers how to write those sections so they are clear enough to reference in a dispute.

A lease agreement also gives you a paper trail artifact. If you ever end up in small-claims court rather than a platform dispute, having a signed document that lists your rules is far better than having nothing. (Whether a specific clause is enforceable in your jurisdiction is a legal question, not one this article answers. Talk to a local attorney for that.)

Where a Lease Agreement Still Falls Short

Here is where most hosts hit a wall.

A lease agreement is only as strong as the proof that the guest received it, opened it, and acknowledged it before the stay began. If you emailed a PDF and the guest never replied, you have a sent email. You do not have confirmation of receipt. You do not have confirmation of review. You do not have a timestamp showing the acknowledgment happened before check-in.

The short term rental house rules PDF article covers this distinction directly: delivery and proof are not the same thing. A PDF in an inbox is not the same as a signed acknowledgment with a timestamp.

There is also the question of what "signed" means. A reply email saying "sounds good" is thin. A DocuSign with a name and date is stronger. But even then, the document has to reach the guest at the right point in the process, and you have to be able to show when it happened relative to check-in.

The Delivery and Acknowledgment Problem

This is the core problem with most host documentation setups, and it affects lease agreements as much as anything else.

Timing matters. If a guest can argue they never saw the document, or saw it only after they had already arrived, the acknowledgment loses most of its weight. Platforms and courts generally want to see that a guest had a fair opportunity to review the rules before they committed to entering the property.

A signed agreement sent two hours after check-in is evidence of almost nothing.

The vacation rental check-in agreement article explains how the timing of acknowledgment shapes how useful the document actually is. Getting a signature is step one. Getting a timestamped signature before the guest gets the door code is a different thing entirely.

There is also the question of which guest signs. For group stays, the booking guest may acknowledge the rules, but the person who caused the damage was their cousin who drove separately. Your documentation should be as specific as possible about who is covered and under what terms.

How to Stack Your Documentation So It Holds Up

No single document wins disputes on its own. What wins is a documentation stack where each layer fills a gap the others leave.

Here is what a solid stack looks like:

Your listing rules. Written clearly in the listing itself so there is a record the rules were published. For help writing them, the Airbnb additional rules examples guide covers language that actually travels into a dispute file.

Your lease agreement. Detailed, specific, and sent to the guest in advance of check-in. Covers fees, occupancy limits, specific prohibitions, and anything else material to how you run the property.

A signed, timestamped acknowledgment before the door code goes out. This is the layer most hosts skip. A guest clicking "I have read and agree" inside a message thread is not the same as a documented, timestamped acknowledgment that you can produce as evidence.

PreArrive was built for this last layer. Before a guest gets the check-in code, they review and sign an acknowledgment of your house rules. PreArrive produces a timestamped evidence certificate tied to that specific stay. When a dispute comes up, you have a record that shows exactly when the guest acknowledged the rules, not just that you sent them. That certificate does not guarantee any particular outcome, but it closes the gap that sinks most claims: proving the guest knew.

For a closer look at how that process fits into a pre-arrival workflow, sign first, then send the code explains the sequencing.

A Simple Checklist for Getting This Right

Run through this before each stay:

• Rules in the listing. Are your house rules published in the listing itself, not just in a separate document you send later?
• Lease agreement sent in advance. Is your short term rental lease agreement delivered before check-in, with enough time for the guest to review it?
• Specific fee language included. Does the agreement spell out the dollar amounts for violations like unauthorized pets, extra guests, or smoking? Vague language is harder to enforce.
• Timestamped acknowledgment on file. Do you have a record that the guest acknowledged the rules, with a timestamp that shows it happened before arrival?
• Pre-stay photos documented. Does your documentation stack include condition photos taken before check-in? A vacation rental turnover checklist can help make this consistent.
• All of it stored where you can find it. When you need to file, you need to find everything fast. Keep your evidence in one place.

A short term rental lease agreement is a meaningful piece of that stack. It is not the whole stack. The hosts who win disputes are the ones who built the whole thing before anything went wrong.