You wrote the checklist yourself. Twenty-six lines, maybe thirty. Strip the beds, start the laundry, wipe the counters, check under the couch, restock the coffee, angle the throw pillows just so. You sent it to your cleaner in a tidy PDF, felt a small flush of competence, and assumed the problem was solved.
Then a guest checks in to find last week's coffee pods gone and a hair dryer that isn't where the listing photo promised. The checklist said restock coffee. It said confirm amenities. The cleaner is good — she's cleaned for you forty times. So what happened?
The honest answer is uncomfortable: the checklist failed, and the checklist was the part you controlled. Most turnover checklists fail not because cleaners are careless but because of how the list itself is built. And there is a surprisingly deep body of research on exactly this — on why checklists work, when they collapse, and how to design one people actually follow under pressure.
The checklist that couldn't be flown
In 1935, the U.S. Army held a flight competition for its next-generation bomber. Boeing's entry, the Model 299, was the obvious favorite — bigger, faster, longer range than anything else on the field. On its demonstration flight it climbed to about three hundred feet, stalled, banked, and crashed, killing two of the five crew, including the pilot.
The aircraft wasn't defective. The pilot was one of the most experienced in the country. The investigation found he had simply forgotten to release a control lock before takeoff — one step, among the many a far more complex plane now demanded, that his memory dropped at the worst possible moment. A newspaper called the plane "too much airplane for one man to fly."
What Boeing did next is the part worth borrowing. They didn't demand the pilots try harder or train longer. They made a checklist — a short, blunt list of the critical steps for takeoff, flight, and landing. With it, that "unflyable" plane went on to fly millions of miles. The surgeon and writer Atul Gawande later built a whole book, The Checklist Manifesto, around this idea, and around a checklist the World Health Organization introduced for surgery. When hospitals adopted that one-page list of surgical steps, complications and deaths fell measurably across very different countries and hospitals.
The lesson is not "checklists are magic." It's that expertise and memory fail in predictable ways under load — and a well-built list catches the failures. A badly built one just adds noise.
Why thirty good items beat zero bad ones
Here's the trap most hosts fall into. You want quality, so you write everything down. Every preference, every nicety, every lesson from every bad review. The list grows to forty lines because each line, individually, is reasonable.
But human working memory — the mental scratchpad we use to hold and act on information in the moment — is small. Decades of cognitive research, going back to George Miller's famous work in the 1950s and refined since, suggest we can actively juggle only a handful of items at once, not dozens. A cleaner moving through a unit on a 90-minute clock isn't reading your list line by line like a contract. She's working from memory and glancing back. When the list is forty items of equal visual weight, the critical ones — the ones that ruin a stay if missed — drown in a sea of throw-pillow instructions.
Aviation has a name for the steps that cause disaster if skipped: killer items. A flooded toilet, a missing key in the lockbox, a dirty bedsheet, a broken AC in July — those are your killer items. A slightly crooked rug is not. When everything is bolded, nothing is. A checklist that treats "confirm the deadbolt works" with the same urgency as "fluff the cushions" has quietly told the reader that neither matters much.
Read-do versus do-confirm
The people who study checklists for a living draw a distinction that turnover hosts almost never make. There are two kinds of checklist, and they are used at different moments.
A read-do checklist is a recipe. You read a step, you do it, you read the next. It's for tasks you don't have memorized — a new cleaner's first few turns, or an unusual unit with a finicky heater.
A do-confirm checklist is different. You do the work from training and habit, and then — at a deliberate pause — you stop and confirm the critical things are actually done. Pilots don't read "lower the landing gear" and then lower it. They've already lowered it; the checklist is the moment they verify it's down before committing to land.
Most experienced cleaners are doing do-confirm work whether you've designed for it or not. They know how to clean. What they need from you isn't a forty-step recipe; it's a short, ruthless confirmation list at a defined pause point — before you lock the door and leave — that catches the handful of things that end a stay. Trying to force a recipe onto someone who's cleaned the unit forty times feels like distrust, and people route around lists that insult them.
Build the list that survives a bad day
So what does a turnover checklist look like once you take the research seriously? A few principles do most of the work.
Separate the killer items from the nice-to-haves. Put the small number of stay-ruining items in their own short block, visually distinct. Beds made with clean linens. Bathrooms have toilet paper and towels for the next headcount. Kitchen has the consumables you promise. Trash out. Door locks and the code works. That's the list that protects your rating. The throw pillows can live in a separate "finishing touches" section that nobody panics over.
Make confirmation physical, not mental. "Confirm the bed is made" is a thought, and thoughts evaporate. A checklist that asks for a photo of the made bed, the stocked bathroom, the staged kitchen turns a vague intention into an action that leaves a trace. This is the same instinct behind the surgical checklist's spoken confirmations — saying it, or showing it, out loud closes the loop in a way silent intention never does.
Anchor it to a pause point. The most dangerous moment in a turnover is the door closing. Build your do-confirm list so it happens there — the last thing before leaving, not scattered through the clean. That single pause is where forgotten coffee pods and missing keys get caught.
Keep it short enough to be respected. Every item you add to the critical list dilutes the ones already on it. If a line wouldn't generate a one-star review when missed, it doesn't belong in the killer-items block. Demote it.
The list is only half the loop
There's a final piece the 1935 crash makes obvious. The Boeing checklist didn't work because it was printed on nice paper. It worked because it was used, every flight, and because the answers were verifiable — gear down is gear down, observably. A turnover checklist sitting in a PDF a cleaner skimmed once in March is just good intentions in a drawer.
The loop only closes when the critical confirmations actually come back to you, in real time, while there's still room to fix a miss before check-in. A photo of the made bed. A flag that the paper towels hit their last roll. A simple done you can see without chasing it down by text at 2 p.m. between your own meetings.
This is the quiet thing Stayput is built to do: it turns your turnover checklist into a per-property set of confirmations your cleaner answers from her phone — photo-confirm the critical items, automatic restock alerts when supplies run low — so the do-confirm moment at the door actually reaches you instead of evaporating. You stop hoping the list was followed and start seeing that it was. If you're managing turnovers across one property or a hundred, that's the difference between a checklist you wrote and a checklist that works: stayput.lumenlabs.works.