Not Selection, Allocation: What Yashasvi Jaiswal's Omission Actually Proves

On Friday afternoon, when the BCCI announced India's ODI and Test squads for the New Zealand tour, one absent name made the loudest sound. Yashasvi Jaiswal was not in it. A batter who four months earlier had made an unbeaten 110 off 86 balls against Afghanistan had been left out of the ODI squad. The first reaction came from R Ashwin, on his own YouTube channel, and he used one word: unfair. I did not watch this match, because there was no match. It was an announcement, a list, a missing name. In eight years of covering selection controversies, almost every one has followed the same architecture: someone is left out, a former player expresses outrage, and the discussion begins with form and ends with form. Yet the document says something else. The explanation for Jaiswal's omission is not in his form. The explanation is in the schedule. Read the document first. The BCCI announced two squads the same day: a three-match ODI series and a two-match Test series. Alongside them came the India A squad, in which Jaiswal is named for a three-match red-ball series in Lincoln starting 26 October, explicitly framed as preparation for the two Tests. KL Rahul is in that squad too, for longer-format match practice. This raises the first question. Ashwin suggested Jaiswal should play the last two ODIs. But if the ODI series and the Lincoln red-ball series run in the same window, that suggestion is not merely ineffective—it is physically impossible. Ashwin's argument does not collapse there; it relocates. The question becomes why a talent was forced to choose between two formats at all. { "The biggest fact here is not a score but a void—a 24-year-old batter is not playing regularly in any format." } Ashwin's own triple question—when did he last play an ODI, a T20I, a Test—has an answer in the Stage-1 record: last Test in Sri Lanka, last ODI in June, no T20I referenced. This is not a story of injury, nor of lost form. It is a story of scheduling. And in cricket, this kind of void damages slowly, because it destroys two things at once: match rhythm, and the layer of confidence that only competitive cricket builds. The industry rule is simple. Batters usually peak between 27 and 33. At 24, Jaiswal stands right at the mouth of that window, close enough to touch—but you cannot touch it from the dugout. Losing twelve to eighteen months of that window is not a policy decision; it is an accounting loss. This is Ashwin's strongest argument, and he made it in his weakest language, by saying 'unfair'. An argument written in the language of feeling becomes heavier when written in the language of data. Ashwin's second comment is the least verified and the most consequential: he said Jaiswal 'is not batting the way he used to bat two or three years ago'. That is the eye-test of a former elite spinner—no data, no reference to a specific innings, no timeframe. If true, it argues for managed exposure, because a player can rebuild slowly in a lower-pressure environment. If false, the sentence is itself damage, because a 24-year-old who internalises 'he is not what he was' will carry that shadow onto the field. That sentence should be treated not as a conclusion but as a hypothesis requiring a technical audit. There is an uncomfortable truth about the innings on which this entire debate rests. 110 off 86 balls, a strike rate of 127.9, against a modern ODI opener benchmark of roughly 90 to 100—exceptional. But Jaiswal entered that XI only because Virat Kohli was injured, not through a planned pathway. His one big opportunity was luck-mediated. This cuts both ways: it weakens the selectors' defence that they gave him a chance and he took it, and it equally weakens the claim that he is a proven ODI performer. One innings does not establish a level; it only shows a flash of potential. So is this omission really a rejection? I doubt it. Consider that on this tour the Test leg is the real priority—two matches, an A-team red-ball series as preparation, and an ODI leg used as a rotation instrument. The announcement itself proves it: Shubman Gill is not playing the last two ODIs, meaning the captain is being rested mid-series. When a first-choice player is rotated out and a high-performing reserve is still not picked, the rotation is not talent-based. It is allocation-based. Here is the uncomfortable part that gets lost in process talk. If the omission is a policy allocation—format prioritisation, where red-ball specialists are deliberately kept in red-ball blocks—then Ashwin's criticism is not of a decision but of a policy. And policy is hard to change, because it is tied to the World Test Championship points table, where away Test results in New Zealand carry disproportionate value relative to a bilateral ODI series. But nobody stated that rationale publicly, and that is the real problem. The communication gap is the largest issue here. No public explanation was quoted from the BCCI or the selection committee—not form, not structure. And that silence speaks loudest. Because an unexplained omission delivers a different message to the player: you are not in the squad, and nobody has told you why. That uncertainty damages more than poor form. A cricketer can lose form and return; a cricketer who does not know 'why' cannot see the road back. One Ashwin sentence I returned to repeatedly: 'the job of the team management and selectors is to create opportunities.' Notice he did not point at the captain. He pointed at the board. That is the language of a former player who was inside the system and now, from outside, questions it. But there is a subtle danger: he himself conceded he can understand Rahul's situation. The problem is not one player's but many. When multiple senior players are under-matched, it is not an individual omission but a structural failure. India's problem is not a shortage of talent but an abundance of it—and mismanaged abundance is a governance failure. The world's deepest talent pool, a fully funded A-team structure, and still a 24-year-old top-order batter sits format-idle. The mechanism that could solve it—India A, structured rotation—exists and was used, but for red-ball preparation, not white-ball development. Here the second question accumulates: is the red-ball leg so important that white-ball development must be entirely sacrificed, or was the allocation accounting done in only one direction? The New Zealand context matters here, and must be stated carefully—it is inference from the venue, not information from the article. Late October and early November in New Zealand bring green, seaming pitches and swing under cloud, conditions that are hard for subcontinental top orders. Prioritising red-ball technique in such conditions is strategically defensible. But it explains Test prioritisation only, not total absence. A three-match ODI series in which the captain plays only one game offered low-cost exposure—unless the fixtures clash. And that clash remains unverified. One thing I want to make explicit, because cricket discussion routinely conflates it: Jaiswal's Test reputation and his single ODI innings are separate pieces of evidence, and neither can be used to support the other. The 'run machine' label was earned in red-ball cricket; it is not proof of ODI readiness, just as his ODI omission says nothing about his Test standing. When the two get mixed, the decision stops being about data and becomes about feeling. In handball controversies I learned one thing—the more intense the emotion, the more necessary it is to return to process. After watching twenty-nine penalties at Russia 2026, I built a ledger: incident, law, threshold, verdict. Drop this omission into that ledger and one column stays empty: because. No explanation was offered anywhere. And that void pulls the discussion in two directions—blaming a former star, or blaming the board. The real answer is probably duller: a talent was not divided between two formats, one format was chosen, and the arithmetic of that choice was never shown to anyone. The question is no longer about Jaiswal's ODI future. The question is: when a board runs on an abundance of talent, who pays for that abundance? Usually it is the player with the least age and the quietest voice. If keeping red-ball specialists in separate blocks becomes permanent policy in India's next cycle, we will see more names who are excellent in Tests and invisible in white-ball cricket. On that day Ashwin's word 'unfair' will no longer be one man's comment—it will be the name of a policy. And personal outrage does not work against policy; only disclosure does.