Short Term Rental Check in Workflow

The first time you ran a check-in, it probably looked like this: you got the booking, you sent a long welcome message with the door code buried in paragraph three, you forgot to set the thermostat, the guest texted you at 9pm because the lights wouldn’t turn on, and then you spent 45 minutes on the phone walking them through a switch panel you’d never actually used yourself. Multiply that by 80 bookings a year and you understand why hosts burn out.

A clean short term rental check in workflow takes that whole improvisation and turns it into a sequence: every device, every message, every fallback in a fixed order, all firing without you. This page is the actual template — not a generic set-up-automation pep talk, but the literal steps and timing I’d hand to a new cohost on day one.

Who this template is built for

Remote hosts running one to ten properties. First-time STR investors who haven’t yet hired a manager. Cohosts who inherited a portfolio with messy, inconsistent processes across each door. Anyone who has ever forgotten which property has which lock model.

The template assumes you can’t be on-site for check-in, you don’t want to babysit your phone, and you’d rather spend 4 hours wiring this once than 4 hours per month re-explaining the same thing to guests. It does NOT assume you have a property management company, a complicated home automation hub, or any coding skills. The whole thing runs on consumer apps, off-the-shelf gear, and your existing Airbnb or Vrbo listing.

What this workflow is actually solving

Three problems, in order of how often they ruin reviews:

The guest can’t get in. Wrong code, dead lock battery, app glitch, no lockbox fallback. This is the single most common 1-star trigger.
The guest gets in but the property isn’t ready. Cold rooms, dark entryway, no WiFi password, no idea where the trash goes. Second most common.
The host is reactive instead of proactive. You learn about a problem because the guest texted you, not because your system told you. By that point, the review is already half-written in their head.

The workflow below collapses all three into a single repeatable pattern. Same template every booking, every property.

Prerequisites: gear and apps before you start

You need these items installed and paired to a single account before this workflow does anything. If you’re missing one, fix that first and come back. The self check-in automation playbook compares the lock options head to head if you haven’t picked one yet.

WiFi-capable smart lock with keypad: Schlage Encode Plus, Yale Assure Lock 2 (WiFi), or August Wi-Fi Smart Lock with the existing deadbolt. Avoid Bluetooth-only.
Smart thermostat: Ecobee Premium, Nest Learning Thermostat (4th gen), or Honeywell T9 — whichever your HVAC system supports.
Two or three smart bulbs or plugs: Philips Hue, Lutron Caseta, or TP-Link Kasa KP125 for entry, kitchen, and bedroom.
PMS or scheduled messaging tool: Hospitable, Hostfully, OwnerRez, Guesty, or native Airbnb scheduled messages for one property.
Outdoor doorbell camera: Ring Battery Doorbell Plus, Eufy Video Doorbell E340, or Nest Doorbell. Indoor cameras are off-limits per editorial policy and Airbnb policy — outdoor only.
Physical lockbox with backup key: not advertised, kept for the day a battery dies.

The workflow, in order

Here is the full sequence for a 4pm check-in. Adapt times to your booking but keep the order. This is the same pattern that powers most professional automated check-in setups for short-term rentals, just stripped of vendor jargon.

Stage 1: Booking confirmed

PMS auto-creates a unique 4-digit code from the guest’s phone last 4 digits.
That code is pushed to the Schlage or Yale lock with a window of check-in day at 2pm through checkout day at 11am.
A confirmation message goes out within 5 minutes thanking them and confirming dates. NO door code in this message.

Stage 2: Day before check-in

Scheduled message at 9am with parking instructions, exact address, map link, and one operational quirk if the property has any (the driveway is the second gravel one on the right).
That message ends with a heads-up: the door code will arrive about an hour before check-in tomorrow. This trains the expectation.

Stage 3: Check-in day, climate ramp

2pm: Ecobee or Nest ramps from vacant preset to comfort preset. Aim for the property to be at target temp by 3:30pm.
If sunset is before 6pm in your market, the entry TP-Link Kasa plug or Hue bulb turns on at sunset minus 30 minutes.

Stage 4: One hour before check-in

The arrival message is the most important touchpoint of the entire stay. The guest arrival routine playbook covers the exact wording, but at workflow level:

Arrival message fires at 3pm. Door code first, lock-model name (Schlage or Yale) so they know which button to press, WiFi network and password, parking spot, one operational note, signoff.
If the guest hasn’t replied or unlocked by 90 minutes after their stated check-in time, you get an alert in your PMS dashboard, NOT a panic notification.

Stage 5: Door unlock event

The lock fires its first valid-code unlock. Doorbell camera optionally confirms a person at the door.
Kitchen smart plug turns on (delay 30 seconds so the entry isn’t a jump scare).
15 minutes later, a follow-up message asks if everything looks good. Most guests say yes; the few who don’t, you catch early.

Stage 6: Settling in

