A three-day festival: the ticket knows its days, the crew its zones

A ticket for all days or for a single day, a three-stage programme in the app and on the website, radios, vests and crew meals by badge. And after the festival — how many people came on each day and to each stage.

  • Example: Northstar Open Air
  • a ticket for one day or all days
  • three stages, three zones
  • crew on badges
  • presence by day and zone
The same tickets screen at the demo summit: Standard, Student, VIP and Online with the active phase, price and number sold
What hurts the organizer

Three days, three stages and a crew in the hundreds

A Saturday ticket turns up on Friday

Security can’t see a date on the ticket. So the gate decides by eye — and differently every time.

The headliner moved by an hour

The app and the website still show the old time. The audience finds out at the stage, when someone else is already playing.

The crew is a festival of its own

Volunteers, sound, light, kitchen, security. Each has their own days, zones, radio and lunch — all of it in different spreadsheets.

Plenty sold. How many came?

Sales are visible; how many people were there on Saturday and where the crowd stood are not. That is exactly what partners ask.

How Aditum is configured

A festival as an Aditum configuration

Days, stages, crew and meals live in the settings of one event. A ticket’s days apply both at the gate and at lunch.

Tickets
  • All days
  • Day 1 · 4 September
  • Day 2 · 5 September
  • Day 3 · 6 September
  • Price phases

A ticket is valid on all days or on chosen ones, in any combination. The days pass to the buyer’s registration and to the Wallet pass.

Programme
  • Main stage
  • Forest stage
  • Small stage
  • In the app
  • On the website

Every stage is a zone with its own programme. A set is published to the app and to the website with separate switches.

Categories
  • Visitor
  • Artist
  • Crew
  • Volunteer
  • Contractor
  • Press

Visitors come with a ticket; crew and volunteers register through closed forms. The category defines the badge and the zones.

Handouts
  • Radios — to be returned
  • Volunteer vests
  • Crew T-shirts by size

A norm per category, an exception per person with a reason. Who hasn’t returned a radio is visible before the shift ends.

Meals
  • Crew breakfast
  • Lunch
  • Dinner
  • Servings per category

The host scans the badge and sees how many servings the person is entitled to and how many were already served. A lunch outside the ticket’s days is not theirs.

Presence
  • Arrivals by day
  • Zone load
  • Retention: day 1 → 2 → 3

Counted from scans at zone entrances. Where nobody scans, there are no figures.

Festival day

Day one through the eyes of the operations team

  1. 09:00
    Console · programme

    The headliner moves to 22:00

    The producer changes the set time in the console, and the app and the website show the new one at once. A push to the audience from the set’s card — and visitors know before they walk to the stage.

    Programme, speakers, partners →
    The same schedule at the demo summit: one zone’s day, sets on a 5-minute grid
  2. 10:30
    Crew desk

    A T-shirt by size, a power bank until the evening

    The welcome kit is for everyone, the T-shirt for the crew only, and the desk sees what is left in each size. Power banks go out to be returned daily: whoever hasn’t brought one back on time lands on a separate list. Anything above the norm needs a reason.

    On-site accreditation →
    The same screen at a demo event: a welcome kit, a crew T-shirt in sizes S–XL, a power bank returned daily and a laptop due at the end
  3. 13:00
    Crew kitchen

    Lunch by badge — no list on the door

    Catering is planned as slots by day: breakfast, lunches, dinner, each with its own serving price and a norm per category. The host scans the badge, and the “served” count grows against the plan. The XLSX servings statement is there to check the restaurant’s invoice.

    Logistics →
    The same plan at a demo event: the restaurant’s slots by day, the serving price, norms per category, served against plan
  4. 17:40
    Gate 2 · Forest stage

    A Saturday ticket on Friday

    Guard shows the refusal and the reason — the argument at the gate is over in a second. If the organizer decides to let the person in, they add a personal exception with a reason, and it shows in the log at once.

    Aditum Guard →
  5. 23:30
    Console · analytics

    How many people stood at each stage

    Arrivals by day, entries minus exits by the hour and zone load are counted from scans at the gates. After day three you see how many came back on days two and three.

    Analytics →
    Presence: arrivals by day, zone load and retention day 1 → 2 → 3

We’ll show it on your festival

Tell us about your days, stages and crew — in a 30-minute demo call we’ll show how it fits into one event.

A 30-minute demo

Tell us about your event — we’ll show it on yours

A demo is a 30-minute call with the team that develops Aditum. Not slides but your scenario: we set up categories, approvals, zones and desks for your event.

  1. Fill in the form: event type, number of participants, a few words about it
  2. Within one business day we email you to agree a time
  3. On the call we show Aditum configured for your event and answer your questions
Or write directly [email protected]
Phone
We’ll call if the email gets lost
By submitting you agree to the privacy policy.