BCCI Conducts High-Level Review Amid Overseas Struggles

The corridors at the BCCI headquarters in Mumbai will be busier than usual on Thursday. This isn’t a routine debrief. It’s a full-scale review of where Indian cricket stands after a bruising run overseas.

Head coach Gautam Gambhir, chief selector Ajit Agarkar and Centre of Excellence head VVS Laxman have all been called in. BCCI secretary Devajit Saikia and president Mithun Manhas will be at the table as well. The board wants answers, and it wants a roadmap.

There is also a strong chance that India’s white-ball leadership group will be drawn directly into the discussion. T20 captain Shreyas Iyer and ODI and Test captain Shubman Gill are expected to attend, underlining how seriously the board is treating this phase.

This meeting was supposed to happen earlier, in the immediate aftermath of the defeats in Ireland and England. The two-Test tour of Sri Lanka forced a delay. The questions, though, have only piled up since.

Champions under scrutiny

India are the reigning T20 World Cup holders. On paper, they sit at the top of the format. On the field in June, they were outplayed.

In Ireland, India slipped to a 2-0 defeat in the T20I series, a result that jolted the setup. Then came England. A five-match T20I series turned into a 4-0 drubbing, capped by a 125-run hammering in Nottingham — India’s heaviest defeat of the series and the sort of scoreline that demands more than just a quiet internal note.

Under Shubman Gill’s captaincy, the ODI leg in England also slipped away 2-1. Different format, same pattern: key moments lost, series surrendered.

A source involved in the process made it clear that the review will not be ring-fenced around those two tours alone. The lens will be wider.

“Not just the tours of the UK, the tours of Zimbabwe and Sri Lanka will be reviewed as well,” the source said.

So this is not a quick fix. It is a deeper audit of how India are travelling, literally and figuratively.

Injuries crowd the agenda

Results are only one part of the problem. The other is more persistent and potentially more damaging: injuries.

The meeting is expected to devote significant time to player workload and injury management, especially with a demanding Test schedule looming. India head to New Zealand in November for a two-Test series, and the BCCI is alarmed by the growing number of players breaking down, often at crucial junctures on overseas tours.

Shubman Gill himself voiced his frustration after the third ODI against England at Lord’s, pointing to the disruption caused by frequent injuries on foreign assignments. It was a rare public glimpse of the dressing room’s irritation.

Jasprit Bumrah’s absence from the Sri Lanka tour after aggravating a left knee injury underlined the issue. When India’s premier fast bowler is repeatedly missing chunks of cricket, every upcoming series starts with an asterisk.

The uncertainty has already spilled into the next assignment. For the T20I series against Afghanistan, announced on Tuesday, four players are still not guaranteed to take the field. Bumrah, Washington Sundar, Nitish Reddy and Harshit Rana must all clear fitness tests at the BCCI’s Centre of Excellence in Bengaluru on September 9 before they can be confirmed.

Selection meetings now come with a medical briefing attached. That is not how a side aiming to dominate across formats wants to operate.

Roadmap or reckoning?

The BCCI has framed Thursday’s gathering as a review and a roadmap discussion. The semantics matter less than the substance. Recent tours have exposed cracks — tactical, structural and physical.

With Gambhir, Agarkar and Laxman in one room, and potentially Iyer and Gill alongside the top brass, this is as close as Indian cricket gets to a war council. The decisions taken in Mumbai will shape not only how India respond to a rough overseas stretch, but also how they protect and deploy their best players in a packed calendar.

The world champions in T20 cricket suddenly find themselves under the microscope. The next few months will reveal whether this is just a stumble, or the start of a harder reset.