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

Late checkout (same day, later time)

The host opens the job and sets a late checkout time. Lemon 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. 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 guest extends on Airbnb or Booking.com and the platform's calendar shows the later checkout. Within about five minutes Lemon moves the job to the new date. The cleaner is told the old and the new date, and you get a message too. If the cleaner cannot do the new date, they decline from the link and Lemon offers the job to the next cleaner.

Two safety rules apply. If the calendar keeps switching between the old and the new date, Lemon does not keep moving the job back and forth. And if the change arrives in the last 24 hours before the original checkout, Lemon applies it but keeps the confirmed job in place rather than cancelling it.

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

If only the arrival date changes, for example the guest arrives a day later, nothing happens to the job and the cleaner gets no message. Only the checkout decides when the clean happens.

Technical details

• A late checkout is stored on the job as lateCheckoutTime; the team notification is late_checkout_set.
• An extension shows up as a later DTEND in the iCal feed. Lemon logs date_change_applied and the host receives booking_date_changed. A decline restarts the cascade.
• If the feed flips between the old and new date within 48 hours, that is treated as oscillation and the job is not reset. A change within 24 hours of the original checkout is applied, but the confirmed job is protected from being destroyed on feed evidence alone.
• A check-in-only change, including Booking.com trimming the elapsed nights of an in-progress stay, is logged as checkin_only_change and does nothing to the job. In the 30 days to 2026-09-10 there were 67 check-in-only changes and 29 real checkout changes.