Scout report intake and duplicate-assessment router
Problem
A scout report lands as free text in an email or a shared document, structured however that scout prefers: club, position, a paragraph of prose, maybe a rating out of ten, maybe not. The head of recruitment reads each one to judge whether the player is worth a second look, and to check whether someone else already saw him play last month. There is no reliable way to know without asking around a messaging group. Regional scouts are given informal watch lists, players to check on over a season, and nothing tracks whether those follow up checks happened. A report that never arrives looks identical to a player nobody bothered to watch. Two scouts assess the same prospect independently because neither knew the other had been sent.
Product idea
A workflow that sits between the scout and the recruitment database. A scout submits a report through a short structured form, or forwards the report email, and the system matches the player against existing prospect records by name, date of birth and club rather than relying on anyone's memory. A match surfaces the earlier report before a second one gets written from scratch. New reports route to the chief scout for triage rather than sitting in an inbox. Watch list assignments carry a due date, and a scout with an open assignment past that date gets a reminder instead of a chase from a colleague who has to remember to ask. The head of recruitment marks a prospect reviewed to close the loop. It does not score or rank players; that judgement stays with the scout.
Who it is for
Head of recruitment, who sponsors it; chief scout, who owns the triage queue; regional scouts, who submit reports and receive assignments; and recruitment analysts who need a prospect history nobody has to re-check by hand.
Possible first version
A submission form for scout reports with free text plus structured fields for player name, date of birth, club and position; name and date of birth matching against existing prospect records with a manual confirm step for near matches; a triage queue for the chief scout; watch list assignments with due dates and an automated reminder when one lapses; and a reviewed or closed status set by the head of recruitment. Out of scope for version one: no integration with third-party data providers, no video attachment or analysis, and no automated scoring of reports.
- Build classification
- Workflow application
- Rough effort
- 4-6 week first release
- Roles involved
- Head of recruitment, Chief scout, Regional scout, Recruitment analyst
- Relevant to
- Professional club, Academy & youth, Collegiate athletics, Women's league
- Systems in play
- Scouting and recruitment databases, Spreadsheets and shared documents, Messaging apps
- Product framing
- Automate a workflow
Questions we get asked
What do we need to have ready before this could start?
A workable list of prospects tracked so far, even an untidy one exported from the current spreadsheet: name, date of birth, club and any past reports. That seeds the matching records. It also needs the recruitment team to agree what counts as a match when name and date of birth are close but not identical, because that judgement call determines how much manual confirmation the tool asks for. Without that agreement the matching step either misses real duplicates or flags too many false ones.
Our scouts already send reports by email. Why would they change what they do?
Mostly they would not have to. Version one accepts a forwarded report email as well as the structured form, so the habit barely changes. What changes is what happens after the report is sent: instead of sitting in an inbox until someone reads it, it gets matched against existing records and placed in the chief scout's queue automatically. The change asked of a scout is small; the change asked of the head of recruitment, who stops manually cross checking names, is bigger.
Who is responsible for this once it exists, and what does it cost them in time?
The chief scout owns the triage queue and needs to clear it regularly, or it becomes a backlog instead of a routing tool. The head of recruitment owns the reviewed or closed decision on each prospect. Neither role is new work exactly, it is work they already do, moved out of an inbox and a spreadsheet into a queue that shows its own age. If nobody checks the queue for a fortnight, it works no better than the inbox it replaced.
Does it rate or score players for us?
No, and it will not in this version. The matching logic only compares identifying details such as name, date of birth and club to catch duplicate assessment, not the quality of a report. Rating, ranking and shortlisting decisions stay entirely with scouting staff. The tool's job ends at getting the right report in front of the right person without anyone chasing it by phone.
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 Scouting & recruitment
- Pitchside prospect lookup chat for scoutsA chat line scouts text from the ground to check whether a prospect has already been assessed, get the verdict on file, and flag that they are now watching too.
- Player approach and agent-contact clearance trackerA workflow that routes a scout's request to approach a player, guardian or agent through formal sign-off, logging who approved contact and when, in place of a phone call or group chat message nobody records.
- Voice capture for trial day player evaluationsA voice tool that lets evaluators dictate structured ratings on each trial player station by station, removing the paper card and the evening typing-up that loses detail.