From Khulna Notebook to ODI Ledger: Format Policy and the Arithmetic of Workload

I learned to count sessions on the Khulna maidan, and the rule that came with it: no claim without at least 270 minutes of tape. In 2026 I logged 47 training sessions and 312 set-piece repetitions in the District League. In 2026 in Qatar, 23 sessions and 7 matches. The numbers accumulate in the notebook, but the question that accumulates fastest is about format: what logic is ODI cricket actually running on now?

Start with the obvious. ODI arithmetic cannot be measured with Test arithmetic, nor with T20 arithmetic. In Tests, time is cheap and wickets are expensive. In T20, wickets are cheap and balls are expensive. ODI sits in the middle, and you have to run two innings' worth of accounting across 50 overs at once. That is why the first variable in any ODI analysis is the format tag. Without it, no conclusion holds, because dragging data across formats turns an error into a systemic one.

Look at the last three matches in the notebook. Run rate climbs in the six-over powerplay, but boundaries thin out through the middle overs. That is not new, but the number says something else: fewer runs conceded in the middle, and fewer wickets falling too. Batters are not taking risk, and bowlers are not building pressure. When both happen together, the tempo of the match stops living in the batter's hands and moves to the scoreboard's. What happens in the last ten overs is then not the product of a plan, but of an obligation.

Here is my central observation. The most neglected number in ODI cricket is the over count: who bowled how many, who got how many rest days, who spent how many days away from family. Reading a fixture list means reading a bill. Paid in knees, in rest days, in sleep. I ask about recovery days before I ask about tactics, because tactics can be changed and knees cannot.

Take a three-match series with four-day gaps. A pacer bowls 10-10-10 overs across three matches: 30 overs, roughly 180 balls, in seven days. That number does not appear on the scorecard, but it appears in his economy rate next series. That is what a dense ODI calendar means: load accumulating in a bowler's body, invisible in one match, visible across five.

I count set-piece repetitions because set-pieces are the cheapest runs in ODI cricket. Runs from dead balls mean the scoreboard moves before the field is set. Watching Morocco's low block in Qatar taught me that 4-1-4-1 is not just a number; it is a contract of patience. Sofyan Amrabat's 48 tackles accumulated across seven matches because the system permitted him to run. In ODI cricket, the middle-overs spinner occupies exactly that role: she does not tackle, she accumulates pressure.

The three-match threshold is a hard rule for me. I do not write off group-stage hype. My 4,000-word Morocco piece came three matches in, after confirming training intensity with two kitmen and a physio. In ODI cricket that rule needs to be stricter, because the format is itself slow: three matches make a pattern, one match makes an incident.

Now the part where outside readings usually go wrong. ODI scoring rates are rising, so many conclude the format is drifting toward T20. My notebook does not say that. What changed is the accounting of the powerplay: teams now treat the first ten overs as a separate innings. That attacking edge softens through the middle because losing wickets leaves no hands for the last ten. The format has not changed; the budget inside the format has changed: how many runs, how many wickets, how many overs, spent in which phase.

The second misreading is of the data itself. Live data now flows to betting companies, and that is where the fastest "analytics" come from. It is the darkest side of the game's datafication. The number that tells me a bowler's workload in my notebook becomes a market somewhere else. Same data, two different purposes. I keep my accounting for the field, not for the scoreboard.

The third error is structural. When the ODI calendar is debated, blame usually lands on one coach or one captain. In my notebook, blame belongs to no one and the arithmetic belongs to everyone. How many matches the board scheduled, how many slots the broadcaster wanted, how far the venue is: those three numbers together produce a pacer's seven-day load. This is not a story about individuals. It is a story about a system.

Spectators in the back tier, empty stands, neutral venues: I write these, but never with sentiment. An empty stand means ticket price, travel cost, board allocation, kick-off hour. In Qatar, when nobody's flag was flying, the question was what a ticket cost and who could afford it. Not beauty. Accounting.

Writing about Khulna invites sentiment. I do not go there. Khulna is a source for me, not a symbol. I quote the coaches, cite the facilities, show the pipeline numbers. The maidan will argue for itself; it does not need my lyricism.

So what is the forward signal? The more matches added to the ODI calendar, the more rotation matters: who is rested, who is not. Over the next three matches I will watch two things: who bowls the first spin over after the powerplay, and who covers a pacer who has played two straight matches. Read those two data points together and you can tell whether a team is thinking of the series as a format, or match by match.

Notebook open. Counting.