The Dot-Ball Ledger: An Audit of Bangladesh's Regime Split on Asia's T20 Stage

Hook

Half past eleven at night, the glow of a laptop on my Khulna desk and a paper ledger beside it — a ledger I have been keeping since 2026. On screen, a match on Asia's T20 stage, Bangladesh batting, the 17th over. Twenty-four balls left, sixty-two needed. The commentator said, "Now we need the big shots." I opened the Khulna ledger, and the very first column stopped me.

It read: in this innings, Bangladesh's middle-overs (7 to 15) dot-ball percentage was 47.3. Across the six matches I tracked, the tournament average was 38.1. The delay did not happen in the 17th over. The delay happened in the nine overs before it — slowly, quietly, one dot ball at a time. When someone says "turning point," I say: a turning point is not a moment, a turning point is a column.

I opened the Khulna ledger, and the first column taught me patience. Today's audit is about the same thing — not the drama of the last four overs, but the arithmetic of the nine in the middle.

Context

The biggest error in talking about Bangladesh cricket is regime-blindness. We arrange Test, ODI, T20I and franchise cricket on one plate and tell one story. In reality these are four different ledgers, four different rulebooks, four different evaluative lenses.

My method is simple. A separate column for each format, and at least three metrics beside every claim. The way I measure pressure with PPDA in football, in cricket I built an equivalent — the dot-ball pressure index. The calculation: the share of balls a batter cannot score off (dots), combined with failed strike rotation, produces a number that is a map of pressure. That is not a picture. The France PPDA map was not a picture; it was a confession of where they pressed. A cricket dot-ball map is the same: a confession of where an innings stopped breathing.

In 2026 I started an xG column for a Dhaka football site. I tracked Abahani Limited Dhaka and Sheikh Jamal Dhanmondi Club over 14 matches; Abahani scored 28 goals from 21.4 xG. I published a regression warning. They drew three of their next five. The site made me analytics editor. From that I learned: read a ledger correctly and it points at the future. In cricket I try to do exactly that.

I began cricket writing in 2026 with Prothom Alo's coverage of the Wills Cup in Dhaka. There was a ledger even then, though the column had no name yet. In 2026 I left The Daily Star to become its Bangladesh correspondent — at home and away with the national team. In 2026, during the historic series win over New Zealand, came my T20I commentary debut. That series taught me that the truth of a T20 innings is not in the last over — it hides in the nine overs after the powerplay.

So Bangladesh's problem on Asia's T20 stage is not one of emotion but of arithmetic. And to see that arithmetic, we must start from the domestic ledger — from Khulna.

Core Analysis

First, the domestic first-class ledger. From the National Cricket League and Bangladesh Cricket League records I kept between 2026 and 2026, one pattern is clear: our domestic pitches are slow, low-bounce, with a session run rate in the 3.2 to 3.5 band. This environment trains patience — the habit of standing at the crease for four to six hours. The problem is that T20 does not reward that patience; T20 demands the decision to take risk in the middle overs.

Now the tournament data. I built a phase-split table for Bangladesh's six matches on Asia's T20 stage:

| Phase | Run rate | Dot-ball % | Boundary per ball | |---|---|---|---| | Powerplay (1-6) | 7.9 | 41.2 | 0.14 | | Middle (7-15) | 6.8 | 47.3 | 0.09 | | Death (16-20) | 9.6 | 31.5 | 0.18 |

Reading the table: our death-over run rate is good, but in the middle overs we are losing almost an over. The tournament's two best sides ran at 8.4 and 8.1 in the middle. The gap is 1.3 to 1.6 runs per over — 12 to 14 runs across nine overs. Matches are lost by 12 runs.

Here comes my second index — the dot-ball pressure index. Counting dots is not enough; what matters is what happens after a dot. In my ledger, Bangladesh batters look for a boundary on the ball after a dot 28 percent of the time; the tournament's best sides do so 34 percent. Our batters carry the pressure of the dot, then try to release it in one ball — and often lose a wicket.

The biggest finding: our middle-over problem is not one of batting talent, but of strike rotation. In the tournament, singles supplied 39 percent of Bangladesh's middle-over runs; for the best sides it was 52 percent. We are waiting for the big shot and dropping the small run.

Now the bowling column. Our spinners concede at 6.4 in the middle overs, third-best in the tournament. But our new-ball economy in the powerplay is 8.2, against 6.9 for the best sides. We take control through spin, but give away 15 to 20 runs at the start. In football we call it conceding early; in cricket it is powerplay leakage.

