Calendars & channels

Blocking dates manually

Block off dates for owner stays, renovations, or repairs directly in Rezi.

Updated June 9, 2026 3 min read

Not every block comes from a booking platform. You can manually mark dates unavailable for an owner stay, a renovation, or a deep clean.

Synced feeds only know what their platforms know, and plenty of real-world unavailability never touches a platform: your own week at the lake house, the bathroom remodel, the deep clean between long stays, the direct booking a repeat guest arranged by text. Manual blocks are how that off-platform reality enters the calendar, and entering it is what keeps Rezi’s “yes, it’s available” trustworthy.

  • Add a manual block on the building’s Calendars tab
  • Rezi treats it like any other block and won’t offer those dates
  • If you’ve exported Rezi’s calendar, the block flows to your other channels too

What deserves a manual block

The recurring cast: owner and family stays, block them the moment plans firm up, not when you pack; renovations and big repairs, block the full window including delivery and cleanup days, contractors run long more often than short; turnover buffers, some hosts block a day between long stays for deep cleaning; direct bookings, any stay arranged off-platform must be blocked immediately, since no feed will ever report it; and soft holds, dates you’re tentatively promising someone while they decide. For recurring family scheduling shared with non-Rezi users, a connected Google Calendar can be the friendlier interface for the same outcome.

How manual blocks behave

A manual block is a first-class block in the merge: the AI won’t offer the dates, quotes route around them, and, crucially, no platform sync can ever remove one, feeds can only add blocks, never subtract yours. Manual blocks live until you delete them. Combined with the export mesh, a block entered once in Rezi propagates to Airbnb, VRBO, and the rest within their refresh windows, making Rezi the single place you need to enter off-platform unavailability.

Block before you announce

Add the block first, then tell guests. That way Rezi never accidentally quotes a date you’re about to take offline.

Order of operations matters

The failure mode the callout prevents is a race: you’ve decided the property is offline in August, but until the block exists, Rezi is still cheerfully quoting August to inquirers, and the platforms are still accepting August bookings. Make the block the *first* act of any plan that takes dates offline: before booking your own flights, before the contractor signs, before you tell the repeat guest “it’s yours.” Blocks are free to create and delete, so when in doubt, block early and release later, the inconvenience of an over-blocked date is a question; the inconvenience of an under-blocked one is a canceled guest.

Can I add a note to a block so I remember why it exists?
Label blocks meaningfully when you create them, “Owner stay,” “Bathroom remodel”, so the calendar stays self-explanatory months later.
Who on my team can create and delete blocks?
Anyone with management access to the building, see roles and permissions. Changes are visible in team activity.
Do manual blocks show on Airbnb and VRBO?
Yes, if those platforms import Rezi’s export feed; they’ll show the dates as externally blocked. Without the export connection, manual blocks affect only Rezi’s answers.
What happens if a platform booking already overlaps my new manual block?
Both exist, the calendar shows the conflict rather than hiding it, and you’ll need to resolve it with the guest or your plans. Blocking early is what prevents this situation from arising.

Was this article helpful?

Related articles