Suryakumar at the Red-Ball Door: How a Single Omission Became a Case for Selection Transparency

For the past few weeks, the most discussed event in Indian domestic cricket has not been a scoreline but an absence. Suryakumar Yadav was left out of Mumbai's Ranji Trophy squad even though the report stated plainly that he was available for selection. Attached to the same report was one sentence: 'He needs more red-ball cricket.' Nowhere does it say who said it, what position that person holds, or in what context.

I have watched the architecture of this kind of news for years. A fact (an omission), an unattributed quote, and a headline — weld those three together and the resulting story usually grows larger than the event itself. Here I want to probe the empty spaces, and see where a routine selection decision actually lands.

Red ball versus white ball: a format is more than a colour

India's premier domestic first-class competition, the Ranji Trophy, is played with a red ball over four innings. Its demands are entirely different from white-ball cricket. In T20, a batter's value is set by output per ball — strike rate, boundaries, sixes. With the red ball, value is set by patience, defence, time at the crease, the discipline to leave the new ball, and the skill to handle movement. One batter, one pair of hands, one pair of eyes — but two different players across two formats.

Suryakumar's identity is currently bound to white-ball cricket. He captains the T20 side and is called a '360-degree' batter because his shot range around the pitch is unusual. That reputation is a product of T20. But if a Ranji selector views him through red-ball eyes, the questions change — how long can he survive the new ball, can he leave the ball outside off, what does his footwork do in the fourth session when the pitch begins to break. None of that shows up in a T20 highlight reel.

Here is the first problem: a reputation in one format is not proof of readiness in another. And an omission in one format is not a verdict in another. The report has fused the two, and that is its deepest analytical weakness.

Why Mumbai is different

The selection context here is Mumbai. In Indian domestic cricket, Mumbai carries a distinct weight — it is the most successful side in Ranji Trophy history, first in titles. So dropping or picking someone there usually acquires an extra dimension. At a low-profile team such an omission might not have been news at all; at Mumbai it becomes a headline.

But Mumbai also has its own red-ball priorities. Its domestic side contains specialists who have proven themselves in first-class cricket year after year. When a selector balances a side, he does not simply look at big names; he looks at who will work in this format right now. This is a miniature club-versus-country puzzle: the national team's white-ball demand and the state side's red-ball need pull the same person in two directions.

I have seen this tug-of-war before, and an omission in it is usually temporary. Selectors reverse course, the story fades. But that happens when the reasoning behind the decision is stated clearly. Here it was not.

The politics of the quote: what an unnamed sentence conceals

The weakest part of the report is that quote — 'He needs more red-ball cricket.' On its surface the sentence sounds innocuous, even positive. As if someone is saying that more red-ball cricket is what this player needs for his own development. But the question is whether the sentence argues for the omission or against it. The report does not answer that.

A subtle device is at work. A sentence is placed inside quotation marks, yet the speaker is withheld. The reader therefore weighs the sentence but cannot trace responsibility for it. That ambiguity manufactures a contradiction: if he truly 'needs more red-ball cricket,' why is he omitted from the red-ball squad? With no answer, the story survives on speculation — and speculation is the longest-lasting kind of news.

From my eighteen years of watching the game, I can say that this kind of unattributed quote usually signals one of three things — a leaked remark, a briefing given on condition that the source is protected, or a deliberately vague message. Each carries different administrative weight and demands a different response. Before a sentence is used as evidence, at least know whose sentence it is.

The technical problem of format transfer

The difficulty of converting white-ball batters to the red ball is not new. Footwork trained in T20 often loads the front foot and attacks the line. With the red ball that habit invites danger — reaching for the ball outside off, edging to slip, losing the wicket while driving at the new ball. With time the problem eases, but time is required, and that time comes only by playing red-ball cricket.

This is the centre of the contradiction. If 'needs more red-ball cricket' is true, then omitting him from a red-ball squad does the exact opposite of meeting that need. It is like announcing that someone needs to read more books and then locking the library door. The argument cannot stand on its own feet unless some other explanation exists that the report left unwritten.

I learned this when I worked on the first VAR penalty — you rely on the protocol, not on emotion. At the 2026 World Cup, VAR awarded its first penalty in the France-Australia match for Josh Risdon's handball. I froze that moment and cross-checked the IFAB protocol, the 'clear and obvious' threshold, and the handball law. The same method is needed here: freeze the frame, read the rule, then judge.

'Despite being available' — who creates that expectation

