The Blank Cell in the Scorecard

The laptop in the scorers' box at Chattogram's Zahur Ahmed Chowdhury Stadium was old and running hot. Beside it lay a handwritten sheet, its corner lifting in the breeze. Down on the field the last session of the day was draining away, the light going soft, the grass still holding the previous night's dew. A left-handed batter at the crease, two men behind the stumps, one at slip. From the back row I could see a column on the screen sitting empty. Runs were being logged, balls were being logged, but the cell beside them — the one that should say what the situation was when those runs arrived — stayed white. I looked at the scorer. He shook his head and said, "I'll fill that in later."

Later never came.

I chased a scorecard and found a poem breathing inside a blank cell. The trouble is that the breath left no record. Next season, when somebody argues about that batter, they will have to trust a memory, or an average that never saw the white cell at all.

I have spent thirteen years moving between grounds in Chattogram and Dhaka. I have listened to the sounds of the field — studs on concrete, a spectator dragging a foot along the boundary rope, the sudden hush that settles over a drinks break. The empty stand taught me that silence can take a wicket without touching the stumps. But I have learned something else I rarely write about: the biggest gap in Bangladesh's domestic cricket is not on the field. It is in the scorers' box.

The structure stands on three levels. The National Cricket League, a first-class competition running since the 2026-2026 season, with eight divisional teams. The Bangladesh Cricket League, launched in 2026-13, another first-class tier built around four zones. And the Dhaka Premier Division Cricket League, a club-based 50-over competition that has been the circulatory system of Dhaka cricket for decades. Above them sits the Bangladesh Premier League, franchise T20 cricket since 2026.

The density of data across those four competitions is wildly uneven. The BPL has ball-by-ball logging, wagon wheels, pitch maps, because a broadcaster is paying for them. International cricket has more. But a four-day NCL or BCL match usually leaves behind a scorecard: who scored how many, who took how many, who bowled how many overs. Which over the ball seamed in, which fielder shifted a step to his right, how low the pitch had become in the third session of day four — none of that is stored anywhere.

India's Ranji Trophy ball-by-ball data lands on the board's website. England's County Championship keeps a record of nearly every delivery, down to a batter's scoring zones. Analysts working on Australia's Sheffield Shield can talk about field placement over by over. Bangladesh has no public record at that level. This is not a hidden conspiracy. It is a question of investment and habit.

That is where the damage starts.

Selection that rests on memory rather than evidence. A selector watches an innings. He remembers the ninety. He does not remember the forty balls before it, when that batter was pushing at spin with a planted front foot because the pitch had begun to turn. When the selection meeting convenes, those forty balls do not exist. Only the ninety exists. A scorecard tells the truth, but not the whole truth. The empty cell was the one that would have said how ready the batter actually was.

The invisible ledger of workload. Consider a seamer like Taskin Ahmed — twenty overs in an NCL innings, another match three days later in the BCL, two one-day games in the Dhaka Premier League in between. If the sum of those overs is not written down somewhere clearly, who says rest is needed? The physio says it from his own notebook. The coach says it from instinct. Nobody says it from a central, public record. Workload management is nothing but data — and without data it becomes guesswork.

Small samples passing themselves off as form. A player scores two hundred across three or four domestic matches and his name suddenly enters the conversation. But against which bowlers, on which pitch, with how old a ball? If there is no way to verify that, the decision rests on the total alone. A total never explains how it was made, and in cricket the how usually matters more than the how many.

The unverified translation between formats. A spinner like Mehidy Hasan Miraz bowls one way in first-class cricket and another way in T20. How much of one transfers to the other becomes visible only when both formats are recorded in the same language. Our domestic structure has not built that language yet.

The lost arithmetic of the age curve. A cricketer's most important information often sits where statistics meet the body — how much slower the first step became at slip after thirty, whether the spinner's speed dropped by two or three kilometres an hour. None of it appears on a scorecard. It lives in video, and turning video into numbers takes time, people and habit.

This gap is not only statistical. It is professional risk. The reporter in a Dhaka newsroom writing up an NCL match usually has a scorecard and little else. So the report takes the shape of '87 to one man, four for 52 to another'. What the match felt like goes unwritten, because there is nothing to write it from. The reader then assumes the match must have been like that. Yet 87 on a fourth-day surface and 87 on a flat first-day pitch are not the same innings at all.

One example stays with me. A few seasons ago a left-arm spinner in Chattogram took wickets across several NCL matches in a row. The number was eye-catching. But nobody recorded what those pitches were doing, how experienced the opposing batters were, or whether his deliveries were being defended or attacked. Two years later, when his name came up in national-team conversation, the only way to check was somebody's memory. Memory sometimes deceives and sometimes rescues. Which one it was here, nobody could say.

If all this sounds like an argument that more data solves everything, one thing gets missed. India's domestic game now has enormous data and no shortage of misreading. A young batter has been promoted to Test cricket on the strength of a Ranji average, only for it to emerge that the average was built on flat pitches against weak attacks. Abundance of information is not quality of information; and an absence of information is sometimes filled with narrative, which is more dangerous still.

The real gap, then, is not volume but a shared grammar. An NCL scorecard becomes useful when anyone opening it can say what the pitch did on day four. Ours tells you who scored what. It does not tell you what the match was. In cricket, what the match was is the actual information.

Cricket already knows how to bind uncertainty into rules. Duckworth-Lewis-Stern reduces a rain-interrupted target to a formula. DRS checks an lbw decision in three stages. Both remain contested and both were adopted, because the alternative was guessing. On domestic data we are still on the guessing side.

I do not cover cricket; I listen for the metaphors hiding between the lines. But a metaphor left unverified becomes decoration. What the blank cell taught me is that the distance between story and proof has to be closed with records, not with feeling. Every incomplete average is a poem unfinished, waiting for a spreadsheet to break its heart.

If ball-by-ball records from every NCL match became public next season, the biggest change would not happen in selection meetings. It would happen in the way fans talk. Nobody could say 'he's doing well in domestic cricket' and stop there. They would have to say 'he's doing well in domestic cricket, but on turning pitches, and the national team needs him on a seaming white ball'. It would sound less pretty. It would also be true.

Will the blank cell ever be filled?