Late team-sheet change routing and acknowledgement log
Problem
When a team sheet changes after submission, a late injury withdrawal or an eligibility swap, the update has to reach several people before kickoff: the fourth official, the opposition technical area, the public address operator, the accreditation point at the technical area gate, and whoever compiles the matchday programme feed. Today that happens by a runner walking the ground, a shout over the radio channel, or a message dropped into a group chat that not everyone is reading. There is no record of who actually saw it. A PA announcement can go out with the wrong name, an accreditation check can wave through a player who was withdrawn, and the only way to learn something was missed is when it goes wrong in front of a crowd.
Product idea
A distribution workflow triggered the moment a team-sheet change is entered against a fixture. It sends the update to a fixed recipient list built from role rather than name (fourth official, opposition technical area, PA, accreditation point, matchday media), and each recipient acknowledges on their own device with one tap. Anyone who has not acknowledged within a set window is flagged, and the competition administrator sees exactly who is still outstanding instead of asking around on the radio. Every change produces a single timestamped record of what was sent, to whom, and when it was seen, which stands as the answer if a PA announcement or an accreditation decision is later questioned. It does not draft the change itself: a person still has to verify and enter it.
Who it is for
Competition administrators who compile and amend team sheets, matchday operations managers coordinating the response, and duty managers who currently send someone to find the right person on foot.
Possible first version
A web form for entering a team-sheet change against a fixture, a configurable recipient list per role rather than per person, push notification or SMS to each recipient with one-tap acknowledgement, an outstanding-recipients view for the competition administrator, and an escalation alert after a fixed delay. Version one has no integration with a competition management platform: the change is entered directly into this tool, and recipients are added manually for each fixture rather than pulled from a roster system.
- Build classification
- Workflow application
- Rough effort
- 3-5 week first release
- Roles involved
- Competition administrator, Matchday operations manager, Duty manager
- Relevant to
- Professional club, League office, Venue & stadium operator, Women's league
- Systems in play
- Competition management platforms, Radio and communications systems, Run sheets and checklists
- Product framing
- Automate a workflow
Questions we get asked
What do we need to have ready before this could run on a matchday?
A recipient list per role for each fixture, agreed with whoever owns team-sheet changes, and a phone number or device for each recipient. It does not need historical data or a fixture calendar import to start. The first live test can run alongside the existing radio process so nobody is relying on it alone until it has proven itself over a few fixtures.
Does this replace the radio channel we already use on matchday?
No. Radio stays for real-time coordination generally, this handles one specific handoff: making sure a late team-sheet change reaches every named role with proof it was seen. It sits alongside the competition management platform used to compile the sheet rather than replacing it. The two are not connected in version one, so the change still has to be entered twice unless someone later builds that link.
Our staff already have a group chat for this. Why would they open a separate tool?
Because a group chat message that nobody has to acknowledge tells you nothing about who actually saw it, and that gap is the reason for building this. If tapping to acknowledge is not obviously faster than scanning a chat thread, the tool will be ignored within a few fixtures, which is a fair test of whether it earns its place.
What happens if a recipient's phone has no signal pitch-side or in a concourse?
The notification queues and delivers once the device reconnects, and the competition administrator's outstanding view shows it as unacknowledged rather than failing silently, so a human still knows to chase it another way. The tool does not try to guarantee delivery inside a dead zone. It tries to make the gap visible instead of hiding it inside a chat thread nobody is watching.
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
- 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.
- Pitch-side and technical area accreditation check logA mobile checklist that replaces the printed accreditation list at pitch-side, technical area and media zone gates with a searchable list, logged decisions and photo evidence on disputes.