Playbook assignment chat for players
Problem
Playbooks are printed and reissued each time a set play changes, but players keep the version they were handed weeks earlier, or a photograph of a page taken with a phone. The night before a game, or during a study session at home, a player unsure of an assignment texts a teammate, a parent, or the assistant coach directly. Close to fixture day the same three or four calls generate dozens of individual messages to the same person, often at a time the club would rather they were not working. Nobody tracks which plays generate the most confusion, so a playbook that keeps confusing players on the same call never gets flagged for a rewrite.
Product idea
A chat interface that answers a player's question about their own assignment using the current version of the club's playbook, nothing older. A player asks in plain language, for example what do I do on the bear call, and receives the relevant diagram and assignment text back. Where the playbook does not cover the question, the chat says so and passes it to the assistant coach as a logged item rather than guessing at an answer. Every version replaces the last, so a player asking at 11pm gets the play as it stands after that afternoon's changes, not the version printed at the start of the month. It does not run drills or explain tactics beyond what is written down.
Who it is for
Players and academy athletes checking an assignment outside training hours, and the assistant coach or coach developer who currently answers the same question by text and would sponsor the rollout.
Possible first version
A web chat that ingests the current playbook as a PDF or slide export, answers only from that document, and shows the matching diagram alongside the text. Unanswered or ambiguous questions are logged and emailed to the assistant coach as a short weekly list rather than resolved live. Access is by a shared squad link rather than individual logins. Out of scope for version one: voice input, any link to the video analysis platform, and any attempt to answer questions about a play that is not yet in the uploaded document.
- Build classification
- Workflow application
- Rough effort
- 3-5 week first release
- Roles involved
- Assistant coach, Academy coach, Coach developer
- Relevant to
- Academy & youth, Professional club, Collegiate athletics, Women's league
- Systems in play
- Playbook and document tools, Messaging apps, Session planning tools
- Product framing
- Voice or chat interface
Questions we get asked
Our players already text the coach when they're stuck. Won't this become just another app nobody opens?
That is the real risk with any tool layered onto a workflow that already works well enough. The test is whether asking the chat is faster than typing a text to the assistant coach, not whether it looks more organised. If a player still gets a faster answer by texting a teammate, they will keep doing that, and the chat will sit unused. Where it earns its place is close to fixture day, when the same handful of questions arrive from several players at once and the assistant coach would rather field one text than six.
Does it explain why a call works, or just what a player is meant to do?
Just the assignment, deliberately. It reads back what the current playbook document says a player does on a given call, not the reasoning behind the call or the tactics that make it work. That distinction matters because a chat confidently explaining tactics beyond what is written down would be guessing, and a wrong explanation delivered at 11pm the night before a game is worse than no explanation at all. Anything beyond the written assignment stays a conversation with a coach.
What do we need to hand over before this can answer anything useful?
The current playbook document, in whatever format it already exists in, PDF, slides or a scanned printout, and a way to reach the assistant coach for the escalation list. Nothing else. It does not need the video analysis platform, the athlete management system or historical seasons of playbooks to be useful on day one. The moment the document changes, the old version needs replacing in the tool as well, or players will be reading last month's calls again.
Who has to keep this current once the season is underway?
Whoever owns the playbook document already, usually the assistant coach or the coach developer, because the tool is only as current as the file it was given. In practice that means replacing the uploaded document each time a call changes rather than editing it separately in two places. The weekly list of unanswered questions is a small extra task, worth a few minutes to skim, and it is also the most useful part: it shows which calls keep confusing players.
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.