The Honesty of an Empty Spreadsheet: Cricket Data's Immutable Ledger

Two in the morning. Fog sits outside the window of my Khulna flat; inside, a single cursor blinks on the laptop screen. Twenty thousand ball-by-ball logs, shot maps from eight matches, three seasons of powerplay data — and after every filter, the same answer comes back: N/A. My fingers stop above the keyboard. There is no one left in this room to lean over my shoulder and whisper, "Just put in a guess, write it up." And precisely because of that, this empty result is worth no less than a full one.

Fifteen years in the press box taught me something no scorebook prints: an empty cell is also a sentence. In cricket analysis we chase the big numbers — strike rate, economy, xG, PPDA. But the moment a model collapses, the real work begins. I built the model in the Khulna press box, then let the league speak — today the league is silent, and that silence is telling me my input was empty.

---

Context: From Scorebook to Ledger

Cricket data no longer lives at the level of a batting or bowling average. A single delivery now breaks into eight or ten variables — line and length, footwork, field setting, the over number inside a powerplay, bounce, the dew factor, even the umpire's position. These variables flow through a pipeline: stage one pulls information points from raw logs, stage two structures those points, then the model.

In my experience, stage one is the most neglected. If someone errs there — no match name, no team identified, no time sensitivity checked — every later decision becomes poisoned. That is exactly what arrived today: an 'analysis' where every field is blank. No match, no player, no team, no league, no rule change. Only a frame, and inside it a dozen rows of 'insufficient information'.

Most people would give up here. I scanned a second time. Working on Bangladesh and Sri Lankan domestic cricket taught me that this region is a laboratory. Here, pitches, weather, administration and talent pathways decide outcomes more than reputations do. From the Khulna press box, one thing is obvious: if a match has no data, no one has the right to make a confident claim about it. My job today is not to explain a match; my job is to honestly measure this emptiness.

---

Core Analysis: Why a Null Result Is Still a Result

A data block is only admissible when its source can be verified. Unverified, it is not data — it is rumour. Just as a block in a blockchain ledger fails to join the chain unless it is bound to the previous hash, a claim in cricket analysis falls off the chain unless it is bound to its source point. Every block in the frame handed to me is empty — so every block is void.

That word 'void' is itself the biggest piece of information, because it proves there is a gap somewhere in stage one of the pipeline. Had someone forced the cells full, the error would have stayed hidden and every later analysis would have drifted the wrong way. That honesty is the first discipline.

The Khulna Press Box Lesson: 14.6 Versus 9

In 2026, at thirty-five, from a Khulna flat, I logged every shot of the Bangladesh Premier League. I built an xG model for Abahani Limited Dhaka and Sheikh Jamal Dhanmondi Club. In their final eight matches Abahani created 14.6 xG but scored only 9 goals.

The spreadsheet was my prayer mat; the data, my daily office. That ledger taught me that the phrase 'deserved to win' is meaningless without data. The gap between 14.6 and 9 is not merely misfortune; it is a confession about finishing quality, shot selection, and decisions in the final fifteen minutes. The day I was told in the Khulna press box that women do not understand tactics, I published the model anyway — because I held a ledger more honest than word of mouth.

Here is today's lesson: if I had never logged those eight Abahani matches, the 14.6-versus-9 story would never have existed. Without input, analysis is never born. Today's empty frame is a witness to that missing input.

PPDA Is Not a Number; It Is a Confession

In 2026, at thirty-six, my xG work earned me a remote analytics contract with a pan-Asian sports site for the Russia World Cup. Before the England–Croatia semi-final I built a model. Croatia's PPDA was 8.7, and Luka Modrić averaged 12.3 progressive passes per 90. England had superior set-piece xG, but my model said Croatia would win midfield and force extra time. Croatia won 2-1.

I trust the model, but I audit the story it tells. PPDA is not a number. It is a confession of where a team hides. Croatia did not dominate the ball; they dominated the spaces between passes. The same logic applies directly to cricket: no team 'dominates' a match; it dominates the gaps between dot balls and the gaps inside a powerplay.

That semi-final changed how I write. I moved from match summaries to process-driven previews, explaining PPDA and progressive passes in plain language. Editors stopped asking for 'emotional colour' and started requesting my pre-match data brief. With today's empty input I have no brief to give — so what I can offer is an honest account of why the brief cannot be written.

