# What happens to the cleaning job when a guest gets a late checkout or extends?

Source: https://lemon.cy/learn/late-checkout-and-guest-extension-handling/  
Publisher: Lemon.cy (Red Tribe Media Ltd, Limassol, Cyprus)  
Updated: 2026-09-10 · Verified against production: 2026-09-10

**Short answer:** A late checkout is set by the host on the job; the cleaner receives the new start time and must acknowledge it. An extension changes the checkout date in the calendar; Lemon picks it up on the next five-minute sync, moves the job, and tells the assigned cleaner. A change to the check-in date alone never touches the job.

## Late checkout (same day, later time)

The host opens the job and sets a late checkout time. Lemon stores it on the job (`lateCheckoutTime`), sends the cleaner an update — "A late checkout has been set for today. Your new cleaning start time is 13:00. Please acknowledge" — and notifies the host's team (`late_checkout_set`). The job keeps its cleaner. If the new start time collides with the cleaner's next job, the dashboard flags it.

## Extension (checkout moves to a later date)

The platform changes the reservation; the iCal feed shows a later `DTEND`. On the next sync Lemon applies the date change (`date_change_applied`): the job is rescheduled to the new checkout, the cleaner is told the before and after, and the host receives `booking_date_changed`. If the cleaner cannot do the new date they decline from the link and the cascade restarts.

Two guards apply. If the feed flips between the old and new date within 48 hours, that is oscillation and the job is not reset. And if the change arrives within 24 hours of the original checkout, the change is applied but the confirmed job is protected from being destroyed on feed evidence alone.

## Early departure (checkout moves earlier)

Handled the same way as an extension, in the other direction. The job moves earlier and the cleaner is told; if the new date is today, the offer becomes urgent.

## Check-in changes

A change to the check-in only — the guest arrives a day later, or Booking.com trims the elapsed nights of an in-progress stay — is logged (`checkin_only_change`) and does nothing to the job. Only the checkout drives the clean. In the 30 days to 2026-09-10 there were 67 check-in-only changes and 29 real checkout changes.

## Related

- [Checkout-driven scheduling](https://lemon.cy/glossary/checkout-driven-scheduling/)
- [Why does a Booking.com iCal booking's check-in date move forward every day during the stay?](https://lemon.cy/learn/forward-trim-booking-com-in-progress-stay/)
- [Why does my synced checkout date keep flipping between two dates?](https://lemon.cy/learn/ical-date-oscillation-checkout-flip-flop/)
- [How are same-day turnovers scheduled?](https://lemon.cy/learn/same-day-turnover-scheduling/)