Cleaning schedule automation for short-term rental hosts

For two and a half years I ran my apartments' cleaning schedule on a single shared Google Sheet. One column per property, one row per day, an emoji for "needs cleaning". My cleaner had a phone bookmark to the sheet. We never lost a turnover.

We also did not scale. The Sheet was held together by my Tuesday-evening reminder cycle and her willingness to scroll on a 5-inch phone screen. The day I added a third apartment, the Sheet needed colour coding, then a separate tab per cleaner, then a cell formula I cannot read three months later. That is when I started looking at proper cleaning-schedule automation, not because the Sheet had failed but because it was the third apartment that broke the pattern.

This is the post on what to actually automate, what to leave manual, and the cleaner-role flow that I now think every host should adopt by their second property.

The actual problem with a shared spreadsheet

A shared Sheet works because it is a list. The trouble is that the list has no view-by-cleaner mode without filters, and filters in Sheets are the kind of thing that breaks the moment your cleaner taps the wrong cell.

Three specific things go wrong as you grow:

1. Different cleaners need different views. Cleaner A handles studios; cleaner B handles family villas. Filters and tabs only work if everyone disciplines themselves not to break each other's view. They do not.
2. Status is fuzzy. "Done" written in green text by Tuesday evening could mean done at 09:00 or done at 14:00. Time of completion matters when you have a 15:00 check-in.
3. History is invisible. "Did the kitchen sink leak last month?" requires scrolling back through cells that were re-edited every week. The original note is gone.

A purpose-built cleaning module fixes each of these by inverting the data model. Instead of a 2D grid where you read across, the cleaner sees a list of their tasks for today, ordered by check-in time. The host sees a dashboard of all turnovers across all cleaners. Same data, two views.

You do not need a $200/month tool to get this. Even our free RentTools instance has a cleaner-role flow, and it is not a unique idea. Smoobu, Hostaway, Lodgify: every paid PMS has the same primitive. The point is to use some purpose-built thing rather than a Sheet.

What a cleaning schedule needs to track

Resist the urge to track everything. The schema that fits on the back of a napkin handles 95% of cases.

For each turnover:

1. Property: which apartment.
2. Date: the cleaning day, derived from the previous booking's checkout date.
3. Time window: earliest start (after checkout) and latest end (before next check-in).
4. Assigned cleaner: the human responsible. One only; if it falls through, escalate.
5. Status: pending → in progress → done. Optional: "issue found", which pings the host.
6. Notes: free text, cleaner-authored. Short.
7. Photos: 0-3 attached. Pre / post / damage.

That is it. Resist adding "expected duration", "checklist of 47 sub-tasks", or "supply inventory". Each of those starts as a good idea and rots into noise that nobody reads.

The cleaning checklist debate is real. My take: a checklist is a separate document from the schedule. The schedule says "this needs cleaning by 14:00"; the checklist says "what cleaning means at this property". Keep them separate. Print the checklist, tape it inside the supply cupboard. Put the schedule in your tool.

For a worked example of how to think about scheduling under sync lag and double-booking risk (which directly affects when a turnover even appears in the schedule), see our cheat sheet on avoiding double bookings.

The cleaner-role flow (no host login required)

The cleaner does not need a host account. Giving them one is a mild security risk (they can see every booking detail) and a UX disaster (the dashboard is not designed for their job).

The right pattern is a dedicated cleaner role. Three rules for what it sees:

1. Today's tasks first. Tomorrow's tasks below the fold. Not a calendar grid; a chronological list.
2. The cleaner's own properties only. If they clean three of your six, they should not see the other three.
3. One action per row: a Done button. Tap, confirm, done. Optional: "report an issue" link beside it.

Authentication is the part hosts overthink. The cleaner does not need a password. A persistent magic-link cookie on their phone is enough; they bookmark https://yourtool.example/cleaner/abc-token-xyz, the cookie keeps them signed in for a year, and rotation invalidates the link the moment a cleaner stops working with you.

If you self-host, this is roughly an afternoon of work. If you use a hosted PMS (RentTools, Smoobu, Hostaway), the flow ships out of the box.

Photos and notes: when to ask and what to capture

The optional photo upload is the single feature that makes a cleaner-role flow earn its keep. Two photos per turnover gives you:

1. Pre-clean. Ten seconds the cleaner takes when they arrive: the state the previous guest left. Settles 90% of "the previous guest broke X" disputes when the next guest reports it.
2. Post-clean. The state the apartment is in when the cleaner finishes. Settles damage claims when a guest checks in and reports broken furniture that was fine four hours ago.

You do not need a polished photo. A phone snap of the bed and a phone snap of the bathroom is enough. File it, forget it, retrieve only when something disputes.

Notes go in two flavours. Cleaner notes ("dishwasher tablets are out", "guest left a coat") are quick text fields. Issue reports ("AC unit is leaking, pinged maintenance") are the same field with a flag that emails or pings the host immediately. One field, two semantics, set by a checkbox.

Resist demanding a photo of every checklist item. The cleaner's time is finite, and if every turnover needs 30 photos, they will photograph blank walls to satisfy the rule. Two real photos beat thirty fake ones.

WhatsApp is a chat tool, not a system of record

Every host I have talked to in Tashkent runs a WhatsApp group with their cleaners. So do I. The mistake we all made for too long was treating that WhatsApp group as the source of truth for cleaning status.

WhatsApp is good for:

• Quick "I'm running 30 minutes late" messages
• Photos of unusual damage that need a host opinion
• Coordination during a change (different cleaner today; supply order issue)

It is bad for:

• "Is apartment 3 cleaned?" with the answer scrolled past two days ago
• Tracking which turnovers were skipped in February
• Onboarding a new cleaner without forwarding 600 messages

Use WhatsApp for chat. Use the cleaning module for status. The two should never compete for the same job. When a cleaner asks "did you mark the apartment cleaned?" in WhatsApp, the right answer is "I don't track that. Your Done button does. Did you tap it?"

This is a cultural shift more than a technical one. It takes maybe a week of discipline before the cleaner stops sending "done" messages and starts trusting their tap-the-button workflow.

One opinionated take

The single biggest cleaning-schedule mistake hosts make is putting the cleaner on the host calendar. They show their cleaner the full booking dashboard, all properties, all guest names, every checkin time. The cleaner is overwhelmed, the host has shared more data than they meant to, and somehow nobody is happier.

Give the cleaner a list. Today. Done button. That is the whole interface. If your current tool cannot give them that, switch tools, or build the role yourself in an afternoon. The two-and-a-half years I ran on the Sheet were good years; they would have been better years if I had built the cleaner-role view in month four.