Event Credentialing and Accreditation Software: What It Costs to Vet, Badge and Zone Thirty Thousand People Before Gates Open

Why accreditation is a security control disguised as an admin process

Eleven days before the first competition day, the accreditation manager has 26,000 applications in a system, 4,200 still waiting on a vetting result, and a rights holder who has just submitted 340 crew members in a single spreadsheet with no passport numbers. The zone map changed last week because the broadcast compound moved, so every pass already printed for that area now grants access to a car park. Nobody wants to reprint 900 badges. Somebody suggests a sticker.

That sticker is the whole problem. Accreditation looks like a paperwork exercise, so it gets resourced like one, and then on day one the gate becomes the place where every unresolved decision arrives at once. A pass that grants the wrong zone is not an admin error. It is a person standing in a place your security plan says nobody should be standing, and the incident report will name the accreditation process.

The buyer for this is usually the head of accreditation or the security lead at a venue, a league or a major event, and the honest description of what they need is a workflow engine wrapped around an identity register, wired into physical access hardware, that can change its mind in real time.

Problem 1: applications arrive from organisations, not from people

Individuals rarely apply for themselves. A broadcaster submits a crew list. A catering contractor submits a workforce that changes daily. A sponsor submits guests two days out. A national federation submits a delegation with roles that map to different zones. Each of those is a bulk submission from a coordinator who does not know your zone taxonomy and does not want to learn it.

Accredit Solutions handles this pattern properly and is the serious incumbent in the space, which is why it turns up at major events. Where a custom build earns its place is when your registrant categories, your role to zone mapping and your approval chain do not resemble the model any product ships with, or when accreditation has to sit inside a wider event platform you already run. Genetec is a different animal altogether: it is an access control and security platform, excellent at the gate, and not the place where an application is written, vetted and argued about for six weeks.

What a custom build does: the organisation is a first class object with a quota, a coordinator, a submission deadline and a delegated approval right. Coordinators submit and correct their own people, which removes the single largest source of accreditation workload, and your team approves categories rather than individuals wherever the risk model allows. Bulk import accepts the spreadsheet the coordinator was always going to send, validates it, and returns the errors to them rather than to you.

Problem 2: vetting has different clocks and different answers

Some registrants need a criminal record check. Some need a right to work check. Some need a police or national security clearance with a turnaround measured in weeks. Some need nothing at all. The check that matters is determined by the zone they are being granted, not by their job title, and the results come back at different times from providers with different interfaces and different definitions of a pass.

The failure mode is not a failed check. It is a check that came back a week late, or a check that was done against a name spelled differently from the passport, or a check that expired between the application and the event because the event runs for three weeks. Meanwhile the coordinator keeps calling to ask why their crew is not approved yet.

What a custom build does: vetting becomes a requirement generated from the zone entitlement, with a state machine per check, an expiry, an evidence reference and an owner. The registrant record shows exactly which check is outstanding and who it is with. Coordinators see their own pipeline, which stops the phone calls. When a check comes back adverse, the system does not silently reject: it routes to a named human for a decision, because the consequences of a wrong exclusion at a major event are real and someone senior has to own that call. Provider integrations get built one at a time and the design has to assume you will change provider between editions of the event, because you will.

Problem 3: zone entitlements change after the badges are printed

Zones move. A compound relocates, a stand is closed for a day, a head of state visit imposes a sterile area for four hours, or a category that was allowed into the field of play is quietly downgraded after a rehearsal goes badly. Printed badges are physical objects and reprinting is expensive, slow and often impossible inside the last week.

What a custom build does: separate the badge from the entitlement. The badge carries an identity and a credential number. The entitlement lives in the system and is evaluated at the gate against the current zone rules, the current time window and the current day. That is what makes a same day change enforceable without touching a printer. It also means the printed zone icons become an indicator for human readers rather than the authority, which is a policy decision your security lead needs to make deliberately, and the design should support both models because some events insist the badge itself is the authority.

Day passes, upgrades and temporary escalations run on the same mechanism. A contractor who needs field access for two hours on Thursday gets a time bounded entitlement that expires by itself instead of a paper note taped to their badge.

Problem 4: revocation has to reach the gate before the person does

Someone is dismissed. Someone loses a badge. Someone is found in a zone they should not be in and their access is pulled by the security lead. In a paper driven process, revocation is a radio call to gates that may or may not be heard, plus a printed list of cancelled numbers that supervisors are supposed to check. That does not work and everyone involved knows it does not work.

What a custom build does: revocation is a single action that propagates to every reader, every handheld scanner and every gate device within seconds, with an audit record of who revoked, when and why. Handheld devices at soft perimeters have to hold a local copy of the credential state so they keep working when the network drops, and they have to converge quickly when it returns. This is where the integration with your access control platform becomes real engineering: writing credential state into a Genetec or equivalent system in near real time, handling the acknowledgement, and reconciling when the two disagree. Anyone who quotes this as a simple API call has not done it during a live event.

What this costs and how long it takes

A first accreditation cycle, meaning organisation and individual registration, category to zone mapping, vetting workflow with one or two check providers, approval queues, photo capture and validation, and badge production, runs $90,000 to $200,000 and ships in 16 to 22 weeks. A full platform adding live entitlement evaluation at gates, access control integration, handheld scanning with offline operation, day passes and upgrades, revocation propagation, and multi event and multi venue configuration runs $280,000 to $650,000 phased over 9 to 18 months.

What pushes cost up specifically here: the number of vetting providers and whether any of them is a government or police interface, because those are slow to arrange and rigid. Access control integration, which is dictated by whatever hardware is already installed and by an installer whose cooperation you have to secure early. Photo capture quality, because a badge photo that fails at a gate under floodlights is a real operational cost and the validation rules are fussier than people expect. And the deadline, since an event date does not move, so the first cycle should be scoped smaller than the ambition and the second edition can absorb the rest.

Build versus buy, and when buying is the right call

Buy if you accredit a few hundred people who are mostly the same from event to event. Your access control system plus a controlled approval form is proportionate, and building software here would be spending security budget on a workflow you could run in a shared inbox. Accredit Solutions is the right answer for a lot of major events, particularly if your process broadly matches how large sporting events already work and you want a team that has done it before rather than a build programme.

Build when the accreditation process is genuinely yours: unusual registrant categories, an approval chain that involves several rights holders and authorities, zone rules that change during the event, or a requirement to sit inside a wider platform you already operate for ticketing, workforce and operations. Also build when you run a recurring event and the tail of value is in the data: last edition's registrants, their checks and their behaviour make next edition dramatically cheaper to run, and that only compounds if you own the record.

How to choose a developer for accreditation software

Ask them how a zone change on the morning of day three reaches a badge printed six weeks earlier. If the answer involves reprinting, they have modelled the badge as the entitlement and you will be putting stickers on passes.

Ask what happens to a handheld scanner at a soft perimeter when the network drops. It must hold local credential state, keep scanning, and converge fast on reconnection, including honouring revocations issued while it was offline.

Ask which access control platforms they have written credential state into, by name, and what they did when the two systems disagreed. Reconciliation between an accreditation system and a gate system is where the actual difficulty lives, not in the application form.

Ask who owns the code, the infrastructure and the registrant data, and get it settled in writing before kickoff. Accreditation data includes identity documents and vetting outcomes, which means retention and deletion policy is not optional and the hosting arrangement needs to be yours. At Digital Heroes the client owns the repository and the data from the first commit.