The Dot-Ball Ledger: A Data Autopsy of Bangladesh's ODI Middle Overs

I opened the match log before I trusted the memory.

Dubai, 20 February 2026. The scorecard from Bangladesh against India at the Champions Trophy told one story at the close: a batting failure. My notebook told a more precise and more brutal one. Between the 30th and 40th overs, Bangladesh's batters faced 59 balls and left 34 of them untouched. In those eleven overs, more than two boundaries came only rarely. What the scorecard calls slowness, the log read as a structure: repetitive, predictable, an almost scripted stalling.

I froze the raw numbers before the narrative could harden. This piece is the audit of that frozen ledger, and an attempt to face an uncomfortable question: is Bangladesh's ODI middle-over problem the private failure of individual batters, or the joint product of selection, strategy and data infrastructure?

Method: what I logged and what I did not

My log holds 14 ODIs: nine from Bangladesh's 2026 World Cup campaign, several bilateral matches from the 2026-25 season, and two from the 2026 Champions Trophy. That gives 814 balls inside the middle-overs definition, the 11th to 40th overs. For every ball I filled six columns: over, bowler type, batter, runs, dot or not, and shot type. This dataset is not a BCB or ICC archive. It is a hand-kept ledger built from the television feed, the ball-by-ball scorecard and my own screen notes. The sample is small, so what emerges is a signal, not proof. Since my 2026 empty-stadium report, I have opened every piece with that limitation.

There are two kinds of dot ball: the dot born of a correct field and a good delivery, and the dot born of a batter's indecision or poor shot selection. The scorecard does not separate them. My log tried. That is where the real story was hiding.

Context: two timelines, on the field and in the office

To understand where Bangladesh's ODI cricket stands, you have to read two timelines together. On the field, Bangladesh won two of nine matches at the 2026 World Cup, against Afghanistan and Sri Lanka, and the top order repeatedly fell into pressure just after the powerplay. In the office, head coach Chandika Hathurusingha was removed in October 2026 and Phil Simmons took charge; after the political shift of August 2026, the BCB presidency changed hands and Faruque Ahmed came in. The selection committee, the analysis department, the central contracts — all of it was promised a rebuild.

I watch Bangladesh from Liverpool, and that distance produces a particular unease. An English county side carries far more video analysts, physios, load-management specialists and data engineers than the Bangladesh national team does. There is no moral accusation to make here; the question is budget and infrastructure, and it has direct on-field consequences. A side that can explain every ball with data is not forced to answer the question of why it stalled in the middle overs with feeling alone.

One historical note. In 2026 I moved from cricket writing into the BCB media set-up; The Daily Star called me the fine cricket writer turned media manager. That experience taught me that decisions in Bangladesh cricket are never taken on match information alone — relationships, seniority and safety are always on the table. That lesson still applies to data analysis, because when the reasons behind a decision are invisible, the results look chaotic too.

The geography of dots

Across my 814 balls, the middle-over dot rate is 54.3 per cent. By comparison, England, India and Australia sat between 41 and 44 per cent in the same window in my log. Bangladesh is wasting roughly one to one and a half extra balls per ten. One ball looks trivial; across 30 overs it becomes 40 to 45 balls, close to seven overs of batting.

The real signal sits in the over blocks. My log shows a dot rate of 48 per cent from overs 11 to 20, 52 per cent from 21 to 30, and a jump to 58 per cent from 31 to 40. In the first two blocks the side survives and the board ticks. In the third the tempo dies. That is exactly when the field spreads, boundaries get harder, and the run rate slides to 4.2 an over.

Split by bowler type and the picture sharpens. Against pace, Bangladesh's dot rate is 49 per cent; against spin, 59 per cent. Spinners conceded only 4.2 runs an over between the 21st and 40th, while also taking 3.6 dots an over. Read those two numbers together and the spinners are not merely stopping runs — they are stopping runs in order to force risk, and Bangladesh cannot take that risk. The returning spinner, the sliding arm ball, the relentless leg-stump line: those three things have been the biggest tax on Bangladesh's middle overs.

The arithmetic of the single

Strike rotation is the least discussed skill in cricket. In my log Bangladesh take 2.9 singles per ten balls; the top five sides average 4.1. The gap looks small, but across 50 overs it is nearly 60 balls of running, six overs of scoring that only strike rotation could have produced.

