Multi-track festival schedule

A festival is not one event. It is dozens of sessions running in parallel across several stages and several days — a kirtan tent, a meditation hall, and a yoga barn might all be holding something at the same hour on Saturday afternoon. For an attendee standing at the gate with a paper map or a phone, the schedule is the thing that actually tells them what their day looks like.

BrightStar's festival schedule turns that complexity into a grid: days across the top, stages or tracks down the side, sessions placed where they belong. You build it once, and that same grid becomes both your internal operational plan and the public timetable people read on your event page.

Each session on the grid carries its own details — what it is, who is leading it, where and when it happens, and how many people it can hold. That last piece matters more than it sounds like it should: a sound bath in a small dome and a keynote talk in a main tent are not interchangeable, and the schedule treats them differently because their capacities are different.

Attendees browse that grid and add sessions to their own itinerary, so a ticket holder arrives at your festival already knowing which workshop they're in at eleven and which one they chose over it. Where a session has limited space, signing up is what actually reserves a spot — it isn't a wish list, it's a seat. That single mechanic is also what gives you a real headcount per room instead of a guess based on total ticket sales.

Because the schedule lives in one place, it stays consistent everywhere it appears — the public page attendees check on their phones, your own planning view backstage, and whatever version you print for the info booth. Nobody is working off a version that's a day out of date.

Signup counts per session give you something a general ticket count never could: a picture of which offerings are filling up and which need a nudge before the doors open. That's the difference between finding out a session is oversubscribed when people show up and finding out with enough runway to actually do something about it.

A session with limited space is only as trustworthy as its capacity number. If people could simply show up, a small room would fill past what's safe or comfortable, and the people who planned around that session would be turned away at the door after building their whole afternoon around it. Requiring signup for capped sessions closes that gap — the number of people who've signed up is the number of people who have an actual place, not just an intention.

That also means the count you're looking at as organizer isn't an estimate. It's the same number attendees are drawing from when they decide whether a session still has room, which is what makes it possible to catch a popular offering early and move it to a bigger room while there's still time to make that change.

The schedule and your ticket types are answering two different questions. The schedule describes what is happening and when — the grid of sessions across your days and stages. Your ticket type describes what someone bought to get in the door.

That separation is what lets a single weekend pass sit underneath twenty different sessions without you having to build twenty different tickets, and it's also what lets you sell different passes that open different parts of the programme if that's how your festival is structured. The schedule doesn't care which pass someone holds — it cares which sessions they've signed up for.