Every club has a collapse. Yours has a pattern.
One collapse is weather. Ten is a shape — the same phase, the same wicket band, the same passage of play. Team-level reading tells you which one you've got.
PlayStats · 17 August 2026 · 3 min read
Four for 120 in the 31st over. All out for 141 in the 38th. By the time the first beer is finished, everyone in the clubrooms has a theory: soft dismissals, the new bloke, the pitch, the umpire, the middle order's collective character. By Tuesday the theory has hardened into a story, and the story gets told for the rest of the season.
The trouble is that every side folds sometimes. Losing 6/21 once tells you nothing at all — teams do that in every grade, every summer, and then bat beautifully the following week. The question worth asking isn't whether your club collapses. It's whether it's the same collapse: the same phase of the innings, the same wicket band, the same passage of play showing up in September and again in February.
That's not a question a single scorecard can answer, and it isn't really a question about individuals either. It's a team question.
A collapse is a partnership that didn't happen
An innings is a chain of partnerships, and collapses are what a broken link looks like from the outside. Read a season's partnerships together and the break usually has an address — a club that keeps folding often has one specific band, say the fourth to sixth wicket, where stands die at a dozen runs a time while everything above and below them holds up fine.
That's a different problem from "our middle order is soft", and it has a different fix. It might be a batting order that puts two identical players back to back. It might be that nobody in that band has ever practised batting with the tail.
Who is actually holding the innings up
The other half of the picture is the spine: across a season, which players are genuinely carrying the batting, and which ones have a single big score flattering their average. One unbeaten 130 in October can hide five months of starts, and the flat number never gives it away. Reading the season as a whole separates the player who scores 40 most weeks from the player who averages the same on the back of one afternoon, and a form strip — W L W W — puts the batting alongside what it actually produced in results.
Formats fail in different ways
A T20 collapse and a two-day collapse are barely the same event. One happens in the accelerating phase against a spread field with the clock running; the other happens against a new ball twenty minutes after a declaration. Rolling them into one season-long number turns two solvable problems into a vague worry, so the team views split by format instead — and two-day cricket is read the way it's actually played, across split rounds, day breaks and declarations. The washed-out games count too: the innings that were played still happened.
Monday night, in print
None of this is much use as a slide. The version that works in a team meeting is the Match Report — printable, both crests, the scorecard, the standouts, and a written read of the match that names the margin and flags where the innings was squeezed or where it fell over. For clubs, the season report gathers the same picture per grade, ladder positions and all.
A scorecard tells you the innings folded. It can't tell you that it folds in roughly the same over every time — and that's the version you can do something about before next Saturday.