Player statistics from matches
Record what actually happened in a match — kills, blocks, digs, serve outcomes — against the players who did it, so development is measured from real games rather than only from drills.
How clubs do this today
Nothing in Spike records what a player did during a match. Evaluation captures how they perform in drills, which is a different question from how they play under pressure.
Clubs that want match statistics keep them in a spreadsheet, which means they exist for one season and then do not.
What we are building
- Per-player match actions — attacks, kills, errors, blocks, digs, serve outcomes — recorded as the match runs.
- A player's own history across matches, alongside their evaluation scores rather than instead of them.
- Team-level totals a coach can use to decide what next week's session should work on.
Also not built yet
TournamentsBuilt, not open yetTryouts and evaluation sessionsBeing built nowScoring a match as it happensPlannedLeagues and organisationsPlanned
See the whole roadmap