Reading the Empty Column: Format, Sample and the Ledger of Honesty in Cricket Data Analysis

It was a Tuesday, half past eleven at night. In my Mumbai flat I opened the laptop, as I have almost every night for fifteen years. On the desk a match data file, beside it a cup of coffee gone cold, and one question in my head: what is this match actually saying? The file opened and my hand stopped. Five columns. Zero facts. A single label hanging at the top — cricket_asia. No format, no score, no overs, no player names. And yet the cameras had rolled for three hours, sweat had dripped under the floodlights, commentators had talked on and on, and millions of phones had buzzed at every six. I opened the spreadsheet so that the World Cup might confess its exaggerations. This time the spreadsheet itself stayed silent. Five empty columns stared back at me, and I felt that this silence was the most honest answer in years. Analysis never begins with the beauty of a scorecard. It begins with a question: what information do I actually hold? That night I reached no conclusion. I did the opposite — I made a list of the things I had been claiming to know without ever having checked them. The list was long. Right now we are in the regular season — a stretch where patience works harder than stardom. The great enemy of regular-season analysis is haste. A team wins three games in a row, rises up the table, and instantly a story is manufactured: they are back. Three matches cannot tell you where a team truly stands; that only emerges when you ask who the opposition was, what the pitch was like, how much dew fell, and how much plain luck was hidden inside. I started a page called BDCricTeam in 2026, and it was my first school of writing. Even then I learned that the most valuable thing in cricket is not the score — it is context. Eighty runs on a dead fourth-innings pitch and eighty runs on a slow, turning third-day track are not the same. They never are. And here arrives the question of format, the one most analysts skip. Test, ODI, T20 and The Hundred each keep separate ledgers. An opener's patience is precious in a Test and can be a liability in a T20. A bowler's workload, spell length and new-ball burst are counted one way in Tests; death-over economy and powerplay strike rate are counted in a completely different way. An analyst who carries numbers from one format into another is not analysing at all — he is merely decorating numbers. This is exactly where my empty file returns. Its only label was cricket_asia. Asia — a region. But the format? Test? ODI? T20? Without that, I cannot even place a single number. Put one bowler's ODI economy beside his T20 economy and any reader will reach a wrong verdict. This mistake is not new; it is the oldest illness of cricket analysis. Let me lay it out — an honest cricket analysis stands on four pillars. First pillar: the information point. Behind every conclusion must sit small, verifiable facts — who, when, in which format, at which ground, did what. Without these, analysis is imagination. That night I had zero facts, so my conclusion was zero. Some call that failure. I call it honesty. Second pillar: sample patience. My rule is that I publish nothing until the sample is large enough. A spinner's effectiveness in Tests needs at least a series; a finisher's value in ODIs needs at least ten innings; an opening pair's pattern in T20s needs twelve to fifteen matches. In 2026 England's Under-17s won the World Cup in India — 28 goals against an expected-goals figure of 22.4. That is 5.6 goals above their true merit. I warned clients that the flood was unsustainable and that regression would come. It did. That was not prophecy; it was respect for numbers. Third pillar: process versus result. Take Spain versus Russia at the 2026 World Cup. Spain: 1,029 passes, 74 percent possession, 2.4 expected goals. Russia: 0.6 expected goals and a PPDA of 31.2 — meaning Russia did not press at all, it sat deep. The score finished 1-1, and Russia won the shootout 4-3. An analyst who reads only the scorecard will say Russia were Spain's equals. But that huge passing phase said the opposite: Spain created and did not score; Russia did not create and scored once. That is the gap between result and process. I advised under 2.5 and Russia +1.5. That was not luck; it was consistency. Fourth pillar: the workload ledger. I count minutes before I count goals. A bowler's overs, spells, back-to-backs, travel and recovery — without these you cannot explain his decline or his resilience. A spinner losing pace in the final Test of a series, a fast bowler's line spraying at the end of a long tour — none of this is mystery, it is simple arithmetic of fatigue. Those who count only wickets cannot see the difference in the last match, because their ledger has no entry for tiredness. Take one example. If, in the last two matches of a five-match T20 series, a fast bowler's yorker rate rises and his line drifts, it is easy to call it a sudden loss of form. But if the workload ledger shows he bowled four overs in each of the previous four games, bowled to the end in two of them, and had only two days of rest in between — the explanation changes completely. This is not form, it is distribution. For an all-rounder like Shakib Al Hasan the arithmetic is more complicated still, because batting workload and bowling workload must be counted together; rest one and you damage the other. Those who look only at the sum of runs and wickets never see this double burden. And one more thing I write again and again — the defensive acts. Dot balls, keeper interventions, run-outs, saves. They never make the thumbnail. For Alisson, I counted the saves that never made the thumbnail. After the 2026 World Cup, in the summer transfer window, when Liverpool bought Alisson Becker from Roma for 66.8 million pounds, many asked whether that was too much for a goalkeeper. I looked at his Serie A save percentage, 79.3, and the 8.4 expected goals he had prevented. My arithmetic said Liverpool's expected goals against would fall by at least 0.3 per match. That is what I told clients. They reached the 2026 Champions League final and conceded only 22 league goals. A transfer fee is a hypothesis; the season is the peer review. The same logic holds in cricket. A keeper's dives, stumpings and catches that are not easy on the eye never appear in a highlight reel, yet they can decide a Test. If a side bowls a whole session of dot balls, the scorecard shows zero, yet that session may have turned the match. By defensive-metric primacy I mean exactly this — the quiet arithmetic of run prevention that nobody writes about. Now back to that empty file. Why does an empty file matter so much? Because it exposes our biggest error: we treat the absence of information as if it were information itself. A neatly arranged report, five columns, tidy headings — it looks full. But if there is not one fact inside, that report misleads the reader into believing the analysis is complete. That is not a risk of analysis, it is a risk to the honesty of analysis. Sixty-six years taught me patience; the data taught me why it pays. I keep a ledger for legends, because memory edits its own columns. The innings people call great today may look ordinary in ten years, because by then they will have forgotten the context. So beside every entry I write: at which ground, against which bowler, in what situation. Memory paints; the ledger wipes the paint off. Notice one more thing. My file had no format, and that is no rarity. Much of the talk around us is format-less. Someone says this batsman is superb — but in which format? Someone says this bowler is finished — but in which format, at which ground? These format-less conversations gather into a fog, and inside that fog we make decisions. My job is not easy, because I must clear the fog every single time. Now a subtle but important question. Many think regression means pessimism. If a player hits six fifties in six innings and I say it is unsustainable, they think I am taking the joy away. The opposite is true. Regression means I believe in consistency, not coincidence. If a player is genuinely good, he will not fear regression, because real ability builds its own foundation. I am only searching for that foundation. Here is one thing I must state plainly, or the analysis stays incomplete. Having data does not make a conclusion correct. The gap between correlation and causation is the biggest trap in cricket analysis. A team wins and its catching rate rises in the same match — that does not mean catching caused the win. Perhaps the opposition was weak, the pitch easy, the toss won, the opponent's best bowler rested. Correlation is easy to see, causation hard to prove. And our brain always seeks a story, because it seeks causes. I opened the spreadsheet so that the World Cup might confess its exaggerations. Every time I find that the timeline was loud, so I regressed it until the noise fell away. We see a star hit five good innings in a row and make him a god, though five innings is an impossibly small sample. And we see five bad innings and declare him finished — equally wrong, because nobody is finished in five matches. This is where the lesson of my empty file applies: if there is no information, silence is better. The rarest courage in cricket is the courage to say — I do not have enough information to know. That courage did not come easily. In the 2026-19 transfer window I checked Alisson's file against at least ten matches of rolling data. I never wrote a verdict from a highlight reel, because if a save looks beautiful from a low angle, that is beauty, not information. Information is how hard the shot before it was, and what the expected goal of that shot was. I write that arithmetic, and over the long run it has served my readers. One thing always astonishes me — how we reach two different conclusions from the same information. One person sees the score, I see the process. One sees the result, I see the method. That difference is not small; it decides whether you err in the next match. In the regular season the difference grows larger, because behind every regular-season match lie fatigue, travel, injury and the fine choices of selection — none of which the scorecard ever mentions. On my desk a small rule is written: when something is extreme, look for explanation, not for cause. When a player does something abnormal, my first task is to ask — over how many matches has this abnormality run? If the answer is one match, I write nothing. If the answer is fifteen, I still wait five more. Some call that laziness. I call it the pause without which the risk of a wrong verdict rises. One thing to remember — data never speaks on its own; data only prepares the ground for argument. An analyst who begins with numbers and ends with numbers says nothing at all. The real work is learning to ask questions while standing among the numbers. Why did this number turn out this way? What was left out? Which variable did I forget to count? These questions separate the analyst from the storyteller. So next time someone says this team is back, or this player is finished, ask one question — how many matches of information? In which format? Against which opposition? At which ground? If no answer comes, perhaps an empty column will fall into your hands too. And if you can admit that empty column rather than deny it, the real analysis begins. The first condition of analysis is honesty, and the first step of honesty is this admission — I do not yet know everything. That empty file is still on my laptop. I have not deleted it, because it is my most valuable dataset. It reminds me every day — what is absent is also information. And the analyst who learns to read that invisible information walks slowly, but errs less.