From Body Ledger to Blockchain: Why Cricket's Bowling-Load Data Can No Longer Stay Buried

Title: From Body Ledger to Blockchain: Why Cricket's Bowling-Load Data Can No Longer Stay Buried

Hook

Last week I was watching a match, a scorecard in hand, and my eye snagged on a blank cell. The bowler I was thinking about — how many overs had he actually sent down in the last twelve days? That number was nowhere. The team's medical update read two words: "under observation." Sitting at the ground, this is precisely what I hunt for, because after more than twenty years of watching matches I have learned that the dangerous thing is never a red number but this empty cell. A blank cell says two contradictory things at once — either nobody measured, or somebody measured and buried it. In cricket both are equally damaging, and both lead to the same ending.

Context

The body keeps a load ledger, and that ledger never lies. Every over, every spell, back-to-back matches, long travel, brutal heat, humidity and too little sleep — together they build an invisible balance sheet. We tell ourselves injuries arrive suddenly, but in truth they arrive as the sum of many small debits. In 2026 I was the only woman in the Sylhet press box, and I was routinely told women don't read bowling actions. I stopped arguing and started logging every Mashrafe Mortaza delivery in a paper ledger. By his twenty-fourth over I could see that the landing angle of his front foot had shifted by four degrees. I showed two physios; both shrugged and smiled. Within months his knee cartilage tore and he was out of the side. The data existed all along — it simply wasn't in any shared, verifiable record. That experience taught me two things: explain injuries in plain human language, not press-box shorthand; and trust my own eyes over the room's opinion.

In the Bangladesh context this ledger is even messier. A packed national calendar, domestic leagues, franchise tournaments and travel all press on a fast bowler's body in fragments. The risk runs higher for young bowlers, whose frames are not yet fully built even as they carry the heaviest trust. If workload is not recorded properly at that age, the error compounds year after year.

Core Analysis

This is where we must stop. Cricket's problem is not a shortage of information; it is that the information is not verifiable, and every party can edit its own book. The franchise keeps one file, the national board another, the player's agent a third — none reconcile. The transfer fee is loud; the medical file is quiet. But if this ledger worked like a blockchain — every entry time-stamped, appendable yet unerasable, visible to franchise, board and player alike — the story would read differently.

Picture a single spell. Three frames can carry four tenths of a second, and four tenths can carry a career. First frame: the stride is shortening in the run-up. Second frame: the hip angle at delivery stride is no longer what it was. Third frame: on landing the front foot falls slightly wider, driving force straight into the knee. If those three frames were deposited, week after week, into an immutable ledger, that four-degree shift would stop being one physio's uneasy hunch and become a verifiable warning.

We would also get answers to a different question. How much recovery debt had this bowler accumulated over fourteen days? How often had he played back-to-back, how far had he travelled, how little had he slept? Had this sat in a shared book, the decision to play him three matches running might have changed. Load management would stop being a game of private memory and become numerical duty.

To my mind, every spell, every recovery window, every scan report should be written into an append-only ledger. Three gains follow. First, load management becomes shared fact rather than private guess. Second, no coach or selector can again say, "we didn't know." Third, the player himself owns the history of his own body, because the record sits with him too. That shared book matters most when a small club's talent is sold to a big one — that is exactly the moment the most information is lost, and the player is reduced to an asset, a price.

Contrarian Angle

Here I have to stop myself, because the easiest solution may be the most dangerous. An immutable injury ledger in the wrong hands becomes not a medical tool but a bargaining weapon. If an old knee scan stays visible forever before an auction, a franchise will use it to knock down the price — punishing the player instead of protecting him. Without consent, privacy and a right to expiry, a blockchain solution is not a solution; it is surveillance.

And more data does not automatically mean better decisions. If workload data hardens into fatalism — if a certain number is taken to make injury inevitable — we will stop understanding the player and only stare at the number. Load must be read alongside technique, sleep, travel and injury history. Data is a warning, not a verdict.

One more thing. The cell that was blank in my hands may have been blank because nobody recorded anything — not because nothing happened. That difference is enormous. So I never draw a conclusion from empty data; inventing a story from guesswork is easy, but responsibility means admitting — I do not know. I did not want this column to be right.

Takeaway

A player is not a spreadsheet, but a spreadsheet can miss a player. The oldest data set is the body — and it is being rewritten every day while we forget to read it. The question is no longer whether the data exists; the question is whether we will keep that book in a form where no one can quietly delete an entry.