# Why should a turnover job never be auto-cancelled within 24 hours of checkout?

Source: https://lemon.cy/learn/never-auto-cancel-inside-24-hours-of-checkout/  
Publisher: Lemon.cy (Red Tribe Media Ltd, Limassol, Cyprus)  
Updated: 2026-09-10 · Verified against production: 2026-09-10

**Short answer:** Because a wrong cancellation the night before a turnover cannot be recovered in time, while a wrong keep costs one wasted visit. Inside 24 hours of checkout, Lemon never cancels a confirmed cleaning job on calendar evidence alone; it flags the booking for the host and keeps the cleaner. This protected 11 jobs in the last 30 days.

## The asymmetry

Every cancellation a calendar-driven tool makes is a guess about why an event disappeared. Close to checkout, the guess has no time to be corrected:

- If the software is wrong and cancels, the cleaner has been told not to come, it is 9 pm, and the next guest arrives at 3 pm tomorrow. Recovering means phoning around.
- If the software is wrong and keeps the job, a cleaner turns up to a flat that was never used and leaves. Annoying, cheap, and visible on the dashboard within the hour.

Lemon's rule 5: **feed evidence alone may never destroy a confirmed job inside the imminent window (24 hours to checkout).** Ambiguity there degrades to host review, keeping the cleaner.

## What "held for review" looks like

The booking gets a "possibly cancelled" badge on the host dashboard and in the host's notifications. The job remains assigned; the cleaner is not contacted. The host can confirm the cancellation with one tap (which cancels the job and tells the cleaner) or press "Keep it". Nothing happens automatically until checkout has passed.

## Why most tools get this backwards

The intuitive design is "the closer the checkout, the faster we must react", which gives imminent bookings the shortest cancellation fuse. That is precisely the window in which the feed is least reliable: Booking.com trims and re-keys in-progress stays continuously, and an in-progress stay is by definition within days of its checkout. Lemon's incident log from 2026 shows every false cancellation with real damage landed the evening before a turnover.

## Evidence

11 `imminent_protected` decisions versus 10 `auto_cancelled` in the 30 days to 2026-09-10 — more jobs were held than cancelled. Source: [feed integrity report](/data/ical-feed-integrity/).

## Related

- [Imminent window](https://lemon.cy/glossary/imminent-window/)
- [When should cleaning software cancel a job because a booking vanished from the calendar?](https://lemon.cy/learn/when-should-cleaning-software-auto-cancel-a-job-from-ical/)
- [Does a booking disappearing from an iCal feed mean the guest cancelled?](https://lemon.cy/learn/is-a-disappeared-ical-event-a-cancellation/)