Sector: a different city every night

The system travels with the tour

A tour is one operation performed in forty buildings. The touring party stays constant, the local layer changes nightly, and the advance lives in whoever's inbox answered last. Bloop keeps the constant constant and makes the nightly layer a fill-in-the-blanks exercise.

  • One touring party
  • Forty venues
  • Local crew, local lists

Touring & production

Before Bloop vs. with Bloop

  1. A touring production, twelve cities

    Before Bloop:

    Every venue wants the crew list in its own format a fortnight out, and the advance is one person re-typing the same 60 names twelve times.

    With Bloop:

    The touring party is entered once and carries between dates. Local crew are added per venue. Export in whatever shape the building asks for without re-keying anyone.

Same party · 40 rooms · One source of truth

  1. The party rides along

    Band, crew and management exist once, with their roles and access template, applied to every date on the routing. No re-keying the same 60 people 40 times.

  2. Local crew, local lists, per date

    Each venue date takes its own local crew, promoter reps and guest list against the touring template. Day sheets and door sheets generate per city.

  3. Advance without the archaeology

    Every venue's contacts, docs and decisions attached to the date. The next tour starts from the record of the last one.

Jobs this size

What this looks like on a real one

  • Touring partyvs.local crew

    Touring and production

    Passes that travel with the show and expire with the date.

    Scenario · sample event

  • A touring production, twelve cities

    • 12 venues
    • a travelling party of 60
    • 12 local crews
    • 12 sets of house rules

    Crew & scheduling

    Use case · sample event shape

Cross-sector

Different rooms, same radio traffic

  • Festivals & outdoor

    Festival accreditation software for greenfield sites: zero signal, thousands of crew. Our home turf.

  • 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.

Touring & production

How it runs on show day

The tour is one operation performed in a different building every night. Band, crew and management exist once with their roles and access template, applied to every date on the routing, so nobody re-keys sixty people forty times. Each date takes its own local layer: local crew, promoter reps, tonight's guest list, all against the touring template. Day sheets and door sheets generate per city from the same spine, so the version at the stage door is the current one rather than the one printed before the last drive. The advance stops living in whoever's inbox answered last: contacts, documents and decisions attach to the date, so the next visit to that building starts from a record. Where a venue's door has no reliable signal, scans queue and sync on return. At the end of the run, the tour has a history rather than forty inboxes.

Questions from your corner of the industry

No. Band, crew and management exist once with their roles and access template, applied to every date on the routing.

Each venue date takes its own local layer against the touring template: local crew, promoter reps and that night's guest list, without touching the core party.

Contacts, documents and decisions attach to the date, so the next visit to that building starts from a record instead of an inbox search.

Scans queue through dropouts and sync when the signal returns, with the queue depth visible to the operator.

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