Short-Term Rental Check-In Instructions That Actually Do Two Jobs

Most hosts have check-in instructions dialed in. Door code. Wi-Fi password. Parking spot. Trash day. It is a good guest experience and it prevents the 10 p.m. "how do I get in?" message.

But those instructions are doing only one job: logistics. There is a second job most hosts never give them, and that gap shows up the moment something goes wrong.

This article walks through what short-term rental check-in instructions need to cover, how to sequence them, and how to add the documented acknowledgment layer that protects you before a guest ever walks through the door.

What Short-Term Rental Check-In Instructions Actually Need to Cover

Logistics come first because they have to. A guest who cannot find the parking spot or cannot get the lockbox open is not in the right headspace to read your rules. So start there.

The logistics layer includes:

• Access: door code, lockbox combo, key pickup location, building entry steps
• Parking: exact spot number or street instructions, any permits needed
• Wi-Fi: network name and password
• Utilities: how to adjust the thermostat, what not to touch
• Appliances: anything non-obvious, the oven igniter, the outdoor shower valve, the TV input
• Emergency contacts: your number, a backup, nearest urgent care if your property is remote

That list is what most hosts send. It is correct and it is necessary. But it is not the whole system.

The second layer is the rules layer. Not a reminder that rules exist. A documented, signed acknowledgment that the guest read them and agreed to them before check-in. Those are different things.

If you have not written your rules out in a form that can be acknowledged, a short-term rental house rules resource is worth reviewing before you build this system.

When to Send Each Piece (and Why Order Matters)

Sequence matters more than most hosts realize.

Before booking is confirmed: Your rules should already be visible in your listing. Guests who book agree to what is posted. That is the baseline, but it is a weak one. There is no record of what they actually read.

Three to five days before check-in: Send the rules acknowledgment. This is the signed layer, not the logistics. You want this done while the guest still has time to ask questions and before you hand over access. Sending rules after you send the door code is backwards. If a guest has already checked in, the acknowledgment is worth much less.

One to two days before check-in: Send the logistics instructions. Door codes, parking, Wi-Fi. This keeps the access information timely and separate from the rules conversation. A guest is more likely to read logistical instructions carefully right before arrival.

Day of check-in: A short, warm confirmation message. "You're all set. Here's my number if anything comes up." That is all it needs to be.

The reason the order matters: you want acknowledgment before access. Once a guest has the door code, your negotiating position on any pre-arrival rule questions is weaker. The sign first, then send the code approach keeps the sequence working for you, not against you.

The Part Most Hosts Skip: Documented Rule Acknowledgment

Sending rules and having proof that rules were seen and agreed to are not the same thing.

If a guest smokes inside, throws a party, or brings an unauthorized pet, the question in any dispute is simple: can you show that the guest knew the rule existed before they arrived? A listing page is not strong evidence. A message you sent is thin evidence. A timestamped, signed acknowledgment is solid evidence.

This is the gap PreArrive closes. Before check-in, guests review your house rules and sign an acknowledgment. PreArrive generates a timestamped evidence certificate tied to that session. If a dispute comes up later with AirCover or a deposit claim, you have a clear record: this guest confirmed these rules on this date, before they had access to the property.

It does not guarantee any outcome. Disputes are decided on the full picture. But documentation gaps are one of the most common reasons AirCover claims fall apart, and a signed acknowledgment directly addresses that gap.

For hosts who have had a claim denied before, the AirCover claim denied guide breaks down what reviewers look for in the documentation you submit.

What to Keep on Record After the Guest Confirms

Once the guest has signed the acknowledgment and you have sent the logistics, your record-keeping is not done. What you document at this stage determines what you can use later.

Keep the following in one place for each reservation:

• The signed acknowledgment and its timestamp, do not let this live only in your email. Download or store it somewhere you can find in 48 hours under pressure.
• Pre-arrival photos, condition of every room, appliances, furniture. Dated and time-stamped.
• The message thread, the full conversation, not just what you remember.
• The access log, if your lock records entry times, export it. This places the guest inside the property at specific times.
• Any mid-stay communication, if you sent a rule reminder during the stay, that is also documentation.

A complete file matters most when something goes wrong fast. You will not have time to reconstruct it after checkout.

How to Handle It When a Guest Ignores Your Instructions

Some guests will not read the logistics. Some will not open the acknowledgment link. Both situations need a plan.

If a guest does not complete the acknowledgment, follow up before sending the door code. A simple message: "Just a heads-up, I need you to review and sign the house rules before I send over the access info. Here's the link again." Most guests do it immediately when they realize access is contingent on it.

If a guest is genuinely unresponsive in the days before check-in, that is useful information. Airbnb and Vrbo both allow hosts to contact support about pre-arrival issues. You are not required to wait until something goes wrong.

If a guest ignores a specific rule during the stay, you need documentation of both the rule and the acknowledgment before you can make a strong claim. If you are in that position now, the guide on what to do when a guest broke house rules covers the step-by-step.

Do not skip the documentation step and expect a good outcome. Reviewers at Airbnb and at insurance carriers see undocumented disputes constantly. Yours needs to stand out for the right reasons.

A Simple Check-In Instructions System You Can Build This Week

You do not need custom software or a complicated setup to run a two-part check-in system. Here is what a working version looks like:

Step 1: Write your rules in a form that can be acknowledged. If your rules are buried in a listing description, pull them into a clear, standalone document. Use plain language. Be specific about fees, quiet hours, pet policy, smoking, and occupancy. The Airbnb House Rules Template is a good starting point if you are building from scratch.

Step 2: Set up an acknowledgment flow. This is where a tool like PreArrive earns its place. Guests receive a link, review the rules, and sign before check-in. The timestamped certificate goes into your reservation file automatically. No chasing PDFs, no hoping a message counts as consent.

Step 3: Separate your logistics message from your rules message. Rules three to five days out. Door codes and parking one to two days out. Keep them in different messages so neither gets lost in the other.

Step 4: File everything after each checkout. Photos, acknowledgment certificate, message thread, access log. One folder per reservation. Thirty minutes of organization now is worth hours in a dispute.

Step 5: Review your rules once a quarter. Rules need to reflect what actually matters at your property. If you added a no-fireworks rule after an incident, make sure it is in the acknowledgment. Rules that are not in the signed document are not in the paper trail.

Check-in instructions are already part of your workflow. Turning them into a two-part system takes one round of setup. After that, it runs on its own before every reservation.