The Powerplay Ledger: A Baseline Audit of Bangladesh's T20 Data and the Overstated Promise of Immutable Records

It was June, in New York. The drop-in pitch at Nassau County kept the ball sometimes below the knee, sometimes at the chest. South Africa made 113 for 6 in 20 overs. Bangladesh fought to the last over and finished on 109 for 7. A four-run defeat. I was in the Bengali commentary box that night, and when everyone else was drafting the innings summary, I opened three separate data platforms with one question in mind: how many dot balls did Bangladesh actually play in the first six overs? Three answers came back — 29, 31 and 27.

Three deliveries across a powerplay sounds trivial. It translates into two to three tenths of a run rate, and that difference decides whether the match report describes caution or aggression. None of the three numbers matched what I saw from the box: the pitch behaviour, the square boundaries, the bowlers' lengths.

That night planted a question about the loudest promise of modern technology. If every cricket record becomes immutable, time-stamped and independently verifiable, does the game become clear? My answer is unfashionable. Immutability is not accuracy. A wrong definition carved in stone stays wrong; it simply cannot be corrected. This article does two things. It runs a baseline audit of Bangladesh's T20 powerplay and death overs from my own notebooks, and then it separates what a verifiable ledger would fix from what it never will.

Context: baseline before verdict, definition before baseline

I have watched cricket for 38 years, and since 2026 I follow one rule: build the baseline before the claim, and fix the definition before the baseline. The Burnley thread of 2026-17 was read by many as proof of passivity because the PPDA was 12.1 and possession 38 per cent. Sorted against league baselines, it read as deliberate design. That Burnley thread looked like noise until I sorted it by phase.

Cricket has no PPDA, no pass chain. Forcing football metrics onto it is not my job. The cricket-native translations are dot-ball percentage, control percentage and phase run rates alongside boundary share. An economy rate without a baseline is decoration; with a baseline it becomes evidence. Modric ran twelve kilometres, but the map showed where the game turned. In cricket, that map is the phase table.

My second rule is the ten-match threshold, and my third is pre-registration: I decide which indicators matter and what threshold triggers which conclusion before I look. Era baselines must come first. A score of 140 was good in the first T20 decade; 175 is par now. Venue baselines matter just as much. The New York wicket at the 2026 T20 World Cup was a struggle surface — India made 119 and kept Pakistan to 113. On that ground, a higher dot-ball rate was normal.

Table 1: Powerplay baseline, overs 1-6 (my working tracking estimates)

2026-2026: run rate 6.2, dot balls 55 per cent, boundaries 11 per cent. 2026-2026: 6.9, 53, 12. 2026-2026: 7.5, 51, 13. Global average 2026-2026: 8.4, 44, 16.

These are working baselines from my own tracking, not official figures, and the method note matters. Still, the direction is clear: Bangladesh has improved, but the gap to the global mean has never closed to less than two or three tenths.

Table 2: Death overs, 16-20

2026-2026: Bangladesh 7.9 against a global 9.2, a gap of -1.3. 2026-2026: 8.4 against 10.0, gap -1.6. 2026-2026: 9.5 against 10.4, gap -0.9. The gap is narrowing, and the cause is not more boundaries but fewer dot balls and better strike rotation. That is where a stability check is needed before any praise. A 22-match rolling window shows the death-over peak came in the second half of 2026, largely from two or three high-scoring innings. Remove them and the trend softens. It is a signal, not an inscription.

Table 3: Venue adjustment at the 2026 World Cup

Dallas, a batting surface: run rate 7.8, dot balls 48 per cent. New York, the drop-in pitch: 6.4 and 57 per cent. St Vincent: 7.1 and 52 per cent. This explains the three conflicting numbers. A 57 per cent dot-ball rate in New York was a condition effect, not a failure, yet without venue adjustment most match reports would file it as failure.

Table 4: Precedent map

Afghanistan, 2026-2026, tool: a settled opening pair, roughly 30 T20Is. Netherlands, 2026-2026, tool: defined powerplay targets, roughly 25. Nepal, 2026-2026, tool: league-hardened openers, roughly 20. Ireland, 2026-2026, tool: slog-field aggression, roughly 35. The lesson is organisational, not statistical: sides that changed their powerplay kept the opening pair stable rather than reshuffling every match. Era adjustment is essential here, because an 8.0 run rate in 2026 and an 8.0 in 2026 are not the same thing.

The data supply chain

Two scorers at the ground, a broadcast graphics team, an ICC-accredited data provider, ball-tracking technology, and in franchise leagues a growing use of wearable GPS. Every layer contains people, definitions and room for divergence. Ball tracking and DRS are comparatively clean because the decision path follows reproducible calibration. Wearable data is a different species: who owns a bowler's sprint count or elbow-load data is unsettled. At the anti-corruption layer, the ICC unit monitors betting markets, and that is an off-field process — a ball-by-ball record can never tell you who said what on a phone call.

So what would an immutable ledger genuinely fix? Three things. Provenance, so it becomes easy to trace who is using a player's biometric data. Contract transparency, so image-rights and payment flows in franchise leagues become time-visible. And new fan-engagement routes, since cricket has already seen digital collectibles and fan tokens arrive.

There is a trap here. A ledger that records only ball-by-ball outcomes can never capture dressing-room chemistry. Cricket's scouting and valuation models overrate youth potential and underrate the accumulative value of experienced middle-order batting. In IPL auctions, an Under-19 World Cup showing can multiply a young player's price, while a number four who grinds 40 off 35 on a difficult pitch barely moves. A ledger that counts only strike rates will freeze that error into permanence. There is also the ownership question: is a player's physical data his own, his board's, or the broadcaster's? Once written immutably, the room to renegotiate disappears, and this may become the most contested legal question of the next five years.

The contrarian angle

My core objection is simple. A bad definition written into a ledger becomes more harmful, because it can no longer be questioned. Take dot balls: one platform counts only run-less deliveries, another includes leg-byes and wides. Control percentage definitions differ by provider too. The problem sits at the definition layer, not the storage layer, and definitions are cricket politics, not engineering — the real prize is who gets to set them, and that is a three-way tug between boards, broadcasters and providers.

Second, corruption. Spot-fixing happens off the field, through calls and intermediaries. A ball-by-ball ledger does not touch that layer, so treating immutability as an anti-corruption silver bullet is a category error.

Third, my own method. I apply a ten-match threshold, but not blindly: ten matches against Pakistan do not carry the same weight as ten against Sri Lanka. So my pre-registration also lists condition-specific exceptions — a different threshold when the venue class or opposition standard changes. If that flexibility itself looks like a loophole, that is fair. A method that will not admit its limits is not a method.

Fourth, records are not explanation. A fixed dot-ball rate tells you a side was cautious; it does not tell you why. That requires the phase table, the bowlers' lengths that night, and the field settings — none of which are automatically verifiable.

What I will watch over the next ten matches

I am writing this down in advance. If Bangladesh's powerplay dot-ball rate falls below 50 per cent across the next ten T20Is and the seventh-over control rate holds above 75 per cent, I will call the trend structural. If it does not, this article becomes a caution: judging a powerplay without a baseline is dangerous. Based on my years of watching matches from the commentary box, the number that matters is never the total. It is where, and when, the match turned.

The final question is not about the record but about people. If every ball's data becomes immutable, who keeps the authority to explain it — the commentator at the ground, or the server farm? Cricket is played in bodies and in decisions, not on a ledger.