Guide · the day before

What to check before doors, whatever you run it on

This is our own event-day runbook with the Bloop-specific steps taken out. It is useful with a spreadsheet and a clipboard, which is rather the point: most show-day failures are process failures wearing a software costume.

2 min read

The day before doors

  • Every gate and door has a named person, a device, and a charger. Count them physically.
  • Print the current sheets last, not first. A sheet printed on Thursday is a Thursday sheet.
  • Walk one person through the full journey: application, approval, pass, scan. End to end, on a real device.
  • Check the access matrix against the physical site. A zone that exists in software and not on the ground causes arguments at 06:00.
  • Confirm who can approve a late change, and how the gates hear about it.

Connectivity, honestly assessed

  • Test signal at every entry point, not at the site office. Docks, basements and back gates are where it fails.
  • Know what your system does when the signal drops, before it drops. Queue? Refuse? Cache?
  • Have a paper fallback for the two or three gates most likely to lose signal, and know who holds it.
  • Agree the radio phrase for "the system is down at gate 4" so it is not a two-minute conversation.

The people layer

  • Gate staff briefed on deny reasons, not just on scanning. "Wrong zone" and "already scanned" need different responses.
  • Someone senior owns exceptions, and gate staff know their name and how to reach them.
  • Contractors arriving before the pass office opens: decide the answer now, not at the barrier.
  • Medical, welfare and security know how to look someone up if a pass is lost.

On the day

  • Check the first ten scans at each gate personally. Configuration errors surface in the first ten or not until the queue.
  • Watch deny reasons by gate through the first hour. A spike at one gate is usually a configuration problem, not a fraud problem.
  • Keep a running note of every manual override. It is the record you will want at the debrief.

After

  • Export the entry data and the change log while the event is fresh.
  • Record what actually happened against what was planned, including the workarounds.
  • Note which pass types were wrong. That is next year's setup, already half done.

More guides

  • Guide · Free

    Event accreditation: the complete guide

    What accreditation is, who gets accredited, how zones, pass types and the access matrix work, the nine steps of the process, and eight questions worth asking any platform.

    9 min read

  • Checklist · Free

    Martyn's Law readiness checklist

    Eight sections: which tier you are in, who must be named, the four public protection procedures, the records that cannot be backfilled, and the notification deadline tied to your on-sale announcement.

    6 min read

  • Tool · Free

    Spreadsheet tax calculator

    What your current accreditation process costs in hours and pounds a year. The link carries your inputs, so you can send the result to whoever owns the budget line.

    Tool

  • Template · Free

    Access matrix template

    Pass types down the side, zones across the top, Y or N in every cell. A worked festival example, why each zone is there, and the CSV. No email.

    Template

  • Guide · Free

    Contractor accreditation

    The documents worth checking, the ones to leave to the contractor, access that ends with the build, and what a good contractor gate looks like.

    5 min read

  • Guide · Free

    Media accreditation

    Running press accreditation as an organiser: approving and conditioning applications, the photo pit, escorted access, creators, and recording why you said no.

    4 min read

  • Page · Free

    Security and data overview

    Where data lives, who processes it, what we keep and for how long. The thing our own pricing FAQ promises when it says "ask us for the security overview".

    3 min read

Start today

Run the next show from one record. Free for up to fifty accredited people a year. No card needed.