Playbook currency and acknowledgement monitor
Problem
Playbooks are printed and reissued each time a formation, set play or call changes, and the reissue itself is the only record that a change happened. A player who missed training, or who never swapped the old page out of a kit bag, keeps working from a version that no longer matches what the rest of the squad is running. Coaches assume an update has landed because a new copy was handed out or a document link was reshared in the group chat, but nobody tracks who actually opened it. The gap usually surfaces at a walk-through, when two players call the same play differently, or mid-session, when a coach has to stop the group to work out which version everyone is actually using.
Product idea
A status board that tracks playbook version against each player and coach, not the document itself. When a new version is published, the board shows who has acknowledged it and who has not, updated as acknowledgements come in through a simple tap rather than a read receipt nobody trusts. A configurable cutoff, for example the evening before a walk-through, triggers an alert to the head coach or coach developer naming exactly who is still on the old version, in time to chase them individually rather than finding out on the pitch. It does not edit or store the playbook itself and does not try to detect what changed between versions: publishing a new version and describing the change stays a manual step for the coach.
Who it is for
Head coaches and coach developers who need to know a squad is actually working from the current playbook before a walk-through, and assistant coaches who publish version updates and chase stragglers.
Possible first version
A manual publish step where a coach marks a new version live and adds a short note of what changed, a player and coach acknowledgement action delivered through a link rather than a new app to install, a status board showing acknowledged against not-yet-acknowledged by name, and a configurable cutoff that sends an email or text alert to the head coach listing who is outstanding. Version one does not parse or store the playbook document itself, and does not integrate with whatever playbook or document tool the club already uses: publishing stays a manual announcement, this only tracks who has confirmed.
- Build classification
- Workflow application
- Rough effort
- 3-5 week first release
- Roles involved
- Head coach, Assistant coach, Coach developer
- Relevant to
- Professional club, Academy & youth, Collegiate athletics, Federation / governing body
- Systems in play
- Playbook and document tools, Messaging apps, Session planning tools
- Product framing
- Monitor
Questions we get asked
What do we need in place before this is worth switching on?
A roster with a working contact method for each player and coach, and someone on the coaching staff willing to mark a version live and add a one-line note when it changes. That is close to the whole requirement for version one. It does not need the playbook document itself, so there is nothing to migrate or re-upload before the board shows anything useful.
Does this replace the tool we already use to build and store the playbook?
No. Whatever you use to design and hold the playbook, whether that is a document tool or a dedicated app, stays exactly as it is. This sits alongside it and answers a different question: not what the playbook says, but who has actually confirmed they have the current one. Trying to make it own the document itself would be a much bigger build for a problem you may not have.
Will players actually tap a link just to confirm they have read something?
That is a fair worry, and it is worth being precise about what the tap proves: that a player opened the update, not that they understood it or will run it correctly. If your squad already ignores playbook messages in the group chat, this will not fix that on its own. What it does is turn an invisible problem into a visible list of names, which at least lets a coach chase the right people instead of guessing.
What happens if someone acknowledges the update after the cutoff alert has already gone out?
The board updates the moment they confirm, so the head coach sees the current state rather than a stale snapshot from when the alert fired. The alert itself is a one-time nudge, not a block: nothing here stops a session from running if someone is still outstanding. It gives a coach the chance to catch it beforehand, but the decision to delay or proceed stays entirely with them.
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 Coaching & training
- Clip request queue for coaches and performance analystsA shared request queue that replaces the messaging group coaches use to ask for training and match clips, tracking each request from ask to delivered link.
- Coach qualification and DBS expiry rostering checkA workflow that checks each coach's DBS and qualification expiry dates before a rota is published, blocking lapsed coaches from youth sessions and logging any override.
- Drill library submission and review queueA submission queue that routes new drills from coaches to the coach developer for review and tagging before they reach the shared library, replacing the photo folder and messaging group coaches use today.