Why do the singles not come? Three causes recur in my notes. Batters are deciding too late to drop the ball, so the soft-hands single disappears. The non-striker is starting too late, so a single becomes a two only in theory. And against spin, with a deep-set field, Bangladesh's batters wait for the big shot instead of working the ball into the gaps.

Of those three, the third is the most worrying, because it is a strategic choice, not a technical fault. That means it can be fixed at the coaching level, if the side agrees to name it as a problem. In my log the best strike rotation came from Towhid Hridoy and Mehidy Hasan Miraz, both of whom decide before the ball pitches. The sample is small and the comparison risky, but the pattern is noticeable.

Shot map: where the runs are born

My screen notes carry a shot distribution for middle-over fours and sixes. The sweep family produced the most, around 38 per cent. Down-the-ground drives came next at 24 per cent. Cover drives and square cuts together made 19 per cent. The rest was miscellaneous.

The issue is not the distribution but the dependency. When nearly 40 per cent of a side's middle-over boundaries come from one shot family, the fielding captain's job gets easier: station two men at deep midwicket and deep square leg, change the line, and the entire weapon goes quiet. International spinners know this arithmetic, and from the 2026 World Cup to the 2026 Champions Trophy they kept doing exactly that.

The reverse sweep, the late cut and the switch hit are almost absent from my log in the middle overs, fewer than ten instances. In the modern ODI these are the shots that create value against a spread field, because they use the gaps at cover and midwicket. A batter who can play all three cannot be held to one line by a spinner; a batter who cannot will find the field closing in and the dots piling up.

The clock of bowling changes

In captaincy analysis I always look at the timing of bowling changes, because strategy becomes visible there. My log shows a consistent pattern: Bangladesh captains changed bowlers every 2.1 overs between the 21st and 30th, but the interval stretched to 2.8 overs between the 31st and 40th. When the game is most sensitive, the hand shakes most.

Opposing captains did the opposite — they held a bowler through the hard phase, because they knew Bangladesh's batters start slowly against a new bowler. In my log Bangladesh's run rate in a new bowler's first over is 4.9, rising to 5.4 in the overs that follow. That small gap says Bangladesh's batters take time to settle against a fresh bowler, and opponents exploit it.

I have written before that the revival of the back three in football is not progress; it is managers sheltering from the reputational risk of an exposed back four. Cricket has a parallel: instructing the top order to play safe through the powerplay so no wicket falls. If the match plan is wicket preservation, nobody wants to take the risk of scoring between the 21st and 40th — and that defensive instinct is what builds the pressure that arrives in the last ten overs.

The wicket window

Between the 31st and 40th overs, Bangladesh lost a wicket every 23 balls, the highest rate among the top ten sides in my log. A wicket in that window forces a new batter to settle, and that settling period is the factory floor of dot balls. Dots and wickets feed each other in this team's middle overs, and that cycle sets the shape of the scorecard.

Notably, at the 2026 World Cup Bangladesh lost more than two wickets in the powerplay in only two matches. The top order could survive the first ten overs; that was the plan, and it worked. The damage came in the middle twenty-five, where there was effectively no plan. An absent plan is not always chaos. An absent plan means the weakest decision becomes the default, and the default is the dot ball.

What the screen never shows

I watch matches in two languages: the television commentary and the silent arithmetic of the scorecard. Between them sits a third language the spectator never receives: the explanation of a decision.

One example stays with me. A review came back as umpire's call; a ball-tracking graphic flashed on the big screen for two seconds and was replaced by an advertisement. The crowd in the stadium never learned how much of the stump the ball struck, why it was umpire's call, or why that decision was final. The rulebook has all of it; nobody in the stands can read it there. Technology has entered cricket in a big way, but the explanation of technology has not. Transparency is transparency only when it reaches the spectator in the back row, not just the regulator's press release.

This connects directly to middle-over data work, because transparency about strategy and transparency about decisions are two sides of the same coin. A spectator who does not know why a review failed will not understand a captain's strike-rotation plan either. The question of respecting the cricket audience with information begins outside the field and ends inside it.

The hidden injury ledger

