The Price of an Empty Cell: Auditing Integrity in Cricket Data

Last Friday, at twenty minutes to midnight, I opened a file on my laptop. The match was over, the scorecard was intact — but the analysis sheet that reached me had every cell empty. No player names, no format, no venue, not a single number. Yet at that exact hour the cricket groups had already filled in the explanations: who lost his head, who could not absorb the pressure, whose intent was wrong. Nobody was asking where the numbers had gone.

I have held scorecards in my hands for more than forty years. To me that empty cell is the loudest signal in the room. A blank data cell is not a neutral event; it is a market, and that market is priced by whoever speaks first. What happened on Friday night was not a cricket event. It was a connectivity event.

Bangladeshi cricket writing has spent the last five years learning a language that is not the scorecard's — it is data's. Strike rate, economy, matchup, phase splits, expected runs. These words are now standard property in the press box, and that is an improvement. My own column is built on them. After Germany's group-stage exit in 2026 I threw away the word shock and wrote that it was the depreciation of a closed economy — an average starting XI age of 27.6, stale Bundesliga minutes. Editors have been asking me for numbers ever since.

That entire scaffolding, though, rests on a chain: source → extraction → classification → analysis. Source means the match, the scorecard, the file, the report. Extraction means pulling information points out of it. Classification means deciding whether this is Test analysis, ODI analysis, or a live blog. Analysis is the last step. If any one link cracks, what emerges at the end is not cricket. It is guesswork.

Bangladesh does not lack data supply. It lacks verification. Almost every Dhaka Premier League match produces a scorecard, age-group games sit on YouTube, the BPL has built separate datasets for six franchises. The raw material is abundant. Verified analysis from that raw material is scarce, because nobody invests in the extraction and classification stages.

An empty cell means nothing is there — that is the easiest reading, and the wrongest. In my experience a blank return has four ordinary causes. One, the source sat behind a paywall, so the whole text could not be pulled. Two, an encoding or parsing fault — scrapers stumble on Bengali conjuncts and mixed fonts. Three, misclassification: a live-update stream got tagged as analysis when no analysis existed in it. Four, the source was never analysis at all — a photo gallery, a video caption.

There is always a cause behind an empty cell, and naming that cause is the actual report. If we sit down to write an explanation without identifying the cause, we are covering a data gap with opinion. This is not a new disease in cricket journalism. It is an old disease in new packaging. The gap used to be filled with lines like it just was not his day. Now it is filled with lines like his expected strike rate was low. Both do the same work: they dodge the obligation to verify.

My second objection concerns heatmaps, and I have been writing it for years. A heatmap shows where a fielder stood. It does not show where he was told to stand. A seamer's economy tells you how many runs he conceded. It does not tell you whether the ball was gripping on a low, slow Mirpur surface or whether dew was sitting on a flat Chattogram deck. A number without conditions is not analysis. It is decoration.

I learned that in 2026, in the empty stadiums. Comparing home win rates across Europe's top five leagues before and after lockdown, I wrote that Anfield's twelfth man was worth 0.4 goals a game. The figure was striking, but it only means something once I say which league, which window, which spectator policy. Stripped of conditions, that 0.4 is a fashion.

Cricket offers a plain example in the powerplay opener. His strike rate in the first six overs is 140; in the death overs it is 180. Held together, the two numbers make a story. Separated, they make a lie. Present only the death-overs figure and you have manufactured a finisher. Present only the powerplay figure and you have branded him slow. Same cricketer, two valuations — the difference is not in the player, it is in the phase.

In 2026, when Italy went thirty-four matches unbeaten, I wrote about Jorginho, Verratti and Barella — not catenaccio, but the first algorithmically balanced midfield. That was a testable claim, because each man's passing and press-resistance numbers could be checked against the conditions on the pitch. That is the distance between a verifiable claim and a handsome sentence.

The third thread is my oldest interest: inheritance. Once a wrong number is printed it stops being a number and becomes a debt, and that debt compounds. The first writer did not check the source. The second writer quoted the first, so no check was needed. The third quoted both, so the matter is now established. In three years an estimate becomes a fact, and nobody has opened the original scorecard once.

I have walked into that trap myself. Some years ago I built an entire column on a strike rate; it later turned out to be the player's figure in another format. No reader caught it, because the number looked credible. That is the danger — bad data never has to look bad, it only has to look precise.

In cricket this debt takes a specific shape: generational valuation. Announce a young batter as the next big name on the strength of three innings, and for the next three years he carries the weight of that announcement. What sits on his shoulders is not expectation. It is the depreciation of a mispriced asset. Nobody in Bangladeshi cricket keeps that depreciation schedule, and yet the pitch charges him for it every single day.

The BPL is the cleanest current example. Six teams, more than forty matches a year, ball-by-ball data. The conversation still sits at the level of who is a finisher and who is not. The reason is simple: turning league data into a decision requires separating phase, venue, and bowling matchup. Nobody does that work, because it is slow and it does not start an argument. Verified information is quiet, unexciting, and rarely shared.

So what should a post-match piece contain? By my count, three things. One verified number, its conditions, and a mechanism — why it happened. A piece without a number is emotion; a number without conditions is ornament; analysis without a mechanism is accusation. Friday's coverage had none of the three. It went out fast, readers took it, the argument built. Three months from now nobody can make a single decision from it, because it contains no testable claim.

Information gain means the reader now knows something they did not know before — and it can be checked. That is the 2026 reader's standard. Readers recognise numbers now, they recognise sourcing, and they get suspicious when the sourcing is missing.

Now I argue against myself. This audit of mine may be unfair.

For one, an empty data field is not automatically a conspiracy. Often the source really was empty — a photo gallery, a caption, a press notice. I go hunting for a pipeline fault where nothing ever existed. For another, the crowd's explanation is not always wrong. The press box's reason — the dropped catch, the pressure of the over — is frequently correct, and my chase after numbers just burns time. And verification can be a luxury. A freelancer who does not file by midnight has no work next month. He has no time to check sources because he has no time at all.

The strongest objection is against myself. Numbers can hide my weaknesses. A fifty-seven-year-old numerate columnist hunched behind a scorecard may not be watching the cricket in front of him. I know that trap because I have fallen into it.

Still, I will take a bet, and the bet is testable. By December 2026, at least one major Bangladeshi cricket publication will print a source line beneath its post-match data pieces — which database, which date, which format. The publications that do not will slowly lose readers to the ones that do.

One lever: the desk editor. One timeline: the next home series. And one question — when you see an empty cell, do you write the explanation, or do you go looking for the cause?