It always lands at the worst time — an exposure camp deadline, a recruiting questionnaire due Friday, a club director asking for "whatever you've got" on a kid two days before a showcase. A parent texts asking for their son or daughter's season stats, and the honest answer is usually "let me dig around and get back to you," followed by twenty minutes of scrolling through a scorebook app, a group chat, and whatever sheet an assistant kept for the first half of the season before giving up on it.
Recruiting advice for parents is everywhere, and most of it says the same thing: keep a file, know your numbers, be ready when a coach asks. What almost none of it addresses is the other side of that request — the coach who actually has to produce the numbers, often for a dozen players, often for a stat nobody specifically built a report for.
What a recruiting stat request actually needs
A single season average rarely answers the question a college coach or camp director is actually asking. "12 points per game" means something very different depending on whether it climbed from 7 to 16 over the season or sat flat the whole way, and whether it came in 18 minutes a game or 30. Game film matters more than any number, but when a number does get asked for, it's the trend and the context — minutes, consistency, late-season form — that actually tells a recruiter something, not one aggregate figure pulled from a final box score.
The scorebook is the wrong source of truth
Most teams still have a real record of the season somewhere — it's just scattered across paper scorebooks, a stats app nobody opens between games, and whichever assistant happened to be charting that night. None of that is built to answer "send me everything from this season" on short notice. Rebuilding it after the fact means retyping numbers from photos of scorebook pages, which is exactly the kind of task that gets half-finished and never double-checked.
Build the record during the season, not when it's requested
The fix isn't a better spreadsheet template for recruiting season. It's logging each game as it happens, attached to the same player all year, so the record already exists by the time anyone asks for it:
- Log the game, not just the final line. Date and opponent attached to every entry means you can answer "how did they do against tougher competition" later, not just "what was the average."
- Track minutes alongside the stat. Points or rebounds without minutes played is a number a recruiter will immediately ask you to explain. Logging both at the same time means you never have to reconstruct it.
- Keep development numbers separate from game stats. Free throw percentage tracked weekly and points per game tracked nightly answer different questions — a parent asking for "progress" usually wants the first one, and most coaches only have the second one on hand.
- Log it the same day, every time. A box score logged within a day or two of the game is accurate. One reconstructed a month later from memory or a group chat screenshot is a guess with decimal points.
What to actually hand a parent
Not a photo of a scorebook, and not a single number typed into a text message. The useful version is a short per-game list for the season — date, opponent, the two or three stats that matter for that player's role — plus the season trend underneath it. That's the version a parent can forward to a recruiter without editing it, and it's the version that actually shows improvement instead of just a final tally.
This is exactly what HoopVault's games and stats tools are built to produce without extra work at request time — log each game as it's played, track the metrics that matter per player over the season, and pull up a clean game-by-game record the moment someone asks for it, instead of rebuilding a season from a scorebook photo on a Thursday night.
Start logging your season in HoopVault — free to browse, no card required.