The Bowlers Aren't Breaking — The Schedule Is: Who Keeps India's Injury Ledger?

Chepauk, 2026

In the 2026 Tamil Nadu Premier League, my job in the scorer's box at Chepauk was not just to write down runs. Across thirty-two matches I logged every bowler's spell, the rest between spells, and every moment the game stopped for what looked like an injury. It was dull work and I finished it.

For thirty matches no column showed a pattern. The pattern turned up in the last column — seven bowlers who sent down more than 120 balls inside fourteen days. Two of them withdrew from local cricket before the next season began. One with a shoulder, one with an ankle.

I was twenty-one and I thought I had found something. Fifteen years later I know I had found nothing. I had simply built the table somebody else should have built first.

In 2026 the cricket was shut and the stadiums were empty. On a Chennai desk with no live cricket to cover, I collected fourteen absence and illness notices and eight Ranji Trophy scorecards. Fourteen absence notices had already arrived before anyone thought to build a table. Five soft-tissue absences in that table sat within eleven days of a three-day turnaround.

This piece starts with those two tables and rests on one question: in Indian cricket, who actually keeps the ledger on fast-bowler injuries?

What the document is, and what it is not

An absence notice is a short document. It carries three things — a name, a number of days, and perhaps one word: soft tissue, side strain, right shoulder. What it does not carry is the date the physio first knew. That gap, between the physio's note and the team sheet, is the most important number in my work. I call it reporting lag, and in Indian cricket the lag is frequently larger than the injury.

From thirteen years of watching matches, one observation holds: a player rested under the phrase "workload management" is very often unavailable three weeks later for an entirely different reason. Television shows these as two separate events. In a ledger they are two instalments of the same event.

India has no public injury database. That sentence sounds simple and is not. The board keeps an internal record, the National Cricket Academy keeps a rehab record, the franchises keep a record of their own players, and the media holds whichever fragment of a team bulletin somebody forwarded. There is no shared column between the four. So when someone calls a bowler "injury-prone", he is not speaking from a table anyone has seen.

There is a second quirk. A bowler who plays through pain and never files a notice is entirely missing from my dataset. A player who sits out for an unrecorded reason is missing too. The absence of a record is not evidence of the absence of an injury — and that is precisely the gap most cricket journalism walks past without mentioning.

The four columns that matter

I do not sort bowlers by name. I sort them by load profile. Four measures: total overs in a seven-day window; spells per session; days between matches with travel days counted in; and the interval from the physio's note to the team sheet. The fourth is the least visible and says the most.

Put all four together and something awkward surfaces. In the Indian domestic calendar the highest risk does not sit with the bowler who bowls the most overs. It sits with the bowler whose load spikes — the one given little work for three weeks and then handed an entire series. I have seen that pattern repeat across three separate seasons, and it is the reason I distrust the simple "total overs" conclusion.

The scorebook does not explain the injury. It only tells you where to start looking.

Sixty matches, twenty-nine bowlers

IPL 2026 came in two halves. The India leg was suspended by the BCCI on 4 May 2026, and the season resumed in the United Arab Emirates on 19 September 2026. I was on a national desk at the time. When the season stopped, I rewatched all sixty matches and coded the spells of twenty-nine frontline fast bowlers.

Twelve of them had bowled more than 24 overs in the India leg. After the UAE restart, that same group produced seven soft-tissue absences.

This is where it is worth stopping, because this is where the easiest mistake gets made. Twenty-nine bowlers is a small sample. Seven absences are not seven causes. Nothing in that data allows me to say that crossing 24 overs in India is what broke them. I did not write that then and I will not write it now. What can be written is this: the group that carried the heavier load into an overseas, air-conditioned, closed-door environment was the group in which the injuries clustered. A cluster is an observation. A cause is a claim.

One more thing from that season never made a graphic. Between the two halves, travel, quarantine and re-fitness were all booked into the same account. Rehab and pre-season were compressed into a single calendar window. That was not a medical event. It was a scheduling event.

