The Ledger's Testimony: The Over Where a Cricket Match Changes Its Mind

The Ledger's Testimony: The Over Where a Cricket Match Changes Its Mind

On 10 September 2026, at the Sher-e-Bangla Stadium in Mirpur, Bangladesh won a T20I series against New Zealand for the first time, 3-2. As dusk fell there were celebrations in the stands, camera flashes, and applause in the dressing room. After the match everyone asked one question — "By how many runs did they win?" Nobody asked, "In which over did the match change its mind?" In my handwritten spiral ledger, that very over had a small star beside it. It was not a run, it was not a wicket; it was time. A T20 result is often decided in the final over, but a match's intention shifts much earlier — in one over, after a drinks break, inside a string of dot balls. The number the scoreboard never prints is often the most honest number of all.

In 2026, at sixty, I left a thirty-one-year sub-editor's desk at a Khulna daily and began hand-coding the Bangladesh Premier League. The television scorecard gives three numbers — runs, wickets, overs. But ninety per cent of what happens in a T20 match never enters those three numbers. Who corrected his footwork on which delivery, which two dot balls preceded a boundary, who feared bowling his slower ball in the death overs — none of that lives in a broadcast graphic. So I began re-watching streams at two in the morning and writing it all down, with dates, with sources, correcting every entry by hand.

For me the ledger's job is to store facts; its larger job is to carry responsibility. I began with a hand-coded book, and the numbers slowly learned to confess their own errors — where my eye was biased, where I hurried. A number becomes trustworthy only when it carries a timestamp, a context, and a way for anyone to check it. Here the economics of cricket data and the idea of a public ledger converge — immutability, transparent timestamps, entries anyone can verify. Cricket is now experimenting with fan tokens, NFT memorabilia and blockchain-based scorecards. But technology does not create truth; it makes truth permanent. Before you make it permanent, a human must decide where the truth lies.

I code a T20 innings at three layers. For a new reader, in one line: I watch three things — pressure, intention and windows. For the experienced reader: each of those three breaks into sub-indices, and every sub-index carries a timestamp.

Layer one — dot-ball pressure. In football, PPDA measures how hard a side presses against the opponent's passes. In cricket I build something close to it: how many "inactive balls" a batting side plays per over — balls that produced no run, no boundary, and no wicket. When that number climbs steadily, the innings is walking a rope; a little pressure will snap it. One caution, though: this index lies when read without pitch and ground dimensions. Six dots on a slow Dhaka surface and six dots on a flat Bengaluru wicket are not the same thing.

Layer two — the over of intent. In every innings I hunt for the one over where a side's method of scoring changes, not merely its speed. Suppose a team is going at 1.1 runs per ball for six overs, but in the seventh the strike rotation suddenly rises, the non-striker starts releasing the ball, and singles are run hard. Nothing big has happened on the scoreboard, yet the story inside the match has changed. The sixtieth-minute line is not a statistic; it is the point where a match changes its mind. In T20, by my reckoning that line usually falls between the twelfth and fifteenth overs; in the four-over death block it sits just before the seventeenth.

Layer three — the boundary-window map. I look at which two- or three-over window produced a side's most boundaries, and who created that window — the batter's placement or the bowler's error? This is where most analysis stops, because television shows "how many fours and sixes", not "in which over". Yet recognising the window changes the decision to switch bowlers.

Here is an example I keep in my own ledger. In a domestic T20, a side was chasing 165. In the first ten overs they made 71, but across four overs they had strung together five straight dots — the score was moving, but the innings' pulse was weak. In the twelfth over the bowling side brought on a spinner, and in that single over the batting side's strike rotation jumped from 0.4 to 0.7. The result? Forty-nine runs in the last four overs. The match turned in the eighteenth over — but the seed of the turn was sown in the twelfth. In my ledger I wrote the result beside over eighteen and the cause beside over twelve. Writing down the cause — that is the real work. Broadcast shows us results; the ledger shows us causes. And if the causes are written with timestamps and sources, they stop being opinion and become testimony.

One more thing I code — the spell after a wicket. When a wicket falls, the mindset of both the bowling and batting sides changes; the next two overs are often the match's most opaque chapter. In the same way, rain breaks and empty stands also get entries in my ledger. Silence has a grammar, and empty stadiums taught me to parse it — which dot ball is fatigue and which is calculation.

Another observation, tied to a rule change. In football the five-substitute rule is a boon for deep squads, but it also lets big clubs turn the final twenty minutes into a war of attrition. Cricket's Impact Player rule is much the same — an extra batter or an extra bowler makes a deep side deeper and a thin side more helpless. The ledger shows it plainly: the more Impact Players have been used in the last four overs of a second innings, the more the game has leaned on end-of-match specialists. The rule is not bad; but the rule is not equal.

Another opaque corner — injury. Boards and franchises disclose only the injuries that suit their commercial interest or image; the rest stays behind the medical-room door. From my years of watching matches I can say that when a bowler abruptly shortens a spell, it is often not planning but pain. The scoreboard will not admit it, and neither will the release. The ledger is helpless here — it can record symptoms, not the disease.

I also have an old habit around BPL auction prices. After a price is announced, I open the ledger and check how many balls that player bowled in the death overs across the last three seasons, how many dots he delivered, how often he was out to an inactive ball. A transfer fee is a rumour until the ledger teaches it to breathe. The auction price and the ledger's price are often not the same — and that gap is my subject.

Now the thing everyone in the data festival avoids: correlation is not causation. A side scored more, therefore it played better — that is not always true. Just as football markets distance covered and high-intensity sprints as proof of effort, when pointless running also produces pretty numbers, cricket likewise lets total runs and strike rate become numbers of self-praise. Lifting a strike rate to 130 by hitting sixes in the last two overs is easy once the match is already lost. The flood of blockchain and fan tokens carries the same trap. A number is not true merely because it is written on-chain; bad data stays bad immutably. Immutability has value — but only when the coding method is transparent and unbiased. Otherwise we are simply making our errors permanent and selling them to the market under the name of transparency.

At the bottom of every report I file there is a small line — what I missed. Because once I was wrong: before play I predicted an over-window, got the window right, but got the sequence wrong. I printed that error myself, before anyone asked. That is the true worth of a hand-coded ledger — it teaches you accountability, including to yourself.

So for the next round I would ask you to watch one thing: not the score, but when the innings' intention changed — in which over, at whose hand. A side that recognises this moment early can change its bowling, bring up the field, break a string of dot balls. A side that only reads results discovers in the final over that the match changed its mind long ago. At sixty-nine I trust slow numbers more than loud ones. The question is not who won; the question is in which over the match decided to win.