If Stage-1 Is Empty, How Do You Write the Analysis? A Ledger Audit of a Cricket Data Report

I started with the balls nobody counted, and the ledger did the rest.

This time the ledger did not contain a ball. It contained an empty Stage-1: twelve fields, four columns, and not a single semantic value. A cricket_world label was stuck on top. That is the moment when a data consultant must first ask: do I have a match, or only the address of a stadium?

Hook: The Table That Looks Full Is Actually Empty

In nine years I have logged 14,412 balls delivery by delivery, rebuilt 824 IPL matches into a single database, and built twelve live metrics across 64 World Cup matches. All of it taught me one lesson: the biggest lie in data is not its absence but its empty structure. When a form has headers but no rows, the table is not "incomplete" — it is deceptive, because it looks like something was measured.

That is exactly what the Stage-1 report did. Article Title, Source, Type — all N/A. Core Viewpoints empty. Information Points had not one entry. Entities were meant to be "identified from the information points above," while above there was nothing. Time Sensitivity was never assessed. To me this report is not "low on information" — it is structurally void.

And writing analysis on void, in my profession, is like writing a match report without a scorecard — knowing only which city the ground is in.

Context: Why Empty Data Costs Most in Cricket

Cricket differs from other sports in one respect: every big story carries a timestamp. A Test score is fixed forever, but its meaning can change next week — injury, selection, transfer window, rankings, weather. A board's annual accounts, an IPL auction's unsold list, a bilateral fixture sheet: these are primary documents, and only from them do I assemble a conclusion, never first.

In the Stage-1 report, Time Sensitivity was "not assessed." In cricket that is not an empty cell on a form. It is the publication date of the story I am about to write. If I am commenting on a player's form and do not know the date of that comment, I cannot even tell whether I am writing history or forecast.

The only usable signal was the domain label cricket_world. Twenty years of experience tells me that any output produced from that label alone will be "general talk about cricket," not "analysis of that article." The first is knowledge; the second is research. I never mix the two in professional life.

Core: A Five-Layer Audit of an Empty Stage-1

I will not say the report is "bad." I will show which layer broke where — because an audit's job is not accusation but a line-by-line demand for answers.

Layer one: the fact layer. Information Points had not a single entry. The implication is clear: there is no fact, no number, no quote available for me to extract and cross-verify. Cross-verification in cricket means matching a scorecard to the official site, a injury report to the team statement, a transfer fee against two separate media reports. None of that is possible on zero facts. When the fact layer is empty, every layer above it becomes guesswork.

Layer two: the argument layer. The author's thesis, stance and purpose were all blank. In my framework I always look for four things: what the claim is, what the evidence is, what the hidden premise is, and where the logical leap is. Not one of the four existed. Argument cannot be assessed without an argument — the same as computing a dot-ball percentage when no bowling took place.

Layer three: the source layer. Source N/A. In cricket, source reliability splits into three tiers: primary (official board announcement, ICC rankings, team medical bulletin, official match data), secondary (media reports summarising a primary source), and anonymous ("a board official said"). I built a rule over my career: I may quote an anonymous source, but I may not base a decisive conclusion on one. Here there was not even a name.

Layer four: the time layer. This is the layer that does the most damage in cricket. I must separate two kinds of information: fixed facts (a completed match's score, a date of birth, a contract's duration) and drifting judgements (ranking forecasts, form assessments, selection probabilities). The first has a shelf life of years, the second of weeks — sometimes hours, when the dew factor shifts after the toss. Without time sensitivity, I cannot even know when my conclusion expires.

Layer five: the blind spot. This is the layer that hurts most because it is invisible. Any cricket conclusion is incomplete without seven variables: sample size (how many matches, how many innings), opponent strength, format difference (T20 versus Test — the same number means different things in each), home versus away conditions, weather and dew, the Duckworth-Lewis-Stern situation, and pitch type. Analysis written without these may be beautiful, but it will fail an audit.

After these five layers, one thing becomes clear: the problem is not the amount of information but the absence of it. The distinction matters. On a low-information report I can write a "cautious estimate"; on an empty report I can only write that the report is empty. The second is also analysis — but of the process, not the subject.

Contrarian: "You Can Debate on Little Data" — When, and When Not

Here I want to challenge a comfortable belief of my own profession. It is said that a good analyst can extract a great deal from little data. That is half true, and half-truth is the most dangerous kind.

Debate from little data works when the data is present but narrow — say, a player's three innings, but ball-by-ball for all three. Then I can say: "The sample is small, so the pattern is unstable, but the direction is this." That is honest analysis. But when the data is absent — zero facts, zero sources, zero timestamps — drawing any conclusion is not using data; it is performing data.

After the 2026 World Cup I audited my own product. Twelve metrics were in the feed, four reached air. PPDA never did — a producer replaced it with possession percentage on the on-screen graphic. At the time I thought the problem was the metric. Later I understood: the problem was transmission, not the metric. In the same way, the problem with the empty Stage-1 is not Stage-1 but the process that forwarded it unchecked.

One more point belongs here, because it connects to the politics of cricket data. Data is never neutral, because collection is shaped exactly like the money and cameras that went there. Where there are no tracking cameras, there is no ball-length data. Where the broadcast contract is small, even the scorecard arrives half-filled. When a report arrives empty, the first question should not be "what is missing" but "who did not record this, and who benefits from the omission." I ask that question of every report coming out of a small cricket board — and writing from Sri Lanka, I have learned that the question is often worth more than the answer.

Takeaway: Next Time an Empty Stage-1 Arrives

I have a standing rule: the ledger closes at a fixed deadline, and any unresolved line is not hidden — it gets printed as an open question. I apply that rule here.

The minimum input can be any one of three: the original text (best — I will rebuild Stage-1 and continue), or at least five to ten Information Points each carrying fact, source and time, or title, publication, publication date and a three-sentence summary.

Next time an empty Stage-1 arrives, the first question will not be "what do we write on this" — it will be "why did this arrive empty." Because the day we start writing analysis on an empty table, we will have no ground left — only a commentary box. And there, as I learned in 2026, only four of twelve metrics ever reach air.

I trust a column only after I have walked its exceptions twice. This time the exception was the whole column.