Regression Auditing the T20 Run-Flood: A Fast-Bowler Workload Ledger and the Quiet Ledger of Dot Balls

Last April, at a Wankhede evening match, I shut my notebook when the first-innings scoreboard flashed. 263 in twenty overs, four sixes in the final two — the stands were roaring, the commentary booth was declaring a new T20 era. Yet my spreadsheet held the week's five-match data, and four of those five showed second-innings run rates nearly 1.8 runs per over below the first. I opened the spreadsheet and let the day confess its exaggerations. Since 2026, writing on the BDCricTeam page, since 2026, running the paid data newsletter, one habit has stuck: the louder the noise, the more necessary the regression.

At sixty-six I have learned one thing — cricket's memory is not a liar, it is selective. It keeps the six, forgets the ten dot balls in that same over. That is why I keep a ledger even for the legends: memory edits its own columns. This piece is one page of that ledger.

First, the fact. Take twelve months of continuous T20 data — franchise leagues, bilaterals, ICC events. Average runs per innings is up roughly 15 to 18 since the 2026-22 cycle. In the 2026 franchise season, the rate of 200-plus scores was about 38 percent, against only 19 percent three years earlier. The number is loud, so I regressed it until the noise fell away.

What lives inside this flood? Four variables. First, the approach in the powerplay has changed: strike rate has climbed from 138 in 2026 to 147 now. Second, spinners in the middle overs are being attacked without matchup planning. Third, batting depth has grown — even number eight can hold a 140-plus strike rate. Fourth, the factor nobody wants to count — fast-bowler workload.

This piece centres on that last cause, because I suspect it is the most neglected. Runs are flowing fast in T20, but who is conceding them, and what are the quicks losing in return — nobody keeps that ledger. I want to.

The workload ledger: count spells, not overs

My method is simple. I don't count overs, I count spells. Four overs bowled straight and four overs in two spells are not the same for a fast bowler. The physiological load differs. So I keep three columns per quick: workload five days before the match, travel day, and length of the previous spell.

Last season's data: quicks who bowled more than three spells per match across six consecutive games saw economy rise by roughly 1.4 runs per over in their last four matches, with death-over yorker accuracy dropping about 22 percent. That is not magic, it is fatigue. But when economy rises on the scoreboard we call it 'bad form', never 'unbalanced spell management'.

The quiet ledger of dot balls

In T20 talk we count sixes, fours, strike rates. But a match is often decided by the balls nobody puts in a thumbnail. Analysing this cycle's 200-plus innings, winning sides manufactured roughly 5.2 extra dot balls per innings — in the middle overs, when pace is taken off.

I have long led with defensive metrics, because attack statistics shout and defence statistics tell the truth. In T20 this means catching discipline, the keeper's quiet footwork, the single saved in the field. A side conceding two to three extra runs per game saves nearly fifteen across a six-match tournament — often the playoff margin.

Regression: is the run rate sustainable?

Here is my core caveat. Unpack the 2026 franchise 200-plus innings through an expected-runs model and 18 to 22 of those runs came from excess strike success — batters who should have been out, but weren't. That surplus is not statistically durable. At the 2026 Under-17 World Cup I saw exactly this: 28 goals, xG 22.4, overperformance plus 5.6. I told clients the scoring was unsustainable. Overperformance is now the texture of T20. Four straight 200-plus games and the media declares a new attacking age. My ledger says: probably a small boundary, a flat pitch, or a weak bowling spell — often all three.

Contrarian angle: correlation is sometimes a false witness

Now the reverse side, turned against myself. If I say only 'scoring is up, so it's temporary', I am wrong, because two things need separating. First, ground dimensions. Many franchise venues have pulled boundaries from 65 to 60 metres, letting batters attempt sixes without risk. That is a tactical shift, not luck, and any xG model must be venue-adjusted. Second, I want to be sure whether scoring rose because quicks are pressed, or quicks are pressed because scoring rose. Two different diagnoses, two different fixes. Third, that constant I prefer not to name: my strike-rate illusion. Correlation between a good innings' strike rate and the bowler's quality is sometimes coexistence, not cause. Here I have learned to pause and judge.

Takeaway: what I watch next cycle

Next season my first look will be at how much a fast bowler bowls in the two overs after the powerplay. If a side finishes two quicks inside 10-12 overs, I will write: this side will be brittle at the death, because what is needed then is yorkers and patience, not tired hands. If a side deliberately preserves a quick's third spell, I will not bet against them — I will wait. The regression taught me patience. Sixty-six years and six straight cycles say the same thing: the louder the noise, the longer the count. Inside the T20 run-flood, what survives is not in the sixes — it is in the dot balls and the fast bowler's shoulder.