Empty Stadiums Did Not Silence Football; They Exposed Its Arithmetic

In 2026, at thirty-eight, with global sport paused, I analysed all 83 Bundesliga matches played behind closed doors after Project Restart. The home win rate fell from 43.3% to 33.3%. Home penalties dropped from 0.29 to 0.18 per match. Others wrote about atmosphere; I built a regression model isolating crowd absence from team quality. After three weeks alone, I partnered with a video analyst to validate referee positioning.

Empty stadiums did not silence football; they exposed its arithmetic. Crowd is a contextual variable, and dropping it does not make a number lie — it makes it incomplete. My writing has been less deterministic since: data never lies, but it needs context.

That lesson matters most in today's pipeline. If someone tells me 'so-and-so lost because he was bad', I first ask: was there a crowd, how much travel, where was the umpire standing, was there dew on the pitch? Without answers to those, the remark is not data — only a remark.

Measuring the Gaps in Cricket: Phases, Pitches, DLS

Cricket has no direct equivalent of football's xG, but the logic of measuring gaps is identical. An innings splits into four phases — powerplay, middle, death, and the finish. Each phase carries a different 'run value'. A six in the 20th over is low-value; a dot ball from a wide yorker in the 6th over is also a value decision — just in the opposite direction.

Mushfiqur Rahim, Shakib Al Hasan, Litton Das, Tamim Iqbal — each has a distinct phase profile, and that can only be measured with ball-by-ball logs. The same holds for Sri Lanka's Kusal Mendis or Dhananjaya de Silva. But before drawing these profiles, what is needed is the context of every innings: whether the pitch was dry or damp, how strong the wind, when dew fell, what the DLS target became.

Here lies the biggest trap — mixing formats. A Test strike rate is not a T20 strike rate; an ODI economy is not a Test economy. A boundary is a breath of release in a Test and an obligation in a T20. An analysis that ignores this distinction is not analysis — it is a slogan.

And luck factors? The toss, DLS, a dropped catch — leave these out and you drag big conclusions from small samples. Declaring a player's 'form' from one innings in one match is as absurd as declaring a whole monsoon from a single cloud.

Honesty Means a Confidence Tag Beside Every Claim

In my spreadsheet I write a confidence level beside every inference. This is not decoration; it is professionalism. If today's frame contained hidden information — a match name, a team, a date — it could be written with a 'low confidence' tag. But with zero input there is no anchor for inference; so no inference can be drawn, not even at low confidence.

That is the rule of the ledger: a block that cannot be verified does not enter the ledger. In cricket we often do the opposite — a viral clip, a troll opinion, a 'I heard' becomes data. The first condition of a data-driven culture is the ability to say 'no'. What arrived today hides a clear 'no' in its very first stage — and admitting that is my most valuable work.

---

Contrarian Angle: Correlation Is Not Causation

There is one trap I fall into more than any other — trying to model everything. The Khulna press box taught me humility: noise is data too. A strike rate falling does not mean a player has become bad. Perhaps he was moved from top order to middle order, perhaps the pitch changed, perhaps the opposition brought on a leg-spinner. Declaring a cause without separating the variables means losing faith in your own model.

The second trap is hedging into invisibility. My validation compulsion forces me to attach five conditions to every claim, and the reader ends up with a fog. The fix? State one clear thesis first, then attach the shadow of uncertainty beside it.

The third trap is data superiority. Data is not a verdict; data is a tool for asking better questions. An analyst who uses data to silence the reader has explained nothing.

And the biggest trap — forgetting human pressure. Fatigue, fear, family, red-eye flights, the courage to play through injury — none of these fit a spreadsheet. A batsman out of form for five matches may have a sore shoulder, or a newborn keeping him awake. Data can be input, but a human is not an input.

---

Takeaway: What I Will Watch Next Cycle

What today's empty frame taught me is that next week my eye stays on stage one of the pipeline — whether the input is genuinely full, or merely looks pleasing while empty. Three signals are lit on my ledger: whether information points return at stage one, whether teams, players and events are identified, and whether source and time sensitivity are populated. If these three blocks are not verified, the whole chain is void.

An empty spreadsheet never lies. The hand that wants to drop a guess into an empty cell is the one that lies.