A guest list sounds like one list, but the moment your event has a backstage, a green room, a crew-only store, or a VIP area, it is really several lists wearing one name. A general attendee should reach the main rooms. A crew member needs the back corridors but has no business in the VIP lounge. A VIP gets the lounge but not the equipment store. A contractor needs the loading bay for two hours and nowhere else. Run all of that on a single undifferentiated list and you are relying on door staff to remember who is who, which works right up until it does not.
Access tiers are how you turn one crowd into a set of clearly defined groups, each with a defined reach. Done on paper, this becomes a stack of separate lists that nobody can keep in sync. Done properly, it is a single system where each person carries one pass, and that pass knows where its holder is allowed. The aim is not bureaucracy. It is so that the person on the green room door can glance at a pass and know, without judgement or memory, whether this person belongs.
Start from the spaces, not the people
The common mistake is to design tiers around job titles, which multiply endlessly and overlap. The cleaner approach is to start from the spaces that need controlling and work back. List the areas with a restriction, the main floor, backstage, VIP, crew store, loading bay, and then ask which groups need each one. The tiers fall out of that almost automatically, and they stay small because most events have only a handful of genuinely restricted spaces.
A typical structure ends up looking like this:
| Tier | Reaches | Does not reach |
|---|---|---|
| General attendee | Main floor, public areas | Backstage, VIP, crew store |
| VIP | Main floor, VIP lounge | Backstage, crew store, loading bay |
| Crew | Main floor, backstage, crew store | VIP lounge |
| Production / contractor | Backstage, loading bay, by time window | VIP lounge, main floor at peak |
The exact rows differ by event, but the discipline is the same: a small number of named tiers, each defined by where it reaches, rather than a sprawl of one-off exceptions. Exceptions are where access control quietly dies, because each one is a thing a door person has to be told and remember. Our wider primer on this is access control basics for event organisers.
One pass, many doors
Once the tiers exist, the pass should carry the tier, and the door should read it. A crew member scans at the backstage door and the system says yes; the same crew member scans at the VIP lounge and the system says no, plainly, without the person on the door having to make a judgement call or cross-reference a sheet. This is the whole value of tying access to the pass rather than to a list on a clipboard: the rule travels with the person, and every door enforces it the same way.
A pass that knows where its holder belongs turns every door into a quiet, consistent checkpoint instead of a memory test for whoever is staffing it.
This also removes the most awkward situation in front-of-house security, which is a member of staff having to challenge someone senior on the basis of a half-remembered rule. When the door simply reads the pass and gives a clear yes or no, there is no argument to have and no judgement to second-guess. The pass said no; the door says no. We cover the mechanics of giving each group its own access in giving crew their own lanes and logins.
Time-bound the tiers that need it
Some access is not just about where but when. A contractor needs the loading bay during build, not during the event. A daytime crew member should not still have backstage access at the after-party. Tiers that ignore time leave doors open longer than they should be, which is how kit walks and uninvited people end up where they should not be. Building a time window into a tier, this access is live from 7am to 11am, closes the gap that a permanent pass leaves open.
Practical ways to keep tiers honest over time:
- Set start and end windows on contractor and build access, not just open-ended passes.
- Collect or deactivate passes at the end of a shift or a day, especially for casual crew.
- Re-issue rather than reuse passes between days, so yesterday's pass does not open today's doors.
- Keep VIP and backstage tiers small; every extra holder is an extra person who could lose a pass.
The point of all this is not suspicion. It is that access which is never withdrawn is access you no longer control, and on a multi-day event that drift adds up fast.
The audit trail makes it accountable
Tiers decide who can go where. The audit trail records who actually went where, and that record is what turns access control from a hopeful policy into something you can stand behind. If a question comes up afterwards, who was backstage when that item went missing, who scanned into the VIP area, a readable log answers it. Without one, you are back to memory and assertion, which is exactly what tiers were meant to replace.
A good system ties every scan to a named person and a place and a time, so the log reads as a plain account of movements rather than a tangle you have to decode. That same log is also a privacy responsibility: it contains real information about real people and should be held and retained with care, not left lying around longer than it needs to be. We treat that balance in an audit trail you can actually read and the retention side in a data retention policy for events.
Access tiers are one of those things that look like overhead until the moment they save you, which is usually quiet and unremarkable: a person reaches a door they should not, the pass says no, and nothing happens. That non-event is the system working. Build the tiers from the spaces, put them on the pass, bound them in time, and keep the log honest, and your event runs with the right people in the right places without anyone at the door having to carry it all in their head.
