The Dot-Ball Ledger: Three Seasons of Pakistan's Middle-Overs Deficit

October 23, 2026. Chennai. I was sitting two rows behind the scorers' box, coding ball by ball. Pakistan had made 282 for 7 in fifty overs. The stands still carried that comfortable belief — this total can be defended. Three minutes into the innings break my phase ledger refreshed, and the line that came up broke that belief in one stroke.

Overs 11 to 40. Thirty overs, 180 balls. My coding said 68 of them were dots, only 14 were boundaries, and the run rate in that block was 4.3. On the same pitch, in the next innings, Afghanistan scored at 5.4 across the same phase. I wrote a one-page note. The conclusion was a single line: this total is 25 to 30 runs short. Rahmat Shah and Ibrahim Zadran batted with patience, Afghanistan reached 286 for 2 in 49 overs, six balls to spare. The result had been written into the ledger at the innings break; only the announcement was pending.

I did not throw that note away. I have spent three seasons auditing it, and what came out is not the story of one batsman's form.

Context: why the middle of an innings is the most expensive real estate

Everyone talks about the powerplay and the death overs. The middle thirty overs are dull for television and heaviest for the books. On Asian pitches an older ball grips, seam movement dies, and the stroke-playing window narrows. A side that keeps the scoreboard turning through that phase walks into the last ten overs holding two extra assets — wickets and time. A side that does not has only risk left, and risk only produces two outcomes: explosion or collapse.

My dataset is built differently. From 2026 to 2026 I hand-coded 96 complete ODI innings against full-member opposition, ball by ball. Four variables per delivery: ball number, phase, the striker's pre-phase run rate, and balls since the last wicket. Then I built a three-season rolling baseline so that one good evening or one bad evening could not become a verdict.

One thing needs saying plainly. I did not import football's PPDA or my own old home-advantage model into this work. Football offers a measurable defensive action at the end of a possession; cricket has no exact equivalent. Grafting a football metric onto cricket does not produce analysis, it produces ornament. So I built a cricket-native proxy: Phase Dot Pressure, PDP.

How the model actually works

PDP does not simply count dot balls; it weights each one. A dot after a boundary is cheap — the batsman is settling, that is normal. But two or three dots, then a wicket, then more consolidation: identical on television, different species in the ledger. I keep two classes, dead dots and pressure dots. If pressure-dot density crosses 40 percent inside a ten-over window, that is not an accident. That is architecture.

I will be honest about sample size and confidence. Ninety-six innings is neither small nor large. Ball quality, the two-new-ball rule and fielding restrictions all shifted together after the pandemic, so no single season can be treated as final. I stopped at 90 percent confidence, not 95. I trust the model, then I audit it until the residuals confess.

The core evidence: what the ledger actually says

Pakistan's problem is not the top order. From 2026 to 2026 their powerplay run rate in my ledger is 5.9, with only 1.2 wickets lost per innings — among the best in Asia. Babar Azam's cover drive and Mohammad Rizwan's flick need no new commentary; that department is healthy.

The trouble begins when the graph dips in the middle. Overs 11 to 40, Pakistan run at 4.6. India run at 5.7, Sri Lanka at 5.2, Afghanistan at 5.0, Bangladesh at 4.8. The gap looks small, but 0.9 runs per over across thirty overs is roughly 27 runs — almost exactly what was missing in Chennai.

Boundary frequency sharpens the picture. In the middle overs Pakistan find a four or a six every 12.8 balls. India find one every 8.4. That gap is not about ability, it is about intent. The ledger shows Pakistan's aggression dropping noticeably for the next three balls after a boundary — the thing we call settling down on air. Dead-dot density climbs precisely there.

It feels safe because wickets do not fall. Pakistan actually lose a wicket every 32 balls in the middle overs, which is not bad. But protecting a wicket and scoring runs have been treated as one decision, when in cricket they are two separate decisions. A side that walks through the middle overs quietly is writing a loan against its own death bowlers. In the last ten overs the per-over pressure on Pakistan's bowlers is clearly higher than India's or Sri Lanka's, because they must defend 20 to 25 runs more, and breathe through the arithmetic.

