3 reasons why India dropping Sai Sudharsan for IND vs SA 2025 1st Test is the wrong move

Team India youngster Sai Sudharsan found himself out of the playing XI for the first Test against South Africa at the Eden Gardens in Kolkata, as Washington Sundar emerges as a new candidate to audition at No.3. The Men in Blue have already tested out Karun Nair and Sai Sudharsan for the slot amid transition, but have gone with a radical approach to accommodate a fourth spin bowling option in the side.

Sai Sudharsan had a decent home series against the West Indies, where he recorded his highest score of 87 in the second Test in Delhi. However, the erratic start of his international cricket continues as he finds himself on the bench yet again, even after the recent promising display for India.

On that note, let us take a look at three reasons why India dropping Sai Sudharsan for IND vs SA 2025 1st Test is the wrong move.

#1 It sends the wrong message and leaves players vulnerable

After an early stage of trial and error, Team India had branded Sai Sudharsan as their long-term No.3, promising him a long run at the spot to acclimatize. Interpreting the words of the team management and selectors regarding their backing of Sai Sudharsan, it would have needed a drastic set of circumstances for India to deviate from their word.

However, nothing of the sort has happened, and Sudharsan still finds himself out of the team. In fact, what makes it worse, is the fact that he is not considered right after he arguably had his most confident outing in an India shirt. After a shaky start, the left-handed batter seemingly had his moment in the second Test in Delhi, where he struck a confident fifty. All he needed was more such outings to cement his place. However, Team India's affinity towards experimentation, even in instances where it is possibly not needed, has cost Sudharsan a massive opportunity.

India making such radical, unnecessary changes, especially when the axed player is not largely at fault, diminishes the value of the promises they have made so far, and the ones that they are going to make. From the player's perspective, knowing that his place is not safe, even if there are performances under his belt, does not allow him to operate at his best, even if an opportunity arises in the future.

Even though the communication between the team management and the player might be optimal, it does not alleviate the core concern at all, which is the player's security.

#2 India can't go with horses-for-courses while tampering with the batting core

Often, when teams want to go overboard with an area of their bowling to suit conditions, they usually make that adjustment within the confines of the overall bowling unit itself, and the batting line-up largely remains untouched. In other rare instances, teams are willing to compromise their batting depth for the extra bowling option, but never the batting core, especially not the top three.

However, a combination of an immense faith in Washington Sundar's batting ability, an obsession with all-rounders, and an unforeseen need for six bowling options has seen even a top-order batter like Sai Sudharsan displaced for an all-rounder at No.3.

Even the South African side has an all-rounder slotted in at No.3, but the circumstances are entirely different. Firstly, he is a proven candidate boasting an average of 75.13, including a triple hundred in the position. Secondly, the Proteas are without an alternative for the No.3 slot, especially with Tristan Stubbs not impressing, and Tony de Zorzi settling into the middle order after a stint as an opener.

#3 Long-term grooming should have been the priority rather than meeting the needs of one game

Given Sundar's recent batting form and his improved confidence, chances are that he might be among the runs at No.3, but will be entrusted with the same role in overseas Tests in more challenging circumstances? Odds are that India might need a pure batter and a much more orthodox option at No.3 to combat such a challenge.

This sort of start-stop trend does not help Sai Sudharsan in any way, and for him to be a successful, long-term No.3, he needs confidence, which can only come with consistent game time. So far, he has been dropped after his very first game, then recalled after two matches. And now, after four games in a row, he finds himself out again for no good reason.

In stark comparison, when Shubman Gill had a tough start to life at No.3 in 2023, he needed at least five matches in a row, before he finally looked settled into the role during the 2024 home series against England. When India already have such a template as to how to groom a player at No.3, it makes their current approach that much more baffling.

The constant omissions will only delay Sai Sudharsan's development at No.3, and hamper India's long-term plans. With each stutter and break that the youngster is being treated with, he should ideally be given that much more time to cover up.

In this particular scenario, developing Sai Sudharsan by continuing to give him a run at No.3 to secure the long-term goal should have been given precedence over including a fourth spinner in the playing XI.