Sector: greenfield

Festival accreditation software, built in a field

Bloop was born on greenfield sites: thousands of crew, dozens of gates, and connectivity that dies the moment the campsite opens. Crew, artists, suppliers, contractors and media apply once, one access matrix decides what each pass opens, and the gates keep scanning when the signal does not. If your site office is a cabin and your comms plan has a wind contingency, this is your home page.

  • Greenfield sites
  • Zero signal
  • Thousands of crew

Festivals & outdoor

Before Bloop vs. with Bloop

  1. A three-day greenfield festival

    Before Bloop:

    Build week runs on a matrix that changes daily, forty suppliers email their crew lists in forty formats, and the site has no signal past the production compound.

    With Bloop:

    Each supplier fills its own allocation against a quota you set. Zones open as the site does, so a rigger who could reach the arena on Tuesday cannot on Friday. Scanners hold the full list locally, so the lane keeps moving when the mast does not.

  2. A build with forty contractors and one site manager

    Before Bloop:

    Compliance documents arrive by email, expire quietly, and nobody notices until an inspector asks for the one that lapsed.

    With Bloop:

    Documents are uploaded against the supplier, checked once, and flagged before they expire. A contractor whose insurance ran out does not quietly keep a working pass.

  3. A site office that runs on radios and goodwill

    Before Bloop:

    Snags are reported by shouting, tracked in a notebook, and closed when someone remembers. Nothing survives to the debrief.

    With Bloop:

    Anyone on site raises an issue from their phone with a photo and a pin on the plan. It gets a reference, a clock and a department. The heat view shows where the trouble is and the wallboard in the production office shows what is still open.

  4. A production budget that only makes sense afterwards

    Before Bloop:

    Costs land weeks after the trucks leave, the budget is archaeology by then, and the overspend was knowable in build week.

    With Bloop:

    Spend commits when it happens: a PO raised, a line committed. Budgets are live during the build, and Xero reads the same numbers without anyone re-keying an invoice.

Field-tested: 10,000-cap shows · 28 gate sheets · Zero signal · Zero drama

  1. Dropouts are the default condition

    Gate scanning keeps going through dropouts and syncs when the signal returns, with a visible queue depth. The lane keeps moving when the mast falls over, on devices your team already owns, with no charge per scanner or per scan.

  2. Build-week chaos, absorbed

    Contractor and supplier accreditation through portals, with document checks and inductions, staged access that opens zones as the site does, and gate sheets that stay current through every "final" version. Artist parties and media apply through the same forms against an allocation you set.

  3. One export for the debrief

    Entry data, incident-relevant logs and briefing records in one pack for your SAG, your licensing authority and your own post-season review. The records a Martyn's Law readiness review asks for accumulate as a by-product of running the gates.

Jobs this size

What this looks like on a real one

  • Build weekvs.show day

    Festivals and outdoor

    Contractors in during build, crew and artists on the day, one matrix for both.

    Scenario · sample event

  • A three-day greenfield festival

    • 25,000 capacity
    • 1,400 accredited
    • 40 supplier companies
    • 6 gates

    Accreditation

    Use case · sample event shape

  • A build with forty contractors and one site manager

    • 3-week build
    • 40 contractors
    • CSCS cards, RAMS and insurance for all of them

    Compliance

    Use case · sample event shape

  • A site office that runs on radios and goodwill

    • Build, show and break
    • 9 departments
    • one WhatsApp group nobody can scroll

    Show day ops

    Use case · sample event shape

  • A production budget that only makes sense afterwards

    • £1.2m production spend
    • 6 departments raising POs
    • a finance office in another building

    Finance & purchasing

    Use case · sample event shape

Cross-sector

Different rooms, same radio traffic

  • Venues & nightlife

    Nightly guest lists, stage doors, and Martyn's Law with your name on it.

  • Stadiums & arenas

    Match-day scale accreditation without match-day-scale software invoices.

  • Corporate & brand

    Corporate events, launches, activations and press moments where the guest list is the whole event.

Festivals & outdoor

How it runs on show day

Festival accreditation starts before the fence is finished. Import last season's spreadsheet by CSV, set your zones and pass types, and invite suppliers. Contractors arrive against staged access that opens zones as the site does, so a rigger who needs the arena on Tuesday is not carrying a pass that opens the campsite on Friday. Suppliers accredit their own crews through portals, artist parties and media apply through branded forms against the allocation you set, and your team reviews the exceptions rather than typing names. Passes are QR, NFC or both, go out as wristbands, laminates or in Apple Wallet, and a pass is only valid while the induction behind it is. On show days, gates run from devices your team already owns: a scan resolves in under half a second, and when the mast falls over the queue keeps moving and syncs when signal returns, with the queue depth visible so the gate knows exactly where it stands. Event control watches entry counts per gate per hour and the deny reasons behind them, which is usually how you find out a pass type was configured wrong before it becomes a radio problem. At de-rig, the same records become the debrief: who was on site, when, and what changed.

Questions from your corner of the industry

It takes applications from crew, artists, suppliers, contractors and media, holds one access matrix that says which pass type opens which zone on which day, issues the passes, and scans them at the gates. Bloop also prints door sheets, laminate runs and wristband manifests from the live matrix, and keeps the record of who was on site and when.

Scans keep going through dropouts: devices queue them with a visible queue depth and sync the moment the signal returns. Nobody stops the lane to wait for a bar of 4G.

Yes. Each supplier gets a portal against their allocation; individuals fill in their own details and documents, and your team reviews exceptions instead of typing names. A first event is typically live within days: import your current spreadsheet by CSV (we help with the first one), set pass types and zones, invite suppliers.

Bloop is one licence for your whole season, priced on the people you accredit in a year, each counted once however many of your events they work. There is a free tier, unlimited devices and scans on every tier, and the people you accredit never pay: the organiser does. The full table is on the pricing page.

Not sure where your event fits?

Promoters, artists, suppliers and crew, working from one shared record.

  1. Passes run on conditions

    Nobody approves anybody. The rules do. Humans handle the exceptions.

  2. One matrix, every door

    Roles down the side, zones across the top. Every sheet, scanner and laminate reads from it.

  3. Offline by default

    Gates keep scanning with no signal and keep the record.

You don't need perfect paperwork. You need one place it all lands.

All sectors