Another heavy phrase in the report is 'despite being available.' Those three words hide an unwritten expectation — that a senior international who is available should ordinarily be picked in the domestic side. Where does that expectation come from? The Indian board generally encourages centrally contracted players to remain available for domestic cricket. It is not a written rule but an administrative habit.

This is the legal point. A 'bad decision' and a 'breach of duty' are different things. A selector may choose wrongly; that falls within his authority. But if an unwritten norm exists and is applied inconsistently, a transparency question arises. The report could have raised the second question but did not — because it holds no citation of any rule.

To me that was the report's biggest missed opportunity. Selection is an administrative act; when the reasoning behind its decisions is not public, rumour takes the space. That is exactly what happened here.

From VAR to the red ball: what I have learned

I have never treated these two worlds as separate. In cricket a selection question, in football a referee's decision — both are exercises of power, and both invite accountability. I learned to read a foul as a fact pattern, not a moral story — who did it, where, under which rule, with what consequence. Suryakumar's omission should be read the same way: a fact pattern, not a moral story.

Similarly, in European football I traced Christian Eriksen's collapse from emergency to legal duty — who acted at which moment, who neglected which duty. A cricket selection decision is certainly not a crisis of that magnitude, but the method is the same: align the timeline, assign responsibility, then opine.

And the Manchester City case taught me that behind an institution's decision there is always a calculation invisible from outside. The Court of Arbitration for Sport overturned Manchester City's two-year ban in 2026, cutting the fine from €30m to €10m. Reading that 93-page award, I understood that the public announcement and the actual reasoning need not match. The same caution applies to selection.

A different reading: perhaps the omission is the path

Now test the counter-argument. Suppose the quote is true and honest. Someone is saying this player's red-ball foundation needs strengthening. Then an omission is not a 'sidelining'; it may be a planned path — building him separately for the longer format, and instead of taking him into this particular squad, giving him red-ball time in another team or camp. Under this reading, the headline is exaggerated.

But the report cannot prove this either, because it wrote nothing about any future plan. So we are left in a position where two contradictory readings are both possible, and the piece chooses neither. Journalistically, that is the greatest failure — a story was created but not resolved.

There is another possibility no one states aloud: workload. White-ball captaincy, the IPL, the international calendar — together these place pressure on a player's body and mind. Dressing a rest decision in the language of 'format judgment' is a familiar device. The report neither ruled this out nor acknowledged it; it simply went silent.

The wrong address for the outrage

One thing keeps returning to me. Of all the anger this episode produced, most went toward 'the omission.' Yet the more important issue is the failure of communication. If selectors had stated plainly — this decision for this reason, this plan — the anger might never have existed. In its place there would have been discussion.

That is the biggest lesson for me. Audiences and fans can actually accept a decision if it is explained. What they cannot accept is ambiguity. An unnamed quote deepens that ambiguity, because the reader does not know whom to trust.

I once wrote, in a different context, that white-ball market value and red-ball preparation cannot be equated. A player's price in the IPL proves he is of international quality, but it does not prove he is ready for Test cricket. This story stands precisely on that gap, even though the report was unwilling to admit it.

The false certainty of the heatmap

Another of my old complaints is relevant here. Heatmaps and modern statistics often give us a false certainty — as if everything is now known. Yet in this episode we saw that there are no numbers at all. One omission, one unattributed quote, and enormous discussion. Without numbers, analysis fills with speculation, and speculation fills with bias.

So the real data gap in this episode is itself data. It tells us we live in a time with many decisions but few explanations. Media builds headlines quickly but explains slowly — if at all. Here it did not.

Looking forward: what to watch

Now it is better to look ahead. Over the next one or two selection cycles, three things are worth watching. First, whether this player returns in the next Ranji or first-class squad — if he does, this was temporary; if not, a pattern is forming. Second, whether the person behind the quote ever steps forward by name — a name will either end the story or transform it. Third, whether the board issues any new directive on domestic availability.

None of these is known yet. That is not weakness; it is honesty. A report that admits its limits endures; a report that hides its limits to build a bigger story is disproven the following week.

To me this whole episode is a small mirror. It shows that Indian cricket is still searching for a balance between red ball and white ball, and that the decisions of that balance are often taken in the dark. A player whose future is in question needs to know why — not only how much. A fan who waits week after week needs explanation, not just announcement.

The final question is simple and the answer is hard. If a player 'needs more red-ball cricket,' how is that need met by moving him away from red-ball cricket? Answering that one question would have saved selectors a great deal of anger. For now the question stays open — and that open question is probably the most honest piece of reporting this week.