90 minutes after first unlock, a final auto-message goes out with the local recommendations PDF or a short list (coffee shop, grocery store, late-night food).
You stop hearing about this booking until checkout time. That’s the goal. The Airbnb departure automation walkthrough picks up at the other end and runs the same play in reverse.

Testing it before guests see it

Do not deploy any of this without a personal dry run. Block your calendar for 24 hours, use a friend’s account to book the property, and walk through the entire workflow as if you were a guest.

Did the booking confirmation message land on time?
Did the door code arrive exactly one hour before check-in?
Did the lock open on first try with the correct code?
Was the entry lit at the actual moment you walked in?
Was the temperature within 2 degrees of the comfort preset?
Did the WiFi credentials in the message actually work on first try?

Every host who runs this dry run finds at least one broken thing. Usually two. Fix them, run it again, then go live.

Fallback plan when the workflow breaks

Things will break. Internet outages, dead lock batteries, PMS hiccups. Build the fallback in advance and tell the guest about it ONLY when something goes wrong.

Physical lockbox with a metal key, mounted somewhere not visible from the street.
A real phone number that rings, separate from Airbnb messaging, listed in the welcome book inside the property.
A trusted neighbor or local cohost who can drive over within 30 minutes if you cannot.
The lock’s manual battery-pack jumper option. Buy a 9V battery and clip it inside the welcome book.

Privacy and the guest experience

Run the workflow with the same rules every time: outdoor doorbell camera fine, indoor cameras and microphones never. If you have noise concerns, use a Minut sensor or NoiseAware Indoor Outdoor monitor and disclose them in your house rules. Guests are fine with monitoring as long as they know about it. They are not fine with surveillance.

Common mistakes

Sending the door code at booking. They lose it. Send it one hour before check-in.
Hardcoding 4pm everywhere. Late check-ins become fire drills. Tie everything to the booking’s actual times. The late check-in automation guide covers the past-midnight version of this in detail.
Skipping the dry run. Always test before guests do.
Building a 12-step welcome book that nobody reads. Three operational notes max in the arrival message; everything else lives in the property in printed form.
Forgetting to brief your cleaner on the workflow. They are part of the system.

Host checklist

Schlage Encode or Yale Assure Lock 2 paired and generating dynamic codes per booking.
Ecobee or Nest with vacant + comfort presets, tied to actual booking times.
Three smart bulbs/plugs minimum: entry, kitchen, bedroom.
Six scheduled messages: booking confirmation, day-before, arrival, post-unlock, 90-minute settling, checkout reminder.
Doorbell camera (outdoor only).
Lockbox + emergency phone line + neighbor contact.
Battery-check task in cleaner’s recurring checklist.
Quarterly self-test booking documented in your calendar.

FAQ

How does this workflow handle multiple properties?

The same template runs across each property because it’s gear-agnostic at the workflow level. Per-property differences (parking quirks, lock model name, WiFi name) live as variables in your PMS message templates, not as separate workflows. If you find yourself cloning workflows per property, you’ve over-customized. Standardize the gear and standardize the messages, and one workflow scales to 30 doors without breaking.

What if the guest checks in much later than scheduled?

Build the workflow so late arrivals are normal, not exceptional. The door code is valid until checkout day, the thermostat holds comfort temp until the lock fires, and the entry light runs on sunset. The only thing that triggers the no-show alert is the absence of any unlock event after, say, 12 hours past stated check-in. The dedicated arrival automation guide walks through the timing for delayed flights and late arrivals.

Is self-check-in automation worth it for one property?

Yes, even at one property. The lock alone pays back in the first guest who arrives at 1am. The thermostat pays back in the first July or January utility bill. The scheduled messages pay back the first time you don’t have to type the WiFi password from a beach. The total gear cost is about $400-500. Most hosts recoup it in a single month of saved time and avoided utility waste, regardless of door count.

Can I use AI to customize this workflow for my property?

Yes. Try: I host a [property type] in [city]. Average guest is [profile]. Check-in time is [time]. Adapt this short term rental check in workflow to my property: [paste the steps]. You’ll get back tuned timing for your climate, message wording for your audience, and gear suggestions calibrated to your property tier. Verify the lock-model and PMS-specific details against the actual app docs — AI is solid on sequencing, less reliable on exact UI clicks.

How often should I update the workflow?

Run a self-test booking once a quarter. After 90 days, gear updates and app changes will have introduced at least one small break: a message that no longer fires, a setting that got reset by an app update, a lock whose battery is sneaking toward dead. The quarterly cadence keeps you ahead of these instead of finding them through a guest’s complaint.

Next steps

Print the host checklist above and run it as a real audit on your most-booked property this week. Anything you can’t tick off is your next project. The Airbnb check-in and checkout automation hub indexes the rest of the cluster, and the Airbnb automation pillar ties this workflow into messaging, pricing, and turnover.