The Match I Found in the Columns: Powerplay Accounting at the T20 World Cup and Bangladesh's Structural Deficit

In the third group match of the 2026 T20 World Cup, Bangladesh finished the powerplay on 41 runs, 19 of those deliveries dot balls. In the same innings, the last five overs produced 68. Place the two numbers side by side and an uncomfortable truth surfaces: this side can hit, but it cannot schedule its own gear change.

I found the match in the columns before I found it on the screen. The commentary said the start was poor. True, but incomplete. A failing powerplay is not a shortage of batting talent; it is an accounting error in risk management, and accounting errors surface on the scorecard last.

This is not a match report. It is a file — the continuation of a ball-by-ball logging method I have kept for years. One admission first, an old habit of mine: the tournament-specific figures below come from my own logs and sector maps, not a governing body database. Small samples exaggerate; I do not draw conclusions from fewer than ten matches.

Context: why the powerplay needs its own ledger

Two host nations, and three variables shifting with every venue — boundary dimensions, when the dew arrives, and how the spinners are apportioned. By the first week, one thing was obvious: an innings no longer runs at a constant speed. It runs in three gears.

The opening six overs are the most expensive in the innings, because the field is restricted and only two men stand outside the ring. The middle overs bring spin, deep fielders and closed gaps. The last four are about boundary hitting, reverse sweeps and long levers.

The problem is that dressing-room meetings still measure all three gears with one metric: strike rate. A strike rate of 130 in the powerplay and 130 in the twentieth over are not the same asset — the first damages the team, the second often saves it.

I learned that lesson in a different sport. Working as a junior Opta data logger at the 2026 World Cup, I tracked Aaron Mooy covering 12.3 kilometres against France, the most of anyone on the pitch. My first read was that he controlled the game. But my PPDA count was 14.2 and France generated 2.1 xG. Rewatching and logging every French entry into the final third, I understood that distance alone lies.

Mooy's distance was not a stat; it was a map of the game. The same holds for a dot ball in cricket. A dot ball is not an event; it is a map.

Core: three accounts the scorecard never shows

One: the opportunity cost of a dot ball

A dot ball in the powerplay and a dot ball in the nineteenth over both read zero. In accounting terms they are nothing alike. In my model, the opportunity cost of a powerplay dot ball is measured by the runs lost across the next two deliveries, because the field is up. A dot ball forces the batter to take more risk next ball, and risk means wickets. Of the 19 dot balls in that group match, 11 were deliveries that could not be worked into the gap between short third and point — a failure of strike rotation, not of defence. Six were genuinely good balls. Two were wides outside the line that could have been attacked.

Two: translating xG into cricket — xR

At Brisbane Roar in 2026, my first task was building an xG model. That season Jamie Maclaren scored 19 goals from 16.8 xG — finishing better than average, but not superhuman. That gap taught me that the final number and the process number are different things. In cricket, boundary percentage is the goal count. Dot-ball pressure and rotation are the xG.

My metric is xR — expected runs per ball. Four inputs: line and length, the batter's footwork position, the field setting, match state. The output is what a delivery should yield on average. A yorker-length ball in the twentieth over carries 0.8 xR. A wide-of-length ball in the powerplay carries 1.9. Both read as one run. One is good batting, the other is failure.

Three: fielding maps and off-ball movement

Fielding data is the most neglected dataset in cricket. I log fielder positions across six sectors for every over, and I clock how often the non-striker leaves the crease. That running happens off camera, but it is where the innings is decided. Three aborted singles in an over make a fast-twelfth-man risk next over, and that fatigue narrows shot selection. This is where the football lens transfers directly: a deep point fielder shifting two steps changes the next ball's shot selection. Esports drafts and football formations are cousins in disguise — and cricket's field settings are their closest relative.

Four: rotation strike rate

My rotation strike rate is the ratio of non-boundary runs per ten balls against dot balls. Boundaries are irregular, talent-driven events; rotation depends on planning and repeatable fitness. In a tournament where the venue and conditions change weekly, repeatability survives longer. Two batters can both make 43 from 36 — one with six fours and two sixes, the other with three fours and sixteen singles. Change the conditions and the first stalls at 10 from 20 while the second reaches 22. A boundary paints one innings; rotation builds a tournament's resilience.

Five: opponent-quality correction

Powerplay run rates hide bowling quality. If the tournament's two best new-ball attacks sit 0.6 runs apart in economy, two teams' powerplay scores are not directly comparable. I cross-check every powerplay score against performance versus the six leading bowling attacks.

The contrarian angle: correlation is not causation

It is easy to look at a low powerplay score and say the batting failed. My log says something else. Across the matches where Bangladesh bowled first versus where they batted first, the powerplay run rates differ by roughly 14 runs on average — same squad, same top order. The difference is dew: the ball slows, the trajectory changes. This is not a batting-coach problem; it is a toss-dependent condition asymmetry.

But here is my second caveat. Fourteen runs rests on a handful of matches. When the A-League returned in a 2026 hub, I modelled home advantage across 120 matches. In empty stadiums Brisbane Roar's home xG differential fell from +0.31 to +0.08, and coach Warren Moon used the report — but I wrote plainly that the sample was too small for firm conclusions. The empty stadium taught me that atmosphere leaves a data shadow, and measuring that shadow takes many matches.

Takeaway

Before the next round, find one number: the gap between powerplay run rates of sides batting first and sides chasing. If that gap stays above ten runs for three straight matches, the tournament's fielding and toss calculations must be rewritten. An innings' speed is measured in sixes at the death. A tournament's speed is measured in how often the seventh to fifteenth over avoided a dot ball. What the broadcast never shows is what wins the trophy.