The Silent Row in the Powerplay: Mapping Bangladesh's T20 Pressure from a Chattogram Ledger

The Silent Row in the Powerplay: Mapping Bangladesh's T20 Pressure from a Chattogram Ledger

A January evening at the Zahur Ahmed Chowdhury Stadium. Rain arrives at 6.2 overs. Match abandoned. The powerplay box on the scorecard holds four digits: 38/3. Which ball was a dot, which one became a free hit, why a spinner came on in the fourth over, when the fielder at fine leg slid across to square leg — none of it survives in that box.

In my ledger it is row 4,271. Since January 2026 this hand-built spreadsheet has accumulated 132 Bangladesh Premier League matches and 1,847 shot-level xG tags. Of those 1,847, on 231 I could never assign a pressure tag, because the field placement for those overs never made it onto the recording. Seventeen percent empty cells. The Chattogram desk taught me that a missing row is a louder story than a headline.

This piece is about those empty cells. Because they are the reason a large part of what we say every year about Bangladesh's T20 powerplay rests on rows nobody ever filled in.

Context: from France's PPDA to cricket's BPF

In 2026, at sixty, I started a bilingual data blog out of Chattogram. In the first year I tagged 132 BPL matches and 1,847 shots by hand. A local betting syndicate rejected my work because I was a woman. I kept the spreadsheet.

At the 2026 World Cup I followed France. In the 4-3 against Argentina, France's PPDA was 15.8 and Argentina's was 8.9. Argentina's three goals came from 0.9 xG in total. That number sits in my notebook in red ink. PPDA has been a fixed column in every match preview I have written since.

PPDA does not transfer directly to cricket, and those who transfer it directly get it wrong. Football pressing is continuous: while the ball is live you can count ninety minutes of opponent passes. Cricket's defensive shape is discrete. Six balls per over. The field is reset between overs. Bowlers have quotas. The pitch degrades.

So I write down the mapped variables separately. For football's passes-allowed-per-defensive-action, cricket gets BPF — Balls Per Forced Error: how many deliveries a bowling side needs to manufacture one beaten edge, mistimed shot or play-and-miss. For football's defensive action, cricket gets the forced false shot. For field tilt, cricket gets the dot-ball cluster.

The disanalogies get written down too, because hiding them makes the rest of the arithmetic worthless. A bowler's four-over quota has no football equivalent. Pitch deterioration is faster and more one-directional than grass wear. And cricket has no recovery phase — a football side whose press breaks can sit deeper, whereas in cricket that option only arrives at the end of the over.

I also pre-register my falsification condition: if across at least three full seasons BPF shows no relationship with powerplay run rate, then BPF is a story, not a signal. Four seasons in, the relationship has held in three. It has failed in one. This article discusses both.

Three columns: chance quality, pressure structure, game state

Since Qatar 2026 I begin every crisis review with three columns — chance quality, pressure structure, game state. In Qatar, Germany had 26 shots, nine on target, 1.95 xG. Japan had 1.36 xG. Japan's two goals came from 0.4 xG. I refused to call it a collapse, because Germany's PPDA of 7.2 had left their transitions open. Outcome and process are separate objects.

Run the same three columns through a T20 powerplay and the picture shifts.

Column one, chance quality. In my ledger, BPL powerplays from 2026 to 2026 average 43.8 runs per six overs, a run rate of 7.3, and 2.1 wickets per powerplay. Read that with the error bar attached: seventeen percent of rows carry no tag, so the margin is roughly four runs. When someone calls to tell me Bangladesh's powerplay has collapsed, I ask which powerplay, on which pitch, in which season.

Column two, pressure structure. This is where the information lives. In powerplays where BPF dropped below 5.5, the fielding side manufactured one extra forced error roughly every two overs. The batting side's run rate in those overs did not always fall — sometimes it rose — but wickets came earlier. Pressure is not fewer balls; pressure is how fast the fielders moved, and which fielder moved. In my ledger, in overs where the third man went up, cover drives fell as a share of the batter's scoring shots while square cuts rose. The outcome was often still a boundary. The process belonged to the bowling side. The scorecard never records that.

