Vaibhav Sooryavanshi at No. 3: A Debate That Has Misplaced Its Format, Its Score and Its Team

At 11:40 p.m. on a Delhi desk, a folder opens. It is called sooryavanshi_position. Inside is one file and four lines. Line one: Vaibhav Sooryavanshi batted at No. 3. Line two: a former India cricketer said he should have opened. Line three: the former cricketer was not named. Line four: the team was not named.

Line five is blank.

Twelve years of watching matches has taught me that line five is the real story — the format, the score, the over in which the innings began, the bowler running in. This time nobody wrote it. I write the date first, because memory is a poor archivist and the beat is not. Here, there is no date either.

What remains is an assertion. And an assertion cannot be read the way a scorecard can.

CONTEXT: the grammar of the "slams" headline

Cricket media runs a ready-made template: an unnamed former international questions a team management's call, and a teenage name carries the traffic. Two things are deliberately left open — the speaker's identity and the match details. The first protects the reporter from a rebuttal. The second protects the report from being checked.

Four days in the Holkar corridor taught me to count footsteps before names. December 2026, Ranji Trophy final, Delhi against Vidarbha. With no press-box seat I worked the team hotel lobby, and heard a Delhi senior call the pitch "two-paced" twelve hours before the toss — a detail no scorecard carried. Since then a filing rule has held for nine years: no report leaves my desk without one detail that could not have come from the scorecard or the broadcast.

That detail is absent here. What I can verify is only this: a teenage batter went in at No. 3, a team management made the call, and an unnamed former India player called it wrong. The career background circulating in the media — Andhra domestic cricket, a big score as a teenager, a franchise contract — sits in my file tagged "pending verification", because the source material does not contain it and I have not independently cross-checked it.

In the summer of 2026 I keyed 143 Delhi Ranji innings from 78 matches into a spreadsheet nobody asked for, testing whether Delhi collapsed more often batting second. The piece ran in August 2026 and two Ranji coaches forwarded it back to me. The habit stuck: build ten seasons of sheet before you ask a player for his time.

No spreadsheet can be built from this story. A one-row sheet is not a sheet. The argument is about a batting position; the evidence is about something else entirely.

CORE: four questions nobody asked

One — format. This is the first question any analyst should have raised and nobody did. No. 3 in T20 means something different from No. 3 in ODI and something else again in Test. In T20, a No. 3 entering inside the powerplay faces only two outfielders — objectively the easiest scoring environment available to a teenager, easier than opening, because the opener gets the new ball from both ends from ball one. A No. 3 entering after the seventh over, by contrast, faces spin with the field spread. In ODI, No. 3 is the anchor slot, often in against the moving new ball inside ten overs. In Test, it is the most technically exposed position in the game. In franchise T20, it is frequently a protected, match-up-driven deployment rather than a promotion or a demotion.

None of this is specified. Without a format, "No. 3 versus opener" is not a debate, it is an opinion — and an opinion printed as news is an editorial choice, not analysis.

Two — is position identity or match-up? The criticism rests on an assumption: opening is this batter's "natural" place, so No. 3 is a step down. That is position essentialism. In modern cricket, batting order is a match-up decision, not a status marker — which bowler arrives in which over, what the left-right combination demands, when the field spreads. A player measured by his slot rather than his entry conditions never consolidates a role at all.

Three — sample size. One innings, one position, unknown outcome. Drawing a technique verdict from that is like writing a pitch report from a single over. We do not even know whether he scored. If he did, the criticism is outcome resentment dressed as principle. If he did not, the same problem applies, because without the score we cannot separate process from result. A claim that cannot be falsified is not analysis; it is a statement.

Four — development and workload. For a teenage batter the real question is role stability, not No. 3 versus opening. Repeated shuffling is a recognised developmental hazard because it prevents a repeatable role from forming; controlled flexibility also has value, broadening technical range and reducing single-position dependency. The difference is whether the shift was planned and communicated or ad hoc. The report says neither. And the number missing from the entire argument is his match-minutes over the last six months, across age-group, domestic and franchise cricket. Writing about a teenage player without asking for his workload ledger is valuing a company without reading its balance sheet.

The unnamed source. "Former India cricketer" is a credential, not a source. Anonymity removes accountability while retaining authority — the result is an unfalsifiable claim with high emotional payload and zero printing risk. It inverts my corridor-log rule, where every line carries a timestamp so that later you know who spoke and when.

Five — the transmission is running backwards. Normally the game flows downstream: development, then selection and role, then media, then brand. Here, downstream media demand is setting the perceived importance of a midstream tactical call. A nameless studio remark cannot decide selection. It can decide how that selection is received — and public reception is what makes a selection committee defensive next time.

CONTRARIAN: the demotion lens may be on the wrong number

The easy reading is that moving an opener to No. 3 is pushing him back. My file suggests the reading may be inverted, at least in T20. A No. 3 entering inside the powerplay is technically better placed than an opener: two fielders out, a new ball but an empty field, licence from ball one. If this was a T20 and he walked in before the sixth over, the criticism weakens considerably. If it was a franchise game, "demotion" is a category error — that slot is often a protected, match-up-based deployment.

I will not overstate my own case. If this was an ODI, the criticism largely holds: the anchor role is a poor developmental fit for an aggressive teenager. If it was a Test, the criticism is technically strong, even though the same position offers the highest developmental value. Which means: the former cricketer may be right, but not for the reason he is being quoted. His stated logic is natural-position fidelity; the real logic would be entry conditions, and entry conditions are exactly what the report omits.

From outside this looks like management versus player. The third party is missing: the ledger that should reconcile all three. Until it is published, the argument will keep circling — one side calling every change strategy, the other calling every change injustice, and a teenager in the middle hearing the same message from both: your place is not yours.

TAKEAWAY: watch the team sheet, not the studio

The next internal signal sits in the next three team sheets. If Sooryavanshi stays at No. 3, it was a planned block and the commentary was noise. If he is restored to opening immediately, the question becomes whether selection changed or pressure changed — and that is the genuinely worrying scenario, because the next young player's role would then be decided by a studio rather than a coaching staff. My corridor log puts the date before the name. Here there is no date, so the verdict stays where it belongs: deferred until the sheet arrives.