Report on a Null Report: How Do You Read Cricket When the Data Itself Is Missing?

Sitting in a small press box in Pune, I came across a report that had no scorecard, no over count, no name of a single batter. On paper it had an eight-dimension template, every cell filled with 'N/A – insufficient information'. Like the people queuing for tickets outside a stadium, this report was waiting for someone who never arrived. Out of old habit, I counted the calls: zero information points, zero players, zero teams, zero dates. The scoreboard remembers what the stands forgot; here the scoreboard itself was missing.

This analysis is not the story of a match, but the story of a lost story. When the Stage-1 deconstruction of a cricket article returns empty — title N/A, source N/A, type 'Unclassified' — the first question is whether the original article never existed or the system simply failed to read it. In my 48 years, such cases usually come from two causes: the page never fully loaded (paywall or JavaScript), or the source was a scorecard/video page mistaken for an article. In either case, drawing any cricket conclusion would be self-deception.

The risk is particularly high in cricket because the metrics of the three formats (Test, ODI, T20) do not translate across scales. An economy rate of 7 is considered good in T20, ordinary in ODI, and irrelevant in Test. If the format itself is undetermined, any claim about 'strike rate' or 'average' hangs in the air. That is why my first act on reading this report was to reject any conclusion that claimed a scoreline, bowling analysis, or player form.

The real question is not what the report lacks, but how to read this nullity. All Stage-1 fields being blank means the extraction pipeline failed, not that nothing interesting happened in cricket. If the research team treats this as 'no risk found', that is false security. In my career I have seen many occasions when 'no information' was read as 'no problem' — whether in a selection committee meeting or auction preparation.

One thing that does emerge from this null report is a lesson in information integrity. In cricket journalism we often fall into the trap of 'story first, data later'. But sometimes there is no data at all. In such a case, the most honest report is the one that returns empty-handed and says: I need more information. I have always taught my three young colleagues: the empty stand is the loudest witness. Here the stand was empty, and it spoke loudly that you cannot say anything yet.

Going forward, Stage-1 must be re-run — this time on raw HTML or API payload, not on the rendered page. If the source is a scorecard-type item, it should be routed to a separate structured-stat extraction path. Until then, any comment on cricket will be mere conjecture. And conjecture, however beautifully written, can never become a scoreboard.