The Missing Row in Chattogram: The Dot-Ball Story the Scorecard Buries

The scorecard said 45 for 1 from six overs. Run rate 7.50. Nobody raised it in the post-match discussion, because 7.50 is neither aggressive nor catastrophic — it sits in that respectable band of numbers that asks no questions. After the game I went back to the video and checked ball by ball. In my handwritten ledger, beside those six overs, there is a column that never appears on the broadcast graphic: 15 dots in 36 balls. Forty-one point seven percent of the powerplay produced no run at all — that empty row is the story, not the 45. The Chattogram desk taught me that a missing row is a louder story than a headline.

I have kept a ball-by-ball ledger of domestic T20 cricket since 2026. In my first season I logged 132 Bangladesh Premier League matches and 1,847 shots by hand, because no commercial data provider was separating dot balls for our domestic league back then. In Chattogram a betting syndicate told me a woman did not need that ledger. I kept the ledger. It is now my only asset.

My method has three layers. The first is the scorecard — runs, wickets, overs; verifiable but incomplete. The second is the video log — who was batting, where the field stood, where the ball landed. The third is ball tagging, where I sort every delivery into six categories: dot, one or two, boundary, wide or no-ball, wicket ball, and missed opportunity. That third layer is never published, and it is where every conclusion is actually built. The error bars must stay visible: my home T20 sample is 42 matches — enough for a trend, nowhere near enough for a single verdict.

Why does the powerplay carry so much weight? Because in T20 the shape of an innings is settled in the first six overs. The runs arrive in the last four, but the size of the innings arrives early. I borrowed this structural thinking from the France–Argentina match in 2026. I followed France — France's PPDA was 15.8, Argentina's 8.9, and Argentina's three goals came from 0.9 xG. The result was 4-3, but the structure was saying something else. Cricket has no direct PPDA equivalent — in football PPDA measures how many passes you allow before you lose the ball; cricket has no ball-loss event of that kind. So I map exactly one variable: the number of balls per over that apply pressure on the opposition, meaning dots plus wicket balls.

Across my 42-match ledger, the average powerplay dot-ball share is 44.1 percent. Split the matches into three buckets and the picture sharpens. Where the dot share fell below 38 percent, the average final total was 168. In the 38-to-48 percent band, that average was 154. Above 48 percent, it dropped to 141.

Those three numbers build a trap, and I am not walking into it. Dot balls falling while runs rise is close to an arithmetical inevitability, because the two are opposite faces of the same coin. The real question is different: when dots fall, is the side hitting more boundaries, or wasting fewer balls?

My tagging says the second. In innings where the dot share dropped below 38 percent, the strike rate on scoring balls averaged 176. Where the dot share sat above 48 percent, the strike rate on scoring balls was 173. A three-run gap — statistically meaningless. The difference is not how hard the ball is being hit, it is how many balls are being thrown away. That is innings efficiency, not innings aggression.

An older note from Qatar 2026 applies here. Germany lost 1-2 to Japan with 26 shots, nine on target, 1.95 xG; Japan had 1.36 xG. Many called it a collapse. My ledger said Japan's two goals came from 0.4 xG, and Germany's PPDA of 7.2 had left the transitions open. Shot volume is not evidence of quality. Nor is 45 runs in a powerplay, if it costs you 15 balls.

Where a batter like Litton Das or Towhid Hridoy is sent — three or five — changes the powerplay dot share directly, because who faces which field is what determines the type of dot. The same logic runs through the bowling side: when Taskin Ahmed takes his first spell sets the opposition's powerplay structure.

Now the young-batter question. In football my rule was 900 minutes — during Euro 2026 I held back a verdict on Pedri despite 629 minutes and 92 percent pass accuracy, because only three of ten teenage midfielders since 2026 sustained elite output beyond 900 minutes. The 900-minute rule is a monastery bell: it calls you back from magical thinking. In cricket I translate it into balls — 900 balls in T20 is roughly 35 to 40 innings. But the translation is imperfect, and I say so: football's 900 minutes measures physical endurance, cricket's 900 balls measures the stability of shot selection. The metric changes; the decision boundary does not.

So when a young powerplay batter in the domestic league holds a dot-ball share under 40 percent for six straight innings, I write down the name. I do not announce it. I write the name and I wait.

The most common reaction is to raise intent. A batter under dot-ball pressure looks for the big shot, and coaching staff push a more aggressive batter into the middle order. In my ledger, that reaction produces the opposite result. In domestic T20 innings where the powerplay boundary-attempt ratio climbed above 55 percent, the dot-ball share averaged 46.2 percent — it went up, not down. Aggression does not change the defence; the defence changes where aggression has room. The fielding side pushes men deep, the batter reaches for balls further from the body, and the dots accumulate.

Process and outcome need separating. In January 2026, Bangladesh's first Test win on New Zealand soil at Mount Maunganui arrived in a stretch where the side had lost four of its previous six matches — yet the ball-by-ball ledger showed the team bowling better throughout. The win created nothing new; it made visible what already existed. Miss that distinction and analysis becomes a servant of headlines.

The second trap sits elsewhere: home advantage. In 2026 I analysed 83 Bundesliga matches before and after Project Restart and found the home win rate fell from 43.2 percent to 33.8 percent. I cut home advantage by 18 percent in my model and tested it across 27 matches. In cricket the translation is only partial — home advantage here does not come from crowd noise, it comes from pitch preparation and toss-dependent conditions. Variables can be mapped; processes cannot. Where the mapping breaks, I stop.

For the next series I will watch the first six overs' dot-ball share, not the run rate. My threshold is simple: below 38 percent across three consecutive matches, the innings structure is trustworthy; above it, the number is only a caution flag. The question will sit in next month's table — will sides reduce the dots, or simply rearrange the strike rate?