Column three, game state. This is my most uncomfortable column. When a side is ahead, the fielding captain attacks less, builds a wide line, sets the field back. So "better BPF in matches won" is frequently reverse causation — your BPF is good because you are winning, as much as the other way round. Fail to flag that trap and every pressure statistic becomes decoration.

The seventh-over cliff

In my ledger, the three overs after the powerplay average a run rate of 6.1, down from 7.3 inside it. The cause is mechanical: spinners arrive, the front-line seamers have burned their first spell, and captains take out slip. For the batting side this is the twelve-ball window where the match is actually decided. Depending on who bats at four and six, that window is worth between eight and fourteen runs a game. We rarely discuss it, because no wicket falls there and no headline is born.

The 900-ball rule

In 2026-21 I learned to respect this same gap from a different direction. Before and after Project Restart I analysed 83 Bundesliga matches; home win rate fell from 43.2 to 33.8 percent. I cut home advantage in my betting model by eighteen percent and tested it across 27 matches. At Euro 2026 I resisted the Pedri hype — 629 minutes, 92 percent pass accuracy, but of ten teenage midfielders since 2026 only three sustained elite output beyond 900 minutes. Pedri himself came good. The rule does not change, because the rule is not about the individual. It is about hurry.

The 900-minute rule is a monastery bell: it calls you back from magical thinking. In cricket I translated it into 900 balls. For a T20 batter that is thirty innings at thirty balls. In Test cricket it is 150 overs, roughly two matches. Until a Bangladesh prospect clears that line, I do not write the word "solution" next to his name, and a strike rate from four overseas league games is not a document to me.

Soumya Sarkar's row

In 2026, while at The Daily Star, I interviewed Soumya Sarkar. Prothom Alo picked the piece up; it was my first verifiable byline. What I wrote that day was a story about talent. Nine years later, when I open his ledger row, something else catches my eye.

His powerplay strike rate in my ledger sits inside an acceptable band. That is not the problem. The problem is his dot-ball share against left-arm spin — the row that, if selection committees actually opened it, would decide whether he faces 35 balls or 18 in the powerplay. In both cases the scorecard might show 28 or 30. Same outcome, entirely different process.

Here I have to argue against myself. This devotion to process can run cold. A bowler dropped because his economy on a 250-ball sample is 0.3 too high has a career, a family, a small town behind him. The number says no, and the number never tells you who pays for the no. I follow the rule. I try to remember who settles the bill.

Germany's 26 shots and cricket's dot-ball cluster

Germany lost in Qatar and I still refused to call it a collapse. Cricket makes the same error when it counts boundaries. One side can hit twelve fours and lose; another hits six and wins. The difference sits in dot-ball clusters. In my ledger, three consecutive dot balls in a powerplay raise the probability of a forced error on the following over by roughly half again. Dots are not separate events. They are a cluster, and the cluster generates its own weight.

Where my own arithmetic contradicts me

The fourth season, the one where BPF and run rate decoupled. There is no relationship there, and I know why. The seventeen percent of empty rows in my sample are not empty at random. The matches lost to rain and recording failure are precisely the weather-affected ones — and rain in Chattogram in January means heavy air, a damp surface, more seam movement. My dataset has quietly trimmed away the seam-friendly pitches. The sample I use to tell powerplay stories is flatter than reality.

That is my second warning, and it matters: the link between powerplay aggression and winning is not causal, or at least not proven causal. Sides that are ahead bowl defensively; sides that attack are usually behind. The arrow points both ways. So when someone tells me an aggressive number four will fix the powerplay, I ask for two seasons of rows. Not before.

What I will watch next round

Wherever the next fixtures land — Karachi, Colombo, or Chattogram again — over the coming three weeks I will track one thing only: the twelve balls after the sixth over. Who is batting, whether slip is still in, and whether the batter is deliberately waiting on the spinner or already reaching for the sweep. The results of those twelve balls will not reach a headline for another four weeks. In my ledger they will already be written. Track the number, not the headline.