Staymaker is live!

Older iPhone? Use Staymaker in your browser.

Why calendar sync can miss a cleaning between adjacent bookings

If a feed turns adjacent stays into one continuous blocked period, the cleaning between them may be missing. Here is how to compare the source, feed and cleaning plan.

The short answer

A calendar import can miss an in-between cleaning if the exported feed represents adjacent stays as one continuous blocked period. Compare the actual source bookings with the relevant feed and the cleaning plan, then add a deliberate manual cleaning if the boundary is missing and no cleaning already covers it.

A continuous block can hide a real handover

Imagine two separate reservations for the same property: one guest leaves on July 8 and the next guest arrives on July 8. A cleaning is needed that day even though the property is occupied on both sides of the handover. In this conditional example, the exported feed shows one uninterrupted block covering both stays. The property appears unavailable throughout, but the date separating the reservations is absent.

An availability block and a guest reservation answer different questions. One can tell you that the property is not available to book without exposing every guest change inside that period. If the export has no record of the internal boundary, a cleaning tool cannot reliably reconstruct it from that block alone. Guessing a checkout date would create a different risk: cleaning the property during a stay.

Compare three places before you change the schedule

Start with the actual reservations in the source system. Confirm that they are separate stays, the departure and arrival dates, the correct property and whether either reservation has changed or been canceled. Do not use the visual shape of a blocked calendar as the only evidence of a handover. A long block could represent one stay, several stays or another kind of unavailable period.

Next inspect the relevant exported calendar feed using the source’s available calendar or support tools. The question is whether the feed contains the handover you confirmed in the reservations. Check the correct export for the correct property, especially when calendars pass through another calendar service before reaching the cleaning tool. Finally, compare that date with the actual cleaning plan. A cleaning could exist on another date or already have been added manually.

Calendar URLs can grant access to the feed. Keep them private and use the tool’s support process if you need help checking one. A useful report names the affected property and dates through the appropriate private channel, rather than posting the complete feed link publicly.

Check a possibly missing handover0/7

Tell a delayed update from a missing boundary

These are different findings. If the source contains the handover and the exported feed contains separate events, investigate whether the receiving tool has the current feed and whether its import has caught up. Use the tools and support information for that connection rather than repeatedly deleting and recreating it. If the correct, current feed already lacks the boundary, another read of the same information cannot reveal what is absent.

Keep the checks specific. Confirm what the source shows now, what the export shows now and what cleaning exists now. An old screenshot may describe the situation before a booking change, while an unrelated feed may belong to a different property. Compare like with like before deciding the problem is a sync delay or a collapsed block.

The table gives you a way to sort the finding. It is a diagnostic guide, not a promise about every calendar service. Import behavior and the information supplied by a connection can differ. What matters for this cleaning is whether the verified guest handover reaches the plan.

What you findWhat to check next
Source and feed both show the separate staysThe receiving connection and the current cleaning plan
Source shows separate stays; current feed shows one blockThe missing boundary, then manual coverage after checking duplicates
Source itself shows a different date or one stayThe actual reservation details before adding a cleaning
A cleaning already covers the confirmed handoverIts property, window and assignment before creating another

Add the missing cleaning deliberately

Once you have confirmed the actual handover and checked for an existing cleaning, create a manual cleaning for the correct property and day. Confirm the real cleaning window, who will do it, the next arrival requirements and the current checklist. Tell the cleaner through your agreed channel, especially if the date is close. Adding an entry alone does not establish that someone is available to complete the work.

The cleaning still needs the same clear instructions as any automatically planned visit. The reference-photo example below shows how a bed setup can remain understandable even when the date was arranged manually. Use the normal property checklist and confirm any stay-specific details you actually know. Missing calendar data is not a reason to guess the guest count, bed use or arrival time.

Record why you added the cleaning in the place your team uses for planning notes. That helps another person understand it when they compare the calendar later. Keep this explanation about the date and the missing handover, rather than copying guest details that the cleaner does not need.

In Staymaker, each checklist step can carry a reference photo, so your cleaner sees how the room should look before ticking it off.

Check again if the imported plan changes

A later feed update or a correction upstream may change the imported plan. Recheck the manually covered handover after that change so one real cleaning does not become two planned visits. Compare property, date and purpose, not just the title. If two entries appear to cover the same work, inspect their assignments and current state before changing anything.

Keep the cleaner informed about the single confirmed plan. A duplicate reminder or two slightly different time windows can create confusion even when the underlying reason is understood. Likewise, if a guest extends or cancels, review the manual cleaning against the new source reservation. A deliberate manual visit needs a deliberate review when the stay changes.

Make adjacent stays part of the planning check

When you review upcoming work, pay attention to stretches with no gap in availability. Compare the actual reservation boundaries for those periods with the cleaning dates. This is particularly useful after you change a calendar route or add another service between the booking source and the cleaning plan. A successful connection test does not by itself prove that every future handover is represented.

If the same kind of missing boundary repeats, ask the source or connection support what the export actually supplies. A direct integration may provide different information, but verify the specific connection before relying on it. Do not assume that a PMS connection is immediate or includes every guest and reservation detail. Choose from confirmed behavior, then keep a practical check for dates that matter.

The useful outcome is one confirmed cleaning for each real handover, with enough time and an available person. The calendar is an input to that decision. When its export lacks a boundary, return to the actual bookings, cover the verified date and keep the manual and imported plan consistent.

For the general calendar-export context, Airbnb’s official help explains availability calendar links and notes that imported calendars depend on the receiving website’s updates.

Airbnb: sync your home calendar with other websites

How to plan enough time for a turnover

The vacation rental cleaning checklist

Keep your cleaning plan and checklist together in Staymaker.

Questions hosts ask

Does a fully booked calendar mean every cleaning is planned?

No. A continuous unavailable period does not, on its own, show every guest change inside it. Compare separate reservations in the booking source with the exported feed and cleaning plan, particularly where one stay ends on the day another begins.

Will refreshing the feed recover a missing checkout date?

A refresh can only read what the current feed provides. If the export still has no internal boundary, the receiving tool cannot reliably infer that checkout from the uninterrupted block. Confirm the reservations and arrange the missing cleaning after checking for duplicates.

Should I add a manual cleaning immediately?

First confirm the real handover and check whether a cleaning already covers it. Then add the missing visit, confirm its window and cleaner, and review it after later booking or feed changes so the manual entry does not duplicate imported work.

Would a PMS connection prevent this in every case?

Verify the actual connection and the information it supplies. Different connections can expose different details, and a direct connection is not a universal promise of immediate updates or complete booking data. Keep the confirmed reservation boundaries as your reference for the cleaning plan.

Sources: Airbnb Help Center, “Sync your home calendar with other websites,” https://www.airbnb.com/help/article/99, reviewed 2026-10-23, supports the general calendar-export and receiving-site update context. It does not establish merged reservations for Airbnb. The adjacent-stay example is a conditional editorial diagnostic scenario from the Staymaker guide brief, not a measured frequency or attribution to a named provider.

Read next

Brief once, for every cleaning

Put the checklist, the photos and the notes in Staymaker and invite your cleaner. They see it all at every cleaning.

Free to start. No credit card.