Workload Ledger and the Quiet Value of Dot Balls: A Data Audit of Bangladesh's Pace Attack

Over the last three matches, Bangladesh's pace attack has seen its middle-overs economy—between the 16th and 40th over—fall from 5.8 to 4.2. Television graphics never show this collapse, because graphics only count wickets, fours and sixes. I opened the spreadsheet, and found that behind the fall sat 147 dot balls, not one of which ever made a thumbnail.

I remember that evening clearly. The 34th over. Taskin Ahmed comes on to bowl the sixth over of his second spell. The noise in the ground has dropped away, because over after over has passed without a boundary. Someone in the commentary box says, "This match is putting us to sleep." Yet in my ledger, that over was the most expensive over of the evening. Every one of those six balls was a decision in which the bowler chose to wait rather than attack—and each act of waiting carved a sliver out of the batsman's patience.

In cricket's marketplace, this labour is never priced. It makes no highlight reel, courts no sponsor, raises no salary. The timeline was loud that week—two wins in three matches, a spectacular catch, one review controversy. So I regressed it until the noise fell away, and what I found was a different story from the one the scorecard tells.

My ledger is simple but merciless. For every seamer I keep three columns: overs bowled, spell length, and the recovery gap between two spells. To these I add travel, back-to-back fixtures, and the day's temperature. Every spell has a chain—each delivery from first ball to last is a link in that chain, and one broken link rewrites the whole spell's account. Sixty-six years taught me patience; the data taught me why it pays. I refuse to discuss a bowler's form until I have at least an eight-match rolling sample, because the five-match story is almost always a lie.

The current bilateral season is a stress test for this ledger. The international calendar is arranged so that you must catch the flight to the next series before the current one has finished. The gaps between Tests, ODIs and T20Is have shrunk to a few days. A fast bowler's body does not recognise these three formats as separate; it only knows whether it is tired or ready. And that tiredness is never written on the scorecard—it hides in the fourth over of a spell, where pace drops two kilometres and the line drifts a little wider.

Bangladesh's pace resources were never limitless. Taskin Ahmed, Mustafizur Rahman, Shoriful Islam—that triangle has been the country's fastest weapon for years. But no two sides of that triangle can play at once, because one man is returning from injury while another is on a league flight. Into that gap step the spin of Mehidy Hasan Miraz and Taijul Islam—but spin as a crutch means trying to cover a pace deficit, and that effort carries a quiet cost.

To see that cost, we must change the language of our indices. Economy rate is an average; strike rate is a frequency. Neither says in which over the runs came, and in which over they did not. Yet in limited-overs cricket, the value of time is everything. Six dot balls bowled in the 35th over and six dot balls bowled in the 5th over look identical on a scorecard, but in win probability they are entirely different animals.

This is where my core finding sits. A middle-overs dot ball is the cheapest and most powerful currency in cricket. The batsman is already set, the fielding restrictions place five men on the boundary, and the required rate begins to climb. A dot ball does not merely waste a delivery—it raises the pressure on the next one, forces the batsman toward risk, and risk means wickets.

I logged every pace spell of the last three matches. In spells where the dot-ball rate sat above 45 per cent, 1.3 wickets fell in the following two overs on average. In spells where dot balls dropped below 25 per cent, that average fell to 0.4. This is not the number of wickets; it is the cause of wickets. To a statistician it is correlation, but to a bowling coach it is a plan of work.

Another layer of the ledger is spell length. A seamer carries his greatest pace and accuracy in the first spell; the second spell keeps control but loses a little speed; the third is usually summoned only in emergencies. I found that our seamers' best dot-ball spells came in the second and third overs of their second spell—that is, when the body is tired but the mind is fully awake. This is where experience beats athleticism.

A warning is necessary here. Last month Taskin Ahmed produced a spell of two wickets in four overs at an economy of just 2.1. On the timeline it became a hero's tale. But I opened that spell up: both wickets came from the batsman's poor shot, not the bowler's design. The dot-ball count was eight—good, not extraordinary. The feat was real; the explanation of the feat was exaggerated.

And this is where regression goes to work. If a bowler's strike rate reads 12 across five matches, my first question is who the opposition were. My second is what the pitch was like. My third is what the light was like. Without those three answers, no number is real. A transfer fee is a hypothesis; the season is the peer review. Likewise, a feat is a claim; the rest of the season is its critique.

