The Sixteenth Man's Ledger: Who Actually Counts Squad Depth in a Tournament Cycle

Four days in the Holkar Stadium corridor taught me to count footsteps before names. December 2026, the Ranji Trophy final, Delhi against Vidarbha. I had no press-box seat — a nineteen-year-old who had spent ₹6,400 of his own money on a train ticket and had made his base in the team hotel lobby. Twelve hours before the toss, a Delhi senior told someone in that lobby that the pitch was 'two-paced'. The line never appeared on a scorecard or a broadcast. Vidarbha won by nine wickets, Delhi were bowled out for 295 and 157, and Rajneesh Gurbani finished the season with 39 wickets, the tournament's leading wicket-taker.

What has stayed with me is none of that. It is the reserve wicketkeeper's four days. First into the nets at 6:40 in the morning, an hour of throwdowns and auxiliary spin bowling, glue changed on the gloves, and then, on match day, a tray of drinks at the boundary's edge. Four days, four columns — all of them someone else's. Not one of his own.

Since then a rule has sat on my desk: no match report leaves it without one detail that could not have come from the scorecard or the broadcast. In nine years I have not broken it.

Apply that rule to a tournament cycle and the arithmetic changes. An ICC squad is fifteen; eleven play. The other four — a reserve keeper, an extra seamer, a middle-order batter, a spinner — play two or three matches across the whole event, or none. The entire architecture of coverage rests on the eleven. The camera shows them, the paper prints their names, the official photograph puts them in front.

A tournament cycle compresses time in a way bilateral series do not. Back-to-back fixtures, city-to-city movement, a new hotel every third day, a commercial day wedged in between. Under that pressure the selection question stops being 'who is our best player' and becomes 'who will not break in the next four days'. That is where the real ledger of depth gets written — and it is where nobody has kept proper books.

I built a spreadsheet nobody asked for, and it became the only honest witness. On any selection question I pull ten seasons of data first and ask a player for his time only afterwards. Interviewing before the numbers identify the question is just politeness.

In my corridor log, the densest cluster of timestamps belongs to the nets. 6:40 — the reserve keeper, first. 7:05 — the extra seamer begins his first spell while the front-line quicks are still stretching. 7:40 — the two reserve batters get the last ten minutes, as the session is being packed away. The order is identical in every city. I have logged it across three separate tournaments and the result never moved.

In tournament cricket, the bench's role is not backup but simulation — it imitates the next opponent, which is why its actual work never lands in a column under its own name. When a left-arm spinner is due next, the batter who has not played in six days spends ninety minutes on the eve of the match facing exactly that bowler, so the man who will actually bat can read the pitch. None of it is measured. No average, no strike rate, no economy.

The distortion begins here. Selection frameworks measure what is public — batting average, strike rate, economy, catches. What goes unmeasured is readiness: how many real balls a player has faced in the last six weeks, how long he has stood at a real wicket, how many pressure overs he has bowled. A reserve opener who has not met a moving ball in seven weeks gets picked for a knockout on the grounds of experience. He has the experience. He does not have the freshness.

I once put this on paper — ten seasons, every player who played two games or fewer in the league phase of a tournament and was then thrown into a knockout. The pattern held: the first-ten-over scoring rate of cold-entry batters sat consistently below their own season average. That is not a skill deficit. It is a minutes deficit. And minutes are in nobody's column, because nobody has built the column.

In long-form tournaments the ledger is squeezed hardest where the rules themselves rewrite the arithmetic. The Impact Player substitution in the IPL, in force from 2026, is the cleanest case. Impact Player gave teams a twelfth name while taking away the seventh bowler's column — what used to be depth became a convenience. A side once kept four specialist bowlers and three all-rounders to hold its bench alive. Now the twelfth man is permission to swap one frame mid-innings, and after it is used nobody remembers what his role was meant to be.

The effect shows in two places. All-rounder market value rose artificially, because a player is counted in two columns even when he is half a player in both. And the young seamer being groomed as the seventh bowler no longer bowls the overs in the nets that tournament cricket demanded of him. The structure looks deep on paper and thin on grass.

Wicketkeeping is where the arithmetic is most warped. A keeper is now bought on his batting numbers and not on his glovework numbers, even though knockout results are frequently decided by the gloves. My diary carries a small column: byes per tournament, missed stumping chances, catch efficiency against spin. Nobody publishes it, because it is not exciting. But when a side picks a keeper with a 140 strike rate and holds no record of his footwork against spin, that selection came out of a press conference, not a ledger.

Travel never enters a squad review. I log both the bus departure and the hotel arrival, because the gap is the actual data point. In a tournament cycle, freshness is spent not on the ground but in terminals, buses and a closed hall — and those hours appear in no selection meeting's spreadsheet. If the commercial day between back-to-back fixtures eats six hours in transit and three in a shoot, the frontline seamer's second spell in the next match pays for it. Teams call that management. Management has no column. Fatigue does.

The women's game poses the same question in a different form, and there it is a question of paperwork rather than talent. In women's cricket, squad size, retention windows and match-day scheduling decide depth — three documents that never make a highlight reel. The Women's Premier League, which began in March 2026, opened a platform for domestic players; the trophy came, the coverage grew. But a question I add to my spreadsheet after every season is this: how many domestic players did not bowl or face a single ball all season? The answer is uncomfortable each time. Depth is not built when names enter a squad. Depth is built when those names get minutes.

From outside, the picture inverts. The commentary box settles on one sentence at the start of every tournament: this team's bench is the strongest in the world. That sentence comes from a list, not from data. The list says who plays and who does not. It does not say how worn the man sitting out is, how fresh, how much fast bowling he has faced.

The real blind spot is that we measure depth by who did not play, when it should be measured by who is ready. The gap between those two questions is enormous. The first produces pride — look at the quality we have sitting down. The second is uncomfortable — look at whether the man sitting down is match-rusty. Injuries in a tournament do not arrive when you are prepared. They arrive in week three, when your most trusted seamer has lost two kilometres of pace and the man coming off the bench has to play immediately.

There is a second cost that gets waved away as 'backup'. The reserve player's biggest contribution is not made when someone gets injured; it is made every morning in the nets. For four weeks he supplies the XI's batters with the exact pace and line the next opponent brings. It is invisible labour, and if that reserve bowler is himself cooked, the damage does not show on a scorecard. It shows in the quality of the morning's practice. Teams routinely call this their real strength and routinely never record it.

One uncomfortable admission belongs here, because I have caught myself in the habit. Treating the quiet source as automatically correct is its own laziness. Groundsmen and reserve players witness what never surfaces in a press conference, but their testimony has to be tested against a second, independent record — a scorecard, a timestamp, the same drill in another city. Anything heard from a single voice and left unchecked should appear in the copy exactly as it is: 'one source said', never 'it has emerged'. I label remote work as remote in the second paragraph, because a reporter who pretends to be in the room can no longer be trusted in it.

So the loudest question being asked from outside this tournament cycle — who should play, who should be rested — is the wrong question. The right one is: the man you plan to use in week four, how many real balls did he face in week one? If the answer is zero, that is not a selection. It is an estimate being presented as strength.

When the next squad is announced I will watch three things, and none of them will be in the press release. First, whether the word before the sixteenth name is 'reserve' or 'cover'. Second, whether that player got a batting slot in the pre-match nets or the last ten minutes. Third, how long the team bus took to reach the hotel.

The day a team manager starts logging readiness minutes with the seriousness he gives to net run rate, the word depth will mean something else. Until then, whenever someone tells me this squad's bench is the strongest in the world, I will ask one thing: do you have the nets log? I do. The 6:40 columns are still blank.