What your calendar does when you are not looking
A Booking.com iCal feed does not describe reservations. It describes closed dates. When the shape of those dates changes — a neighbouring booking arrives, a stay begins, a night is trimmed — Booking.com may re-export the same stay as a brand-new event with a new identifier. To a cleaning schedule that trusts identifiers, the old reservation has vanished and a new one has appeared. Airbnb does it less, but does it.
Lemon measured it. In the 30 days to 10 September 2026, across 18 connected calendars (9 Airbnb, 9 Booking.com), the feeds were read 129,351 times and 540,461 calendar events were observed. Seventy-eight reservations were silently re-keyed — about 4.3 per feed per month. Booking.com also re-exported in-progress stays with the elapsed nights removed on nearly every fetch: 1,240 times in the month.
Why you should care, and why you will never notice
A naive sync cancels the clean when the identifier disappears and creates a new job when the new one appears — or, worse, cancels and does not recreate. Either way a cleaner is stood down for a turnover that is still happening, and the next guest walks into yesterday's sheets. That is the failure mode of every calendar-driven schedule, and it is invisible until it costs you a review.
Lemon's answer is to keep the cleaning job attached to the stay, not to the identifier:
- Identity by checkout. A re-keyed reservation with the same checkout at the same property is recognised as the same stay and its job is kept, with the cleaner still assigned. 78 times last month.
- The check-in is pinned. When Booking.com trims elapsed nights off a stay in progress, Lemon keeps the original check-in. 1,240 times last month.
- Check-in-only changes leave the job alone. Only the checkout drives the clean, so 67 changes to arrival dates touched nothing.
- Real date changes move the job and tell the cleaner: 29 last month.
- A confirmed job within 24 hours of checkout is never cancelled on calendar evidence alone. It is held for you: 11 were held for review last month against 10 automatic cancellations, out of 1,445 decisions in total — 0.7 per cent.
From your side, what you notice is the absence of something. The job stayed. The cleaner came. The dashboard is green.
Every decision is written down
Lemon logs each of those decisions with its reason and keeps a snapshot of every calendar fetch, so when a job does change you can see exactly which line in which feed caused it, instead of guessing. The aggregate is published every month as the OTA Calendar Feed Integrity Report, under an open licence, numbers and method included. Hosts cannot check a claim like "reliable sync"; they can check a table.
What this buys you in a season
Fewer things to think about. The 78 re-keys, the 1,240 trims, the 67 arrival changes: in a WhatsApp-run operation each of those is a possible mistake, a job cancelled by a well-meaning tool or a screenshot mis-read at 23:00. Here they are 1,445 decisions taken by the same rules every time, ten of which resulted in an actual cancellation, and every one of which you could audit if you ever wanted to. You will not want to. That is the point.
Production figures from the September 2026 OTA Calendar Feed Integrity Report (30-day window from 11 August to 10 September 2026).