That one-page Chennai note taught me a habit I still keep: verdict first, evidence after. Nobody inside a tournament reads twenty pages of analysis; twelve minutes at the innings break only accommodates one page, and one page can change a decision. That became my rule for writing.

This is where the player's body enters the accounts. My ACL tore, and I rebuilt myself as a ledger of lost minutes. That habit does not stop when I look at Asian fast bowlers. In the 2026 T20 World Cup final Shaheen Afridi injured his knee attempting a catch and could not finish his spell. In the 2026 Asia Cup a shoulder injury ruled Naseem Shah out of the entire ODI World Cup, forcing Pakistan to rebuild the new-ball pairing mid-tournament. Those lost minutes feed straight into over allocation. A side short of middle-overs runs asks more overs from its lead seamer, recovery drops, and the first three matches of the next cycle lose rhythm. That is not an injury story, it is a load calculation.

The traffic inside the subcontinent matters here too. When Sri Lanka lose Wanindu Hasaranga, nobody performs the middle-overs strangling job, and the ability to shove the opposition's plan into a hurry disappears — dot pressure becomes a statistic instead of a weapon. Bangladesh are handing that phase to players like Towhid Hridoy because their problem is resources, not structure. Afghanistan have made their biggest gains in exactly this area.

The economics of the format have shifted as well. A generation shaped by T20 is not trained to hold patience across thirty overs, and the franchise calendar gives it no time to learn. More tournaments mean more matches, but middle-overs craft does not scale with them — it shrinks, because bowler workload and batsman patience are both finite assets.

The contrarian angle: dots are a symptom, not a cause

There is a trap here and I nearly fell into it. More dots means fewer runs — the simplification is so clean that it is wrong. My ledger contains innings with heavy dot counts that still crossed 300, because pressure-dot density stayed low and the scoreboard never stopped. The reverse also exists: few dots, three wickets inside one window, match lost. Dot balls correlate with results; they do not cause them. The cause sits in role architecture, and the ledger catches it late.

An uncomfortable truth sits in my own numbers. At the 2026 ODI World Cup, Bangladesh chose aggression through the middle overs, with visible urgency on strike rate. The result? Wickets in clusters, innings flattened, a finish near the bottom of the table. A side that wrecks its batting balance to fix strike rate gets beautiful numbers and ugly outcomes. I sense the same risk in Pakistan — promoting a power hitter upward would damage the dependable 5.9 powerplay rate first.

On one point I have deliberately walked away from my own earlier writing. What I measured during the empty-stadium season of 2026-21 — home advantage falling from 0.51 to 0.14, set-piece conversion down 18 percent — belongs to football, to Belgian and Dutch grounds. In cricket, crowd effects travel entirely different routes, through reverse swing and an umpire's sense of the boundary, and the effect is much smaller. The urge to run an old model in a new sport is the data analyst's most common failure. Pakistan's problem is not in the crowd. It is in the overs.

What to watch next

For the coming tournament cycle I will track three signals. One: Pakistan's boundary ratio between overs 11 and 25 — if it approaches one every ten balls, the structure has moved. Two: pressure-dot density per over in the middle phase — below 35 percent means the side has genuinely learned to chase. Three: Shaheen's and Naseem's over load across four consecutive matches — with that injury history, this is the earliest warning anyone will get. I do not treat selection gossip as data; selection gossip is an unhedged narrative, and unhedged narratives cannot measure over allocation.

This is my v1.0 and I am labelling it as such. Once at least fifteen innings from the 2026 cycle are coded, I will publish v1.1 with an innings-by-innings changelog — which match changed my conclusion, and on which delivery. That 282 for 7 in Chennai no longer lives in my memory as a defeat. It lives as a forgotten innings-break question. If fourteen boundaries across thirty overs is a limit you wrote for yourself, then what changes — the man or the role? The ledger will answer, on one condition: it also knows whether you asked the question properly.