From Twelve to Sixteen: Counting India's Bench Line

On a February morning I opened five domestic seasons' scorecards side by side. The purpose was narrow: to count how many innings a specialist batter sitting somewhere between twelfth and sixteenth in the national queue actually gets in a full first-class season. The answer arrived by afternoon — roughly fifteen to eighteen innings for a player whose team reached the final, twelve to fourteen for one whose team went out in the group stage. That is the number that unsettled me, and the number nobody discusses on a television panel.

A tournament squad is fifteen. Eleven take the field. The four in between are precisely the men the entire domestic structure exists to produce — and that same structure gives them seven league matches a year. Seven matches, fourteen innings, and then a selection meeting in which three people must decide who is the fourteenth name on the next overseas tour.

This piece is about that fourteenth name.

Seven matches a season, fifteen in a squad

The Ranji Trophy runs thirty-two Elite teams in four groups of eight, seven league rounds each, then quarter-final, semi-final and final — a maximum of ten matches. I am leaving the Plate group out of this count, because the distance from there to the national team is still mostly theoretical. In ten matches a fast bowler who stays fit and is picked every week bowls somewhere between 150 and 200 overs. A specialist batter faces 1,000 to 1,400 balls.

That does not look small until you compare it with the work that data is supposed to do.

The BCCI's annual contract slabs — A-plus at seven crore, A at five, B at three, C at one — cover roughly thirty names. Slightly more than two XIs. So when somebody says India's bench is the strongest in the world, what they are praising is a list of contracted names, not the match time those names have behind them. Those are two different things, and collapsing them is the founding error of this entire argument.

The IPL economy runs the other way. Ten teams, fourteen league matches each, and at the 2026 mega auction every franchise held a purse of ₹120 crore. The retention slabs for capped players sat at eighteen, fourteen and eleven crore, with a four-crore corner reserved for uncapped players. The slab is not the interesting part. The interesting part is that the data required to push an uncapped player's price to four crore consists of fourteen to seventeen T20 innings, played on surfaces where bowling carries limited risk and batting carries most of the reward.

The selector has twelve red-ball innings. The market has seventeen white-ball ones. Both sit with their own file, and both believe the other's file is the more reliable document.

Let me declare my vantage, once. I write from Manchester. I watch these matches on a stream, check the scorecard three times, and where the claim depends on pitch behaviour or heat, I call a stringer in Mumbai who is actually at the ground. Last season I sat through 4,300 deliveries with the audio open, and I counted every one — I repeat this because when you are not present, your most likely mistake is to mistake structural confidence for presence.

The arithmetic of the gap

I have one firm, falsifiable claim, and it is this: India's bench problem is not a shortage of opportunity but a bias in the opportunities it gets — and that bias is manufactured by the calendar, not by the selectors' instincts.

Here is the unpacking.

There is no consensus on how large a sample is needed to judge a first-class batter, but the people who count generally ask for thirty to forty innings, spread across different conditions — some on turning pitches, some on bouncy ones, some in heavy moisture. Now look at seven league rounds. Eight teams to a group, seven rounds, and the venues a side meets are usually its own and its neighbours'. A batter in the Rajkot or Jaipur group may get one genuinely turning surface all season. A seamer in the Delhi group may get two glimpses of real bounce.

The conclusion is unwelcome: twelve innings is not only small in number, it is narrow in variety. The selector's sample is tiny, and what exists is homogeneous. In that condition even a perfectly rational selector ends up leaning on the most recent thing he saw in the clearest colours. That is the IPL. This is not glamour worship; it is a data constraint.

There is a further layer people skip. The Ranji season spreads from October to March, but the matches arrive in clusters — a dense fortnight, then a long gap. For a fast bowler that clustering imposes a load not unlike a foreign tour, minus the support a foreign tour brings: no rotation, no scientific workload control, and direct pressure from the team's fate to pick the best bowler every single week. Domestic cricket has no room for rest, because the man resting is the man taking your place next season.

The result is that the domestic system is not manufacturing depth. It is manufacturing auditions. And in an audition you show what you already have, not what you might learn.

The auction is the real selector

I first felt this in 2026. In January I wrote a forty-page pre-auction file arguing that Jos Buttler, as an opener, was worth double his likely price. Rajasthan bought him for ₹4.4 crore, pushed him to the top of the order in April, and he made 548 runs with five consecutive fifties. The 4.4-crore file stayed closed for a month, and that was the work. I was right about the player and wrong about nearly every other price in the room — a note I wrote in the margin and never published.

What that year taught me is the thing that still governs how I work: mechanism and money are separate objects. An auction piece should open with the match-up and bury the figure in the fourth paragraph. Every transfer window is a spreadsheet pretending to be a story, and beneath every spreadsheet sits a question the spreadsheet cannot answer.

That question is this: when the market has seventeen innings and the selector has twelve, whose data is actually better?

The technical answer is that they answer different questions. The auction asks how many runs this player produces in the next fourteen matches, and the answer comes from T20 conditions. Selection asks what this player does on day four of a five-day match, in thirty degrees, in the fourth innings, on a surface turning square — and that answer is not in seven Ranji matches, because that situation may have occurred once.

