Powerplay Control Percentage: A Ten-Match Audit of Bangladesh's T20 Batting Baseline

1. The over that pushed me back ten matches

One over from June 4, 2026 still sits apart in my logbook. The ball-by-ball column reads 32/2 — three dots in the over. The broadcast graphic kept replaying those three dots. My own column recorded a control percentage of 61 for that over. Five of the eight balls were outside the batter's control: two edges, a mis-hit, a late shot, one step into an LBW trap.

The scoreboard said patience. My column said something else.

I spent that evening on a balcony in Rangpur asking a simple question: forget one over, where does Bangladesh's powerplay actually sit across the last ten matches? Sorted into ten-match blocks, the answer is uncomfortable. Run rate rising, control falling. In cricket, scoreboard improvement and method improvement are rarely the same thing.

This is an audit of a phase, not a verdict on an innings.

2. Baseline first, opinion later

I moved from cricket writing into the board's media setup in 2026, and the habit formed early: write the baseline before the argument. When I started weekly data threads on the Premier League in 2026, the habit hardened. That Burnley thread looked like noise at first — 38 percent possession, 12.1 PPDA, everyone writing 'passive football'. Sorted by PPDA, it became a deliberate low block. The number did not convict anyone; the sorting did.

Football's PPDA does not transfer cleanly to cricket. Each sport needs its own vocabulary. The cricket-native measures I use:

Control percentage (batting): the share of deliveries a batter played fully in control — line and length read early, middle of the bat, shot as intended. Slight edges, top edges, mis-hits and mistimed slogs fall outside.

False shot percentage (bowling): the share of deliveries that induced an error. A proxy for pressure.

Boundary percentage: how much of the scoring came in fours and sixes. Control falling while boundaries rise is a warning bell.

Phase split: 1–6, 7–15, 16–20.

The sample is mine: 72 Bangladesh T20Is from January 2026 to June 2026, 421 innings-phases, coded from my own score sheets, broadcast feeds and cross-checked against public archives. Every phase entry carries its match state, wickets, required rate and opposition tier. Without those tags, a phase table means nothing.

I do not apply a ten-match threshold blindly. I pre-register why ten and what the conditional exception is. The arithmetic is plain: ten matches is roughly 60 powerplay overs, about 300–360 balls. At that size a proportion carries a 95 percent interval near ±5 points; smaller samples run ±8 to ±10. A three-point move is noise in my book. Even a four-point move over eight matches waits, because one outlier innings can manufacture it.

Table 1: Global T20 phase baseline (my log, 2026–2026, 420 innings-phases)

| Phase | Run rate | Wickets/over | Control % | False shot % | Boundary % | |---|---|---|---|---|---| | 1–6 | 7.9 | 0.35 | 73.4 | 17.2 | 15.1 | | 7–15 | 7.6 | 0.39 | 75.1 | 15.8 | 11.4 | | 16–20 | 10.1 | 0.58 | 71.9 | 19.4 | 18.7 |

The powerplay carries the highest control percentage, because the new ball swings and seams and batters take fewer risks. When control drops in the powerplay, it is usually evidence of forcing.

3. Core: three blocks, one bend

Table 2: Bangladesh powerplay batting, three ten-match blocks

| Block | Run rate | Control % | Own false shot % | Boundary % | Wickets lost/match | |---|---|---|---|---|---| | Block 1 | 7.41 | 71.6 | 18.4 | 13.8 | 1.4 | | Block 2 | 7.88 | 69.3 | 20.9 | 14.6 | 1.6 | | Block 3 | 8.27 | 67.2 | 23.1 | 15.9 | 1.9 |

Powerplay run rate up 0.86. Control down 4.4 points. False shots up 4.7 points. Wickets lost in the phase up 0.5 per match. The runs have been bought with risk, not with skill. Control percentage falling means batters are not resisting better balls — they are imposing themselves on them. Against a global baseline of 73.4, 67.2 is a six-point gap.

Block 3's best powerplay innings carried a run rate of 11.4, more than two standard deviations out. Its control percentage was 68.2, below average. Even the outlier leans against the trend.

Table 3: Bangladesh powerplay bowling, three ten-match blocks

| Block | Economy | Line-length accuracy % | Induced false shot % | Dot ball % | |---|---|---|---|---| | Block 1 | 7.02 | 68.9 | 18.1 | 42.6 | | Block 2 | 7.36 | 71.4 | 19.8 | 41.1 | | Block 3 | 7.81 | 73.8 | 21.2 | 39.4 |

The bowlers improved — accuracy up five points, induced errors up three — while economy rose 0.79. The batters are taking more risk and converting it for now. That structure is hard to sustain, and if it persists the question shifts: the constraint is not execution, it is the plan.

Table 4: Match-state split (last 30 matches, powerplay only)

