Somewhere tonight a guest is standing in your kitchen at 10:40 a.m., suitcase by the door, reading your checkout list on their phone. Strip the beds. Start the dishwasher. Take out the trash and recycling. Wipe the counters. Gather the towels. Turn off the AC. Lock the windows. Somewhere around item five, something in them gives up. They grab their bag, leave the key, and go. They meant to be good guests. They might even have done everything if you had asked for less. Here's the part most hosts never hear: the length of that list may be what made them quit.
This isn't a story about lazy or entitled guests. It's about a predictable thing people do when they feel told what to do, and how a few changes to the wording can turn a list people resent into one they finish.
The quiet rebellion behind ignored checkout lists
In 1966 the psychologist Jack Brehm proposed what he called psychological reactance: when people feel their freedom to choose is being threatened, they get motivated to take it back. Often they do that by refusing the request, or doing the opposite, even when the request was reasonable and they would happily have done it unprompted.
You've felt this. A sign that says Absolutely no food or drink makes you want a coffee. A coworker who reminds you three times to send the file makes you want to send it a little later. The request isn't outrageous. The pressure is, and the reaction is aimed at the pressure, not the task.
Checkout lists set this off very reliably, for a few reasons.
The guest has already paid. In their head the deal is finished. They paid a nightly rate and probably a cleaning fee. A long list of chores feels like you're changing the terms after the fact, which reads less as a request and more as being asked for free labor.
The tone is often imperative. Lists get written in commands because commands are short: Strip beds. Empty fridge. Do not leave dishes. Short is efficient. It also sounds like a sign in a breakroom.
The volume signals distrust. Seven instructions say something the host never meant to say: I expect you to leave a mess. People tend to live up, or down, to what they think is expected of them.
Then the guest makes a quick, half-conscious choice. They don't think I refuse. They think this is a lot, and they do the two things that are easy and skip the rest. Or they do none of it, as a small private way of reclaiming the morning. Either way, the list that was meant to protect your turnover has made it worse.
Why 'because' does so much of the work
One of the best-known findings in social psychology is a modest experiment by Ellen Langer and her colleagues in the late 1970s. A researcher asked to cut in line at a busy photocopier. When the request included a reason, even a weak one, people agreed noticeably more often than when there was no reason at all. Giving some explanation changed how the request felt.
Later research has added caveats. For bigger asks, the reason has to actually be a good one. But the basic idea holds up, and it fits reactance theory well: an explanation turns a demand into a shared problem. It tells the other person you see them as an adult who can understand why something matters, not a subordinate taking orders.
Compare these two:
Strip all beds before leaving.
Our cleaner has about three hours before the next family arrives, so pulling the sheets off the beds is the single biggest help you can give her.
The second one is longer, and it gets done more often. Now the guest isn't doing a chore for a faceless host. They're helping a specific person meet a specific deadline. That's a reason people are glad to act on.
There's a second, quieter benefit. When you have to write a reason for every item, you find out which items don't have one. Wipe the counters has no good reason behind it, because wiping counters is what you're paying the cleaner for. Asking guests to do the cleaner's job, half-heartedly, doesn't save anyone time. It just creates something to argue about.
The short list that actually protects your turnover
The real question isn't what would I like guests to do? It's what can only the guest do, or what does the guest do much more cheaply than anyone else?
That list is almost always short:
- Things that save the cleaner real time. Pulling sheets and gathering towels in one spot can save meaningful minutes on a tight same-day turnover.
- Things that prevent damage or cost. Turning off the heat or AC, closing windows if rain is coming, not leaving food that will spoil in an unplugged fridge.
- Things that only the guest can tell you. Anything that broke, spilled, or stopped working. This is the most valuable item on the list, and most lists leave it off.
That last one deserves a moment. A guest who mentions the shower drain was slow at checkout is giving you hours of notice your cleaner wouldn't otherwise have. They only do it if asking feels safe: no blame, no threat about the security deposit, just tell us so we can fix it before the next people arrive. Treat it as a favor and not a confession, and you'll hear about problems you would otherwise have found through a review.
Everything else, like dishes, counters, sweeping, or the pile of recycling, belongs in a separate category: nice if you have a minute, never expected. Some guests will do it anyway. People often reciprocate when they feel well treated, and a host who asks for little tends to get more than they asked for.
What this has to do with the cleaner
It's easy to think of checkout instructions as a guest-relations issue. They're really a cleaner-relations issue.
If the guest ignores a seven-item list, the cleaner walks into the leftovers: beds still made, trash full, a fridge of half-eaten takeout. They're behind before they've started. Worse, they never know which version of the house they'll get. Some days guests did everything, some days nothing, and they can't plan their time either way. That kind of unpredictability wears people down more than hard work does.
A short, reasoned list makes the cleaner's arrival far more consistent. Beds are stripped and towels are in the tub is something they can almost count on. That predictability is worth more than an occasional bonus of wiped counters.
Your next moves
- Rewrite your checkout list tonight, capped at three items. For each one, finish the sentence this matters because… If you can't write a real reason, delete the item.
- Change every command into a reason plus a request. Swap Strip the beds for Our cleaner has a tight window before the next guests, so pulling the sheets is the biggest help. Use the cleaner's first name if they're comfortable with it.
- Add one line asking guests to report anything that broke or isn't working, and say plainly that there's no penalty. For example: If anything broke or isn't working, just reply here so we can fix it before the next arrival. Accidents happen and we'd rather know.
- Move the nice-to-haves into a clearly optional line, or drop them. If you have a spare minute, a quick rinse of dishes is always appreciated, but never expected.
- Ask your cleaner which single guest task would help them most, and put that first. They know better than you do what costs them twenty minutes.
Making the morning predictable
A good checkout list does one thing: it makes the cleaner's next three hours predictable. Stayput is built for the other half of that job. Each property gets its own cleaner SMS when a turnover starts, photo confirmation when the beds are made and the bathroom is done, and a restock alert when the coffee or toilet paper runs low. So you know the house is ready without having to ask. If you've been trying to fix your turnovers by asking guests to do more, it may be worth asking them to do less and closing the loop with your cleaner instead. You can see how it works at stayput.lumenlabs.works.