Hook

Fifteen overs gone, South Africa were 147 for 4. A target of 177, thirty needed off thirty balls, Heinrich Klaasen and David Miller at the crease. June 29, 2026, Kensington Oval, Bridgetown. Over the next five overs South Africa made 22 and lost four wickets; India won by seven runs and lifted the ICC Men's T20 World Cup after seventeen years (Source: ICC match report, June 29, 2026). What everyone talked about afterwards was Jasprit Bumrah's yorkers, Hardik Pandya's slower cutter and Arshdeep Singh's nineteenth over. That is what the commentary box does, because the highlight reel only ever shows the last five overs. My dashboard lit a lamp in a different window: overs 7 to 15, where the camera almost never turns. That is exactly the gap where I start every squad audit for the 2026 T20 World Cup. I found the replacement gap where the highlight reel never looked.

Context: the template comes before the opinion

As scheduled, the 2026 ICC Men's T20 World Cup runs in India and Sri Lanka from February 7 to March 8, 2026. Twenty teams, fifty-five matches, three different venue environments: the dry, spin-friendly surfaces of the subcontinent; Sri Lanka's slower, lower-bounce conditions; and the travel rhythm between the two countries. The biggest enemy of this format is sample size. A team plays three group games; a batter's six innings means 90 to 120 balls. In that sample, the word form is mostly noise.

The template I have built since 2026 — the one that became a twelve-page report from a desk in Brisbane in 2026 — has five layers. Fixture context: where, when, what temperature, what humidity, how many days of rest. Selection baseline: who plays, who is left out, and why. Replacement-level benchmark: what the incoming player actually delivers in that specific phase. Fatigue load: travel, time zones, back-to-back series. And finally an exception column, where I write down the conditions under which my own model could be wrong.

Cricket has no xG the way football does. So I built four proxy variables. The Powerplay Dot-Ball Pressure Index (PDI) measures how many dot balls a side faces and forces in the first six overs. Second-Change Overs Economy (SCE) measures the quality of bowling changes between overs 7 and 15. Keeping Save Value (KSV) measures the quiet contribution of byes, stumpings, dives and review decisions. Boundary-Saving Fielding Value (BSF) measures runs saved in the deep cover and third man. Each comes with a confidence interval. If the sample is small, I widen the interval; if the edge is small, I pass. Nobody gets called an upgrade before 900 balls or 900 minutes of data. I wrote that rule down in 2026 and have not broken it once.

I audit the inputs before I trust the number. The figure you see on television is usually the result of a decision, not a description of a process.

Core: the five layers of the replacement gap

In the 2026 edition I watched several matches from beside the scorer's desk, and one thing kept surfacing. The crowd looks at a batter when the ball hits the boundary; in my notebook the four dot balls before it sit on a separate line. A twenty-team tournament means every squad carries at least two players who do not play regularly for a major side. The difference between those two players is what decides knockout matches.

Powerplay dot balls

In my database, the sides that reached the 2026 knockout stage averaged a powerplay dot-ball percentage below 42; the sides eliminated in the group stage averaged above 49. A seven-point gap means roughly four extra dot balls per powerplay. Four dot balls in six overs is not simply four runs lost — the real cost is downstream. Batting under that pressure forces a player to shelve his scoring shot, and in overs 7 to 15 that breaks strike rotation. On Sri Lankan surfaces, where the new ball moves little but the midday heat strips the ball of its grip, those four dot balls cost even more. Watching PDI across the first two group games tells you which side is surviving purely on sixes.

Second-change overs, 7 to 15

This is my real mine. About 35 percent of a T20 innings happens in this window, yet the highlight reel gives it almost no space. Two kinds of teams appear here. One rotates two spinners through overs 7 to 15 and keeps the scoring rate under 7.2. The other alternates pace and spin almost every over and leaks above 8.6. The difference is 1.4 runs per over, roughly eleven runs across eight overs — a knockout margin.

