The Powerplay Dot-Chain: Four Variables the Points Table Refuses to Measure

The last ball of the fourteenth over went into the covers off a square drive, and the scoreboard announced 62 needed from 42. Sitting in the commentary box, I was not reading the scoreboard. I was reading the ninth column of my ledger—eleven dot balls inside that innings' first six overs, seven of them across two consecutive overs, and five of those seven produced by deliveries that pitched on leg and stopped in the cover-point ring. The batting side lost the match. The collapse did not start in the fourteenth over. It started in the third, when six dots came back to back and nobody recorded them.

One number has kept me uncomfortable all regular season. The side with the fastest powerplay scoring rate sits seventh on the table, and the slowest-scoring side sits in the top three. The six-over figure is not lying. It is being incomplete.

My method was not born in cricket; I borrowed it from football. At fifty-nine, working as a volunteer statistician for Abahani Limited Dhaka in the 2026-16 season, I hand-coded 132 matches: every shot's xG, every player's progressive carries per ninety. The ledger flagged a 21-year-old winger with 4.7 xG chain contributions per match, a figure no local scout had quantified. The club signed him for roughly $40,000; eighteen months later he was sold abroad for $185,000. I built the first xG chain ledger before the league knew it needed one, and it happened in football. In cricket the same question arrives in different words: the ball before the boundary explains the run the way the pass before the shot explains the goal. I follow the ball before the boundary, because the chain explains where the runs came from and where they did not.

The 64 matches of 2026, more than 1,700 shot events hand-coded across 33 days—that post-mortem was never a burial for me. The 2026 post-mortem was not a burial; it was a transfer blueprint. Croatia reached the final while conceding 1.4 xG per match less than their opponents' expected output, and nobody wrote it down because nobody looked outside the goals column.

In cricket I work to a fourteen-column template: match ID, innings, over, ball, batter, bowler, line and length, shot type, field zone, runs, expected runs, chain value, context coefficient, dot-cluster flag. I publish no claim unless a per-over figure sits beside it. The context coefficient is built from four inputs: dew, crowd presence, travel and rest gaps, and pitch age. During the 2026 hiatus I cleaned 512 matches played behind closed doors—home advantage fell from 0.38 to 0.11, home penalty awards dropped nine percent. When stadiums refilled to roughly sixty percent capacity in 2026, the effect began returning. At sixty-one, I learned that silence has a crowd coefficient.

Here is the central evidence, laid out in a table. Powerplay data from the first sixteen matches of this regular season; league average powerplay dot rate is 48.1 percent, league average back-to-back dot rate is 14.8 percent.

| Team | Powerplay SR | Powerplay dot% | Back-to-back dot% | Win% | |---|---|---|---|---| | A | 142.6 | 46.1 | 18.3 | 50.0 | | B | 121.4 | 51.2 | 11.0 | 75.0 | | C | 128.8 | 48.7 | 9.6 | 62.5 | | D | 134.2 | 44.9 | 21.7 | 37.5 |

Read the two right-hand columns. Team A owns the league's highest strike rate but a back-to-back dot rate of 18.3 percent and a win rate of only fifty percent. Team B plays the slowest powerplay in the league, 121.4, yet wins 75 percent of its matches because its back-to-back dot rate is 11.0 percent. Team D is the cleanest witness: 134.2 strike rate, real capacity to squeeze an opponent by the tenth over, yet 21.7 percent back-to-back dots and a 37.5 percent win rate.

The real currency of a powerplay is not the dot ball but the arrangement of dot balls. Two dots spread across two overs and two consecutive dots look identical on a scoreboard. In the second case, though, the bowler bankrolls an extra over inside fielding restrictions, the batter's strike rotation breaks, and the required rate climbs in steps rather than a line. My ledger shows run rate falling to 7.1 in the over after consecutive dots, against 8.4 after isolated dots.

The middle overs sharpen the picture. Between overs seven and fifteen the league economy is 7.4. When a wicket falls inside the previous fifteen balls, that figure drops to 6.1; when no wicket falls, it climbs to 8.2. The two overs after a new batter arrives are where seasons quietly break, which is why an experienced middle-order hand who survives through rotation—Mushfiqur Rahim at his best—becomes the most expensive asset on the sheet. A powerplay half-century is priced; dragging an innings from the eighth over to the thirteenth is not.

In the death overs I isolate one variable: the response dot, meaning the share of dots a bowler returns within six balls of conceding a boundary. The league average is 34.2 percent; the best bowler sits at 48.7 percent. Consider Mustafizur Rahman on 18 June 2026 at Mirpur, taking 5 for 50 on ODI debut against India and finishing that three-match series with 13 wickets. The cutter was a mystery then. A decade on, the question is consistency, not mystery: what share of dots does he return after being hit, and how much does that share fall on a dew-soaked surface?

I do not manage transfers; I manage the arithmetic of regret and opportunity. My auction price band emerges from the ledger on two conditions: a response-dot rate at least 1.2 standard deviations above league average, and a powerplay back-to-back dot rate under twelve percent. For pacers meeting both, 1.3 to 1.6 times base price is defensible. Anything above that is being priced by a sponsor's camera, not by a ledger—cameras hunt the batter's face, and endorsement budgets follow.

Test that against an outside number. Shakib Al Hasan made 606 runs at the 2026 World Cup, batting through from start to finish in almost every innings. The aggregate is superb, but an aggregate never stands alone: wickets, strike rate, opposition bowling depth, dew and daylight all belong in the same calculation. Comparing that season to today without context coefficients is a bet, not arithmetic.

The causal web needs clearing too. Sixteen matches cannot establish that back-to-back dot rate causes wins; a side winning six of fifteen from that sample posts a fifty percent win rate, and three of those six may have gone to the final over. Match-outcome variance in this league is enormous. So I pre-register coefficients before the toss, never after the outcome. Adjusting a coefficient once the match is finished means the model is narrating the game rather than forecasting it.

Counter-evidence sits in my ledger as well. Team D owns the highest back-to-back dot rate, yet two of its defeats came on the final ball by a single run; in those matches the dot-chain was not the cause, dropped catches and one umpiring call were. I also refuse to measure catching efficiency as a separate column, because loading more than five coefficients into a fourteen-column template turns a model into a match description. Toss and dew never share a room with the dot-chain either; strip dew out and second-innings strike rates fall eight to ten points, a movement unrelated to dot clusters.

The real work of a regular season is not reading the table but reading the dot map of the five weeks that produced it. In the next round I will watch three things: whether back-to-back dot rates in overs one to six keep falling, what economy follows a wicket in overs seven to fifteen, and who keeps returning dots after conceding boundaries. The side that holds two of those three will show up in the ledger before it shows up on the table.

One word on the crowd coefficient. A full house straightens a pacer's line, makes an umpire marginally braver on leg before, and lifts an out-fielder's shoulders. Dew pulls that courage back down. Silence and noise are both measurable, provided somebody is keeping the column.