The Dot-Ball Ledger: How a Glittering Asia Cup Scoreboard Buries a Fast Bowler's Workload

Last September at the Dubai International Stadium I was not counting runs. I was counting overs. In a group game at the 2026 Asia Cup, a fast bowler was into the 21st over of his spell for the second time in 24 hours, while the broadcast camera zoomed in on the batsman's footwork. The scorecard said 7.8 an over; the commentary said outstanding death bowling. I went home and opened the spreadsheet. Scorecards do not keep a ledger of spells, only a ledger of wins. The tournament ran from 9 to 28 September and India beat Pakistan in the final. What no column recorded was how many overs sat on whose shoulder, or how many days each man spent in a hotel bed away from the game. Asia's calendar has taken a geometry over the last three years in which the same fast bowler appears in three franchise leagues in three countries, with a bilateral one-day series in between and an ICC event after that. The ICC Future Tours Programme for the 2026-27 cycle had already raised the volume of mandated matches for full members, and league windows sit on top, from the Bangladesh Premier League and the Indian Premier League to the Pakistan Super League, the Lanka Premier League and ILT20. On a September evening in the UAE, with the outfield wet with dew, that load doubles: the ball slips in the second spell and gripping it costs extra effort. Since taking up digital and media duties as a Bangladesh Cricket Board adviser last year, I have been able to read the calendar from the other side of the screen. A board's file and a broadcaster's file are not the same document. The broadcaster wants the best match in its best slot, the board wants revenue, and the bowler on the field wants one outcome: his seven days. No empty column exists between those three demands. The emptiness lands on the bowler's shoulder. In May 2026 I was in a Dhaka press box writing out Shakib Al Hasan's over distribution while the screen beside me showed an English domestic game. Two screens, two languages: one counting overs, the other counting matches. That night I decided a bowler could not be appraised on wickets and economy alone. The spell-by-spell count had to enter the file, and not over a handful of matches but on a rolling sample. In the 1980s cricket statistics were scorebook pages. Now they are ball-tracking data. The question has not moved: how many overs can pile onto one fast bowler's shoulder before his effectiveness begins to slide? Answering it forced me to build a larger sample, and that made me slower. I opened the spreadsheet and made the Asia Cup confess its exaggerations. The method was plain: ball-by-ball data for six frontline fast bowlers from 24 months of Asia-region internationals and franchise matches, split into 10-match rolling samples, measured on three pillars. Dot-ball percentage. Boundary concession rate in the death overs, from the 16th to the 20th. And a workload ledger: overs per seven days, number of spells, back-to-back matches, and the recovery window in days. The first thing to emerge was a safe ceiling for dot balls. In my ledger, below eleven to twelve overs in a seven-day window, a fast bowler's dot-ball percentage stays broadly flat, in the 42 to 46 percent band. Cross that line and the picture changes. With overs piling up into a third consecutive week, the dot-ball rate drops four to six percentage points, while economy barely looks worse because the ball is still landing near the right spot. What drops is the consistency of line and length, and the boundary concession rate in the death overs rises three to five points. I counted the dot balls that never make the thumbnail. On Asia Cup pitches this is even clearer for spinners: the workload curve for an off-spinner like Mehidy Hasan Miraz behaves differently from a fast bowler's. A tired seamer loses pace; a tired spinner adds flight, and for a while his dot-ball count actually rises because batsmen searching for runs make mistakes. That is exactly where the gap opens between safe statistics and real contribution. There is a simple way to value a dot ball. In a T20 over of six balls, four dots and two twos mean two runs for six balls spent. If the same bowler is then hit for two sixes in his next over, the spell average looks respectable while the damage spreads across the match. So I keep the account at spell level. Holding the first two overs of a three-over spell and then conceding the big shot in the third means fatigue is showing, and that detail dissolves into the sixth column of the scorecard. The workload arithmetic is harsher still. Asia's calendar carries so much travel that two flights and a training session inside a seven-day window can cut recovery to two days in practice. In my ledger, a fast bowler's average pace in a second spell in that condition fell two to three kilometres per hour below his first, and it was visible before it reached the score: in whether the batsman was moving his feet a second time as the ball left the hand. This method did not start with cricket. At the FIFA Under-17 World Cup in India in 2026, England won with 28 goals against an expected-goals figure of 22.4, an overperformance of 5.6. I told clients then that the scoring was unsustainable. The following year, in Russia, Spain completed 1,029 passes and held 74 percent possession against Russia with an expected-goals figure of 2.4; Russia's was 0.6. It finished 1-1 and Spain lost on penalties. Passes and possession do not measure dominance. I wrote that into the file that day. Back in cricket the same truth holds. Runs and wickets do not measure dominance. Over counts and the quality of a dot ball come closer. Taskin Ahmed's case occupies a column of its own in my ledger. His injury history is no mystery, but the timing of the breakdowns is the actual information. In the match blocks where he bowled, at least two had a seven-day over count above twelve, and pace dropped in the match immediately after. That is not the cause of an injury. It is the pre-signal. The signal appears two matches before the headline, just as data begins to murmur before the regression is run. The timeline was loud, so I regressed it until the noise fell away. That is where the largest trap sits. A dot ball is a safe, countable act, and countable things pull the mind off course. Defensive bowling to a set batsman on a flat deck also produces dots. Those dots say nothing about the result, yet they take the hero's chair in my table. The same error happens with economy. Four overs for twenty-nine at the death draws praise, but what if the seven overs before that produced no wicket and let the opposition's set batsman bat through? What is that bravery worth? The distance between safe statistics and actual impact is the weakest part of my accounting, and I keep that admission in the file. The workload-and-decline relationship also demands care. Heavy overs and falling effectiveness occur together, which does not make overs the only cause. Sleep, travel, time zones, even a wedding season, all of it leans on the same shoulder. Sixty-six years taught me patience; the data taught me why it pays. So I look for trendlines and change points, not just averages. Then there is the ground and the crowd. When the stadiums emptied, I listened for the home advantage to disappear. At neutral venues in the UAE nobody holds it, yet the talk of umpiring tilting toward the big side does not fade, even in an empty ground. I rewatched one match and saw a review decision explained two different ways on two screens. The difference was not in the explanation, but in the moment and the context around it. My table keeps one separate box, the anomaly box. At the last Asia Cup a wicketkeeper's stumping changed the tempo of a match, and no metric holds his name. For a goalkeeper I counted the saves that never made the thumbnail; in cricket that work belongs to the keeper's dive and the fielder's run-out, and I keep their ledger too. Next series I will not read the average on the scorecard. I will read the overs-per-seven-days column. If a fast bowler sits above eleven for two straight weeks and his line begins to drift, my signal is ready. Which bench is holding that bowler today is the next question.