Badrinath Explains Patidar Omission With Goalkeeper Analogy, Questions Hardik Pandya’s 2027 World Cup Plan

The Analyst Who Can Hold Two Things at Once

Subramaniam Badrinath has had a busy Saturday and Sunday with the Cricket commentary microphone. Earlier, he delivered a withering assessment of how Suryakumar Yadav was discarded from India’s T20I setup: ruthless, pattern-repeating, and likely permanent. Now, on the same platform, he has produced an equally clear-headed but entirely different verdict on a different controversy: Rajat Patidar’s absence from the same squad.

Here, Badrinath defends the selectors. And the defense, built around one of the most vivid analogies in recent Indian cricket commentary, is both logically coherent and persuasively argued. His “goalkeeper and forward” framing cuts through the noise around Patidar’s omission and locates the actual reason he was not selected, which is not the one most of the discourse has been using.

But Badrinath is not finished. He has a second issue with the India squad announcement: the decision to rest Hardik Pandya for the next three T20I assignments, with the 2027 ODI World Cup cited as the rationale. Here, he returns to the critical mode, and his questioning of that planning logic is sharp and, given what he said about SKY’s treatment, not without a pointed irony.

The Goalkeeper Analogy: Why Patidar Is Not Competing With Dube

The most widely circulated argument for Rajat Patidar’s inclusion in India’s T20I squad had been that he should replace Shivam Dube. The logic seemed obvious: Dube had a mediocre IPL 2026; Patidar had an exceptional one. If the squad needs a middle-order batter who can score quickly, the player who scored 500-plus runs at a strike rate of 192.69 as his franchise’s captain is the natural candidate.

Badrinath identifies this framing as the fundamental error in the Patidar debate:

“Patidar comes in a different category than Shivam Dube. If Patidar warrants selection, he should be ahead of one of Tilak Varma, Ishan Kishan, or Shreyas Iyer. Definitely not, and hence his non-selection is justified. Replacing Dube with Patidar is like replacing a goalkeeper with a forward. Dube regularly bowls for the Indian team, so he comes into the finisher-all-rounder category.”
— Subramaniam Badrinath

The goalkeeper analogy is precise and immediately clarifying. In football, a goalkeeper and a forward both wear the same jersey, play on the same pitch, and count as one of the eleven. But they are functionally different in a way that makes substituting one for the other nonsensical regardless of the forward’s quality or the goalkeeper’s poor form. You do not replace a goalkeeper with a forward because they perform entirely different jobs. Their respective performance levels are irrelevant to the question of whether they can cover for each other.

In cricket terms: Shivam Dube is a finisher-all-rounder who regularly bowls for India. He provides overs, applies pressure at death, and offers options to the captain that a pure batter cannot. His place in the squad is justified not purely by his batting output but by this dual function. Replacing him with Patidar, a specialist middle-order batter who does not bowl, removes the all-rounder dimension entirely and creates a structural gap in the squad’s composition regardless of how many runs Patidar scored for RCB.

The competition Patidar is actually engaged in, Badrinath argues, is for the top-order and middle-order batting spots occupied by Shreyas Iyer, Tilak Varma, and Ishan Kishan. Against that competition, the case is much harder to make:

“Patidar comes in the exact category of Shreyas. So when Shreyas is the T20I captain, how can Patidar be in the squad? Tilak Varma has done brilliantly for India and has done well even in this IPL. Patidar has done amazingly well for RCB in the IPL, but there is no place for him in the Indian team.”
— Subramaniam Badrinath

Patidar vs. Tilak, Iyer and Kishan: The Actual Selection Battle

Repositioning the debate correctly reveals why the selectors’ decision is more defensible than the surface-level analysis suggests. Once you accept that Patidar is competing for a top-order or middle-order batting spot rather than Dube’s all-rounder role, the field changes significantly.

Patidar has never played a T20I for India. He has three Tests and one ODI to his name across his entire international career. Against a comparison field that includes the man who has just been made captain, a player Badrinath describes as having “done brilliantly for India,” and an experienced wicketkeeper-batter, the case for Patidar forcing his way in becomes significantly less straightforward than the headline numbers suggest.

Badrinath’s observation about Vaibhav Suryavanshi adds the most precise calibration to this argument: “Even Vaibhav Suryavanshi had to break the door to come. Rajat Patidar hasn’t done that well to warrant such treatment.” The word “break” is doing specific work here. Suryavanshi did not simply perform well enough to merit consideration. He produced something so compelling that the selectors found it impossible to leave him out. Patidar’s 500-plus runs are outstanding by franchise T20 standards. They have not yet reached the level of “door-breaking” performance that would displace an incumbent in a specific squad slot for which genuine international competition exists.

Harbhajan Singh vs. Badrinath: Two Readings of the Same Facts

It is worth noting that Badrinath’s position on Patidar stands in direct contrast to the one articulated by Harbhajan Singh earlier in the cycle. Harbhajan’s commentary after the squad announcement described the omission as “unfair” and characterized Patidar as “easily the best middle order in India” with a “proper striker with good technique.”

