Zero Information Points: The Silent Failure Inside Cricket's Data Pipeline

The report arrived in eight sections. Each section had a table, each table had four to six rows, and the assessment column of every row carried roughly the same sentence — "insufficient information, assessment not possible." Format. Key-phase performance. Venue. Batting average. Strike rate. Economy. Broadcast rights. Franchise valuation. The Big Three's revenue share. Slow-over rate. Audience expectation. The transmission map. The same sentence everywhere, only the nouns changed.

The first instinct on reading a sheet like that is to start filling it in. That is what we all do in cricket — where the number is missing, we build a bridge out of experience. I was about to do exactly that when I opened the box at the very top. "Information Points" — the list was empty. Not one entry. And beneath it, the domain label: cricket_asia, when the agreed category was Cricket.

If the total on a scorecard does not match the sum of the individual batsmen, you do not read the match — you audit the bookkeeping first. That is what happened here. Eight sections, more than a dozen tables, dozens of rows, and not a single fact on which any conclusion could stand.

Cricket analysis now runs like a factory, and like any factory it has two halves. The first half prepares the raw material: pulling the title, source, article type, information points, core viewpoints, entities involved, time sensitivity and source quality out of the original text. The second half moulds that material into eight frameworks — format and match, player technique and data, team landscape and rankings, league and commercial ecosystem, rules and governance, risk, public narrative and expectation, and industry transmission.

The frameworks are not bad. On the contrary, they carry a discipline most cricket writing lacks. Test, ODI and T20 benchmarks were never pooled into one column. The home-away differential — the single largest structural variable in the sport — was kept separate. The auction was treated as revealed preference rather than a performance carnival. These are the right questions.

The quality of a framework and the quality of its input are two different things, and no framework fills the gap between them. Between the two stages sits a dispatch decision, and often it has no owner. Stage one says the material is ready; stage two says that whatever the material is, it can be poured into eight moulds. Nobody in the middle asks what the material actually is.

Across fourteen weeks of lockdown I hand-coded 3,000 deliveries from India's 2026 World Cup campaign. It included the Manchester semi-final, where New Zealand reduced India to 5 for 3 and bowled them out for 221. The real benefit of coding 3,000 balls by hand was not clean data. It was that an empty cell was visible. I built the database before I ever trusted the eye test. A blank row in a spreadsheet makes no noise; one cell stays white and you postpone filling it until the next morning. In an automated pipeline, that same white cell becomes a full, table-laden report.

A single empty field says nothing; the picture forms when three things arrive together. An empty information-points list, a domain label outside the agreed taxonomy, and an "unclassified" article type. Their co-occurrence is what matters, because individually none of them means anything. A cricket article containing not one item of cricket information is rare — why would anyone write it? Text-parsing failure is far more common. And if the text had genuinely been cricket-free, how did the domain label reach cricket_asia at all? That label is itself a residue — evidence that something read the text halfway and then broke. My read is an ingestion failure, held at medium confidence.

A second danger rises directly out of that label. Read cricket_asia and any experienced analyst's mind sprints immediately towards the Asia Cup, India-Pakistan tension, ACC politics and the high sentiment coefficient of the South Asian market. Those are real subjects and they deserve coverage. But a label is not evidence, and the South Asian market prior is strong enough that it starts mistaking itself for insight. That is precisely where an analyst sitting at a distance mistakes distance for objectivity and misses the dressing-room texture no database encodes. The empty list did one unintended service here: it gave speculation nowhere to stand.

The real danger in this report is not that it is empty. It is that an empty input produced a complete, eight-section, table-filled report that travelled forward silently. The cost of catching a defect rises the further down the pipeline you go. At the top sits an empty list, which is easy to fill. At the bottom a reader finds that every risk category is marked N/A and reads it as "no risk present." In between, someone has to decide what an empty list beneath eight full tables means. That decision is not easy, because effort went into building those tables, and mistaking effort for evidence is a human habit.