So the selector has an option he never states out loud: pick the player about whom he knows less, but whose small body of evidence is loud. We call that courage when it works and carelessness when it does not. Either way, we do not count.

What the bench has produced when measured

One thing in this debate gives me confidence: when the bench has actually been measured, it has returned measurable answers.

In October 2026 in Pune, Washington Sundar was a late addition to the squad against New Zealand — not the name the coverage was built around. He made 152 in the first innings, in conditions where spin dominated and India were under pressure. In December 2026 at the MCG, Nitish Kumar Reddy made 114 on Boxing Day, the most-watched day in the sport, as a player on whose Test credentials nobody had a settled view.

My question is not how good those innings were. They were good and everyone saw them. My question is how much sample preceded them, and how foreseeable they were from that sample. The answer is: barely at all. Both selections were made on partial data, and both succeeded. The success did not validate the data. It merely proved that the system retains gaps through which a good player occasionally passes.

That is exactly where my own model dies. In July 2026 England chased 378 at Edgbaston, and I spent three weeks coding all 79.4 overs — fielders' depth at release, how many stood outside the frame, how early each batter committed. My pre-meditation index explained roughly sixty per cent of the innings. In a 6,000-word piece I published the model in full and then named the forty per cent it could not reach, which was, more or less, Jonny Bairstow.

The same applies to the bench. I keep a column for what the model cannot see. It is always full.

The calendar's arithmetic

Now the part people wave away as 'the system', which is in fact the engine of the whole thing.

India play more matches every year. Test series are getting longer, white-ball legs are being attached to every tour, and a preparatory series now sits in front of every major tournament. For the top eleven this is a load. For the bench the logic inverts: more matches means more rotation, and more rotation means more opportunity for men twelve through sixteen.

And yet bench game-time does not rise. Why?

Because rotation does not travel downward; it circulates within the top group. When a captain rests one of four seamers, he usually does not bring in the fifth seamer. He brings in an all-rounder, or an extra spinner already in the squad whose inclusion disturbs team balance least. That is sensible. That sensibility is the bench's deadliest enemy.

In 2026, when I first sat in the chair behind the dressing-room door, I saw for the first time that teams are afraid of their benches. Being afraid of the bench does not mean the bench is bad. It means the information about the bench is so thin that when the moment comes to use it, the coach does not trust the man to do the job he was picked for. And the job he was picked for was never specified, because specifying it required playing him first. It is a loop, and the loop strengthens itself every season.

I also counted how many players over the last three domestic seasons made twelve to fourteen innings in one season and then, for whatever reason, fewer than eight the next. The number struck me as surprisingly large, and I am not printing it here precisely because it is only a number. I do not have a name for the system it is evidence about. I do not publish tallies without a mechanism.

What I can name is this: the first-class season builds what I call interval capacity — the habit of playing a great deal of cricket in a few weeks. International cricket demands holding capacity — the habit of making the right decision on the first ball after sitting still for two months. Those two capacities rarely coexist, and our structure builds the first while testing the second.

The mistake we all make

Now the bitter part.

Every squad announcement produces the same argument: who was picked and who was not. That argument is worthless, because it is an argument about a selector's taste, not about data.

The real question is the conditions in which the twelfth-to-sixteenth man plays when he does play. I went back through those appearances over recent seasons, and three things recurred.

First, he usually plays once the series is decided. The last Test, or the last ODI, or the fixture in a tour already won. Which means his sample is built from matches where the rest of the team carried the least pressure.

Second, he usually plays on the flattest surface. A home side tends to spend its result-wicking pitches early in a series, and the last match is left with the surface that does least — which is frequently the rotation match.

Third, he usually plays against the weakest opposition. That is logical, but it means his numbers are inflated and his ceiling unmeasured.

So the opportunity arrives, and the conditions of the opportunity are such that the outcome cannot become the basis for the next opportunity. I call this opportunity bias. It is nobody's malice; it is the sum of three separate needs — calendar, pitch curation, team balance.

And when that happens, almost every selection call is made from recent memory. Recent memory is the seventeen innings somebody played at night, under lights, on a small ground. In technical language this is recency bias. In plain language it is picking the last thing that looked good. They are the same thing.

One note on imported metrics. England argues endlessly about county workloads, and its metrics — overs per season, days bowled, rest windows — do not transfer cleanly. The Indian domestic season is shorter, the travel longer, and the variance between pitches so wide that overs-per-season tells you almost nothing on its own. A metric that works in England dies in translation here. The day we accept that, thinking about the bench becomes easier.

What to watch in the next series

One suggestion, and it is simple: in the second innings of the next series' first Test, watch the fourth seamer's first spell — if he plays at all.

Watch when it arrives. If it comes at 40 for 3, that was an opportunity and its outcome means something. If it comes at 140 for 3, it was a formality and its outcome means nothing. That single piece of over-level information will tell you more about the player than the entire domestic season he just played.

Twelve parts in, the thread stops being a thread and becomes a badge. On the bench we are still counting threads while looking at the badge. The day we start writing down the over number of the spell, bench strength stops being a phrase and becomes a measurement.

The question is not whether India's bench is strong or weak. The question is whether we have ever tried to measure it — and if we have not, on what basis are we calling it strong?