Glossary/Checkout-driven scheduling

Glossary · OTA calendar behaviour

Checkout-driven scheduling

Definition

The principle that only a booking's checkout determines the cleaning job. A change to the check-in alone never resets a job, never drops a confirmed cleaner and never fires a "dates changed" message, because the clean happens on the day the guest leaves.

Also called: rule 4, checkout anchor

Term defined by Lemon.cy · verified 2026-09-10 · Markdown

Checkout-driven scheduling is rule 4 of Lemon's sync and the reason its booking identity is anchored on the checkout date (rule 1). Forward-trims move the check-in daily; merges move the check-in; a guest arriving a day late moves the check-in. None of those change when the flat needs to be cleaned. In the 30 days to 2026-09-10 Lemon logged 67 check-in-only changes that did nothing to any job, against 29 checkout changes that rescheduled one.

The principle also decides what a cleaner is told. A check-in change produces no message, because nothing about the cleaner's day changed; a checkout change produces one message with the old and new time. Late checkouts are the one exception in the same direction: the checkout stays on the same day but the start time moves, so the cleaner receives the new time and is asked to acknowledge it.

Cite this page. Lemon.cy (2026). "Checkout-driven scheduling". Verified against production on 2026-09-10. https://lemon.cy/glossary/checkout-driven-scheduling/