"Unmeasured" and "cleared" are not the same thing, and cricket shows us the difference every day while we forget it every day. All six rows of the risk matrix — sporting, personnel, commercial, rules and integrity, public opinion, systemic — read N/A. They were unmeasured, not cleared. When ball-tracking itself fails in a DRS review, the outcome is not "umpire's call"; the outcome is that the answer to the question does not exist. Yet three letters flash on the screen and the stadium reads them as a verdict. Data reporting works the same way — an empty field, sitting among filled ones, starts to look like a decision.

The one solid thing this report yields is a specification for what stage one must deliver before any re-run: title, source, article type, at least one substantive information point, entities with an explicit format context, time sensitivity, and source quality. Alongside that, a gate: if the information points are empty or the label falls outside the approved set, stage two must not begin.

In cricket we install such gates every day and never name them. Three reviews, a clear-evidence threshold, then a verdict — DRS is itself a gate. A player who fails the fitness test does not walk into the eleven; selection is a gate. Every transfer rumour is a hypothesis; the medical is peer review. In our line of work that gate is missing, which is why an empty list travels through without being stopped.

It is also worth noting that the frameworks left the fields empty rather than filling them with guesses. That was not cowardice. Had the analyst poured Test, ODI and T20 benchmarks into one column, the report would have looked full and been entirely wrong. At Edgbaston in August 2026 I watched Virat Kohli make 149 and 51, and India still lost by 31 runs. That innings is assessed on Test terms, where leaving the ball is a skill and the fourth-stump line is a strategy. Measuring the same innings against Kohli's ODI strike rate is bookkeeping across two currencies. Edgbaston day four is where I learned to hear the signal under the noise — and the loudest thing in the noise is always whatever arrives wrapped in a filled table.

The transmission map was empty too — broadcast, the South Asian market, the talent supply chain, capital networks, betting and fantasy, derivative markets. Writing even one line on any of them requires a hard fact, and no hard fact existed. Saying anything at all about betting would have been more irresponsible still, because what that space needs is not merely facts but accountability.

The economics of a newsroom reward the opposite. An editor on deadline cannot publish white space. The reader clicks the headline, the channel wants a verdict within minutes, and "this input yields no conclusion" is a sentence somebody has to defend. The incentive is plain: guess, write it in a confident register, and put the caveats in small print. An analyst who refuses is not refusing work — he is absorbing a cost, and he absorbs it alone.

Nobody quite remembers when the data desk won cricket's tactical argument. The charge against the commentary box is settled: it chants the liturgy of centuries, fifties and records, it cannot read a required rate, and its fifty-over obsession survives every analytical advance. The charge is fair.

But the data desk has a liturgy of its own, and it is more dangerous because it looks literate: the filled table. A report with all eight sections populated and not one information point is, in analytical terms, exactly what a century in a losing innings is — a superb output with no relationship to the input. We recognise milestone liturgy because it is spoken loudly. The liturgy of the empty list is spoken quietly, inside a table, and that is why it escapes detection.

I have to check whether I am overreaching. One empty return is not a disease of the whole pipeline; it may be a one-off ingestion glitch. I have a single observation, so I make the systemic-defect claim at low confidence and the recommendation to test at high confidence. A coach sees the error; a commentator sells it. I try to do the first — and the error in this report belongs not to cricket but to the machine that claimed to have read cricket.

The next time a sheet like this arrives, do not look at the table first. Look at the length of the field. Whether the list holds even one entry, whether the label sits inside the agreed taxonomy, whether the article type is settled — those three questions decide the fate of the entire report.

If the same three symptoms appear in the other reports from the same batch, the question is no longer about one article but about the whole machine. One run at Gahunje is still the cleanest proof that systems fail late — and they usually fail late because nobody in the middle looked at an empty cell. The day the information-points list fills again, this report becomes obsolete. Until then the question stays open: are we willing to call an empty space empty, or will we fill it with a guess, as we always have?