One more column matters — wicket temperament. Dubai and Sharjah pitches are slow, low on turn but sluggish. My slow-pitch index (a simplified measure of how late the ball reaches the bat) was 6.2 for this tournament, against 5.4 on Bangladesh's domestic T20 pitches. The stage was slower than we are used to — and we could not adapt our strike rotation to that slowness.

The franchise column is even more instructive. Those who did well in the domestic T20 league saw their strike rates drop by 12 to 18 points on the international stage. The reason is clear: thinner bowling depth at home, less middle-over pressure, a different slow-pitch map. Franchise form does not translate internationally — this is the core of my ledger-bound scepticism.

Before I look at any player, I ask: what is the sample? A batter's middle-over strike rate across six matches cannot be the basis of a decision. From 2026 to 2026, across all T20s, Bangladesh's top six ran at a middle-over strike rate of 118; the top five teams averaged 142. This gap was not built in one innings; it is a structural ledger.

The death-over bowling column also needs separate reading. Our death economy is 9.6, against 8.7 for the best. But there is a subtlety — our wide and no-ball rate at the death is 0.42 per over, among the highest in the tournament. Under pressure our delivery discipline breaks. That is not technique; it is routine — and routine is built in session-by-session practice, not only on match day.

One thing outside the table I want to write, because no table captures it. Of these six matches, three were lost by margins under 10 runs. We are in the contest, we just cannot convert. The shape of the defeat is not "destruction" but "incompletion" — and the space of an incomplete defeat lies exactly in the gaps of the middle overs.

Another column — partnership breakdown. In my ledger, the average second-wicket partnership in this tournament was 22 runs, against 38 for the best sides. The second wicket falls in the first three overs after the powerplay, exactly when the middle overs begin. That is the moment the dot-ball pressure index jumps hardest.

Contrarian Angle

Now the part where I must stand against my own table. Everyone will say, "Raise the middle-over strike rate and you win matches." That is the classic trap of turning correlation into causation. Raising middle-over runs does not guarantee wins — because taking more risk in the middle also costs wickets, and if our top order fails, the lower order is squeezed.

The real question is the risk budget. In the tournament, 61 percent of the wickets Bangladesh lost per innings fell in the middle overs. For the best sides it was 48 percent. We are taking risk in the middle, but not calculating it — we either play dots or lose a wicket outright. The middle path is absent from the ledger.

The second trap — the "turning point" story. On commentary we hear, "That six in the 17th over turned the match." My ledger says otherwise: in the matches where we reached the 17th over needing more than 50, 75 percent were already lost by the 10th over. The late drama only keeps the viewer busy; the arithmetic was settled earlier.

The third trap — mixing formats. Someone shows patience in domestic first-class, enters the Test side, and then that same patient mindset is dragged into T20 — and dots pile up in the middle overs. Separate the regimes, keep separate ledgers. But a crossover note is essential here: those who average 40-plus in first-class and rotate strike well can convert to T20 too — the condition is a separate training routine and a separate role definition.

The fourth trap — reading silence. In two of my six matches, some scorecard cells were incomplete, because ball-by-ball data in domestic and limited-broadcast matches is never complete. Here I want to be explicit: missing data, deliberate quiet, and structural darkness are three different things. The information darkness of domestic cricket is structural; you cannot build a story on it, you must build a system fix.

When the stadium emptied, I audited the silence and found the game still breathing. In an empty domestic ground, runs still come, wickets still fall, the ledger still fills — only no one watches. Our selection cycle stands on exactly that unseen ledger.

The fifth trap — load management. Around this Asian tournament, in the crush of franchise schedules and bilateral series, player rest is often a euphemism that makes room for commercial tours. In my ledger, of those with the highest middle-over dot-ball percentages, two had played back-to-back franchise and international matches without a break. Fatigue hits strike rotation first — not the big shot.

Takeaway

For the next cycle my one signal: make middle-over strike rotation a separate, measurable target. Cut the powerplay leakage. And most importantly — fill the dark cells of the domestic ledger, because a selection built on an incomplete ledger is itself incomplete.

A clean row of data will outlast a thousand hot takes. The question now: will our selection committee watch the drama of the last over, or turn back to that quiet dot ball in the seventh — the one that had already written the match?