An Empty Box in the Ranji Scorebook: Indian Cricket's Hardest Selection Question Lives Where Nobody Takes Photographs

On a Wednesday afternoon I stood outside the outer nets at the M. Chinnaswamy Stadium for about forty minutes. A twenty-year-old left-arm seamer was bowling his seventh over — in the nets, not in a match. His first three overs were straight and easy. In the fourth his arm angle shifted by two degrees and the coach said nothing. In the fifth he wandered off his own line, and I wrote the date in my notebook: ordinary for three overs, interesting in the fourth, undisciplined in the fifth. None of that afternoon will appear in any scorebook. That is my point today.

Over the past fifteen months I have watched twenty-two net sessions across three states' Second XI and Ranji camps, and the same picture appeared everywhere: the players who get picked for the senior side are generally the ones with the brightest numbers, not the ones with the most reliable temperament. This is not a new complaint. What is new is that the cause is administrative rather than technical — and it can now be measured.

Context first: what the selection machine actually looks at

The Ranji Trophy structure runs to more than thirty teams, split into Elite and Plate groups. A player gets six to eight first-class matches in a season. If a seamer finds reverse swing on three pitches and not on two, his season average is not an honest map of his ability — it is a map of the pitches he was given. The Vijay Hazare Trophy makes this truer still: fifty-over games, in the same week, in different cities. A selector does not have the time to watch video of every match of every player. He has reports — the coach's, the captain's, and now to some extent an analyst's.

In my 2026 notebook there is a page on Sunil Joshi's arm angle, written at six in the morning, without any press conference. Karnataka won the trophy that season and the papers printed Joshi's bowling figures. But the real story was that he had shortened his run-up gradually over three weeks, and nobody made it news. I am not saying the papers were wrong. I am saying that what gets reported and what determines selection are two different worlds.

The core: selection's real problem is unequal information, not skill

India's hardest team to make is the one nobody photographs — and that is not a metaphor, it is an administrative fact.

Consider what a selector actually knows about a Ranji player. He knows runs, average, strike rate, wickets, economy. He does not know what that player looks like on the third morning when his team is batting to avoid the follow-on; what kind of bowler he is when the captain calls him in the thirty-second over rather than the fifteenth; what kind of fielder he is in the eighth hour of the day. None of those three things is recorded in a scorebook, and all three determine whether a player survives Test cricket.

Last season I asked a Ranji team's assistant coach — I will not name him, the conversation was off the record — how they send player reports to the state association. The answer: "One email, three paragraphs, at the end of the season." In three paragraphs you cannot convey which player bowled his best over in the fifth day's sun. You can convey that he took eighteen wickets. And eighteen wickets is information everyone has — the opposition, the local paper, the agent.

From this comes my second point, which is less popular. Data has not solved this problem; it has made it more visible. When you have only an average, you trust the average and you know it is incomplete. When you have twenty different metrics, the illusion is that you have the whole picture. Twenty matches is a very small sample for any statistical conclusion in Ranji cricket, and the people who work with it know that. The people who do not work with it build a story out of those twenty matches. I have seen both — at the newspaper desk and in the corridors after selection meetings.

The contrarian reading: we are not picking the wrong players, we are asking the wrong question

The easiest complaint from outside is that selectors favour big names and big states. That may be true, but it is not the whole story, and saying it distracts from the real thing.

The real thing is that our selection system is built to answer a question that should never be asked. The question is: "Who scored the most runs this season?" The right question is: "If this player has to play four Tests in England next year, which weaknesses will be exposed, and have we ever measured them?"

I remember the 2026 final — RCB against Sunrisers at Chinnaswamy, a loss by eight runs. At two in the morning I was sitting in an empty stadium and a twenty-one-year-old seamer had bowled the nineteenth over in which the match slipped away. That night I made a decision: he would not be the first sentence. Two sharp calls came from the desk; I listened and let them go. The next season that same player began texting me his injury news before the franchise announcement. He gave me three years of information that never appeared in a press release.

I bring this up because the same logic applies in Ranji cricket. Information you get through trust is always better than information you get through a report. And in Indian domestic cricket that channel of trust is almost entirely informal — a coach who calls an old player, a senior who writes two sentences about a youngster. We cannot call that a system. We call it luck, and luck is not a selection policy.

What to watch next

For the rest of this season I will be watching three things, and I am writing them publicly so that nobody later claims this was inside information. First: whether any state association starts sending month-by-month, player-wise notes instead of the three-paragraph end-of-season report. Second: whether Second XI matches are publicly videoed, because a match that cannot be watched cannot be selected from. Third: whether any selector publicly explains a pick made against the numbers — and why.

I am waiting for the name of the twenty-year-old who changed his angle in the fourth over on Wednesday. His name will probably appear nowhere this season. But in my notebook it is there with a date, and on the day he makes his Ranji debut I will open that page and check whether the system found him or he waited for the system.