Another count, via the Impact Player

In 2026 the IPL introduced the Impact Player rule. Most analysts declared a tactical revolution. I waited thirty-eight matches, then coded all seventy-four games and separated tactical substitutions from injury replacements.

Result: 128 Impact Player uses, of which only 19 were injury-related. That number is itself a story. If the rule's purpose had been to reduce the physical burden on players, the injury share of substitutions would not sit near fifteen per cent. Second, batting totals rose while bowling workload did not fall in proportion — an extra batter arrived, so the fielding side still had to fill the same bowling quota, and usually with the same bowler.

The Impact Player opened a door for batting and left the bowling wall exactly where it stood.

How big the sample is, stated plainly

In every piece I write I state the n, name the window and mark confidence. That is not a style rule, it is a defence. A pattern across thirty-two matches and seven bowlers is a hypothesis, not a mechanism. Fourteen notices out of a population of about 1,320 is a signal, not a diagnosis.

What returned across three separate audits was not a number. It was a shape: load rises, rest falls, and nobody records the interval between the two. The 2026 TNPL showed it, the 2026 Ranji scorecards showed it, the 2026 IPL showed it. Finding the same shape in three places is a direction. Finding it in three places does not prove the shape is the cause.

Thresholds that were borrowed

My early framework came from Australian load management. There, a real off-season exists, the heat is milder, there are fewer formats, and a player gets a few weeks a year in which nothing is expected of him.

In India all three are inverted. Ranji runs through the winter, the IPL through spring, bilateral white-ball cricket through the rest of the year, and no window stays empty. Playing in heat is normal. Travel days are counted into the season; rest days are not.

So when an acute-to-chronic load ratio derived from an Australian study is applied to an Indian fast bowler, one variable quietly goes missing — the one that existed in Australia and does not exist here. That variable is the off-season. A threshold imported from another calendar is an estimate here, not a measurement. Whenever I use a borrowed number I now write down that it is borrowed.

The label is the question, never the answer

Whenever the phrase "injury-prone" appears, I read it as a claim under test rather than as an explanation. A claim needs evidence, and the evidence can only be what I counted above — overs per seven days, spells per session, days between fixtures, and a comparison against the team median.

I have never called a bowler fragile without first checking his overs against his team's median. That is not a moral position, it is a procedure. Run the median and you often find that the man being described as repeatedly broken is bowling about twelve per cent above his team's average — while somebody else in the same squad is quietly bowling twice as much, and his name never appeared in a bulletin.

The calendar is the injury

This is the part where I have to argue with my own method.

Most Indian fast bowlers are not breaking. They are being scheduled into failure. And there is one detail in that schedule that gets too little attention. Centrally contracted players are not released to offload overs in overseas T20 leagues. That is the release valve every other major system has — a bowler spends a few weeks in a league, keeps his rhythm, and his board can rest him from national duty at the same time.

Here that option does not exist. Every rest decision therefore has to be carved out of the domestic or national calendar, and there is very little left to carve.

Now the objection to my own method. I only count what produces a document. My dataset therefore silently assumes that an injury is whatever got filed. That is a bias, and its name is absence-notice bias. The bowler who played through pain and never filed a notice never entered my table. That does not mean he was fit. It means my work is incomplete.

And I distrust my strongest result too. A clean last column across thirty-two matches looks like proof. It is not proof. It is a very well-kept question.

What comes next

If Indian cricket wants an answer, the first fix is administrative, not clinical. A public availability list, three columns per player: out since, on what basis, returned on. No diagnosis, no medical detail. Just dates. That is not dangerous for any board. It is simply publishing the table that already exists inside.

Until that table exists, every major tournament will produce the same sequence. A bowler clutches his side in the eighteenth over, the camera finds his face, commentary says his body is not cooperating, and three days later a notice arrives containing two words.

The question is not what happened to his side. The question is why nobody kept the account of his previous twenty-eight days.

Empty stadiums did not reduce the injuries. They only removed the noise around them.