Schedules let you define your venue's availability once and reuse it across multiple tickets, instead of configuring recurrence ticket by ticket.
1. What is a schedule
A schedule is a reusable availability configuration. You define when your venue is open, add seasonal changes, mark one-off closures or special events, then link your tickets to it. The system generates time slots automatically based on the schedule's rules.
Why use schedules:
Avoid duplicating recurrence rules across tickets that share the same hours
Update seasonal hours in one place, not ticket by ticket
Handle closures and special events without editing every ticket
Keep availability consistent across multiple tickets, and across multiple venues if you operate more than one
Priority order when slots are generated:
Exception > Period adjustment > Base.
If a date is covered by both a period adjustment and an exception, the exception wins. If no exception applies, the period adjustment wins over the base.
2. Limitations to know before you start
Before you create your first schedule, check that your use case is supported.
Limitation | What it means |
Only recurring simple tickets | Schedules can only be linked to recurring simple tickets (time-based capacity). Tickets with a seating plan cannot be linked to a schedule yet. This is coming in a future release. |
Only newly created tickets | Schedules apply to tickets you create from now on. Your existing tickets stay on the legacy availability logic. They will not break and will continue to work as before. Migrating an existing ticket to a schedule is opt-in and done with the help of your account manager in the future. |
One schedule per ticket | A ticket can be linked to only one schedule at a time. |
Locked slots are never touched | Slots with active bookings are never modified, deleted regardless of any change you make. |
Generation horizon | Slots are generated up to 365 days ahead by default. A daily job extends this horizon automatically. |
3. Create a schedule
📌 How to access: Products > Schedule manager > Create schedule
Enter a name and a description. The name must be unique for your venue.
Choose your availability mode:
Always open: your venue operates by default. Add exceptions for closures.
Open during specific periods only: your venue is closed by default. Add open windows for the dates you operate.
Open by default with seasonal closures: open most of the year, with defined closed stretches.
The schedule stays in draft status until it is linked to a ticket and slots are generated for the first time.
4. Define your base
The base is your normal operating pattern.
Set the following fields:
Days of the week (multi-select)
Time window (start and end time)
Duration of each slot
Break between slots
The slot frequency is calculated automatically from duration and break, and shown to you before saving.
You can add more than one base to the same schedule, for example a morning pattern (Mon to Fri, 09.00 to 12.00, 30-minute slots) and an evening pattern (Mon to Fri, 17.00 to 20.00, 60-minute slots). Each base is independent. Two bases cannot generate slots at the same date and time, this is flagged as a blocking conflict.
The base has no start or end date, it is always active unless overridden by a period adjustment.
5. Add a period adjustment
Use a period adjustment to override your base for a specific date range, such as summer hours, winter hours, or school holidays.
Set:
Valid from and valid until dates
New time window
New duration (optional, inherits from base if not set)
New break (optional, inherits from base if not set)
Examples:
Summer hours: 01.06 to 31.08, extend to 21.00, shorter break
Winter hours: 01.10 to 31.03, start at 10.00, smaller window
Two period adjustments cannot have overlapping date ranges. A period adjustment can extend beyond your base time window, this is allowed and not flagged as a conflict.
6. Add exceptions
Use exceptions for one-off changes on a specific date.
Full day closure: blocks the entire date. No slots are generated. Add a date and an optional reason (for example "Bank holiday", "Maintenance day", "Private buyout").
Partial day closure: blocks a time window only. Slots outside the window stay available. If a slot starts before the closure window and ends after it, the slot is blocked entirely, it is never split. This protects you from situations such as a guide starting a tour that cannot be completed.
When you save an exception, you are always asked:
"This exception applies to:
All tickets linked to this schedule
Only a specific ticket"
This is a mandatory choice, there is no silent default. This protects you from accidentally closing tickets you did not intend to affect.
7. Add an extra session
An extra session creates a one-off slot that does not exist in your base or any period adjustment, for example a special evening show on a date you would normally be closed.
Set:
Date
Start time
End time
Reason (optional)
Difference between exceptions and extra sessions:
Exception modifies or removes a slot that already exists
Extra session creates a slot that did not exist before
The system blocks an extra session if a slot already exists at the same date and start time for the same ticket. Change the start time or remove the existing slot first.
If an extra session lands on the same date as a closure exception, the extra session takes priority. The closure still applies to all base slots, only the extra session runs. A warning is shown.
8. Preview your schedule
Before linking any ticket, you can preview your full schedule from the schedule detail view.
The preview shows:
A calendar view of all slots that will be generated, colour-coded by source: base, period adjustment, exception, extra session
A summary of total slots, date range, and how each rule contributes
This is the right moment to check that your schedule matches what you expect, before you link any ticket.
The system also runs conflict detection automatically:
🔴 Blocking conflicts must be resolved before you can link a ticket (overlapping bases, overlapping period adjustments, duplicate slots).
⚠️ Warnings require your explicit confirmation but do not block (for example, slots that fall outside your venue's operating hours).
9. Link tickets and generate slots
📌 How to access: Products > Tickets > Create Ticket > Date and Time
Slots are generated when you link a ticket to the schedule, not before.
Create a recurring simple ticket .
Optionally set a duration override for that ticket. Use this when several tickets share the same schedule but each runs for a different length, for example a 60-minute general admission, a 90-minute guided tour, and a 45-minute kids workshop, all sharing the same start times.
Save .
Duration resolution priority (highest to lowest):
Ticket duration override
Period adjustment duration
Base duration
Generation runs asynchronously in the background, up to 365 days ahead. You can keep working, you will be notified when it is complete.
✅ Locked slots (with bookings) are never modified or deleted, under any circumstance.
10. Edit your schedule
📌 How to access: Schedule detail > Edit
Any change to a base, period adjustment, exception, or extra session shows an impact summary before applying:
Future unbooked slots that will be updated
Locked slots that will not be touched
Tickets affected
Date from which changes apply
11. Duplicate, archive, or delete a schedule
Duplicate: copies all bases, period adjustments, exceptions, and extra sessions to a new draft schedule named "Copy of [original name]". Linked tickets, generated slots, and version history are not copied.
Archive: stops generating new slots, cancels future unbooked slots, keeps locked slots bookable, and unlinks all tickets. Archived schedules can be restored, but cancelled slots are not regenerated automatically. Use this when a schedule is no longer needed but you want to preserve its history.
Delete: permanent. Only available if the schedule has no locked slots. If it does, archive instead. Deletion removes the schedule, its configuration, and all future unbooked slots.