Aakash Chopra on Prabhsimran Singh's Omission: 'What's His Mistake?' Before the 3rd T20I vs Zimbabwe

Aakash Chopra has spent two matches asking the same question out loud. With India already 2-0 up against Zimbabwe and the third T20I about to be played at Harare Sports Club on Sunday, the former India opener wants to know what Prabhsimran Singh has actually done wrong to be sitting out every playing XI the team management has named so far.

The question Chopra has put on record

On the eve of the third and final T20I at Harare Sports Club, Aakash Chopra addressed Prabhsimran Singh's omission in his YouTube broadcast and asked a question that has been hovering over India's white-ball squad since the team was announced. "What's his mistake?" Chopra said, in so many words. He pointed out that the squad had travelled to Zimbabwe with Prabhsimran as a wicketkeeper-batsman option, and yet two matches have passed without a single appearance. If he is not in the XI now, Chopra argued, when is he ever going to be, and on what specific decision was the team management basing that call?

Chopra's suggestion, made explicitly and on the record, was to rest Ishan Kishan and give Prabhsimran the gloves for the third T20I. The reasoning is uncomplicated: India are 2-0 up in a three-match series, the result of the contest no longer carries consequence for the scoreline, and a one-match debut window is exactly the sort of platform selectors traditionally use to blood a wicketkeeper-batsman with a long domestic record. That Prabhsimran remains untouched heading into the final match is what prompted the question.

It is worth stating the obvious about selection conversations of this kind. Chopra is not part of the team management, and his suggestion is one of several that fans, broadcasters and former cricketers have put forward in the last week. The India head coach, the captain and the chairman of selectors retain the final call, and they have not publicly responded to his specific proposal. The interest of the story is that a former India opener with a direct line into the fan conversation is making the case that the squad composition itself deserves scrutiny, and that argument sits naturally against the backdrop of two convincing wins that have already settled the series.

What India have already done in this series

India went into the third T20I with an unassailable 2-0 lead after winning the opening two matches in Harare. The second T20I was the more decisive of the two: India posted 219 for 5 in their twenty overs and bowled Zimbabwe out for 129 in the 18th over, a margin of 90 runs. That scoreline tells you almost everything you need to know about how the middle order is currently functioning. Ishan Kishan was named Player of the Match for an innings of 81 off 44 balls, and Tilak Varma finished not out on 60 from 29 deliveries at a strike rate that is genuinely hard to sustain over twenty overs. Together those two were the engine of the chase-defying total.

That context matters for the Prabhsimran debate. Ishan Kishan is not merely occupying a squad spot, he has been one of the two standout performers of the series so far. He has kept wickets, opened or batted at the top of the order in both completed matches, and his 81 in the second T20I is the kind of innings that hardens a captain's trust. The selector's case for retaining him for the third T20I does not need to be invented: it is sitting on the scorecard. Chopra's counter is that "hardened trust" is exactly the moment to rotate, not the moment to dig in.

Prabhsimran Singh's domestic record in the room

Prabhsimran Singh's case for selection is built almost entirely on his T20 numbers at Punjab Kings in the IPL and his domestic T20 record across formats. Before the India tour to Zimbabwe, his T20 career sat at roughly 3,665 runs in 127 innings at a strike rate of about 151.50. That is the headline statistic that selectors, broadcasters and fantasy cricket users have all been quoting since the squad was announced. It is also the statistic that fans are using to argue that an opportunity should come sooner rather than later.

The context for those numbers matters. Most of Prabhsimran's T20 runs have been scored in the IPL for Punjab Kings, in conditions that range from flat Mohali decks in mid-April to slower surfaces in the second half of the league. International cricket in Harare is a different environment: a relatively short boundary square of the wicket on one side, a slower outfield than what Indian crowds are used to, and Zimbabwean spinners who will bowl a lot of overs through the middle phase. Chopra's argument is essentially that the only way to find out whether those numbers translate is to give him the gloves for a match and let him find out for himself.

What the selectors have not done, as of the eve of the third T20I, is publicly indicate when the next opportunity will come. Chopra's question, on his YouTube channel, was specifically aimed at this silence: if Prabhsimran is not playing in the third T20I in a series that is already won, then in which fixture is he actually pencilled in? There is no public answer yet, and that absence is the heart of the story.

Abhishek Sharma's quieter start to the series

The other player in the selection conversation is Abhishek Sharma, who batted in the top three in both opening T20Is. Chopra's recommendation was specifically to rest Ishan Kishan rather than drop Abhishek Sharma, a distinction that tells you what Chopra thinks is actually happening in India's middle order. Abhishek Sharma scored 1 in the first T20I and 8 in the second T20I — modest returns in a series that has otherwise been dominated by big scorers. The chopra case is that Abhishek is being kept in the XI because the team management is investing in his role over the next year or two, and that rotating the wicketkeeper-batsman slot at the back end of the series is the simpler swap.

The Times of India coverage of the same selection conversation noted exactly this distinction. Abhishek's scores, the paper wrote on 26 July, do not reflect his long-term value to the side. Chopra agreed on that point but disagreed on the conclusion: he would have preferred the rotation at the wicketkeeper position rather than at the top of the order, on the grounds that Ishan Kishan's 81 has already given the team management what they needed from him in this series.

There is also a context question that the broadcast did not dig into as deeply. India have a T20 World Cup cycle ahead, and the selectors are likely to use bilateral series like this one to test combinations. If Abhishek Sharma is being groomed for a specific role in the 2026 cycle, his two-match run in Harare is one piece of a longer evaluation. That does not change the strength of Chopra's argument about Prabhsimran, but it does explain why a rotation that looked obvious from the outside has not happened.

