The Dot-Ball Ledger: Where T20's Real Value Hides

Last week I watched the final over of a T20 match. The scoreboard said five runs had come off it. A friend on the sofa said, “The bowler got lucky; the batter made a mistake.” I opened my ledger. In that single over there were five dot balls, one diving stop, and a half-chance that died in the wicketkeeper's gloves — which the scorecard recorded only as “dot.” The stadium board never counts those. They never make the thumbnail. And yet the story of that match was written in the five dot balls, not in the five runs. I have watched cricket for fifty-six years, and for eighteen of them I have explained it with numbers. One thing recurs: T20 conversation is almost entirely about a batter's strike rate and six count. The reason is simple — those are quick to see and quick to share. But matches are usually decided by the acts nobody counts. In a fixture like India versus Pakistan the pull is even stronger — hours of talk about a single shot from Rohit Sharma or Babar Azam — while the ODI World Cup head-to-head still reads 8-0 to India. That is not the story of one shot; it is the story of sustained defence and absorbing pressure. In 2026, when India hosted the Under-17 World Cup, I was running a paid data newsletter. England scored 28 goals but their xG was 22.4 — five or six goals of overperformance. I told clients the scoring was unsustainable. I applied the same logic at the Russia World Cup in the Spain-Russia match. Spain had 1,029 passes, 74% possession, xG 2.4; Russia had xG 0.6. It finished 1-1, and Russia won the shootout. The lesson is plain: the number you notice is the number that says least. In cricket that least-noticed number is the dot ball — joined by wicketkeeper interventions, run-outs, and economy under death-overs pressure. When I analyse a T20 match, I go down three layers. The first is fixing the sample. I do not write a verdict off one match or one series; I hold a rolling window of at least ten. Five dot balls in a single match can be the pitch's doing; over ten matches it becomes a pattern. So I wait — and the waiting is itself a method. The second layer is dot-ball rate, not raw count. A bowler's overall economy tells you nothing about which overs he bowled. I separate powerplay dot rate, middle-over dot rate, and death-over dot rate. Example: one bowler in my ledger has an overall economy of 8.4, but in his last four overs his dot rate is 38%, roughly one and a half times the league average. On the scorecard two bowlers look identical; inside the match they are entirely different. The third layer is the defensive ledger. How many half-chances the keeper saved, how many byes he did not concede, how many stumpings or catches he took — I log these separately, with run-outs beside them. Over the last two seasons I calculated one keeper's “runs prevented”: his footwork against the reverse sweep, his glove placement against the yorker. It came to six to eight runs a match — runs that never appear in any statistical column. Here is the heart of it. We argue for hours about a batter's strike rate, yet a bowling side's win probability depends far more on its dot-ball rate. In T20 the real currency is time — the fewer balls spent, the less the pressure at the end. So every innings I log a separate figure: “pressure economy” in the death overs. That number is far more honest than average economy, because it measures the ability to force a batter into risk. Before every series I build a baseline sheet — league-average dot rate, average powerplay score, average death-over economy. After each match I lean on that sheet and ask who has moved ahead of the baseline. The names that do go into a separate ledger — that is my watch-list for the next series. And I regress the timeline, because the timeline always shouts. “This bowler is in form,” or “this side's powerplay is fearsome” — loud claims. I run them through four controls: baseline, opponent quality, venue, and form. Most of the time the claim is inflated. Sometimes change-point detection is needed — to find where a rhythm broke. One example: a spinner's economy spiked mid-series although his line and length had not changed; what changed was the length of his spells and the travel load. The number was showing form; the cause was workload. That is why I log a bowler's overs, spells, travel, back-to-backs, and recovery windows. When a bowler suddenly declines at the end of a series, the answer is usually in the ledger, not the form book. In the 2026-19 window, when Liverpool signed Alisson Becker for £66.8m, I argued their xG against would drop by at least 0.3 per match. The number held. I reached that view not from highlight reels but from checking ten-match rolling data. Cricket obeys the same rule — watch ten matches before you buy a bowler or a keeper, not one clip. There is a trap here that I catch myself in often. Dot balls and keeping interventions are easy to count, so there is a risk of overpaying for them. But not every dot ball is equal. One dot ball may be the product of a superb yorker; another may be the joint gift of a batter anchoring and a slow pitch, where the bowler's credit is thin. A run-out may be sharp fielding, or a batter's bad call. The number is one; the cause is two. So I never read dot rate alone; beside it I keep context-adjusted impact — pitch type, powerplay field setting, the depth of the opposition batting. One more thing. Often a dot ball comes from a defensive field and safe bowling — which actually hurts the side, because the batter cuts loose next over. Counting this “fear-driven dot” as heroism flips the arithmetic. It is the same trap many fall into: treating what is countable as what is valuable. So in every analysis I keep at least one anomaly section — where the numbers say nothing, the smell of the match speaks. Next series, when the scoreboard counts sixes, look once at the wicketkeeper. See whether his interventions are rising or falling over the last five matches; see whose death-over dot rate is climbing. Because the result of a match is often written in the column nobody turns into a thumbnail.