Closures & Maintenance
A closure blocks a venue or a single pitch for a date range — pitch resurfacing, a private event, winter maintenance — so no new booking can land inside it. This page covers creating a closure, what happens to bookings that already overlap it, and how a closure interacts with opening hours and scheduling conflicts. It's the companion to Opening Hours and Conflicts & Overrides.
Same audience as everything else on the facility calendar's write side: an org owner/admin, or staff with the manage facility calendar capability. Anyone who can reach Facilities → Settings sees the closures list read-only; only that same full-access group sees the add/edit/delete actions.
What a Closure Is
A closure is a scheduling block, not a cancellation tool — it stops new or edited bookings from being placed inside it, but it never touches a booking that was already scheduled there before the closure was added. Nothing is auto-cancelled and nobody is auto-notified; a closure only ever answers "can a booking go here?" going forward.
A closure can cover either an entire venue (every one of its pitches, for the whole date range) or a specific facility — optionally narrowed further to one or more zones of that facility, the same halves/thirds a booking itself can be scoped to.
Adding a Closure
From Facilities → Settings → Exceptions / Closures, pick the venue (if the organization has more than one) and tap Add closure. The form collects:
| Field | Notes |
|---|---|
| Date range | Start date and end date, both required. The range is inclusive of both days. |
| Applies to | Entire venue or A specific facility. Choosing a facility optionally narrows further to one or more of its zones; leaving zones unpicked closes the whole facility. |
| Reason | Required free text — shown to anyone with full facility-calendar access, and masked (hidden) for everyone else, same as a booking's own details are masked below full access. |
Existing Bookings & the Overlap Warning
Before a closure is actually saved, the app checks whether any existing, non-cancelled booking already falls inside the range and scope being closed. If it finds any, Save doesn't go through immediately — instead a warning banner lists the overlapping bookings (up to five, with a count of how many more there are), so the person adding the closure sees exactly what they're about to close over. Tapping Save again proceeds and creates the closure anyway.
The warning is informational only. Every overlapping booking stays exactly as scheduled after the closure is saved — the closure and the booking simply coexist until someone deliberately reschedules or cancels one of them.
Changing any field on the form — the date range, the scope, the reason — clears an overlap warning that was already shown, since it answered a question about the previous draft, not the new one; the next Save tap re-checks from scratch.
How a Closure Blocks New Bookings
Once a closure exists, trying to save a new booking, move an existing one, or generate a recurring series occurrence into it is blocked with a "This facility is closed for the selected time" notice, plus the closure's reason when one is visible to the viewer.
Unlike an outside-hours booking or a scheduling conflict, there is no "book anyway" for a closure — not even for an org owner. Checks run in a fixed order: a closure is always evaluated first, before opening hours and before a scheduling conflict are even considered. If a manager genuinely needs to book inside a closed window, the closure itself has to be edited or deleted first — an explicit, deliberate action rather than a one-tap override.
A recurring series treats a closure the same way a single booking does, with one difference: while a person is building or editing a series, any occurrence that would fall inside a closure is simply left out of the series (see Recurrence Summary & Limits) rather than blocking the whole series the way a single booking is blocked outright.
Editing & Deleting a Closure
An existing closure can be edited (date range, scope, reason) or deleted from the same Exceptions / Closures list, using the same full-access permission as creating one. Deleting a closure only removes the block itself — it never touches any booking, including ones that were placed after the closure existed by editing it down to a smaller range first.
Next Steps
Set a venue's weekly hours and per-pitch overrides — and see exactly where a closure fits in the check order.
What counts as a scheduling conflict, and who can book anyway.
Weekly, biweekly and custom series, and editing one occurrence versus the whole series.