How to build a list without a spreadsheet

Every selection meeting looks the same. Forty names on a long-list, five people around a table, and somewhere in the second hour someone says "he's a better player than that" about a batter averaging 19. They might be right, but nobody in the room can verify it, so the loudest memory of one innings in November wins.

Selection is a comparison puzzle. You have more players than places, a question — who bats three, who bowls the tough overs, who keeps — and you need the same information about every candidate, at the same time, under the same conditions.

Which is why every selector eventually builds a spreadsheet. The problem isn't building it — it's that the moment you finish, it starts going stale. Someone plays on Saturday. By Monday the averages are wrong. You update them, two more rounds go by, they're wrong again. The list is never current because cricket doesn't stop, and a spreadsheet only updates when you do.

A PlayStats watchlist has no equivalent failure mode. Match data flows in automatically — you're not maintaining anything, you're just reading.

A list per group, not a tab per group

Pathway programs don't have one squad. They have a network of them. Under-17 metro, under-17 country, under-19 metro, and so on — with national squads sitting above them all.

That's the shape a watchlist is built for: multiple named lists, each one a library you maintain deliberately. Players move between them as the season plays out — the country under-17 fringe player who forces his way into the final 14 watchlist mid-season. You drag and drop. The list updates.

Watchlists can be shared with coaches and spotters, who can share them further down. The person who owns a list writes it; everyone it's shared with reads it. So the regional coach in the country zone and the head of the program are looking at one squad list, not two spreadsheets that diverged in October.

The quieter half — and it's the part that makes the numbers usable — is player identity. Junior players are hard to follow. Two clubs in a year, school cricket over winter, rep teams, trial games. Add a player to a list and those fragments are merged into one identity. The number on the row is their complete season, not a partial record from whichever club they happened to be at when you last checked.

Compare on any column, in either discipline

Once a list is on one page, selection becomes reading.

Sort the batting view by average, or by strike rate, or by scoring-shot percentage — the share of balls a batter actually scores off, which separates the 40 off 90 from the 40 off 45. Or by innings, not-outs, runs, high score, thirties, fifties, hundreds.

Flip to bowling and the same list re-reads itself: overs, wickets, average, economy, strike rate, maidens, dot-ball percentage, boundary percentage, three-, four- and five-wicket hauls. Flip again for fielding — catches, keeper catches, stumpings, run-outs.

38.4

The lens is the point

The columns aren't the interesting part. The lens is.

Every list has filters — season, format, grade, batting position — and they apply to every player at once. The question stops being "what does he average?" and becomes the question you were actually asking:

• Who is the best number three in this group, in white-ball cricket, this season? Set the format, set the position, sort by average or boundary percentage.
• Which of these bowlers blocks an end in the longer format? Set the format, sort by economy, read the dot-ball column beside it.
• Who has done it this year, not two years ago? Every list opens on the current season by default.

That's nine questions answered in the time it takes a spreadsheet to answer one. And when you close the list and come back, it opens clean — current season, all grades, all formats, every position.

The columns are honest

Two things matter more in selection than anywhere else.

A player with no qualifying innings under your active filter doesn't float to the top of the averages. The list shows an em-dash rather than a misleading number. And a bowler with no wickets can't top the bowling averages — average and strike rate need a wicket before they render, so figures of 0 for 40 don't quietly masquerade as elite economy.

The result: sort any column and trust the top of it.

What it deliberately won't tell you

It will not tell you that the country under-17 averaging 44 is better or worse than the metro under-17 averaging 31. There is no peer average, no grade percentile, no composite rating anywhere in the list view.

The grade sits on the row. The format and the season are yours to set. What the list removes is every avoidable difference between two players — different seasons, different formats, different positions in the order, half a record missing. What you're left with is the real comparison, and a cricket discussion between coaches rather than a data-cleaning exercise.

The list keeps going after selection day

A spreadsheet stops when you close it. A PlayStats watchlist updates as the season plays out — same list, new numbers, live as matches complete. On a Saturday, put it on a screen in the coaches' box on live view and it becomes a real-time picture of your team in play.

Selection is a hard job. Balancing what you can measure against what you can't always will be. What PlayStats can do is clear the avoidable noise — so when there's a debate in the room, it's about cricket, not about whose spreadsheet is current.

How are your teams looking for Round 1?