| State | Control % | Run rate | Boundary % | Wickets | |---|---|---|---|---| | Batting first | 65.3 | 7.94 | 14.2 | 2.1 | | Chasing | 71.8 | 8.61 | 17.1 | 1.3 |

A 6.5-point gap. With a target in front, Bangladeshi openers bat with far more control. The powerplay problem is not technique; it is setting-state planning. Batting first, the powerplay is treated as a phase. Chasing, it is a phase and a target at once — and the control rises accordingly.

Table 5: Powerplay versus pace and spin (last 20 matches)

| Type | Balls | Control % | Runs/ball | Induced false shot % | |---|---|---|---|---| | Pace | 218 | 70.4 | 1.31 | 20.1 | | Spin | 142 | 64.7 | 1.24 | 24.6 |

Against spin, Bangladesh score less and control less. Those overs produce neither runs nor wickets, which pushes the pressure into the middle phase.

4. Phase-turn map: where the match actually turns

After Croatia's 2026 World Cup semi-final I logged Luka Modric's 12.8 kilometres alongside Croatia's 9.7 PPDA. The distance looked magnificent. Mapped over-by-over, the extra-time resilience came from a specific middle zone, not from the total. In cricket that map is a phase table, not a distance.

Table 6: Which phase separates wins from losses

| Phase | Run-rate gap | Wicket gap | Control gap | |---|---|---|---| | 1–6 | +0.41 | −0.2 | +1.8 | | 7–15 | +1.17 | +0.9 | +4.9 | | 16–20 | +0.63 | −0.3 | +2.1 |

Bangladesh's matches are decided in overs 7 to 15. The powerplay's control gap of 1.8 points matters mostly because it sets the state for the middle phase, where the gap swells to 4.9.

5. Stability checks: where the claim held, where it cracked

Opposition tier. Against full members, control fell from 70.9 to 65.8 across the blocks — the direction holds. Against associates it moved 73.6 to 71.1, on thin samples. The claim does not travel there without adjustment.

Venue. In Asia, control fell 73.1 to 69.4. On SENA pitches it barely moved (68.2 to 67.9) while run rate jumped 8.1 to 9.1 — a different illness, about where bowlers pitch the ball.

Match state. Batting first, the decline is stark (70.1 to 65.3); chasing, near-flat (72.6 to 71.8).

Outcome. Winning innings average 69.8 control, losing 67.1 — real but secondary against the 4.9-point middle-phase gap.

Three of four slices hold. I call this a condition-dependent trend, strongest in Asian conditions and in the setting state.

6. Contrarian: the precedent-table trap

In my 72-match log, the correlation between powerplay run rate and match wins is 0.21. Middle-phase run rate: 0.48. Middle-phase control percentage: 0.53.

The popular line — that the powerplay sets a T20's mood — is weakly supported in my sample. The interval around 0.21 runs from roughly 0.01 to 0.40. That is not a foundation for selection.

Table 7: Precedent map, era-adjusted, with caveats

| Era | Powerplay RR | Control % | Adjusted index | Caveat | |---|---|---|---|---| | 2026–2026 | 6.8 | 72.1 | +0.3 | Small sample; older fielding rules, slow pitches | | 2026–2026 | 7.5 | 70.9 | +0.1 | Mixed conditions | | 2026–2026 | 8.1 | 68.4 | −0.2 | Covid-era scheduling | | 2026–2026 | 8.3 | 67.2 | −0.5 | Pace-friendly pitches; match-state confusion |

Placing 2026's 6.8 beside 2026's 8.3 and declaring progress mistakes two different experiments for one. Fielding restrictions changed after 2026, bat profiles changed, pitch preparation changed, and opposition analysis became an industry. A 4.4-point control loss is not necessarily lost talent; it may be opponents who have found a weakness that has not been answered.

And correlation is not causation here. In my log, in 64 percent of matches where powerplay control fell, middle-phase control fell too. A third variable — opening-pair preparation, pitch reading — is likely driving both.

7. Takeaway: what I will watch in the next ten

One, setting-state control. If it climbs above 69 while run rate holds above 7.5, my reading is wrong, and that is good news.

Two, runs per ball against spin in the powerplay. If a side pushes that above 1.40 without raising control, it is a deliberate strategy, not a weakness.

Three, control in overs 7 to 15, where the 4.9 points actually live.

The question is no longer why the powerplay underperforms. It is why a side that knows its matches turn in overs 7 to 15 does not bank its best planning, its best ball-selection and its best patience for exactly those seven overs.

Method note

All figures come from my own log. Control percentage requires three conditions to be met simultaneously; borderline deliveries are counted as uncontrolled, so the numbers lean conservative. Phase codes, sample sizes, standard deviations and z-scores are archived separately in my logbook for anyone who wants to reproduce the count under the same rules.