India's No.3 Dilemma: A Documentary Audit of the 'Flexible Batting Order', Where the Evidence Is Three Matches Long

In that first IPL auction room in Mumbai in February 2026, when I began logging every sold lot against its base price, I learned that cricket's truth never sits in the headline — it sits in the annexure. The debate raging over India's T20I batting order these past few days reminds me of that same file. Three former internationals are repeating one line on television: modern T20 demands a flexible batting order. It sounds wonderfully modern. But before I talk, I did what I always do — I pulled the paperwork, opened the numbers, and checked who is actually paying the bill for this 'flexibility.' The answer was written plainly on page one: the youngest player.

The trigger for this debate is an injury, not an idea. Ishan Kishan's groin injury vacated the No.3 slot for the second T20I against New Zealand, and team management, rather than disturbing the settled Samson–Abhishek opening pair, sent Vaibhav Sooryavanshi to No.3. This was not a strategic experiment. It was a least-disruption default — the newest player was the one asked to move. And the result is on the record: Sooryavanshi looked out of sorts at No.3, and the moment he returned to opening, a record powerplay stand followed.

This brings back an old memory. In May 2026, when arrests were being made in the IPL spot-fixing case, I was the only woman journalist on the Mumbai briefing calls. I deliberately stopped chasing the crime and started reading the paperwork — which clause voided a fee, who owed a franchise what. That experience taught me that when there is noise everywhere, the quietest voice is often the most correct. In this batting-order debate there is plenty of noise, but the quiet voice — the data — is saying something else.

The first evidence for flexibility is Ishan Kishan, and he is the only one. At No.3, 933 runs in 28 matches at an average of 35.9 and a strike rate of 171.2 — an established, reliable profile. As an opener, 176 runs in five matches at 35.2 and a 193.4 strike rate — a small sample, but the direction is clear. Kishan is the only player in the entire Indian team with a credible record in both positions. If the flexibility doctrine should apply to anyone, it is Kishan. But those arguing 'everyone must be flexible' are ignoring the fact that flexibility is not free for everyone.

Tilak Varma is the strongest refutation of this doctrine. At No.5, 348 runs in 17 matches at 38.7 and a 145.0 strike rate — this is a batter built to accumulate through the middle overs and explode at the death. At No.3, seven matches, an average of 16.4 and a strike rate of 108.5 — a collapse of roughly 36 points. This is no coincidence. This is the profile of a player whose game is built not against the new ball's pace but against spin and death bowling. Send Tilak to No.3 and you convert his greatest strength into his greatest weakness. Here the slogan of 'flexibility' becomes a direct loss-making deal.

Now the figure most twisted in this debate. Sanju Samson's No.3 numbers — three matches, 27 runs, an average of 9.0 — carry no statistical meaning whatsoever. Three matches cannot support any conclusion. And this is the biggest data-integrity trap in the entire debate. Those saying Samson cannot bat at No.3 are mistaking three matches for truth. Those saying the senior player should be the one to move are making an argument of culture, not performance — a leadership and fairness argument, and it should be honestly called that, not dressed as data. Both sides can be right in their own logic, but both make the same error: they are building policy on samples of three to seven matches.

I have a documentary point to make here. Those backing flexibility do not have the evidence of player numbers; they have the evidence of former players' voices. Three former internationals are saying the same thing, and the media is turning it into consensus. But listen closely and there is no consensus — there is a split. One side says the batting order should be flexible. The other says it should be flexible, but the senior player should make the change. These are two different things. The first is a principle; the second is an implementation condition. And the least-heard voice in this debate is the one asking: if flexibility is so essential, why is it being applied to the youngest player? Is sending Sooryavanshi to No.3 a development decision or a convenience decision? That question should be put to team management, not to the commentary box.

Let me be clear that I am not against flexibility. I am against the way it is being proven. India does not lack openers — it has a surplus: Abhishek, Samson, Sooryavanshi and Kishan are all fundamentally No.1–2 players. This is a luxury problem, not a crisis. And a luxury problem is solved not by doctrine but by role-mapping. Kishan is the one piece you can use in two places. Keep Tilak permanently at No.5. Give Samson and Abhishek stability at the top. Let Sooryavanshi develop in his natural position. Flexibility should be applied once, not everywhere.

I remember when I began as sports editor at The Times of India in 2026, we had a golden rule: before printing any claim, ask for its source. Today every number in this debate is circulating without attribution. 28 matches, 933 runs, 171.2 strike rate — which database is that from? Up to what date? Does it include matches on small grounds? Until those questions are answered, no policy conclusion can stand on paper. And this is my biggest concern: we are changing the role architecture of a national team on the basis of a debate whose data foundation is three to seven matches. No position-specific conclusion should be called a trend on a sample of fewer than 15 matches.

What next? The thing to watch in the next series is whether Kishan, on return, sits at No.3 or opens. If he returns to No.3, it means this flexibility was not a permanent policy but a temporary injury fix. If Samson is tried at No.3, it means the senior-first principle won. And if Tilak is sent to No.3 despite his numbers, it means doctrine has outgrown data. The answer to all three will be on the next team sheet. I will be sure to read that paper — because whatever the headline says, the truth is always written in the one column nobody reads: the team sheet.