Short Term Rental House Rules PDF: Delivery Is Not the Same as Proof

Most hosts have a short term rental house rules PDF. They attach it to a booking message, drop it in a guidebook app, or paste a link in the check-in instructions. That part feels handled.

It is not handled. Sending a PDF proves you sent it. It does not prove the guest opened it, read it, or understood what they were agreeing to. When a dispute lands in front of Airbnb support or a small-claims judge, "I sent it" is a weak foundation. This article walks through how to build something stronger.

What a Short Term Rental House Rules PDF Should Actually Contain

Before worrying about delivery, the document has to be worth delivering. A vague list of preferences will not hold up when you need it most.

A solid short term rental house rules PDF covers these areas:

Occupancy. Maximum number of guests allowed, whether day visitors count, and what happens if that number is exceeded. If you charge an Airbnb extra guest fee, state the amount and when it applies.

Noise and quiet hours. Specific hours, not just "be respectful." Include any local ordinances that apply, and note that local rules are subject to change, confirm current requirements with your city.

Smoking and substances. Where smoking is prohibited, what the fee is if someone violates the rule, and whether that applies to vaping or cannabis. See our Airbnb smoking fee guide for how to frame this clearly.

Pets. Allowed or not, with any fees or restrictions spelled out.

Parking. Number of vehicles, where they park, and any towing policies.

Check-in and check-out times. Exact times, not windows. Include what happens if a guest overstays.

Property-specific rules. Pool hours, hot tub rules, trash and recycling procedures, thermostat limits, and anything else specific to your property.

Fees for rule violations. State each fee by name, amount, and trigger. Vague language like "additional charges may apply" is nearly impossible to enforce. For more on structuring fees that can survive a dispute, see itemizing STR fees that hold up.

Keep the language plain. Short sentences. One rule per line. If a guest has to read a sentence twice to understand it, rewrite it. For additional phrasing examples, Airbnb additional rules examples covers common rule categories with language that reads clearly.

Why Sending a PDF Is Not the Same as Proving Receipt

Here is the gap most hosts do not notice until they are already in a dispute.

When you attach a PDF to a message thread, you have a record that you sent the file. You do not have a record that the guest downloaded it, opened it, or read past page one. Email and messaging apps do not track that. Most guidebook tools do not either.

If a guest says "I never saw that" or "I didn't know that rule existed," your sent message does not disprove the claim. Airbnb support cannot confirm the guest read an attached file. A small-claims court will not assume receipt just because you can show a sent timestamp.

The legal standard for enforceability varies by jurisdiction, and this article is not legal advice. But practically speaking, the difference between "I sent it" and "they acknowledged it" is enormous. One is a paper trail. The other is a starting point.

This is the same problem that makes AirCover claims get denied even when hosts are clearly in the right. The documentation gap, not the merits of the case, is usually what collapses a claim.

Three Ways Hosts Typically Deliver House Rules (and Where Each Falls Short)

1. Attachment in the booking confirmation message

Common, easy, and almost invisible to guests. Airbnb's message thread is not designed to surface attachments. Many guests book on mobile and never tap a file attachment. You have no record of whether they opened it.

2. Guidebook or welcome app (Touch Stay, Hostfully, etc.)

Better than an attachment in terms of readability. These tools present rules in a formatted, easy-to-browse layout. But most do not generate a timestamped record of when a specific guest viewed specific content, and almost none require the guest to actively acknowledge the rules before receiving the entry code. The information is there if the guest goes looking for it.

3. Paste rules into the Airbnb listing or check-in message

Guests can see the rules before booking, which is useful. But Airbnb does not generate a confirmation that a guest read the additional rules section, only that they completed booking. A completed booking is not the same as a signed acknowledgment.

Each of these methods moves information toward the guest. None of them close the loop on confirmation.

How to Build a Delivery and Acknowledgment System That Creates a Paper Trail

The goal is a workflow where you can point to a specific record and say: this guest, at this timestamp, reviewed these rules and confirmed they understood them.

That requires a few things to work together:

Structured rules, not a wall of text. The guest needs to be able to move through the document in a way that shows engagement. A wall of text does not support that.

A required acknowledgment step before check-in. The guest should not receive the entry code or door code until they have completed the acknowledgment. This is the mechanic that turns a passive delivery into an active confirmation. Sign first, then send the code covers the logic behind this sequencing in more detail.

A timestamped record of the acknowledgment. Date, time, and a link to the exact version of the rules the guest reviewed. This is the document you produce if a dispute arises.

Storage somewhere you can retrieve it. A record that lives only in your email inbox is fragile. Keep a copy in a folder organized by booking or property.

Building this manually is possible. You can use a PDF form with a signature field, email it, and keep a copy. The friction is real, though, and it scales poorly across multiple properties or booking platforms.

What a Timestamped Evidence Certificate Adds to Your PDF Workflow

This is where PreArrive fits into the picture.

PreArrive is built specifically for short-term rental hosts who want a documented record that a guest reviewed and acknowledged the house rules before check-in. The guest works through the rules, confirms they have read and understood them, and PreArrive generates a timestamped evidence certificate tied to that booking.

The certificate is not a contract. It is not legally binding in any formal sense. It is evidence, a record that the guest saw the rules before they walked in the door. When you are dealing with an AirCover claim, a security deposit dispute, or a property damage situation, that record is what separates "I told them" from "here is proof they knew."

For more on how the evidence side of this works, Airbnb damage claim evidence walks through what a complete documentation file looks like and where most hosts have gaps.

If your current workflow relies on a guidebook app but you want to add an acknowledgment layer, PreArrive is designed to sit alongside what you already use, not replace it.

The Bottom Line: Delivery Plus Documentation

A short term rental house rules PDF is only as useful as the record attached to it.

Write rules that are specific, readable, and organized. Deliver them before check-in, not after. And build in an acknowledgment step that produces a timestamped record you can actually produce when you need it.

Delivery is step one. Documentation is what protects you when something goes wrong.

For hosts who want to understand the full picture of what a guest acknowledgment record looks like and how it fits into a dispute workflow, the vacation rental guest acknowledgment form guide is a good next read.