Recurring Bookings
Instead of creating the same training or reservation week after week, a booking on 4league's facility calendar can repeat — weekly, every two weeks, or on a custom set of weekdays — and later be edited or cancelled as just one session, this session and every one after it, or the entire series. This page covers building a series, the difference between editing one occurrence and editing the series, and what happens to a session that was already edited on its own or falls inside a closure.
Setting Up a Recurring Series
Recurrence is set on the booking form, right below the date and time, and only ever appears while creating a brand-new booking — once a booking already belongs to a series, its own recurrence is no longer decided from this form (see Editing One Occurrence vs. the Whole Series below). Tap Repeat and choose one of:
| Option | What it does |
|---|---|
| Does not repeat | The default — a single, standalone booking. |
| Weekly | One session every week, on the same weekday as the booking's own date. |
| Every 2 weeks | One session every second week, same weekday. |
| Custom | Pick any combination of weekdays — for example Monday and Thursday for a twice-a-week training slot. At least one day is required. |
Once a repeat option is chosen, two extra fields appear: Series start date (defaults to the booking's own date) and Series end date, which is optional — leaving it empty creates an open-ended series.
Recurrence Summary & Limits
As the rule is built, a one-line summary previews it — for example "Weekly, Mondays · until 30 Jun 2026" for a fixed end date, or "Weekly, Mondays · shown until 30 Jun 2026" for an open-ended one (the display horizon, not a real end — see The 12-Month Display Horizon). Right next to it, a session count spells out exactly how many bookings the rule will create.
| Limit | Detail |
|---|---|
| Series span | Up to 24 months from the series start date when an end date is set. |
| Sessions per series | Up to 500 occurrences. |
| Session length | A single occurrence can't be longer than 24 hours. |
| Time zone changes (daylight saving) | A rule that would land a session on a date/time that doesn't exist because of a daylight-saving change is rejected with the affected dates listed. |
While the rule is being built, the form also checks the real calendar (not just the rule's own math) and warns when some of the sessions it would create fall inside a closure: "N sessions fall in closed periods and will be skipped." Those sessions are never created and never block the rest of the series — only the closed ones are left out.
Editing One Occurrence vs. the Whole Series
Opening or cancelling a booking that already belongs to a series asks first which occurrences the change should apply to:
| Scope | Meaning |
|---|---|
| Only this booking | Changes (or cancels) just the one occurrence being viewed. The rest of the series is untouched. |
| This and future | Applies the change to this occurrence and every later one in the series. Earlier occurrences keep whatever they already had. |
| Entire series | Applies to every occurrence the series' rule governs, past and future alike — except past sessions, which are never rewritten (see below). |
Whichever scope is chosen, a session that has already started or already happened is left exactly as it is. An "Entire series" edit still only ever touches occurrences that haven't started yet.
The dialog also shows how many sessions changed once the save completes — updated, kept as individually modified, cancelled, and newly added — so a broad "This and future" or "Entire series" edit never leaves any doubt about exactly what it touched.
Individually Edited & Skipped Occurrences
A session that was edited or moved on its own — using Only this booking — becomes an individually edited session. From that point on, a broader edit made with This and future or Entire series leaves it exactly as it is instead of overwriting it back to the series' own rule: the point of editing one session by hand is that it's supposed to stay that way.
If a later series-wide edit genuinely needs to reset those sessions too, a toggle appears — Also overwrite individually edited sessions — which resets their time and other fields back to what the rule now produces. It never reactivates a session that was individually cancelled; a cancelled occurrence stays cancelled no matter which scope is used afterward.
FC Thunder books a weekly Monday-evening slot for their U16 squad. One week the pitch is needed for a cup match, so the manager opens that single Monday's booking and moves it to Tuesday using Only this booking. Two weeks later she shortens the whole series' end date with Entire series — the moved Tuesday session is left alone, since it's now an individually edited occurrence, while every other Monday still following the rule is updated normally.
Cancelling One Occurrence or the Entire Series
Cancelling works through the same scope choice as editing. Cancelling Only this booking removes just that session; the series keeps running on every other date. Cancelling with This and future or Entire series cancels every future occurrence covered by that scope in one action, and confirms with a count of how many bookings were cancelled.
A cancelled series (or a series cancelled by a broad "Entire series" cancel) can't be edited or re-cancelled afterward — opening any of its remaining occurrences simply confirms it's already cancelled rather than offering the scope choice again.
The 12-Month Display Horizon
An open-ended series (no end date) is never generated infinitely far ahead — sessions are only ever materialized up to roughly 12 months out. Once the calendar reaches the last generated occurrence of a series that continues beyond that point, a dashed "ghost" block or chip appears right after it, marking that more sessions exist but haven't been scheduled yet. It's purely informational and can't be tapped — the real sessions appear on the calendar automatically as the horizon rolls forward.
Next Steps
What counts as a scheduling conflict, and who can book anyway.
Block a venue or a single pitch for a date range, and how that blocks new bookings.
The full feature overview — the shared calendar, conflict detection, recurring bookings, closures and client appointments.