Skip to content
TixFin

Festivals & multi-day

The sale, the site and the crew

Passes, day tickets and camping in one checkout — plus the shift plans, briefings, gates and incident command that make the weekend actually run.

In short

How does TixFin work for festivals?

A festival is two problems: an oversubscribed sale and a multi-day operation. TixFin covers the sale with day tickets, full passes, add-ons and bundles, plus a lottery for fair allocation and FIFO waitlists that release returned capacity automatically. It covers the operation with CrewOps — shift planning, crew profiles, versioned briefings with acknowledgement, run sheets, an incident command centre with SLAs and equipment tracking — and with multiple check-in lists per event so every gate validates its own allowed ticket types server-side.

  • Day tickets, passes, camping add-ons and bundles
  • Several gates, each with its own check-in list
  • Shifts, briefings and incident command in CrewOps

Capabilities

What you get for a festival

  • 01

    Passes and add-ons

    Day tickets, full passes, camping, parking and merch sold together, with bundles that package a ticket and its add-ons at one price.

  • 02

    Lottery allocation

    Configure groups and rules per event, run and re-run the draw as versioned runs, and notify winners and non-winners automatically.

  • 03

    Gate-specific check-in lists

    Several active lists per event, each with its own allowed ticket types, extra capture fields, scan statistics and CSV export.

  • 04

    Temporary scanner accounts

    Door and gate staff get time- and context-limited access without a full account, restrictable to individual check-in lists.

  • 05

    CrewOps

    Shift planning with templates and availability, crew profiles with skills and certificates, briefings with acknowledgement, run sheets and handover notes.

  • 06

    Incident command

    A dedicated queue with escalation levels, response and resolution SLAs, evidence links and automatic timeline logging for the review afterwards.

Event operations

Set up next year from this year

Roles, locations, shifts, briefings, run sheets and shift templates can be copied from a previous event, so a recurring festival is configured once rather than rebuilt annually. Ops analytics then reports fill rate, no-show rate, punctuality and incident distribution for the debrief.

The TixFin event manager with a multi-day festival programme
The TixFin event manager with a multi-day festival programme

Challenges

What multi-day events run into

  • Demand beats the site

    Capacity is fixed by the ground, not by the sale. Fair allocation needs a lottery, not a race to the fastest connection.

  • The crew is bigger than the office

    Hundreds of shifts across stages, gates and camping, staffed by people who need a plan on their phone, not a spreadsheet.

  • Every gate is different

    Crew, press, day tickets and weekend passes must not validate at the same entrance under the same rules.

Workflow

Planning the weekend

  1. 01

    Copy last year

    Bring roles, locations, shifts, briefings and run sheets across from the previous edition instead of starting blank.

  2. 02

    Open the ballot

    Configure the lottery groups and rules, collect public applications and run the draw with a full run history.

  3. 03

    Prepare the gates

    Create a check-in list per entrance with its allowed ticket types and the fields the gate has to capture.

  4. 04

    Run and review

    Work the run sheet live, command incidents from the queue, then read the ops analytics snapshot afterwards.

Key facts

Key facts for festivals

Ticket structure
Day tickets, multi-day passes, add-ons and bundles
Allocation
Lottery with groups and rules, plus FIFO waitlists with auto-release
Entrances
Multiple active check-in lists per event, validated server-side
Crew
Shifts, templates, availability, profiles, briefings, run sheets, handovers
Review
Fill rate, no-show rate, punctuality, incident heatmaps, CSV export

Features

The features behind it

FAQ

Festival questions

  • Yes. Lotteries are configured per event with groups and rule definitions, applicants apply through a public flow with verification, and the draw is executed manually and can be re-run as a versioned run with full history.
  • Yes. An event can run several active check-in lists, each with its own ordering, description and allowed ticket types. The scanner sends the list identifier and the backend validates event assignment, active state and permitted types before accepting the scan.
  • CrewOps provides shift planning with a calendar view, reusable shift templates, crew availability reporting and crew profiles with skills, certificates and preferences. Each team member gets a personal staff hub with their shifts, tasks and briefings.
  • No. Roles, locations, shifts, briefings, run sheets and shift templates can be copied from an earlier event, so a recurring festival keeps its operational configuration.

Plan your next edition

Set up the sale, the gates and the crew plan in one place — and copy it forward next year.