The Economics of the Dot Ball: Middle-Over Baselines, the Ten-Match Threshold and the New Question of Data Verification

Hook

On page 23 of my coloured notebook, the 2026 Burnley thread is still glued in. That winter I wrote on a Premier League fan network: 12.1 PPDA, 38 percent possession. Someone called it noise. I sorted the data by dot-ball percentage, and the thread found its own footing. That lesson dragged me into cricket, where I discovered we write about the dot ball as if it has one single price.

Last February I sorted my 412-match T20 log by middle-over dot-ball percentage, overs seven to fifteen. My assumption was that teams who ate fewer dots win more. The result ran the other way. Teams with a low middle-over dot count won 53 percent of their matches. Teams who ate dots in the middle and then failed to cover that dot with a boundary in the next two balls lost 71 percent of their matches in my log. The problem is not the number of dot balls. The problem is the price of a dot ball. And that price is not the same in every phase.

Context: No Number Means Anything Without a Baseline

I begin with method, not with the thrill of a specific match. Unless format, venue, era and phase are held constant, reading dot-ball percentage gives you cricket advice, not cricket analysis.

Format comes first. In T20 the powerplay is six overs, the middle phase is nine overs (seven to fifteen), the death phase is five overs (sixteen to twenty). In ODI the powerplay is ten, the middle is thirty, the death is ten. The weighting is entirely different. In my log T20 data sits in one drawer and ODI data in another. Dragging numbers across drawers is, to my mind, a professional offence.

Venue is the second variable. In my experience the Sher-e-Bangla National Stadium in Mirpur offers a slow surface with low bounce that rewards spin; once the ball softens, run-scoring is laborious. Sylhet International Cricket Stadium is flatter with shorter boundaries; the scoring does not stop after the powerplay. Chattogram sits between the two extremes. By my log, average first-innings totals in the BPL were 163 in the 2026 edition and 171 in the 2026 edition. Isolate the Mirpur matches and that average slides to 154. Without venue weighting, a single edition's average should never appear in a batter's appraisal.

Era is the third variable. T20 scoring has risen sharply since 2026 for obvious reasons: bat manufacturing, data-driven shot mapping, and the rehearsed slog-sweep at the death. A 2026 death-over strike rate and the same strike rate in 2026 are not equivalent currency. My precedent tables always carry an era-adjustment column. Without it, the tendencies of a 34-year-old and a 21-year-old sit on the same line, and the conclusion tilts the wrong way.

The fourth variable is bowling quality and match state. A dot ball in a chase tightens the required rate; a dot in a first innings merely burns an over. In my log, chasing sides carry a middle-over dot percentage roughly two points higher than setting sides, because an extra fielder drops back.

Here is the table with those four variables applied. Every number below comes from my own log, not from a broadcast graphic.

| Phase | Run rate | Boundary % | Dot % | Wickets/over | |---|---|---|---|---| | Powerplay (1-6) | 8.1 | 21 | 42 | 0.28 | | Middle (7-15) | 7.0 | 12 | 38 | 0.39 | | Death (16-20) | 10.4 | 24 | 27 | 0.51 |

Read it three times, then do one small sum. A 38 percent dot rate in the middle means 2.28 dots per six balls. The remaining 3.72 balls produce seven runs, so each scoring ball yields 1.88. Bring the dot rate down to 30 while holding the per-scoring-ball return steady and the over yields 7.9. Cutting middle-over dot percentage by eight points is worth roughly 0.9 runs per over—about eight runs across nine overs. That is the price nobody discusses.

Core: Who Pays the Bill for Fewer Dot Balls

In my log, a wicket in the middle overs reduces the final total by about 11 runs on average. A wicket at the death, particularly between overs sixteen and eighteen, costs about eight. The gap between those two numbers is the most neglected truth in Bangladesh's batting ecosystem. A middle-over wicket murders future runs; a death-over wicket only removes the current over's runs.

So the real bill for reducing middle-over dots is charged not to the batter's account but to the team's innings-building system. A side that knows what to do across the seven overs after losing a middle-order wicket can both cut dots and protect wickets. A side without that system either eats dots or panics into a slog and gives a wicket away.

My ten-match threshold earns its keep here. I publish nothing about a batter's dot-ball improvement until ten consecutive matches of rolling splits sit on my table. Three matches can swing a dot rate on one field setting or one wicket. Ten matches reveal whether the improvement is real.

