A weekly class, a three-night run, a season of home fixtures and a festival weekend are all one event with many dates, and treating them as one is what keeps the admin sane. This guide covers how multi-date events work on tickts, what each date carries, how a run looks to a buyer, the tools that only make sense once you have more than one date, and the two traps that catch organisers at multi-day events.
One event, many dates
Every event can have one date or a hundred. Each date carries its own venue, its own start and doors time, its own ticket types and capacities, and its own sales close time if you want one. The buyer sees one page with every date on it, each with its own price and availability, and picks the night. You get one set of settings, one description, one link to promote, and a Sales view that can be read per date or across the run.
Adding a run
- By hand for a handful of dates: add a date, set its time and tickets, add the next. The first date's venue and tickets are the template for the ones that follow, so a ten-night run is ten clicks, not ten forms.
- Clone a finished event to start the next run with the venue, the tickets and the settings already in place.
- Import fixtures, in Club mode, from a link to your league's fixture page; tickts reads the season and builds the home dates, cup ties marked so they can sit outside the season pass.
What a buyer sees
The event page lists the dates with their prices. A date that has sold out says so honestly and offers the waitlist; a date with a few left can show "last few" if you switch that on, and never a fake one. When prices differ between dates, the page says "From" the cheapest until a date is picked, then shows that date's exact price. Each ticket is tied to its date: a Friday ticket admits on Friday and through the night until 6am, not on Saturday.
Tools that only matter with more than one date
| Tool | What it does |
|---|---|
| Per-date sales close time | Close online sales early for a night you want to manage by hand, or keep an all-day event selling online through the day instead of stopping at its start time |
| Per-date label | "Day 1", "Preview", "Gala night", shown beside the date in the list |
| Per-date waiver | A notice buyers of that date must tick, such as a preview performance warning, without touching the other dates |
| Overall capacity per date | Caps every ticket type combined at what the room holds that night |
| Season and weekend passes | One purchase across the run, admitting once per date, with cup ties in or out; a Pro feature in Club and Festival modes |
| Calendar | Every date across every event in one diary, by month, week or list, with a booked-against-capacity bar, and a feed you can subscribe to in Apple, Google or Outlook |
Changing a date after tickets have sold
Edit the date from the Events list. If tickets have sold, every holder is emailed the new date and time automatically and their wallet passes update on their phones within a few minutes. Their tickets stay valid for the new date. If a whole run moves, do it once per date; if a single night is called off, cancelling that date refunds its holders without touching the rest.
Reading the run
On the Events list each date's bar shows how it is selling in colour, orange until three-quarters sold, amber after, and red at sold out, so you can see which nights need pushing without opening the numbers. Sales can be exported per date, and the door list is printed per date, which is the one you want on the door that night rather than the whole run.
Two traps at multi-day events
An all-day festival that starts at noon comes off sale online at noon. Set a custom sales close time on each date, for example 23:59, and walk-ups can keep buying on their phones all day. It bit a real festival on its first day this month.
At the gate, one scanner offline and one online is fine; two offline at once can each admit the same weekend pass before they sync. Keep one phone online where you can, and read the scan log the next morning.
Recurring classes and courses
A term of classes is a run of dates with the same venue and the same ticket. Sell a pass covering the sessions, or a ticket per session, or both; the pass wording on the page can be set to "Sessions" so parents are not told their camp pass covers "all home fixtures". Set the venue once and it applies to every date, and use the calendar's diary entries for the private bookings and holds that do not sell a ticket but still take the room.