Workload management now lives in the physio's diary, sometimes in an annexe to a central contract, sometimes only on the dressing-room wall. Nobody outside knows how much fatigue has gathered in a fast bowler's side, or which shot brings him pain.

My log contains a pattern that demands explanation: after matches in which Bangladesh lost more than two wickets between the 31st and 40th overs, quick bowlers' spells shortened in the next series. I cannot prove causation — small sample, unknown medical information. But a little more transparency would help the audience here. Clubs and boards tend to announce the injury that suits their ledger — match preparation, tickets, sponsorship. Information that does not serve them stays safely behind the wall, and fans never see the dressing room's hidden arithmetic.

Two ledgers, two countries

Through a diaspora lens, the measurement of cricket is itself a culture. In Bangladesh a cricket debate centres on winning and losing, moral evaluation of performance, and the ledger of a player's virtues and faults. In England the same debate is far more number-driven: over-by-over run rate, wicket probability, match-up data.

The two practices rarely meet. A young Bangladeshi fast bowler entering the English county system learns something different: how to read his own bowling data, at which angle he is effective, in which field set his economy drops. Back in Bangladesh he finds no place to use that language. The result is data migration — the talent lives in one country, the language of measurement in another. To me that gap is the biggest invisible problem in Bangladesh cricket, because it never shows on the scorecard, yet it appears in every middle over.

First pass chaos, second pass France

Kazan, 1 July 2026. France 4-3 Argentina. For many it was pure thrill. In my log it was information at two levels: France 2.1 xG, Argentina 1.6, and seven goals. Kylian Mbappe's six dribbles and 37.1 km/h sprint broke the back line, yet France's pressing intensity fell to 14.8 once they dropped deep. First pass chaos, second pass France — and on the third pass, the crack that later let Argentina back for two goals.

I bring that method to cricket. When a Bangladesh ODI folds for a small total, the first pass says the batting collapsed. The second pass shows the dot-ball cluster from the 31st to the 40th over, the 59 per cent dot rate against spin, the absence of strike rotation — three things that together built a system, and the scorecard is its output.

During Project Restart in 2026 I reviewed all 92 Premier League matches behind closed doors, with Liverpool 1-1 Burnley on 11 July 2026 as the case study. Anfield's home advantage fell by 0.31 goals per game, and Liverpool's home pressing figure rose from 8.1 to 10.4. The stadium was empty, but the data kept breathing. That pandemic experience taught me that when the environment of measurement changes, the measurement changes too. Cricket's empty stadiums, neutral venues and day-night schedules are all extensions of the same lesson.

What is correlation and what is not

The easiest reading is this: Bangladesh play more dot balls, therefore they lose. That reading is the most dangerous. My log also holds matches where the dot rate stayed below 50 per cent and the side still lost, because too many wickets fell. The reverse exists too — matches won at a slow tempo because the opposition's batting line-up was the more fragile.

So the dot ball is a symptom, not a cause. The causes sit at three levels. Selection: a side without specialist strike-rotators in the middle will always carry a high dot rate. Strategy: under instructions to avoid risk, a batter does not see a dot ball as a problem but as safety. Measurement: a side that does not know it is scoring 4.2 an over between the 31st and 40th will not feel the need to fix it.

One counter-argument deserves testing. Someone will say that survival, rather than chasing, is Bangladesh's best strategy, because the bowling attack can win matches. That is partly true. It collapses when wicket preservation in the powerplay leaves the side on 110 for 2 after 30 overs; then even 7.9 an over in the last ten leaves the total short of a competitive mark. The imbalance between conservation and accumulation is the core problem, not a single shot or a single batter.

A limitation, stated plainly: 14 matches and 814 balls cannot settle anything. Across different venues, pitches and opponents the numbers will move. So the claim here is bounded — a signal, not proof.

What I will watch next series

Next ODI series I will not look at the scorecard first. I will look at the dot-ball cluster from the 21st to the 40th over, the strike-rotation rate, and Bangladesh's run rate in a new bowler's first over. If those three numbers shift even slightly, the problem has been named. If they do not, the question moves to the selection committee's table — because the same result repeating is no longer coincidence, it is policy.

I will leave one question open. Does cutting the dot balls raise the side's risk, or is the safety calculation simply wrong? The numbers point to the second — but the sample is small, so the next ball will settle it.