Why closures do not take effect, and the other problems that come up.
Last updated
Check the closure status. If it says Pending, it was never confirmed and it blocks nothing. Confirm it. This is by a distance the most common cause.
If it says Confirmed or Active, check the window dates against the bookings getting through. A booking at 7pm on the last evening is usually a window that ends earlier in the day than you assumed.
The ticket has no scheduled start and end date yet. Set the schedule, then link the amenities. The closure window comes from the work, so there is nothing to close until the work has dates.
Only amenities set up for the property appear. If it is missing, it has not been created yet, or it belongs to a different property than the ticket. Check the ticket is on the property you think it is.
The confirmation step offers the choice between cancelling overlapping bookings and only blocking new ones, and it defaults to showing you what it found first. Contact the affected residents directly and rebook them. Paid bookings are refunded automatically, so the money side is already handled, but the conversation still needs to happen.
Cancellations notify only the residents who had bookings. Everybody else learns nothing. For a closure of any length, post news as well, and include the date the amenity returns.
Revisit the closure rather than leaving it to run its window. An amenity closed for three days it did not need is a genuine loss of service that residents notice and remember.
Extend the closure before the window ends if you possibly can. Once a window lapses, bookings can be taken again immediately, and the first one is often that same evening.