Both men are reading the same data and arriving at different conclusions, and the difference is instructive. Harbhajan is looking at the raw output: 501 runs at a strike rate of 192.69, back-to-back IPL titles as captain, sustained excellence over a full tournament. By those measures, the exclusion is genuinely difficult to justify.

Badrinath is looking at the structural question: what job does India need done in this squad position, who is already doing it, and does Patidar’s profile fit the vacancy that exists? By those measures, there is no vacancy. The positions Patidar would fill are either already occupied by players who have proven international credentials or occupied by someone who is now the team’s captain.

Both perspectives have merit. The debate between them is the actual interesting question in the Patidar discussion, and it is one that the commentary around his omission has not always located clearly enough.

The Hardik Pandya Problem: Planning for 2027 While Ignoring 2026

Having defended the selectors on Patidar, Badrinath turned to a decision he found considerably less defensible: the resting of Hardik Pandya for the next three T20I assignments, justified by chief selector Ajit Agarkar as a measure designed to keep Pandya fresh for the 2027 ODI World Cup.

Badrinath’s response was pointed and built around a specific logical inconsistency in the management’s stated rationale:

“Though they’ve said that he’s being rested with the 2027 World Cup in mind, what happens if Nitish Kumar Reddy does really well? Hardik has not played the full IPL and has had a poor run of captaincy and form. And now he’s not in the squads for the next three T20I assignments. Even if he’s tested or dealing with an injury, can’t his place be assessed after one series?”
— Subramaniam Badrinath

The Nitish Kumar Reddy question is the most strategically interesting part of this concern. If a young all-rounder is given Hardik’s role across three T20I series and performs exceptionally well, the selectors face a selection dilemma of their own creation: do they bring Hardik back at Nitish’s expense, potentially undermining a player they chose to develop, or do they maintain Nitish’s place and effectively end Hardik’s white-ball career earlier than the 2027 planning horizon assumed?

Planning three T20I series ahead for a single player, while acknowledging that the selection landscape can shift dramatically within a single series, is a level of projection that the Indian management’s own recent decisions suggest it does not reliably honor. Badrinath made this point with the irony it deserved:

“These aren’t meaningless T20s. Will Hardik Pandya play only World Cup to World Cup? When you are removing a World Cup-winning captain in two months, 2027 is far away to be planning for. Anything can happen before that, so not playing Hardik in these three T20I series for the sake of the 2027 World Cup is something I can’t understand.”
— Subramaniam Badrinath

The internal contradiction Badrinath exposes is real. A management that moved on from Suryakumar Yadav, a World Cup-winning captain, within two months of the title, demonstrated clearly that it does not find long-term planning a reliable obstacle to immediate decisions. Using the 2027 World Cup as the justification for resting Pandya across three T20I series in mid-2026 applies a planning horizon to one player that the same management conspicuously did not apply to another. If SKY could be discarded two months after the World Cup, why does Pandya get the protection of a planning horizon that extends 18 months forward?

Hardik’s Recent Record: The Context the Management Is Working With

The decision to rest Hardik does not exist in a vacuum. The context includes a difficult IPL 2026 campaign in which he struggled both as an all-rounder and as captain of Mumbai Indians, with MI missing the playoffs for a second time in three editions. The physical management of a player with Hardik’s injury history is also a genuine and legitimate consideration: he has had multiple serious injury setbacks across his career, and a proactive resting approach before an 18-month build toward a major tournament is not inherently unreasonable as a physical management strategy.

But Badrinath’s point is about the communication and framing of the decision as much as the decision itself. Saying publicly that a player is being rested with the 2027 World Cup in mind while simultaneously replacing a 2026 World Cup winner within weeks of the title creates a visible inconsistency that invites exactly the kind of criticism Badrinath is delivering.

Conclusion: The Goalkeeper Analogy Works, But the Planning Contradiction Remains

Subramaniam Badrinath’s analytical contributions to the India T20I squad debate have been among the most substantive of the post-announcement commentary period. His goalkeeper analogy correctly reframes the Patidar discussion: the exclusion is justified not because Patidar lacks quality but because the position he would fill is already occupied by players with superior international credentials, and the position the public assumed he was competing for is a structurally different role that his profile does not cover.

His concern about Hardik Pandya’s three-series absence is equally well-grounded: the 2027 planning argument is undermined by the same management’s demonstrated willingness to make short-term decisions regardless of longer-term continuity. The contradiction between these two approaches does not have a clean resolution, and it is to Badrinath’s credit that he calls it out rather than accepting the stated rationale at face value.

India’s T20I squad for Ireland and England has been chosen. The series begins on July 1 at Chester-le-Street. The debates about who is in it and who is not will follow the squad across both tours, measured against results that will either validate or challenge the selection decisions made on that Saturday in June.

The goalkeeper cannot replace the forward. The planning for 2027 cannot explain decisions made in 2026 if the same management removes its World Cup captain two months after lifting the trophy. Both things can be true at once. Badrinath said both of them, and both of them are worth hearing.