Dew, Dot-Ball Clusters and the Powerplay Puzzle: Counting Pressure on a Dhaka Pitch

A day-night match at Mirpur's Sher-e-Bangla Stadium. At the fifteen-over mark the required rate stood at 7.8; in scoreboard language, the chase sat comfortably in the hand. My notebook, however, already carried fifty-one dot balls, fourteen more than the opposition. In the four overs that followed, six wickets fell, and five of them arrived off deliveries that were not themselves dots — they arrived immediately after a dot-ball cluster. Pressure in cricket is not a mood. Pressure is a countable event. Before the model had a name, I counted chances by hand, and every dossier I build still opens with my hand counts.

I borrowed a concept from football — PPDA. At the 2026 World Cup in Russia, Germany posted a PPDA of 6.2 against South Korea, yet conceded 18 shots and 2.4 xG while generating only 0.8 xG of their own. The number tells you how much pressure was applied, never how much pressure was absorbed. Cricket does not accept that logic literally, because cricket pressure is discontinuous: balls, spells, drinks, timeouts, rain. Time here comes in fragments. So the dossier runs in four fixed steps — baseline, split, corrected figure, verdict — each in its own column, so that anyone recounting the same match three months later can reconcile the rows.

My definitions number four, and without all four columns I do not file a match report. One, dot-ball cluster: three or more dot balls in a single over. Two, pressure event: a dot immediately after a boundary, a wicket ball, the first ball after a timeout, or two consecutive dots in the death overs. Three, release over: two or more boundaries and two or more dots in the same over — an over that opens and shuts a game simultaneously. Four, Dew-Adjusted Expected Runs (DER): identify the over in which dew begins in the second innings and adjust run expectation for every over thereafter.

My baseline is the 2026 T20 World Cup Super Eight, where Bangladesh arrived for the first time and lost all three matches. Across those three games the powerplay dot-ball rate averaged 52 percent. The same side at home in the first six overs sits between 58 and 63 percent. That is not a change in batting character; that is pitch and ball behaviour. At Mirpur the new ball stays a touch low, and on a slow, low surface a batsman must push his weight forward to play back-of-length, which ruins timing. No timing, no runs, more dots.

Set the Super Eight baseline beside the home split and the picture sharpens. Abroad, Bangladesh's opening pair scored 6.8 runs per over with a 48 to 52 percent dot rate. At home those two numbers become 6.1 runs and 58 to 63 percent. The run gap is 0.7; the dot gap is more than ten percentage points. That spread says the problem is not scoring rate, it is ball consumption. Every extra dot ball transfers additional risk onto one batsman in the following over.

The middle overs, seven to fifteen, carry the most information for me. Whether strike rotation survives that phase tells you whether a side is absorbing pressure or storing it. At home, 57 percent of Bangladesh's middle-over runs came in singles, yet only 6 percent came in twos despite the large boundaries. The ball was finding gaps; the batsmen could not commit weight. This is exactly where the heatmap deceives. A heatmap shows where the ball went; it never shows why the batsman could not place it there. The eye test is a witness, not a judge; the model keeps the transcript.

In the death overs a dot ball is multiplied in cost. Between overs sixteen and twenty, one dot often forces a boundary attempt on the next delivery. In one cycle I paired every death-over dot with the output of the following ball: scoring-shot rate rose roughly 22 percent on the ball after a dot, while dismissal risk rose roughly 31 percent. Pressure does not change probability so much as it shortens decision time — that is the only usable definition of pressure.

Now dew. From 83 Bundesliga restart matches in empty stadiums in 2026 I built a correction coefficient: home win rate fell from 43 percent to 33 percent, goals per game from 3.2 to 3.0. In cricket the equivalent correction is dew, not crowd. On a normal Dhaka evening, once humidity passes 80 percent, the ball gets wet after about the twelfth over, spinners lose grip, and the slow cutter loses its bite. In my DER frame I add 0.11 runs to every remaining over of the second innings; if dew begins after the seventeenth over, I add half that. Across the 47 hand-counted day-night matches I have logged in Dhaka and Chattogram between 2026 and 2026, a side that lost more than four wickets before dew began won only six times.

In player dossiers the correction hits seamers hardest. A cutter-dependent bowler's economy inflates on a wet ball, while a seam-based bowler loses less, because seam position depends on the wrist rather than on friction. That single line proves a dry-pitch XI and a wet-pitch XI are not the same team, even when the squad is identical.

Caution, though. Correlation is not causation, and dew is a variable, never an alibi. My personal trap is environmental determinism — explaining every outlier as pitch, dew, humidity or resource gap. So the rule is strict: correction factors are pre-registered, and unadjusted numbers always run beside adjusted ones. In this match the unadjusted dot rate was 59 percent and the dew-adjusted rate 54 percent. Dew explains under six percentage points. The remaining five have no alibi, and that five percent is the real investigation.

The second trap is toss narrative. We say winning the toss in Dhaka means winning the match. In my 47-match log, toss winners took 25 games — 53 percent, inside coin-flip range. What predicts better is the powerplay dot cluster. A side producing four or more dot clusters in the first six overs lost 74 percent of those 47 matches. The toss does not decide the night; powerplay ball consumption does.

My dossier carries a template exception section, and this series forced it open. In one rain-shortened match the Duckworth-Lewis-Stern target shifted so sharply that standard pressure events became meaningless. I added a new variable there: conditional progression, the rate of actual progress against the revised par each over. It now sits in its own column, because a dossier that forces a game into a template lies about the game.

So what do I watch next? Not the powerplay dot rate itself, but the quality of the decision on the ball after a dot. Two things get tracked: the over in which dew arrives, and the strike-rotation ratio in the fourth over of the powerplay. If those two columns reconcile, the run rate reconciles itself. And if someone tells me again that this is simply what Dhaka pitches do, I will ask which over the dew came, and how many dots had accumulated before it. The scoreboard will not hold that answer. My notebook will.