For India this phase belongs less to Bumrah than to the two spinners. In the 2026 edition India's spin pair produced one of the tournament's three best middle-overs economies. The batting question is harder. Who bats at number five changes almost every edition, and every edition the decision is made after the second group game. My index shows that sides using three different batters at number five in this phase regularly lost 0.4 runs per over there. Role stability, not form, is the dominant variable.

Quiet keeping

When I write about Bangladesh cricket, one regret follows me every time. The wicketkeeper and the lower-order batter barely register in our coverage. Liton Das's one-day form has generated a fraction of the writing that his stumping speed or his saving of byes against leg-spin deserves. KSV is the widest gap in my index.

This variable matters most in Sri Lankan conditions, because the ball turns low and the keeper has to stand very close. One bye does not lose a match, but three byes an innings means the pressure of an extra boundary at the death. A wasted review returns in the final over.

Runs saved beside the boundary

I have an old habit of sitting down with a fielding map. Subcontinental grounds have short boundaries, so runs saved at deep cover and third man are a large number in the equation. In the group stage this value is almost invisible; by the Super Eight a single dive changes a final's path. Across BSF, a three-to-five-run swing per match is routine. Five runs is the price of one delivery in the last over.

Accounting for fatigue

Here comes the Fatigue Forecaster. The structural problem for 2026 is the calendar. The Big Bash League runs into January, ILT20 begins in January, and SA20 finishes mid-January. Many international players will walk out of a franchise league straight into a World Cup on February 7, sometimes with less than a week of rest. That is not a guess; it is the shape of the calendar.

I attach a Rotation Risk Score (RRS) here, built on three inputs: balls bowled in the last four weeks, total hours of intercontinental travel, and number of time-zone shifts. The Bangladesh-to-Australia rhythm is familiar to me — Dhaka to Brisbane is roughly fourteen hours in the air plus a four-hour time difference. The route from Asia through Europe to the Caribbean is crueller.

One warning I write for myself. Fatigue explains away a poor performance too easily, and that is the trap. In my template, fatigue is always the last column, never the first. I check execution, whether the track changed, whether shot selection failed. Then I weight fatigue. Otherwise the analysis stops being statistics and becomes an excuse.

| Phase | Metric | Input | Why 2026 differs | |---|---|---|---| | Overs 1–6 | PDI | Dot balls, boundary rate | Low bounce with the new ball in Sri Lanka | | Overs 7–15 | SCE | Spin overs, run rate | Midday heat strips the ball | | Keeping | KSV | Stumpings, byes, reviews | Standing close to low turn | | Fielding | BSF | Deep cover, third man | Short boundaries | | Off-field | RRS | Balls, travel, time zones | January franchise league clash |

Contrarian: empty stadiums, cheap proverb

The United States leg of the 2026 edition was a gift. At Nassau County, several matches drew nearly empty stands, the pitch behaved unpredictably, and both sides were equally uncomfortable. That leg gave me a natural experiment to reprice home advantage. The 2026 IPL in the UAE, played in empty stadiums, offered the same opportunity.

What keeps emerging is that home advantage is not one number but the sum of four things: familiarity with the pitch, the absence of travel, scheduling convenience, and the crowd. The crowd is the lightest component yet commands the heaviest market weight. The idea that home advantage in the IPL is purely a crowd effect collapses quickly, because home sides retained their pitch familiarity even in empty stadiums. Correlation and causation walk hand in hand here, and that is the most dangerous pairing.

In 2026 India play at home, and the market has already priced that in. My model suggests part of India's home advantage fades at Sri Lankan venues, because those conditions are not equally new to both hosts. On travel load, every side is nearly equal in the Sri Lanka leg, so the difference will be built on pitch familiarity, not on the crowd.

Takeaway

In the first week I will watch three things. First, every side's PDI across the opening two group games — not the six-hitting reel. Second, how many batters rotate through numbers five and six, because role churn drags the run rate down. Third, the RRS of players arriving directly from January franchise leagues, especially those who bowl with the new ball. The market moves first; my job is to know whether it moved for information or for noise. The question is not who wins. The question is which number you have not looked at yet.