Sooryavanshi at No. 3: An Ex-India Cricketer's Objection and the Four Missing Facts

I start with a table. In this story, what was left out matters more than what was printed.

Table 1 — The report's record

| # | On the record | Off the record | |---|---|---| | 1 | Vaibhav Sooryavanshi walked out to bat at No. 3 | The format — Test, ODI, T20 or franchise | | 2 | A former India cricketer criticised the decision | The innings score, balls faced, outcome | | 3 | The call was attributed to 'the team management' | Team, opposition, venue, date | | 4 | The objection: he should have opened | The former cricketer's name and full reasoning |

My hypothesis, in one sentence, filed before the outcome: where a report never names the format, 'No. 3 versus opener' stops being a technical debate and becomes an opinion. I do not read opinions as data.

The tape showed the injury before the scoreboard did. Here the sequence has reversed — the headline showed the controversy before the match. The entire report rests on four information points and not one of them is a number: a teenage batter, a batting slot, a decision by 'the team management', and the displeasure of an unnamed former international.

Indian cricket has built a parallel economy around teenage batters, and its demand never dips. Every decade needs a next Tendulkar, and the market wants him manufactured early. Sooryavanshi is the freshest name on that pipeline. He is publicly recorded as a left-handed top-order batter from Bihar (this line is not in the source report; verification pending). Publicly reported figures place his IPL auction signing with Rajasthan Royals at roughly ₹1.10 crore, at an age then reported as thirteen (again, public record, not the source report; verification pending).

Against that backdrop, former players commenting on selections is a structural feature of Indian cricket, not an anomaly. A television studio or a YouTube channel needs one 'the call was wrong' line after every match, and a former player's face lends that line an authority a single data point cannot buy. The transmission here runs backwards: the downstream content economy is deciding how large a bog-standard midstream tactical call will become.

Now the cricket, which is the thinnest part of the report and the part that was actually needed.

Table 2 — What No. 3 means changes with the format

| Format | What batting at No. 3 actually involves | Does the objection hold? | |---|---|---| | T20 | Entry either inside the powerplay after an early wicket, or at the start of the middle overs against spin with the field spread | Partly — the powerplay allows only two fielders out, objectively the easiest scoring environment for a teenager | | ODI | Usually the anchor slot, frequently in within the first ten overs against a moving new ball | Largely — anchoring duty is a poor developmental fit for an attacking teenager | | Test | Maximum technical exposure: new ball, the opposition's best seamer, inside the first ten overs | Strong on technical grounds, and simultaneously the highest developmental value if he survives it | | Franchise T20 | A deliberately protected deployment built around match-ups | The framing is wrong — this is a coaching call, not a demotion |

An operational definition, held to one short block: in this article, 'opening' means batting from the first ball — new ball, both ends bowling seam, the field up. That is as far as it goes, because beyond this point the piece becomes an explainer and an explainer is not what this story needs.

One more thing sits inside the report's framing. The criticism treats 'opener' as an identity rather than a deployment. In modern cricket, a batting position is a match-up decision, not a status marker. When a former player says 'he should have opened', he is describing the map in his memory, not what the pitch, the opposing attack and the team's requirement were asking for that day.

Third comes sample size. One innings, one slot, and no score attached to either. Building a technical verdict on a teenage batter from that is years premature. Had the report published the score, the argument could have been tested — a good innings would have exposed the criticism as pure ideology, a failure would have exposed it as outcome bias wearing the costume of principle. Those are different stories, and the reader is never told which one they are in.

Fourth, and here I put my oldest bias on the table: sending him in at No. 3 could be a shield rather than a punishment. If the new ball was moving that day, protecting a teenager from the first ten overs and introducing him against spin is a defensible plan. The report spends not one word on that possibility. A ruptured knee taught me to distrust any system with one point of failure, and here I have to restrain my own reflex. So let me be precise: the question is not whether a second option existed. The question is whether a second option existed and was deliberately left unused, or whether the system has no redundancy at all. The first is tactics; the second is structure. The report distinguishes neither.

Fifth — the four questions the report needed to ask. I numbered the issues because the questions kept outliving the answers:

1. Which format was this?
2. Which team made the call, against which opponent, at which venue?
3. How did the innings actually go — runs, balls, out or unbeaten?
4. Who is the former cricketer, and what is the full reasoning?

Not one of the four is answered. That does not make the story false. It makes it unfalsifiable.

Sixth, and this is where the genuinely consequential issue hides: for a teenage player, the batting-order question is small. The workload and safeguarding question is not. Is there a written workload cap for under-18 players? When a franchise's commercial interest collides with a national board's development plan, whose call prevails? Is a role change communicated to a young player formally, or managed informally? None of this appears in the report, even though board-level medical age-verification procedures are a matter of public record (verification pending). Franchise scouting is quietly doing what zonal selectors once did — selection has become a valuation market, and inside that market a teenager's traffic value runs ahead of his verified output.

Now the part where I disagree with the consensus, filed in advance rather than assembled afterwards.

The consensus is that the management wronged the teenager. I read the failure somewhere else: the weakest link in this story is not the decision, it is the criticism.

The reason is simple. Had Sooryavanshi made 40 off 25 at No. 3, the same former cricketer would have praised the flexibility. The criterion is outcome, not process — and the outcome is not even in the report. We are forming a judgement about an innings whose score nobody has published.

The second reason is heavier: anonymity. The credential 'former India cricketer' survives; the name does not. Removing the name removes accountability while preserving authority. That is an excellent arrangement for the content economy and the worst possible one for the reader.

The third reason is that the frame is expensive for the player. Hearing 'you are being wronged' early becomes a habit, and every subsequent change starts to feel like an insult. The conversion rate from Indian media's next-Tendulkar labels to sustained international performance is very low, and early-career positional controversies carry close to zero predictive value.

I will also file my own condition, so that I cannot quietly rewrite this later: if Sooryavanshi's batting position changes again within the next three matches and the team management does not state a reason publicly, the criticism converts from noise into signal and I will move back toward the consensus. Pre-registration is how I keep hindsight from wearing a victory lap.

The next variable is not the batting order — it is role stability. When Sooryavanshi's score next appears on screen, look past the score to the number he walked in at, and whether that number moved from last time. Three innings at the same slot and I will treat the former cricketer's objection as dismissed, with the dismissal recorded in this column. If it moves, the question stops being 'opener versus No. 3' and becomes whether the team has a settled plan for this teenager at all. The Bengaluru desk taught me to read a match sideways: sometimes the answer is not on the scoreboard but on the team sheet.