Pitch-side and technical area accreditation check log
Problem
At most grounds, entry to the pitch-side, technical area and media zone is checked against a printed accreditation list held by a steward at the gate. The list is compiled the day before and photocopied for each checkpoint, so a late change, a replacement broadcast engineer, a team sheet amendment, a photographer swapped at the last minute, means someone rings the control room, who relays it over the radio to whichever steward can be reached. When a name is refused and the person disputes it, or when someone without a valid pass turns up pitch-side after the match, there is no record of who checked what, when, or against which version of the list. The paper is binned at the end of the day.
Product idea
A mobile app for the person on the gate. The day's approved list loads from an uploaded file, grouped by zone, and the steward searches a name rather than scanning a printed sheet. Allow and deny decisions are logged with a timestamp and checkpoint, and a denial can carry a photograph of the credential presented. Late additions or revocations are entered once by the duty manager and reach every checkpoint device within seconds, so the printed list stops being the record of truth. It does not replace the organisation's access control system at the turnstiles and it does not do facial matching. It is a log for the smaller set of zones where a person still makes the call at the gate.
Who it is for
Stewards and accreditation officers on pitch-side, technical area and media zone gates, with the duty manager or competition administrator maintaining the approved list and handling changes during the day.
Possible first version
A mobile web app that loads the day's approved list from an uploaded spreadsheet, grouped by checkpoint, with name search, allow or deny logging, optional photo capture on denial, and live sync of admin changes to all devices during the match. Includes an exportable log per checkpoint after the event. Version one has no integration with the turnstile access control system and no barcode or NFC pass scanning. Lookup is by name against a visual check of the credential, and any scanning hardware is a later decision once the manual version proves useful.
- Build classification
- Workflow application
- Rough effort
- 3-5 week first release
- Roles involved
- Duty manager, Control room supervisor, Competition administrator
- Relevant to
- Professional club, Venue & stadium operator, League office, Collegiate athletics
- Systems in play
- Competition management platforms, Access control and turnstile systems, Radio and communications systems
- Product framing
- Verify or inspect
Questions we get asked
What do we need ready before the first match we try this on?
A spreadsheet of the day's approved names against zones, in whatever form the competition administrator already produces it in, and a list of which gates count as checkpoints. That is the whole day-one requirement. There is no connection to a wider database at this stage, so the file is only as current as the last time someone updated it before kickoff.
Does this replace our access control system at the turnstiles?
No. Turnstile access control handles ticket holders at scale and is a different category of problem. This covers the smaller, higher-stakes zones, pitch-side, technical area, media, where a steward makes a judgement call against a list rather than a barcode. The two would sit alongside each other rather than compete.
Our stewards already know the regulars by sight. Why put a screen in front of that?
For the regulars, nothing changes, and the app should not slow that down. It earns its place on the days it usually matters least: a late credential swap, a name the steward does not recognise, or a dispute after the fact where someone asks who was let through and when. Recognition stays with the person on the gate. The app is there for the record and the exception.
What happens if a checkpoint loses signal partway through the event?
The approved list and any changes made before the drop stay on the device, so lookups and logging keep working offline. Entries queue locally and sync once the connection returns. What a steward will not get mid-outage is a change made by the duty manager during that window, which is why any change judged urgent enough should still go out on the radio as a backup, not only through the app.
Is this your workflow?
Tell us one sports workflow that still runs on paper, spreadsheets, WhatsApp or an outdated system. We will map it and show you what a simpler product looks like.
Tell us about itMore in Matchday & competition operations
- Late team-sheet change routing and acknowledgement logA workflow that routes a late team-sheet change to every role who needs it and logs acknowledgement, replacing a runner sent round the ground to find people.
- Live readiness board for the matchday control roomA live status board that turns department-by-department readiness checks into one view, with alerts that escalate unresolved items to a named person before kickoff.
- Matchday incident routing and closeout workflowA workflow that captures a matchday incident from a phone, routes it to the named owner by category, and escalates automatically if it isn't acknowledged and closed before an agreed deadline.