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
Zone: the diligence
Most vendors say 'ask us for the security overview'. This is it, in public. If your procurement process needs it as a PDF with your company name on the request, there is a form at the bottom.
3 min read
For this website, Templar Works Ltd is the controller. Inside the product, the event organiser is the controller for the people on their events (crew, suppliers, artists, guests) and Templar Works Ltd is their processor, acting on their instructions under a data processing agreement available on request.
The application and database run in a UK/EU deployment region. Object storage for documents and photographs is eu-west-2 (London). Analytics is PostHog EU cloud, served through our own domain so nothing is requested from a third-party host in the browser. The full sub-processor list, with what each one receives and where that company sits, is on the privacy page.
Every record is scoped to an organisation, and every endpoint checks membership and role before returning anything: deny by default rather than filter afterwards. Portals for suppliers and individuals are separate session types bound to a single allocation or person, so a supplier login cannot reach the event team's data.
Every create, update and delete of significant data writes an audit entry: who did it, what changed, before and after, and when. The actor is typed (staff user, supplier, individual, system) so the trail is forensic rather than approximate. Secrets are redacted from audit payloads.
Session cookies are httpOnly, sameSite lax, and secure behind the proxy. Scanner device API keys are stored only as hashes and are rotatable. Third-party OAuth tokens (Xero) are stored encrypted, never in plain text.
Some events require health and safety induction records, dietary requirements or DBS status. These are held because the organiser needs them to run the event safely, are scoped like everything else, and are covered by the retention schedule the organiser sets.
The organiser's retention schedule decides. Bloop ships with GDPR-sensible defaults which the organiser can adjust, and deletion actually deletes rather than hiding a row.
No. People accredited through Bloop receive transactional messages about the event they are working on and nothing else. Any SMS can be stopped by replying STOP, which suppresses that number permanently and globally.
Full detail, including the sub-processor table and your rights, is on the privacy page. A DPA and our record of processing activities are available on request.
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
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
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
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
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
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
The checks worth running the day before doors, whatever software you use. Written from ours, generalised so it is useful without it.
2 min read