
Mid-stay cleaning requests against turnover capacity
A protocol for comparing mid-stay cleaning requests with the cleaner hours and travel time actually available between scheduled turnovers.
A mid-stay clean competes for the same cleaner hours and travel time as a turnover, so the request should be measured against capacity rather than calendar whitespace.
Methodology
- The unit of analysis is one mid-stay cleaning request attached to one active reservation and one property. A request enters the population when the guest asks for cleaning during a stay rather than at checkout. Requests for a late checkout or an early arrival are excluded and counted elsewhere. Each case carries the property, the stay dates, the requested service, the requested window, and the cleaner assigned.
- Requested service is classified before scheduling as a tidy, a linen change, a bathroom refresh, or a full clean. The classification comes from the guest’s words and the property’s service menu, not from what the cleaner eventually did. A request that changes scope after the first reply is recorded as both the original and the final service. The reviewer keeps the first classification because it explains the capacity planning that followed.
- Available capacity is calculated from the cleaner’s scheduled turnovers, the travel time between properties, and the reset time the property requires before the next arrival. The reviewer records the schedule as it stood when the request arrived, not as it looked after the visit was inserted. A visit that fit only because a turnover was shortened is marked as a capacity override. The report distinguishes a real gap from borrowed time.
- The promised window is the time the guest is told, and the delivered window is the time the cleaner actually arrives and finishes. Both are recorded, along with the notification time if the window changed. A visit that starts late but finishes on time is different from a visit that finishes late and delays the next turnover. The protocol keeps arrival and completion separate.
- Guest presence is recorded because it changes the work. A guest who stays in the unit requires the cleaner to work around them, while an empty unit allows a faster reset. The reviewer notes whether the guest was asked to leave, chose to stay, or was absent without notice. A visit planned for an empty unit but delivered with the guest present is flagged as a planning gap.
- The cost measure is cleaner minutes, not the amount charged to the guest. The reviewer records scheduled minutes, actual minutes, and any overtime or delayed turnover caused by the visit. Minutes are compared with the original turnover plan so the effect on the next arrival is visible. The report avoids converting minutes into labor rates or presenting a local result as a market benchmark.
- Sampling uses every request in the window when fewer than forty cases exist. Above that volume, the frame uses a fixed interval across properties and weekdays, stratified by service type and by whether the stay had a same-day turnover. The frame is frozen before the first schedule is read. Late additions are accepted only to replace a documented error, and the reason is recorded.
- Two reviewers code the first fifteen cases independently and compare the service class, the available capacity, the promised window, the delivered window, and the guest presence. Disagreements are resolved by the operations lead, who records the rule that settles the case. Reliability is reported as the share of matching fields. The cleaner is not asked to reconstruct the visit from memory.
- Guest notification is recorded separately from the cleaning window because a visit can be completed without the guest knowing when it will happen. The reviewer notes the first message that states a confirmed time and any later change. A change sent after the cleaner has left counts as a missed update even when the work was done. The protocol treats communication as part of delivery, not as an optional courtesy.
- The property’s service menu is checked against the work the cleaner is asked to perform. A menu that offers a full clean on a day with two turnovers is a planning conflict before any guest asks. The reviewer records the menu version and the daily turnover load. A property that sells a service it cannot staff consistently is flagged separately from a one-off request.
- The report states the number of requests, properties, cleaners, and delayed turnovers in the window. It also states the share of cases with a confirmed cleaner finish time and the share with an unverified guest schedule. Those conditions limit how far the result travels, and the note says so before offering a recommendation. No local rate is presented as a standard for the wider market.
Findings
- Most mid-stay requests arrive on the day the guest wants the service, which leaves little room to move a turnover. The reviewed cases show the same pattern across properties: a morning message asking for a clean that afternoon. A listing that offers a scheduled mid-stay refresh would shift some of those requests earlier. The protocol reports same-day requests separately because they carry a different capacity risk.
- Full cleans are the service most likely to be promised without a capacity check. The request sounds small in the message, but a full clean takes a cleaner away from the next turnover for a comparable block of time. Properties that classify the service before scheduling show fewer delayed turnovers. The classification is a five-second step that prevents an hour of recovery later.
- Travel time is the most commonly omitted input. A cleaner who appears free for ninety minutes between two properties may have only forty minutes after packing, driving, and setting up. The review marks a visit as an override when the plan ignored travel. Teams that added a travel buffer scheduled fewer visits but delayed fewer turnovers.
- Guest presence adds time in a way that is rarely captured at booking. A guest who works from the unit while the cleaner tidies requires the cleaner to move around them and to wait for access to a room. The reviewed visits with a guest present ran longer than the scheduled window in most cases. The protocol recommends asking about presence before the cleaner is dispatched.
- Requests from guests on longer stays are more predictable than requests from short stays. A guest on a two-week stay can plan a clean a few days ahead, while a weekend guest asks at the last minute. The pattern holds even when the property is the same. The protocol groups by stay length so the scheduling rule can differ.
- The clearest operational repair is a standard mid-stay service window with a cutoff. When the window is stated in the welcome message, guests ask earlier and accept a shorter menu. The local sample cannot establish causation, but the association appears across several properties. A second window after the next seasonal peak is required before the rule is treated as settled.
- A reduced service is often a better answer than a squeezed full clean. The reviewed cases that offered a towel and trash refresh kept the schedule intact and satisfied the guest in most instances. The reviewer codes the offered alternative and whether the guest accepted. The alternative is not a rejection of the request; it is a capacity-aware answer.
- Mid-stay visits are rarely logged in the turnover record, which makes the next request harder to plan. When the visit is logged with scope and minutes, the property can see whether the same guest or property asks repeatedly. The absence of a log turns every request into a first-time event. A short note at the door is enough to build the pattern.
- Cleaners absorb the cost of an unplanned visit through a shortened break or a faster turnover. The review does not measure fatigue directly, but it records whether the next turnover was shortened or delayed. A property that relies on absorbed time should expect a quality problem in the following stay. The report treats the downstream effect as part of the visit, not a separate issue.
- A final check compares the guest message with the cleaner’s instruction. The two can diverge when the coordinator describes a tidy and the cleaner is told to do a full clean. The reviewer codes the mismatch separately from a late arrival. A single confirmation message to both parties would remove the most common source of rework.
Research standards
Every review freezes its observation window before findings are calculated. Reviewers retain a row-level evidence ledger with the original artifact reference, timestamp, responsible role, status at cutoff, correction history, denominator, exclusions, and unresolved cases. Ambiguous records are coded independently before reconciliation, and both readings remain visible until an accountable adjudicator applies a documented rule. Missing information is treated as unknown rather than silently classified as success or failure. Sensitivity checks remove major record classes in turn so a pattern that depends on one owner, channel, event type, or reporting cycle is disclosed instead of presented as stable. Elapsed time is not translated into labor, an association is not described as causation, and local observations are not converted into external benchmarks.
Interpretation begins with counterexamples and the cases still open at the cutoff. A formally complete record may lack usable evidence, while an authorized alternative path may achieve the intended outcome without matching the expected workflow. The review therefore states the strongest alternative explanation, identifies the additional artifact that could distinguish it from the preferred reading, and records what would reverse or retire the resulting operating rule. Comparisons use the same field definitions and equivalent work classes; a material change in coverage, tooling, policy, or sample composition creates a new baseline rather than a trend. Follow-up records name the decision taken, responsible owner, anticipated signal, review date, exception path, and evidence required before a stronger intervention can be justified.
Governance checks keep only information necessary for the research question. Sensitive content is replaced with a controlled reference whenever an authorized reviewer can reproduce the classification without holding a copy. Access boundaries, retention expectations, correction ownership, disputed-interpretation routes, duplicate handling, spanning-record rules, and cutoff treatment are documented before release. Absolute counts appear beside percentages, small samples avoid false precision, and every external statement links to a listed source without implying that the publication measured the local record set. The proposed action must be proportionate, reversible, and reviewable. If the available evidence cannot support it, the gap becomes an explicit evidence request rather than an assumption.
This research note supports the STR Virtual Assistant topical map for vacation-rental guest communication, property readiness, issue routing, and evidence-based operational follow-through.
Sources
- OSHA worker guidanceOSHAChecked 2026-11-10
- OSHA safety and health topicsOSHAChecked 2026-11-10
- CDC hygiene guidanceCDCChecked 2026-11-10
- CDC cleaning and hand hygieneCDCChecked 2026-11-10
- EPA coronavirus guidanceEPAChecked 2026-11-10
- DOL wage and hour recordkeepingU.S. Department of LaborChecked 2026-11-10
- DOL homeU.S. Department of LaborChecked 2026-11-10
- SBA business guideSBAChecked 2026-11-10
- SBA manage your businessSBAChecked 2026-11-10
- NIST Cybersecurity FrameworkNISTChecked 2026-11-10