I keep a ledger for keepers too, because the same invisible labour lives there. Standing back to Mushfiqur Rahim, the footwork, the ball stopped beside the stumps—none of it is a catch or a run-out, yet each act saves a handful of runs. Cricket has no index for this labour, just as football has none for a goalkeeper's save. For Alisson I counted the saves that never made the thumbnail; for Mushfiqur I run the same book.

Now to the index I have built: the quality-adjusted dot-ball rate. A plain dot-ball percentage treats every dot ball as equal, which is wrong. A dot ball to a set batsman on a good pitch in the 30th over and a dot ball to a new batsman just after the powerplay in the 12th over do not carry the same weight. So I break each dot ball into three components: the batsman's settled state, the fielding restrictions, and the phase of the match. Weighted this way, our pace attack's true contribution becomes far clearer.

On this index, Bangladesh's pace attack has a true run-suppression capacity of 3.7 runs per over across the three matches—against a scorecard average of 4.2. Half of that run prevention is written in no statistic at all. This is no surprise; it is simply the labour that nobody counts. If I were placing a bet—and betting is my trade—I would trust that invisible half, because everyone trusts the scorecard, and so its price has already been counted in.

One more thing caught my eye: a change point. Across the first four matches of the season our seamers' dot-ball rate averaged 31 per cent. From the fifth match it jumped to 46 per cent. That jump was not sudden. It was exactly when the team's bowling coach changed, and a simple rule entered the plan: do not attack with the new ball, hold the line and wait. That small change rewrote the season's story, and it appears in no headline.

I keep this ledger year after year, because I keep a separate book for legends—because memory edits its own columns. Television forgets how good a bowler was in a given series; the ledger does not. The contribution of an all-rounder like Shakib Al Hasan cannot be measured in wickets or runs alone; the rest he spends batting between bowling spells is itself a workload investment. That two-faced accounting is Bangladesh's greatest asset.

A format distinction matters here too. A dot ball is worth more in T20 than in ODI, because there are fewer balls, so the opportunity cost of each is higher. In ODI the value of a dot ball accrues slowly, but it accrues. This is why the same bowler often proves more effective in ODIs than in T20—his real strength is waiting, and the ODI gives him more time to wait. Selectors routinely forget this truth.

And one more thing that sticks in my throat. We judge a seamer returning from injury in his very first match—"prove yourself." That pressure is cruel, because in a comeback match body and mind do not work together, and that pressure raises the risk of re-injury. In my ledger I write comeback matches in a different colour, because their data obeys different rules. If someone takes an economy of 3 in his first spell back, that is not a feat—it is merely a normal return.

Now to the uncomfortable part, where not everyone will agree with me. In truth, the link between dot balls and victory is also correlation, not causation. It may be that the side bowling well naturally bowls more dot balls—meaning the dot ball is not the cause of success but its symptom. Miss this distinction and you will arrive at a wrong conclusion: that bowling more dot balls alone wins matches. In reality it does not, because a dot ball that fails to lower the run rate is merely time wasted.

The second uncomfortable point: our journalism and analysis now love aggression and despise patience. The bowler who hurls a yorker and is hit for six is "brave"; the bowler who holds his line and delivers dot balls is "lifeless." Trapped in this narrative, many young seamers are sacrificing their real strength—accuracy. Just as gegenpressing has turned football into athletics, this mindset is dragging cricket down from a game of patience to a game of chance.

Another trap is over-regression. My rule is to set a pre-registered threshold—eight matches, or 240 balls. Before that I reach no conclusion, but I do not stall either; I write interim notes so that information is not lost. This balance has made me slow, but it has made me reliable. Clients were impatient at first; later they learned what that slowness is worth.

One thing must be said. In cricket, decisions are never applied equally to big and small teams—this is no conspiracy, it is the real effect of stadium aura and media pressure. On a marginal lbw or a fine catch, the doubt around a big team clears quickly, while a small team's bowler must trust his own luck. When our seamers bowl against the big sides, they bowl not only against the batsman but against an invisible bias. That cost sits in my ledger too, though on no scorecard.

So where will my eye rest next series? First, the dot-ball rate in the second over of the first spell—that is the barometer of our true strength. Second, the recovery gap between spells: if it falls below 48 hours, the pace of the third spell will drop by itself, and that is a story of fatigue, not of will. Third, the change point: when the team's plan shifts, and how many matches it holds. Watch these three before the wickets fall, and you can read the result early.

I leave one question behind. We counted so many dot balls, kept so many recovery accounts—but if this labour has no price in the market, why would the next generation of seamers choose this invisible path? That is cricket's biggest data question now, and the scorecard will never answer it.