The two debutants who have already played

One piece of context that often gets missed in the Prabhsimran conversation is that India have used the first two T20Is to hand international debuts to two young fast bowlers. Ashok Sharma and Yash Thakur both debuted in the series — one across the first two games — and the team management has been open about wanting to test fast-bowling depth ahead of a busy year. The clear implication is that this tour has been used, by design, as a development window for bowlers India consider part of their white-ball future.

If that framing is correct, the question for Prabhsimran Singh is whether the team management sees the third T20I as a development opportunity for wicketkeeper-batsmen in the same way that the first two games were a development opportunity for fast bowlers. Chopra's argument is that the symmetry is obvious and that the team management should act on it. The selectors have not, as of publication, given any public indication that this is how they are framing the third T20I selection.

The fast-bowling picture is also worth dwelling on for a moment. Prince Yadav suffered a hamstring injury during the second T20I and had to leave the field mid-spell, which is the kind of on-field disruption that often prompts a tactical reshuffle even when the captain's instinct is to hold his XI. Whether Prince Yadav's injury changes the third-T20I calculus on the bowling side is a separate question, but it is one of the variables that the team management has had to weigh into the selection meeting.

What Shreyas Iyer's captaincy record tells you about this series

Shreyas Iyer's captaincy in this series is the first bilateral series win of his tenure as India's white-ball captain. The wider context here is important. India lost the T20I series in Ireland and then lost the T20I series in England before this tour began, and Iyer's first series win as captain is therefore also the first opportunity his side has had to reset the conversation around his leadership. The 219/5 in the second T20I, and the 90-run margin that followed, are exactly the kind of performance that does the resetting.

That context cuts both ways in the Prabhsimran debate. On one side, the captaincy is being judged on results, and a 2-0 lead gives Iyer the room to blood a debutant in the dead rubber without risking the headline numbers. On the other side, the captaincy is also being judged on man-management, and one reading of the situation is that Iyer will want to lock in his core group for the next series rather than test a new combination on the way out of this one.

The Hindustan Times coverage of Chopra's remarks also noted that this is Iyer's first series win, and framed the debate partly as a question about how Indian captains manage dead rubbers. The article did not name a specific captain who has handled that question either way, but the implication is that a leadership group in transition tends to be more cautious about late-series changes than a leadership group that has settled into a run of results. India's white-ball unit is somewhere in the middle of that transition, which is why the third T20I is a more interesting selection decision than it might otherwise look.

What fantasy cricket users are watching for in this XI

For MyTeam11 users who build teams around the India T20I squad, the selection question matters less for fantasy points on Sunday and more for what it tells you about the team's white-ball thinking over the rest of the year. Fantasy team selection is, at root, a forecast: you are betting that the player you pick will be in the XI, will bat in a specific position, and will keep wickets or bowl a specific quota. The forecasts become more useful when you understand which players the team management is willing to rotate and which they are not.

If Prabhsimran Singh plays the third T20I, the immediate fantasy implication is straightforward. He slots into the wicketkeeper-batsman slot and you get one match of data on his international ceiling before the next series. If he does not, the data point you actually take away from Sunday's match is that the team management is happy to carry him as a non-playing squad member, and you build your fantasy plans around that reading. Both readings are useful; they are just useful in different ways.

The Ishan Kishan captaincy question is the more concrete fantasy angle, regardless of what happens to Prabhsimran. Ishan has been Player of the Match in the second T20I and has been India's most decisive white-ball performer of the series so far. On the MyTeam11 ownership feed, captaincy on Ishan is likely to be heavy if he is confirmed for the third T20I. The differential read is to captain someone else from the same side and use Ishan as vice-captain, which is the standard fantasy logic when ownership runs hot. The Chopra rotation proposal would change that calculation, but only if the rotation actually happens.

The other fantasy-relevant detail is Prince Yadav's hamstring injury. If he is ruled out of the third T20I, India will almost certainly name a replacement bowler and the bowling attack for the final match will look different from the attack that won the second T20I. The MyTeam11 platform does not always reflect injury-driven changes in the projected-points feed until the playing XI is announced at the toss, so the practical advice is to wait for the toss before locking any team that includes Yadav.

Where the debate is likely to go next

The most concrete way to measure whether the team management has heard Chopra's argument is the third T20I playing XI itself, which will be announced at the toss on Sunday afternoon. If Prabhsimran Singh is named, the debate effectively closes: selectors acted, the rotation happened, and the next question is how he performs. If he is not, the conversation extends into the rest of India's white-ball calendar, because every XI announcement is going to be read against the standard Chopra just set.

For fantasy users, the watchpoints for the toss are simple: confirmed XI at 4:00 PM IST, MyTeam11 lock-in 30 minutes later, and then the live scoring engine takes over. For readers who are following the wider selection debate, the watchpoints are the team management's press comments after the third T20I and the next squad announcement, whenever that comes. There is no indication yet of when that next squad will be named, and that uncertainty is itself part of what makes Chopra's question land.

The wider point worth holding onto is that the selection logic in white-ball cricket is rarely as straightforward as a single innings or a single series. India have won the series 2-0, the new captain has his first series win, two fast bowlers have debuted, and the squad depth is being stress-tested for the next twelve months of fixtures. Chopra's argument that Prabhsimran should get a game in the dead rubber is one of those cases where the obvious reading and the team-management reading are pointed in different directions, and the playing XI on Sunday is the cleanest answer to which reading wins out.

Frequently asked questions

For more coverage on this series and live India cricket, browse Live Cricket Matches for fantasy captain reads, post-match analysis, and the next toss-time preview.