Cricket's Invisible Ledger: The Book That Forgets a Bowler's Four Overs

The last ball of the fourth over sailed towards deep midwicket, and the big scoreboard at Mirpur still had the bowler listed at 2.4 overs. That evening my laptop had three things open: the day's scorecard, a fourteen-day bowling log, and a blank spreadsheet. The colleague sitting next to me asked why the boy had been given four overs straight. Nobody had the answer.

The scorecard will tell you how many runs were scored, how many wickets fell, what the economy rate was. The scorecard will not tell you who suffered, who came back on an eight-hour bus the night before, what sits under the tape on whose shoulder. I keep accounts slowly, because without an account a claim turns into a story, and a story has no place left to appeal.

Cricket is called a game of numbers. The reality runs close to the opposite: cricket's account book survives on paper, not in the body.

I came to data analysis from broadcast production, so a scorecard is not just a result to me. It is a ledger. Every ball is an entry, every over a block, every innings an immutable page, dated and open for all to read. That book has run since the nineteenth century, and it is astonishingly good. It records only outcomes. A bowler's over-by-over load, the relationship between a batsman's strike rate and his hamstring, the release letter between a board and a franchise, the contract clause, the image-rights split, none of it lands in any ledger.

I tracked PPDA, xG and distance covered across all 64 matches of the Russia World Cup alone, sitting in a rented room in Mymensingh. That work taught me a grammar. A match is not a list of events but a system, where crowd noise, travel distance, sleep and pressure are all variables. Watching the empty-stadium Bundesliga in 2026 produced this: without spectators, home advantage fell from 0.45 goals per match to 0.22. The environment is itself a variable, and Mirpur is no exception. The roar of five thousand people makes a 19-year-old pacer's hand shake, and that tremor never reaches anyone's spreadsheet.

The problem is less about money than about design.

I built my own phase model, because Dhaka's cricket deserves its own ghosts.

I split every T20 innings into four phases: powerplay (1 to 6), middle (7 to 12), death setup (13 to 16), death (17 to 20). In each phase I measure three things, the dot-ball rate per over, the share of runs arriving from boundaries, and the frequency of bowling changes. What these three produce together cannot be said in the language of a scorecard. A side that keeps its powerplay dot-ball rate under 45 percent does not improve in the 13 to 16 phase; it loses tempo instead, because the set batsman consumes extra deliveries and even with wickets in hand the over loses rhythm. You can touch a run rate; you cannot touch a rhythm.

The model's real gap sits outside the field, though.

A bowler's fourteen-day ball ledger does not begin with twenty-four match deliveries. It begins with the morning warm-up, six overs in the field, a bus seat, an airport wait, and lost sleep. I keep a rolling count: competitive overs in the last fourteen days, plus an estimate for warm-up deliveries. In a domestic season this number spikes in two places, April to May, when first-class and List A cricket run together, and December to January, when the franchise tournament seizes Dhaka's calendar.

A young bowler's body carries an annual budget; nobody in cricket writes that budget down. When the boy walks into a first-class dressing room at eighteen, his bones, shoulder and elbow are unfinished, yet nobody eases his overs, because the team is fighting near the bottom of the table. I call this the untimely account: the bill arrives three years later, the selfie arrives today.

The second blank book is the return timeline.

Board statements carry a phrase, one to two weeks. Commentators say fitness is being monitored. In my own log, for strains and side injuries, players have stayed absent well beyond the announced date, because the return ladder, shuttle runs, net bowling, sprinting, each move at a separate rhythm, and selection pressure enters there. A body does not read a calendar; a body reads the history of load. The bowler pushed into a six-over spell in April has that account settled by his shoulder in February.

The third book is blurrier: the movement of players.

Auctions, retentions, no-objection certificates, permission to move from one league to another, and in recent years the practice of temporary player loans between franchises, all of it lives in scattered emails, PDFs and verbal assurances. Small boards and small franchises are development factories here: they build the player, a bigger league harvests him, and nobody holds a complete record. We discuss the calendars of bowlers like Mustafizur Rahman and Taskin Ahmed, yet nobody can display the full chain of approvals behind them, whose release came when, who agreed to a spell of how many balls, who took on the risk afresh.

This is where the ledger question arrives, and where the common mistake happens.

A ledger is not crypto. A ledger is a book in which every claim carries a time and a signature, and which nobody can quietly alter afterwards. If a bowler's workload record, release dates and contract clauses sat on a shared, verifiable book, then at retention time the player's representative and the franchise could not sit down with two separate truths. A ledger does not raise money; a ledger only says who claimed what, and when.

Cricket has had such a book before. The scorecard is itself an immutable ledger, over after over, innings after innings, impossible to erase. But a scorecard records what a thing produced, not what it cost. The gap in the accounts is not in the event; it is around the event.

Which is exactly where caution is due.

The biggest risk of an immutable book is simple: wrong information becomes permanent. Where field verification is missing, a ledger is not the fix, it is the pretence of a fix. Note down incorrectly that a bowler sent down six overs today and that line circulates for years, and later nobody can erase it. Every cell in my log therefore has a fixed address, verified, partial, estimated, because if it is not written down whether the data grew out of mud, the analysis itself turns into rumour.

The second objection is ethical. A seventeen-year-old's medical file, his shoulder scan, his nerve conduction speed, if all of that lands on a public and immutable book, then in the name of protection we build surveillance. Who owns the information, the board, the club, or the boy himself? Any data initiative that skips these questions stays incomplete.

The third objection is statistical. More workload, more injury, the relationship is easy to see, and easier still to avoid seeing. But correlation and causation are different things, and the more models I run, the more selection bias appears: those who play well get more matches, so they get more records, so they get more injuries. A residual is the story the model did not expect; I read it slowly, and I claim less.

Next round I will watch three things.

First, whether any domestic side publishes its rolling workload numbers; if not, the account is being kept hidden on purpose. Second, the release window: whether a star moved mid-season carries a visible ball ledger behind him. Third, whether my phase model's powerplay dot-ball signal survives the next six matches; if it does not, the credit is not mine, and neither is the correction.

Grassroots football taught me that data grows from mud, not from dashboards. Cricket's data is the same, born on a dressing-room bench in Mirpur, on a bus seat, in a bucket of ice. The ledger is written on paper, but the bill arrives in the bones.