Take a middle-order batter whose dot percentage oscillates between 34 and 39 against his long-run baseline. In the ten-match split I separate three things: venue (Mirpur or Sylhet), opposition spin type (leg-spin or left-arm orthodox), and match state (setting or chasing). Only if the trend survives all three filters do I write. Otherwise I stay quiet.

Disciplined middle-over batting does not mean a shortage of six-hitting. It means building a runs-balls-left footprint without burning the first twelve balls. In my log, chasing innings with a middle-over dot rate under 32 kept the required rate below twelve in the last five overs in 64 percent of cases. Those between 32 and 40 did so in 41 percent. The difference is not the count of dots. It is the control of dots.

The Bowlers: Who Manufactures a Dot

Eighty percent of dot-ball talk concerns batters. Yet a dot ball is a manufactured bowling product, and looking at the producer changes the story.

In my log Rishad Hossain's leg-spin control percentage is high through the middle overs, and his dot percentage exceeds that of the off-spinners, because the speed differential between his slider and his googly forces the batter to change his line. His dot rate at Mirpur and at Sylhet are not the same number. I keep them in separate rows and then state which part is his skill and which is the surface's gift.

A bad habit creeps into almost every analysis of Mustafizur Rahman: his death-over economy is presented as proof of the cutter's magic. In my table I separate the cutter action from the dot balls. Death-over dots come in two kinds—the pressured dot, where a batter who could have scored chose not to, and the manufactured dot, where the bowler nailed his line. Only the second is durable. The first will regress.

Taskin Ahmed's hard length works in the powerplay, but his middle-over dot percentage falls, because by then batters have learned to hit that length, and the dot-ball pressure lands back on his own shoulders. With a pacer like Nahid Rana I use an age-adjusted baseline. Comparing a 24-year-old's death economy directly to a 28-year-old's is a category error, because workload management and ankle conditioning are still in the rough training phase. That workload variable is a bigger addition to my method than anything else in the last two years.

A Venue-First Scoreboard

Every piece I write starts with venue. In Mirpur, spinners' dot percentage reaches 44. In Sylhet it drops to 31. Same bowler, same batter, same month—the difference is the ground. So when someone writes that a bowler has lost form, I ask on which surface he was bowling.

| Venue | Middle-over run rate | Spin dot % | Pace dot % | |---|---|---|---| | Mirpur | 6.4 | 44 | 35 | | Chattogram | 7.1 | 37 | 33 | | Sylhet | 7.9 | 31 | 30 |

The biggest lesson appears when you split setting from chasing. At Mirpur, chasing sides score 0.6 runs per over fewer than setting sides in the middle phase, because scoreboard pressure stops a batter taking the risk of covering a dot. At Sylhet that gap is 0.2. The slower the surface, the heavier the pressure, and the heavier the pressure, the higher the price of a dot.

This is where my caution paragraph belongs. We routinely credit spinners for Mirpur's low scores. But the same spinners take fewer wickets in Chattogram and Sylhet in the same year. That is not a growing skill; that is a specific soil behaviour. Credit belongs after the venue table, never before it.

The Ten-Match Threshold: Why I Refuse to Rush

My rule is simple; the reasoning is not. I do not write about a batter's dot-ball or strike-rate tendency, publish a profile, or pass a verdict unless ten consecutive matches of data sit on my table.

Why ten? Because in T20 a middle-order batter gets roughly 18 to 22 innings across ten domestic matches. Three come on excellent pitches, four on slow ones, two are rain-shortened, one carries Duckworth-Lewis pressure. In a five-match sample that distribution is random. At ten it acquires some order.

But I do not make ten a sacred number. It is a doorway. Past the doorway I run three stability checks.

First, split by opposition type. If a batter's dot percentage stays under 35 against spin-dominant attacks and against pace-dominant attacks alike, only then do I call the trend real.

Second, split by match state. Setting and chasing are separated. Many batters strike at 140 when setting and 114 when chasing. That is common, but some writers hide it inside a team average. Hiding it is withholding information.

Third, the runs-balls-left footprint. I look at per-over run distribution, not just the final strike rate. A batter who eats two overs and then hits sixes has a different over-by-over shape from one who grinds from ball one, even when the final strike rates match.

