The Ledger of Rest: What the Scorecard Never Writes Down

Three matches. Eleven days. One number: twenty-seven.

Last February, at two in the morning in a Liverpool flat, two things lay open on my desk. On the left, a notebook: over-by-over logs, when each spell started, when it ended, who bowled which over. On the right, a spreadsheet: the same information arranged in rows, with rest days, travel days, format and venue sitting alongside. In the middle phase of the innings, the window between overs twenty and thirty-five, a side's frontline seamers bowled twenty-seven overs in the first match, nineteen in the second, fourteen in the third.

The scorecard called it a batting failure. The spreadsheet called it the calendar.

I charted forty-six matches by hand before I trusted the model. In August 2026, aged eighteen, I bought a nine-pound notebook and logged every shot Tranmere Rovers took and faced — distance, angle, body part, defensive pressure. Twelve hundred and fourteen shots. Nobody paid me. I did it because the club's run was being explained with a single word: momentum. My sheet said the real driver was shot quality.

That habit is now my only tool in cricket. Where a hundred thousand people watch every ball, I count the days behind the ball.

The schedule nobody reads

Cricket's regular season is no longer the story of one league. It is a chain of windows. The Indian Premier League launched in 2026, the Big Bash League in 2026, the Bangladesh Premier League in 2026, the Pakistan Super League in 2026; 2026 added SA20, ILT20 and Major League Cricket. Beside them sits the ICC Future Tours Programme, which carves out its own bilateral windows.

The viewer sees eleven players. The administrator sees an availability ledger. That is my day job: as a Transfer Market Administrator, my screen holds rows of cells — no-objection certificates, rest windows, insurance, match fees, restriction dates. A transfer is not a rumour; it is a row of cells awaiting confirmation.

Test cricket's arithmetic is simple. Five days, ninety overs a day: a maximum of four hundred and fifty overs. One day washed out takes it to three hundred and sixty. A one-day international is a hundred overs, a T20 forty. How full those containers get is decided by the over rate. And the over rate is decided by rest — who got how much.

Four hundred and fifty overs against three hundred and sixty. A match is sometimes written by that single gap, and the points table has no column for it.

One thing needs saying here, because without it the rest of the accounting makes no sense. I was born in Bangladesh and I work in Britain. The two places keep different books. English county cricket has ball-tracking, load monitors and physio databases: years of auditable records. The subcontinental pipeline was built on hand-written scorebooks, age-group tournaments and tape-ball streets. That is not a deficit story, it is a different ledger. One has sensors, the other has memory. Both produce players; only one produces the audits a franchise can actually buy. My hand-charted notebook is therefore never a substitute for a sensor. It is the audit I can carry myself.

The middle-phase spell: birth of a metric

I call the metric middle-phase spell length: how many consecutive overs a bowler delivers inside the twenty-to-thirty-five window, and how many days of rest preceded it. There is no imaginary model here. It can be counted straight off an over-by-over log, with a pen.

Three things keep returning in my logs.

First, spells shorten fastest in the middle phase, and they shorten for want of rest, not for want of ability. Twenty-seven, then nineteen, then fourteen across three consecutive matches. A single match where a seamer bowls fourteen overs looks like a plan. Across three matches, 27-19-14 stops being captaincy and becomes arithmetic — not of tactics, but of scheduling.

Second, the over rate is a hidden tax. In a six-hour day, a side bowling twelve overs an hour delivers seventy-two overs instead of ninety. Eighteen overs are taken away from the batting side, and eighteen overs of extra load land on the bowling unit — usually on the fourth or fifth bowler. On the scorecard it shows up as a slow over rate and a fine. In my notebook it shows up as next match's spell length.

Third, and least comfortable: a franchise buys a bowler by overs, not by wickets. Wickets are the headline; overs are the invoice. In my combined workbook, the price of a frontline seamer tracks the number of middle-phase overs he bowls more closely than it tracks his wicket count. A side does not pay a premium for two wickets in four overs. It pays for the bowler who can lock a batting side down across a seven-over third spell.

To see why that matters, you have to look inside the sessions. A Test day runs in three sessions of roughly thirty overs, split by lunch and tea. When a session stretches, the work has to be shared. A side without four fit seamers cannot share it; it simply stretches the ones it has. In my logs, the average seamer's spell in the last ten overs of the second session runs one to two overs longer than in the first session — and that is precisely the ten-over block where the scoring rate climbs fastest.

This is where the ledger question arrives. At the administrative level — player registration, no-objection certificates, contracts, payments — cricket is discussing immutable ledgers and blockchain-style systems. The argument is clean: once written, nobody can go back and change it. Auditability rises, fraud falls.

On paper, the argument is elegant. A ledger does not tell the truth; a scorer does. An immutable ledger built on an unverified input is simply a faster rumour — except this time the rumour cannot be deleted. I see it daily in my own work: once a row is confirmed, it stops being an estimate. But before it is confirmed, whoever typed it is the only source of error. The technology merely makes the error permanent.

Where I testify against myself

The spreadsheet did not lie; it waited for me to catch up. But waiting does not license me to conclude whatever I like.

The weakest part of my rest-related observation is sample size. What I chart by hand is one slice of one season — a league, a handful of teams, certain venues. At that size I can show a tendency, not prove a cause. And the gap between tendency and cause is the largest trap in my trade.

The alternative explanations sit inside my own workbook. Sides with fewer rest days are often touring sides — playing in unfamiliar conditions, at hostile venues. The reverse also holds: a side with more rest sometimes loses rhythm, especially in T20, where rhythm is a measurable force. In 2026 I hand-coded all eighty-one Bundesliga matches played after the Covid restart. With empty stands, the home win rate fell from 43.3 per cent to 33.3 per cent. A small sample, a modest effect. I did not tweet it; I wrote it as a dissertation chapter — because the smaller the effect size, the more verification it demands. The same rule applies to cricket's rest data.

The second trap belongs to ledger enthusiasts. Immutability is not accuracy. Anyone who believes that moving registration data onto a blockchain will improve squad selection is making the exact mistake they criticise in model worshippers: trusting the output without auditing the input. Auditing means counting by hand. It means reconciling two sources. It means admitting a number went missing, and writing that down too.

The third trap belongs to my own identity. Writing about subcontinental cricket from Europe, the easiest thing in the world is to list deficits — fewer analysts, fewer load monitors, fewer grounds. I recognise that lens because it sits inside me as well. But the accounting can be read from the other side. Systems working with fewer resources often build something more durable: bowling-load management that is a coach's memory plus a diary rather than a physio database; tracking that is an age-group fixture list rather than a GPS vest. A different ledger with a different accounting method. Treating the two as rungs on one ladder means losing half the story inside the data.

What I am waiting to see next round

The satellite-franchise system lets large clubs and boards bypass homegrown quotas; the prodigy of a small league becomes a rented asset. Inside that structure, the gap between a bowler's body and his own team's needs will widen — a gap invisible in the regular season until it appears as a hamstring.

So next block I will count three things. One, middle-phase spell length in the second innings of back-to-back fixtures. Two, over rate in the third session — and that side's fielding setup in the match after. Three, the distance between rest days and travel days, which nobody has yet put in a table.

What the scorecard will not write down, I am writing down. The question now is this: if rest is the real currency of the regular season, then whose account is the points table really keeping — the scorer's, or the scheduler's?