Khulna's Unwritten Scorecard: Why Domestic Cricket Needs an Open Ledger

Last November, a first-class National Cricket League match was underway at the Sheikh Abu Naser Stadium in Khulna. In the second innings a left-arm spinner took seven wickets, and in my hand-coded log it was the only seven-wicket innings that week. At nine that night I opened the online scorecard. Overs were listed, maidens were listed, runs were listed. But there was no account of the four wickets that fell after the 31st over, no over number matched to any batter's name. By the next morning the gap had been filled, three new rows appended, one row quietly altered. Nobody claimed anything had broken. The match had no broadcast, no ball-tracking, only a scorer and a notebook. So the question was not simple: between what happened on the field and what is written on the website, I had no independent way to prove which was true.

Asia's cricket data economy has never been equal. Almost every Ranji Trophy match in India is broadcast, every ball enters a live log, and selection indices for age-group cricket are built on that log. Pakistan's Quaid-e-Azam Trophy and Sri Lanka's domestic first-class tournaments are partially archived. Bangladesh's National Cricket League has carried first-class status since the 2026-01 season, yet the ball-by-ball record of a large part of it has never been centrally deposited. What exists lives in a few club notebooks and a few scorers' personal files. The 2026 Asia Cup was held in Pakistan and Sri Lanka; India beat Sri Lanka by ten wickets in the final, and every ball of that tournament sits in a database. That same year in Khulna, three young spinners bowled more than forty first-class overs each, and to find out what actually happened after the 23rd over of one of them I needed the phone numbers of three different scorers.

That asymmetry is not merely a reporting inconvenience. The selection window is narrow, and the ticket into it is a number. A bowler whose overs cannot be counted has a workload that cannot be measured; a workload that cannot be measured cannot generate a rest question. So the story of a young player's body being spent is always written afterwards — when the knee gives way, and we go looking for the overs and discover the past was never written down.

I have been sitting in these domestic grounds since the late nineties, and over the past two years I have hand-coded the ball-by-ball log of 94 first-class matches — more than 28,000 events. One pattern returns again and again out of that log, invisible if you read only the wickets column. Spinners under the age of 23 who averaged 17.2 overs per innings across their first four matches of a season, and then bowled more than 22 overs per innings across the next six, lost roughly twice as many matches to injury the following season as those who did not. The sample is small — 31 bowlers in total — so I am not claiming causation, only correlation. But the correlation is the political part, because a full workload record existed on paper for only nine of those 31. For the other 22 I stitched the data together from three notebooks, two newspaper reports and one scorer's memory.

What emerges is a measurement artifact. We say Bangladesh does not produce fast bowlers and has always produced spinners. Yet the foundation under that claim is itself incomplete: home pitches built for spin, a compressed season, and uncounted overs. Together those three things manufacture a reality in which a spinner gets more opportunity to succeed and less accounting of what it costs him. The way a heatmap conceals a player's actual role inside a system, variation in conditions conceals a generation's actual capacity. The numbers were not lying; they were waiting for a better question.

The question is who writes the record, and whether anyone can change it after it is written. Four years ago I coded 1,240 goals from qualifiers and club football across four continents and published one claim in Expected Noise: 43 percent of knockout-stage goals would come from dead balls. The tournament delivered 73 set-piece goals from 169 — 43.2 percent. My format carried a falsification line, so anyone could check it. In cricket we have never drawn that line, because cricket lacks a clean qualifier-stage dataset.

So the idea is now plain: if a domestic scorecard sits in an open ledger, where the end of every innings produces a small cryptographic hash, the scorer signs it with their own key, and the record cannot be deleted but only appended — then the question of swapping the scorer disappears. I call it the Unwatched Archive. The first-year cost is modest: 34 venues, 34 tablets, 34 scorers, one signature per innings. By the second year the overs-load index falls out of the ledger by itself, and a young bowler's 23rd over becomes a piece of information no one can quietly edit. I do not chase the current; I build a monastery beside it.

The danger in that recommendation deserves equal clarity. A ledger does not make information complete, and complete information does not make decisions correct. A ledger cannot see the session washed out by rain, cannot see the bowler who was never selected, cannot see the innings that ended before it could be scored. Correlation is never causation — behind rising injuries among under-23 bowlers there may be winter fitness preparation, or a loan-with-obligation contract in which a small club is structurally condemned to finish half-made players for a giant. But a fact that is unwritten is still a fact; in Khulna I learned that silence is also a dataset.

My target next round is specific: the economy of the Khulna Division left-arm spinner between the 11th and 20th over of an innings, and how many consecutive matches he can hold that window. If the window survives more than three matches, the overs-load accounting has to be rewritten. If it does not, we need an open ledger — not only for him, but for the 22 whose records do not exist anywhere today.