An Empty Spreadsheet and the Honest Limit of Cricket Analysis

There is a page in my notebook I never fill. It has column headers only — delivery type, length, trigger movement, field position — and the space beneath them is blank. That page is not a technical memento; it is a reminder. Whenever someone hands me a piece of "cricket analysis" in Pune that carries only headline-shaped frames and no facts, I open this page. Empty columns are often the most honest data anyone can offer: they show what is not there.

That is almost exactly what arrived last week. An output came through from a data pipeline tagged "cricket_asia", but the article title was empty, the source field empty, the article type unclassified, and — more importantly — the list of information points was completely empty. The material the analysis was supposed to stand on was absent. My first instinct was to say nothing and go back to sketching the field map for the next match. But an empty output is also a story, and in the current fever-pitch of cricket-media debate, it deserves to be filed.

Context: When the raw material of analysis is missing

The entire scaffolding of cricket analysis stands on information points. A delivery's length, a fielder's position, the pressure built in one over — these are the bricks from which any solid conclusion is built. When the list of information points is empty, no player, team, tournament, or institution can be identified. Nor can the author's stance be fixed, or the purpose, or the reliability of facts. A domain tag such as "cricket_asia" tells me at most that, if content existed, it would involve Asian cricket. That is not enough for any concrete claim.

My method has a rule I never break: before deploying a metric in a report, I write down its failure mode. Until I know which conditions would make this metric lie, I do not convert it into a verdict. Faced with an empty information-point list, that rule applies first — there is no metric, no counter, no timestamp. I cannot invent a story because I do not have the building material.

Now consider where this same absence happens daily in cricket coverage. A tournament throws up a big decision and by next morning the headline is out — selection, transfer, retention — but if the information chain underneath is empty, the reader never knows. The reader reads the headline and assumes analysis was done, when in fact no field map was ever drawn.

Core: Empty columns give the cleanest conclusion

The most honest result of an analysis is the one that states its own limit, and with empty information points that is the only truth available. In this country cricket lovers are plentiful, and the speed of their commentary often substitutes for fact-checking. I have seen, many times, a captain's negative field-setting criticised in print when the writer did not even have a diagram in hand. On my side, no claim about a captain's "defensive" field can survive without a hand-drawn diagram. And today I have zero diagrams, zero information points. So my one defensible variable is that I will fabricate nothing.

This "breakdown" can be read as a straightforward technical event. In the pipeline producing this output, latent silent-failure points exist at several places. First, the scraping stage may have received an empty body or a 403 page and thrown no error. Second, the HTML-text extraction selector did not match that site and returned an empty string. Third, the information-point extraction/JSON stage failed and was quietly converted to an empty array. Fourth, the model returned a structure that did not contain the information-points field at all. All four share one thing: the system did not report failure as failure.

That is the real story here: silent failure is becoming cricket media's biggest flaw, and it is dangerous precisely because its product looks clean. I treat cricket as a system that can be broken into diagrams — rings, gaps, release angles. Those diagrams are not decoration; they must be evidence. In a situation where the diagram is an empty shell, commentary should stop. Sending an empty output to the next stage without error is like writing a match report knowing you never got the scorecard, then printing the story anyway.

Examples turn up across the game. A middle-order "panic" narrative often begins with the over in which the run rate crossed the wicket-risk line — but whoever writes the story does not have the momentary detail of that over. Temperament is easier to write. My writing method insists that any sentence explaining a wicket by mood should be deleted. In analysing an output with empty information points, the same line must be drawn.

In my experience, Test and T20 techniques have different rules of evidence. T20 is the format where sequencing and clocks are legible; red-ball cricket is governed by draw, follow-on and session context. No frame should be used unless it can survive a Day Three session. With empty information points, this matters even more — because when there is no material, imposing any 96-ball or 90-minute frame is pure invention.

So the conclusion that emerges is that the right response to an empty output is a pipeline-level engineering fix. An assertion must be added at output: if the information-point count is below a minimum threshold N, the system should throw EmptyDeconstructionError or return status: failed. This is the same discipline I keep in my notebook — an empty page is not an excuse, it is a condition that the number comes first and the sentence second.

Contrarian: The clean output is the greatest danger

A counter-question arises, and it applies to my own method too. Is an empty output always the bad thing? No. A filled but wrong output can do more damage than an empty one, because it gives the reader confidence. An empty list at least says clearly that something is missing. But when a system fails silently yet returns a "complete"-looking structure, it cheats the reader — because the tidiness of the format hides the absence of facts.

The same happens in sports journalism. A cleanly drawn field map is not always proof — if it is decorating a claim nobody was disputing. I have a habit: write the claim as a single sentence first, then check whether the diagram is decoration or evidence after that sentence. If decoration, cut it. This rule saves me from my own beautiful blank notebook.

On the other side, another risk is drawing a verdict from a single variable. Making one over's dot-ball percentage or one auction price the whole story. In my method I always write the variable's failure mode first — which condition would make this metric lie — and then deploy it. When information itself is absent, that discipline matters most.

One facet of this debate is resource allocation. Today cricket coverage's real shortage is not of "star stories" but of time and labour — roles within a team are many and slots few, so every decision draws envy-laden debate. When information points are empty, only emotion remains in that debate. I prefer to speak from budget, not emotion — retention lists, auction prices, bench composition. An empty file also silences that budget language.

Takeaway: Next time the output comes back empty

When the output comes back empty, the biggest mistake is the rush to fill it. For the next six months my condition stays the same: any analysis I write will have at least one information point, one timestamp, and one variable whose failure mode can be written down. If all three are missing, it is not something to publish. For those working on the pipeline, the question is not how to fill an empty output but when a mechanism for declaring it a failure will exist. In cricket the clock runs on every ball; in analysis, the time to call zero zero must also be fixed.

In which session did we last learn to tell the truth from an empty spreadsheet?