What Happens in the Four Hours Between Checkout and Check-In

The most dangerous four hours in a short-term rental operation are the ones between checkout and check-in. Not because anything is usually hard about them. Because a lot of things have to happen in sequence, and when one falls behind, everything after it falls too.

A guest who checks out at 11:03 instead of 11:00 is not a problem. A cleaner who shows up at 11:15 and takes two and a half hours is not a problem. A new guest whose early check-in request you forgot to turn down is a problem, one that shows up at 1:30 expecting to walk into a clean unit.

Multiply this across three or four properties on a busy Saturday and you've got a coordination challenge that most operators handle through group texts, phone calls, and glancing at their phone between other things.

That works until it doesn't.

What has to happen before check-in

Most operators know the list. What's worth spelling out is who owns each item and when it needs to happen, not just that it needs to happen.

The checkout reminder goes out the night before or morning of, reminding guests of the checkout time and what to do (garbage, towels, any physical keys). This one is easy to automate.

The lock code rotation is trickier. If you're using a smart lock, you can schedule the outgoing guest's code to expire at checkout time automatically. If you're not, you're either trusting the guest to lock up and not caring whether the code stays live, or manually rekeying after every stay.

The cleaning slot needs to be confirmed before the day starts. If your cleaner is unavailable, you need to know at 8am, not at noon when you text to check in. A confirmed turnaround estimate is the dependency everything else rests on.

Thermostat reset. Pool heat deactivation (or pre-activation if the incoming guest paid for it). Any maintenance flagged during the stay. These are easier to forget on a busy day and more likely to generate a complaint if they're missed.

And finally: when does the new guest's lock code activate? When does the check-in information go live in the portal or welcome message? This should happen at a specific time, not "after the cleaner texts you."

The three things that go wrong

The first is the late checkout. Guests who stay past checkout usually aren't being malicious; they lost track of time or assumed you wouldn't notice. A message the evening before and a reminder at 9am eliminates most of this. A polite "we have guests arriving this afternoon and the cleaning crew needs access" covers the rest. What it doesn't cover is the guest who is simply non-responsive, which requires a more direct check.

The second is the early check-in collision. This happens when you've told someone you'll try to get them in early, the cleaner runs behind, and now the new guest is texting from the parking lot at 1pm. The fix is not promising early check-in you can't guarantee. If you offer it, offer it with a confirmed window: "ready by 1pm if the cleaner is done, I'll message you to confirm." If you don't confirm it, the guest assumes it's happening.

The third is the manual dependency chain. If the flow is cleaner texts "done" → you change the lock code → you send check-in instructions → guest arrives, you've created a process where every step waits on a human. One missed text delays the chain. On a day with four properties turning over, you'll miss something.

When the cleaner runs over

A two-and-a-half-hour clean on a property with a three-hour window is fine. A three-hour clean on the same property is a problem.

The useful thing is not to panic, but to make a decision at 90 minutes in: is this going to finish on time? If yes, hold the check-in time. If no, contact the incoming guest before they're already in the car. A "we're running about 45 minutes behind, checking in at 3:45" message sent at noon lands very differently than the same message sent at 3:15.

For automated guest messages to cover the check-in sequence properly, the timing has to be flexible enough to account for a delayed ready time. A static "you can check in at 3pm" message that goes out at noon regardless of cleaning status creates its own problem.

What the incoming guest experience should look like

The check-in information shouldn't be available before the unit is ready. If the gate code and door code are visible in the portal and the cleaner isn't done, a guest who shows up "a little early" will let themselves in and be standing in the middle of a cleaning. Fixable, but awkward.

A staged portal handles this by showing the access codes only after a confirmed ready time. The guest gets a link at booking, they check it during the pre-stay period, and the specific access information appears at the right moment. If the property uses smart locks, the door itself is the gate: it won't open before the code activates, so a guest who taps the keypad at 2:58 is not inside the property.

Building the checklist

No matter how much of the sequence is automated, a turnover day benefits from a confirmation loop. A checklist per property per turnover: cleaner confirmed, cleaning complete, codes rotated, thermostat at arrival temp, pool heat running or confirmed off, check-in instructions live. Someone checks off each item. If an item isn't checked by a certain time, there's a flag.

For properties with smart home devices, half that list is confirmed by the devices themselves: thermostat state, lock code status, whether the cleaner triggered motion events after checkout. The remaining items are the ones that still need a person.

The properties that run same-day turnovers without chaos aren't the ones with the most generous windows. They're the ones where the dependencies are explicit, ownership is clear, and nothing waits on a text that might arrive late.