Conflicts & Overrides
Every booking against a pitch — a training, a match, a team reservation, a client appointment — is checked against everything else already on that pitch's calendar. This page covers what counts as a scheduling conflict, what the conflict warning looks like, when the Book anyway override is offered, and who is allowed to use it.
What Counts as a Conflict
Two bookings conflict when they're on the same facility, their zones overlap (a booking on the full pitch conflicts with one on either half of it; two bookings on different halves don't), and their times overlap once the venue's changeover buffer is added on both ends. The changeover buffer is a venue-level setting — "free time between two consecutive bookings on the same facility" — configured from Facilities → Settings; with it set to zero (the default), two bookings that end exactly when the next one starts are back-to-back and do not conflict.
A cancelled booking never conflicts with anything, and a booking never conflicts with itself while being edited.
The Conflict Warning
Trying to save a booking that overlaps another one shows a warning banner right on the form: "<Facility> is already reserved between <start time> and <end time>." Tapping an existing conflict indicator on the calendar itself opens a similar read-only view titled "Overlaps with", listing every booking the tapped one collides with.
What a conflicting booking's own row shows in that list depends on the viewer's calendar access: someone with full visibility sees its type, title and team; a masked booking (visible to a lower access level) shows only a generic Reserved label; and a plain busy block (no bookable detail at all) shows as Busy. Either way, the fact that a conflict exists is never hidden — only the level of detail about the other booking changes.
Who Can Override a Conflict
A Book anyway button appears on the conflict warning only when both of the following are true:
| Condition | Detail |
|---|---|
| The viewer has full facility-calendar access | An org owner/admin, or staff with the manage facility calendar capability — the same audience that can edit opening hours and closures. A team admin booking their own team's training does not qualify, even for a conflict against their own team's other booking. |
| The server marks that particular conflict as overridable | Both conditions are required together — having full access alone doesn't add a Book anyway button if the conflict itself isn't flagged overridable, and vice versa. |
Without both, the same red banner is shown with no Book anyway action: the booking simply can't be saved at that time until the conflict is resolved some other way (picking a different time, a different pitch or zone, or cancelling/moving the booking it collides with).
FC Thunder's academy coach tries to book Tuesday 18:00–19:00 on the main pitch, not noticing the first team already has a training booked for 18:30–19:30. The form shows the overlap banner — her team-admin access doesn't include an override, so she picks a free slot instead. The facility manager, who does have full calendar access, later needs to squeeze in a one-off session at the same overlapping time for a cup preparation; the same banner shows for them too, but this time with a Book anyway button, and confirming it saves the booking alongside the existing one.
Closures, Hours & Conflicts — the Order Checks Run In
A booking is checked against three things, always in the same fixed order:
Closures
Never overridable, checked first. A closed time blocks the save outright, regardless of who's booking.
Opening hours
Checked next. Outside-hours bookings can be acknowledged and confirmed by someone with full access; everyone else is blocked the same way a closure blocks them.
Scheduling conflicts
Only checked once a time is inside opening hours (or acknowledged) and outside every closure. This is the check this page covers.
This fixed order means a person is never asked to override a conflict, or acknowledge an outside-hours slot, only to then discover the time was closed all along. Whichever blocker applies first is the only one shown.
Conflicts in a Recurring Series
Creating or editing a recurring series checks every occurrence the rule would produce (or the change would touch) as one batch. If any occurrence in that batch conflicts with something else, the whole batch is rejected — the series is never saved with only some of its sessions written and the conflicting ones silently skipped. The same "Book anyway" permission applies to override it: with full access and an overridable conflict, confirming writes every occurrence in the batch at once, including the ones that were flagged.
Who Sees a Conflict at All
A small conflict indicator can appear next to a booking elsewhere in the app — for example in the Facilities Overview dashboard's list of today's bookings. That indicator is only ever populated for a viewer with full facility-calendar access; below full access the field is left out entirely, the same masking convention applied to a booking's own details throughout the calendar.
Next Steps
Block a venue or a single pitch for a date range, and how that blocks new bookings.
Set a venue's weekly hours, per-pitch overrides, and booking outside opening hours.
Weekly, biweekly and custom series, and editing one occurrence versus the whole series.