"Harshit Rana Doesn't Fit the Bill Yet": Aakash Chopra Slams India's 'Baffling' Decision to Drop Arshdeep Singh

Former India opener Aakash Chopra has delivered a scathing critique of the Indian team management's decision to exclude Arshdeep Singh—the country's highest T20I wicket-taker with 101 scalps—from the playing XI for the rain-affected first T20I against Australia in Canberra. Speaking on ESPN Cricinfo, Chopra called the selection "quite baffling" and questioned whether pace-bowling all-rounder Harshit Rana, who was picked ahead of Arshdeep, possesses the consistent batting ability to justify his inclusion at number eight.

A Historic Omission

Arshdeep Singh's absence from the XI raised eyebrows across the cricketing world. The 26-year-old left-arm pacer has been India's most potent weapon in T20I cricket, picking up 101 wickets in just 65 matches at an average of 18.76 and a strike rate of 13.44. He was instrumental in India's T20 World Cup 2024 triumph and played a key role in their recent Asia Cup 2025 victory, finishing as the tournament's joint-highest wicket-taker.

Yet, for the second consecutive match—following his benching in the third ODI against Australia—Arshdeep found himself on the sidelines, with India opting for a three-spinner attack featuring Kuldeep Yadav, Axar Patel, and Varun Chakaravarthy alongside pacers Jasprit Bumrah and Harshit Rana.

Chopra's Critique: Batting Over Bowling? Chopra didn't hold back in his assessment, suggesting that the decision reflects a flawed selection philosophy prioritizing lower-order batting depth over proven wicket-taking ability.

"It's quite baffling that India's highest T20I wicket-taker can't find a place in the playing XI—even in Australia. Of course, it didn't happen in the UAE for the Asia Cup. What are the chances of him playing in the World Cup? That's the first thought that crosses the mind," Chopra said.

He continued: "The biggest takeaway is the philosophy with which this team has been playing for a while—that you need somebody who can bat at No. 8. In this case, Harshit Rana was picked ahead of Arshdeep Singh not because of his bowling ability, but just because of his batting."

Does Rana Fit the Bill? Chopra's most pointed criticism centered on whether Harshit Rana—who has played just eight ODIs and two T20Is—has demonstrated enough with the bat to justify his selection as a batting all-rounder.

"You could possibly understand if there were a better, more capable batter playing at No. 8. But the sample size we have of Harshit Rana's batting ability is not big enough to actually suggest that he is a batter who can deliver regularly at No. 8. Harshit Rana doesn't fit the bill yet," Chopra stated emphatically.

Rana showed promise with a quickfire 16-ball 24 in the second ODI at Adelaide, which helped India post a competitive total. However, his T20I batting credentials remain largely unproven. In domestic T20 cricket, he has batted sparingly in the lower order, with his primary role being that of a genuine fast bowler.

The Team Balance Debate

India's decision appears to stem from a desire to strengthen their lower-order batting—a strategy that has worked in recent times with players like Washington Sundar, Axar Patel, and the now-injured Hardik Pandya contributing crucial runs from numbers seven and eight.

The playing XI for the first T20I featured:

• Abhishek Sharma

• Shubman Gill

• Suryakumar Yadav (c)

• Tilak Varma

• Sanju Samson (wk)

• Shivam Dube

• Axar Patel

• Harshit Rana

• Kuldeep Yadav

• Varun Chakaravarthy

• Jasprit Bumrah

While the lineup boasts strong batting depth down to number seven, the question remains: does that extra batting cushion justify excluding your best T20I bowler?

Fan Outrage and Social Media Backlash

Chopra's comments echoed the sentiments of thousands of fans on social media, many of whom questioned whether there's an underlying issue between head coach Gautam Gambhir and Arshdeep. The left-arm pacer has been a regular omission under Gambhir's tenure, fueling speculation about favoritism toward Rana, whom Gambhir coached at Kolkata Knight Riders.

"Does Gautam Gambhir have a problem with Arshdeep Singh?" became a trending question on X (formerly Twitter), with fans pointing to Arshdeep's consistent exclusion despite his stellar record.

The Match That Wasn't

Ironically, the debate over Arshdeep's exclusion couldn't be settled on the field, as the first T20I was abandoned due to persistent rain after just 9.4 overs. India were cruising at 97/1, with captain Suryakumar Yadav (39 off 24) and vice-captain Shubman Gill (37 off 20) looking in ominous touch before the heavens opened up.

The performance of Harshit Rana—or lack thereof, given the shortened match—means the selection debate will carry forward to the second T20I at the Melbourne Cricket Ground on Friday.

What's Next? With four more matches to go in the series, the big question is: will Arshdeep Singh get a game? Or will India continue with their current strategy, risking the ire of fans and experts who believe the team's most successful T20I bowler deserves better treatment?

For now, Aakash Chopra's words hang heavy in the air: "Harshit Rana doesn't fit the bill yet." Whether the team management agrees remains to be seen.