In study trials, many bright strike rates that failed these three checks turned out to be the gift of two or three venues. Once the flat Sylhet surface is removed, the face does not return.

Precedent Table: Five Batters, Step by Step

| Batter | Role | Ten-match dot % | Last-five dot % | Dot % minus venues | Match-state gap | Note | |---|---|---|---|---|---|---| | Liton Das | Powerplay | 51 | 53 | 55 | 4 | 51 percent dots means three wasted overs per innings | | Soumya Sarkar | Powerplay | 48 | 46 | 52 | 5 | Boundaries expand at Sylhet, stop at Mirpur | | Mehidy Hasan Miraz | Middle | 33 | 31 | 36 | 3 | Most stable under spin pressure | | Jaker Ali | Death | 27 | 26 | 27 | 2 | Low venue sensitivity, hence reliable at the death | | Mahedi Hasan | Death (bowling) | — | — | — | — | Specialist at strangling the fourth over |

I built this grid myself, and I build it to remember what to look at before a decision, not to change the decision. Notice Jaker Ali: strip the venues and his dot percentage barely moves. His death-over boundary capacity is his own, not the ground's. Liton's venue effect is plain. Both get placed on the same row far too often, though their ten-match foundations differ.

Liton's powerplay dot rate of 51 percent frightens once and then invites sympathy. My powerplay baseline sits at 42 percent. He is nine points above it. The question is whether those nine points are his own stroke selection or seven years of resisting a field set for the right-hander's slog-cover. That is partly it. If he could play straighter, the number would fall—through a small change in his trigger movement or a rebuild of his footwork. The coach answers that question. I do not.

Contrarian: A Gap Lives Between the Number and the Story

Now my caution section—the one I like writing least, because it interrogates my own handsome tables.

Many writers convert the relationship between dot-ball percentage and winning into direct causation. That is wrong. Two things occurring together do not make one the cause of the other. In my log, the sides that won more did eat fewer middle-over dots—but the sides they beat also bowled poorly through the middle. The source of the wins may have been opposition weakness, with the low dot count riding along.

Second gap: death-over dot samples are tiny. A batter faces roughly 15 to 18 balls at the death across ten matches. Two dots or four missed slogs swing the whole statistic. When a contract worth crores is priced on that small sample, the loss belongs to the franchise, not to the celebrity.

Third gap, and my largest caution: data is not neutral, because humans type it. An operator records every ball; corrections follow; the correction often carries no date. Two versions of the same over can tell two stories, and nobody knows which was written first.

This is where blockchain-anchored record verification becomes relevant. Over the last two years I have seen franchises and broadcasters consider anchoring a cryptographic hash of the ball-by-ball log at a fixed time, so that any later alteration becomes visible. I am not an advocate for the technology; I am describing the practical demand. In a game that moves tens of millions of dollars, an immutable timestamp for every delivery is not exotic.

Smart contracts in franchise auctions go further. Base price, cap, right-to-match clauses—all of it lives in rules, and the force of a rule depends on who interprets it. If contract terms execute automatically, the player-league-franchise argument shrinks sharply. That is a question of individual freedom, and that debate has not yet reached cricket writing. It should.

Fourth gap, and this one sits on my own neck: the data I publish comes from my own workbook, which contains typos placed exactly where they are hardest to find. So every published table now carries a short note on sample size, cleaning steps and date. If you use my numbers without my note, you are making a mistake—and the fault is mine.

Transfer Logic: The Price of Youth and the Chemistry of the Dressing Room

Auction models still commit the sin I have been writing about since 2026. They pay a premium for youth potential and price dressing-room chemistry at zero. A 22-year-old opener with three dazzling shots gets a price tag; a 34-year-old middle-order batter who de-risks a side for a whole season gets almost nothing. My ten-match table says the 34-year-old's runs-balls-left footprint converts 70 percent of its setting-overs output into slot runs. The model cannot see him, because the model counts boundaries.

Takeaway: What I Watch in the Next Ten Matches

In the next ten matches I will not count middle-over dots. I will check whether the dot rate and the strike-rotation rate move together. If those two lines head the same way, the side is learning. And if the side batting first at Mirpur slows its six-hitting between overs seven and fifteen in favour of grinding, I will know it has read the venue table. If it does the same at Sylhet, I will know it has not. The difference lies in the definition of a surface, and that definition is the coach's business.