The Dot-Ball Ledger: The Twenty-Two Missing Balls in Pakistan's Middle Overs

National Stadium, Karachi, 19 February 2026. The Champions Trophy opener. New Zealand 320/5, Pakistan bowled out for 260, a 60-run defeat. That is all the scoreboard says. The ball-by-ball log says something else. That night I hand-coded 240 deliveries, and one thing kept returning: in the first ten overs Pakistan's batters found a boundary every 6.2 balls; between overs 11 and 30 — precisely the window where a match's real account is written — boundaries came once every 14.8 balls. I counted 71 dot balls in that window. Fifty-nine per cent.

Seventy-one dots in a single match is not a trend. It is an event, and I do not write forecasts out of events.

Context: how I keep the books

Years of watching matches have given me a habit — I read the delivery-level log before the scoreboard. In 2026, at twenty-six, a third ACL tear ended my semi-pro career and I joined Union Saint-Gilloise as a junior performance analyst, hand-coding 380 Belgian second-division matches. That is where the method came from: claim, evidence, baseline, constraint, then a verdict that fits on one page.

My ACL tore, and I rebuilt myself as a ledger of lost minutes. In cricket that ledger is called the Dot-Ball Pressure Index, DBPI for short. It is not a translation of a football metric. It stands on three cricket-native components: dot density — dots per over from overs 7 to 15; strike rotation rate — the ratio of singles and twos per ball; and a boundary suppression index — balls spent per boundary. Each component is calibrated separately across three seasons, then weighted.

There is a temptation here that I refuse. At the 2026 World Cup in Russia, at halftime, PPDA whispered to me that Japan's press intensity had fallen from 12.4 to 8.9; that one-page note helped Belgium return to a 3-4-3 and win in the 94th minute. After that success colleagues wanted to bolt PPDA onto cricket. I declined. Dot balls are not PPDA, because in cricket ball possession is not shared — a bowler delivers one ball and stops. A proxy imported without calibration collapses at the first sign of pressure.

The core account: a three-season baseline

I coded Pakistan's ODI middle overs — overs 11 to 30 — from 2026 through 2026 and compared them with the average of the top five sides. In my tracking Pakistan's middle-over run rate sat 0.4 to 0.7 runs per over below the opponent average across those three years. The curious part: Pakistan's boundary-per-ball rate in the same window is not poor — roughly level. The gap is created by the crowding of dot balls, and that crowding is never evenly spread.

This is where a phase-break autopsy is needed. I found that in the five overs after a Pakistan wicket falls, dot density rises by roughly 38 per cent. A new batter arrives and Pakistan stops scoring — not to settle in, but out of an inability to control pressure. That five-over sample now spans 41 innings, and the pattern has held.

The conclusion runs the other way

The common explanation says a wicket lowers the run rate. My log says the wicket is the trigger, not the cause. The cause is the dot cluster that follows it. Afghanistan's first-ever ODI win over Pakistan in Chennai on 23 October 2026, and the Super Over defeat to the United States in Dallas on 6 June 2026 — both show the same shape: a wicket, then four or five near-dormant overs, then a late surge.

I trust the model, then I audit it until the residuals confess. Late in 2026 I added Pakistan's matchup history against spin in overs 11 to 16, because the first model was mis-forecasting that window. The residuals showed the problem was not the quality of the spin but the geometry of singles when two right-handers are at the crease — fielders cut the ball off easily, and the rotation rate fell from 0.71 to 0.49.

There is a cost to modern T20 batting orders that nobody wants to book. While everyone manufactures 'finishers', the specialist who rotates strike, finds gaps and absorbs the middle overs — apparently slow — is being squeezed out. An innings loses its rhythm, because rhythm is not acceleration.

Load and balance

One more ledger is directly tied to middle-over scoring: fast-bowling spell minutes. After Shaheen Shah Afridi injured his knee in the T20 World Cup final at the MCG on 13 November 2026, Pakistan's death-overs planning shifted and his availability became uneven for two seasons. In my accounting, if a fast bowler's lost spell minutes in a season cross a defined threshold — I use 40 overs — his economy in the following season rises by about 0.8 above baseline. I do not apply the rule to every seamer, only to those who cross the threshold.

An old objection returns here. Distance, sprints, coverage — these effort metrics produce pretty numbers, and in cricket pretty numbers are often false comfort. A batter can make 45 off 50 and keep the run rate tidy while leaving the burden of twelve match-defining dot balls on the team. Run rate is the pretty number. The dot cluster is the truth.

Contrarian: not strike rate, but timing

The most familiar complaint about Pakistan cricket is a low strike rate. My data does not support it, at least not in the middle overs. From 2026 to 2026 Pakistan's middle-over strike rate was roughly level with the top-five average; the difference lies in how that strike rate is distributed. Other sides spread risk evenly across overs; Pakistan stores it for the last five. In hard tournament matches the required rate arrives, but the wickets are paid for all at once.

This is where correlation and causation get confused. The argument runs: Pakistan lose the matches in which they lose early wickets, so protecting wickets is the fix. I say a wicket and a defeat are related, but the wicket is not the cause of the defeat. The cause is the dot block that follows, and that is a coaching and role-definition problem, not a talent problem. The six-wicket defeat to India in Dubai on 23 February 2026, and the group-stage exit, showed the same structure.

There is a further layer I will not skip: tournament structure. Back-to-back matches, travel, short turnarounds — all of it shapes the quality of middle-over decisions, chiefly through fast-bowling workload. My position on tournament expansion is simple: more teams mean more matches, but recovery hours do not grow with them. The side that treats workload as a primary constraint scores fewer dots in the middle overs, because its bowlers can still change plans in the final over.

The forward signal

For the 2026 T20 World Cup my one-page verdict is this: Pakistan's selectors should ask first not who is scoring most, but who can rotate strike from overs 11 to 16. The second question should be which fast bowler has crossed the spell-minute threshold. Answer those two, then write the batting order.

Those 71 dots in Karachi still sit in my log as an index number. The question is simple: in the team's ledger, at what line is a dot ball written — on the last page, or on the first?