Indian Cricket's Ledger: Chennai's Quartet, the Workload Arithmetic, and Three Questions Still Awaiting an Answer

Early mornings at Chepauk do not begin with the sound of a bat. They begin with a stopwatch. I have been following that sound for twenty-three years, from the sports desk at The Times of India to now, and I have no hesitation in admitting that more than half the big narratives I wrote in that time were later corrected by the scorebook. Which is why I now work backwards. Paperwork first. Noise later.

Over the past three weeks I have filled four separate notebooks in four separate places — a franchise practice session in Chennai, a visit to the national academy in Bengaluru, a domestic fixture in Ahmedabad, and four hours outside a selection meeting in Delhi. These four have nothing in common except one thing: in each of them I was asked the same question, and in each of them I had to give the same answer — "I don't have that data."

This piece is the record of that honesty. It will not tell you who wins. It will tell you whose books are being kept, whose are not, and which question has been stretched so long that it has stopped being a question and become an excuse.

Context: where the numbers are, there is no story — and where the story is, the numbers are missing

In 2026, covering Tamil Nadu's Ranji Trophy campaign, I built a simple spreadsheet. Every over bowled by every seamer — date, spell length, rest days. Three matches in, one name surfaced: Aswin Crist, twenty-one years old, one hundred and twenty overs in twenty-one days. I went to the team manager, asked for training data, was refused, cited the BCCI's media access rules, and eventually got it. He was rested after the report ran in The Hindu, and the stress fracture did not happen.

I repeat this episode because its real lesson differs from the popular version. The popular version says: data saved a body. The real lesson says: data is worthless until somebody owns it, and the owner of training data is never a journalist. I got that data under the pressure of a rule, not as a favour. Even today, when a franchise promises me "full cooperation," I ask — under which document?

This year's domestic calendar sharpens the question. The Ranji schedule, the A tours and the franchise pre-season camps overlap inside the same window. When I asked a coach in Ahmedabad which of the three his fast bowler was available for, the answer was: "All three, and that is why he is half available for all three." It was not a joke. It was the most precise description of a workload-planning problem I have heard this year.

Core analysis: four things I can verify from my notebook, and one I cannot

One: Chennai's pattern is not captaincy, it is batting order. In 2026, when I was assigned the Chennai return as beat reporter, I logged batting positions at every practice session. Dhoni was not batting fourth in the nets; he was batting fifth. I wrote that he would be used as a finisher across the season — not merely an observation but a tactical forecast, and I put a date on it. In the first five matches he batted at five or six, making one hundred and fifty runs at a strike rate around one hundred and sixty.

But I will not present that forecast as a triumph, because the same notebook has another page I never showed. Early that season I wrote that Chennai's middle order was thin on depth and would sit down under pressure. That was wrong. The first rule of my method is that a forecast carries a date, and a wrong forecast stays in the same document. People who remember only the forecasts that held are not writers, they are publicists.

Two: workload arithmetic is not only fast-bowler arithmetic. Workload has been debated heavily in recent years, but ninety per cent of that debate stops at the seamers. What I actually see on the domestic circuit is different: the wicketkeeper's load, the all-rounder's load, and above all the mental load. A BCCI official told me in conversation — and this is paraphrase, not an official statement — that digital medical files are maintained player-by-player, but there is no public framework governing the discretion with which they are shared with team management. Having data and using data are two separate institutional capabilities.

Three: selection is an accounting problem, not a talent problem. From the meeting outside which I stood in Delhi for four hours I obtained no inside information — let me be clear about that, because that distinction should stay alive in sports journalism. But while standing there I saw something I can put on paper: the three names under discussion had wildly different domestic records, yet nearly identical international caps. "In the mix" is a status that can be maintained for years without producing a verifiable evidence trail. That is not a charge against selectors' intentions; it is a charge against their documentation. When a player gets eleven innings across fifty matches, saying his "evaluation is ongoing" is an accounting sentence with the expense line removed.

Four: franchise and domestic cricket are not the same milestone. Agenda-setting routinely assumes franchise success benefits the domestic structure. I opened the spreadsheet and looked differently: between a large franchise's retention architecture and the domestic load carried by players from the associated state association, I found no clean relationship. A retention ledger describes a team's policy; it does not describe whether that state is producing fast bowlers.

And the one thing I could not verify: the actual workload data behind any major selection call this year. I asked. I received aggregate-level information, not player-level. Where the paper was not provided, I will not turn inference into conclusion.

The contrarian angle: perhaps the entire workload argument is asking the wrong question

Here I want to challenge my own coverage, because my age and my beat have kept me close to people who take the older argument as natural.

The conventional argument runs: overs = load = injury. Therefore count overs. But what I have heard in recent years from the people who actually keep the medical files suggests this arithmetic is incomplete. Over counts tell you how much work was done; they do not tell you how it was done — at what cost, between which rest cycles, after which travel sequence, on which pitch surface. The most useful honesty in this piece is that the full relationship between workload and injury remains publicly unproven, and those who argue as though it is settled are in fact selling an under-reported phenomenon as a robust theory.

A second comfortable belief falls to the same reasoning. Many of us assume Chennai's long success is the product of one man's leadership genius or some vague "environment." I have written that directly; it is my franchise verdict, and here I disagree with my own source. What is visible is this: the composition of the retention sheet, separately recruited bowlers dedicated to death overs, and auction money spent on a role map fixed before the auction rather than on names. That is not aura, it is arithmetic. And I had to write that sentence first against the franchise that has given me fourteen years of press access, otherwise the whole exercise would be for show.

The reverse side also applies, and I will admit it. The same logic applies to the criticism I level at others. When I say selectors do not show their papers, someone can stand up and ask: where is my notebook? I have recorded one of my own failed forecasts in this article. In my second instalment I owe the full notebook, unedited, or I am doing precisely what I accuse others of. Accountability that only runs upward is not accountability, it is a press card.

The takeaway: three things settled in the next six months, and three answers the domestic stage will or will not provide

First, the calendar question. The collision of the domestic season, A tours and franchise pre-season that showed up this year will sharpen in the next window, and someone will then make a management choice without written agreement with anyone involved. Dated in my notebook today: this overlap will be decided not by a policy document but by an individual request, and we will not know about it until later. That is a forecast, and I cannot dodge it; it is on the record.

Second, the selection documentation question. If the board does not make the basis of workload and selection publicly traceable, this debate will never end, because every question will receive the same answer: "individual assessment." And "individual assessment" is the phrase that defers accountability indefinitely.

Third, and hardest. Whether we journalists can summon the nerve to publish our own errors, particularly in coverage where access is good. The material I hold from the Chennai dressing room makes me feel like a colleague. The scorebook does not. The scorebook remembers what the highlight reel forgets — and the most important assignment I have this year is not covering someone else's Ranji debut, but striking out one of my own old lines in public. I did not ask for this ledger; I built it. The pressure to read it is mine now, and I hope that when I lift that page, nobody has swapped the table underneath me.