N/A: The Cricket Story That Was Never Recorded

It is two in the morning. On a laptop in a Hyderabad flat, an eight-row table sits open. Row one — Format: N/A, insufficient information. Row two — Player: N/A. Row three — Team: N/A. Row four — League and commercial structure: N/A. Row five — Rules and governance: N/A. Row six — Risk matrix: N/A. Row seven — Public narrative: N/A. Row eight — Cricket industry transmission: N/A.

Eight rows. Not one name. Not one date. Not one number.

I have been watching and writing about matches for seventeen years, and I have a long relationship with blank screens. The women's cricket and women's football archives are so full of holes that the first instinct is always that the stream betrayed us again — buffering, a freeze, 480p, something. This time the network was innocent. The material sent for analysis genuinely contained nothing. Title N/A, publisher N/A, summary blank, the information-point set blank, the entity list blank. One thing survived: the domain label, cricket_asia.

That label is the most honest finding in the entire exercise. cricket_asia is not information; it is a geography tag. Some pipeline read the page metadata, decided this was cricket copy, forwarded it without reading the body, and at the next desk an empty envelope was accepted as an 'eight-dimension analysis.' Every cell said N/A, so nobody asked.

This article is about that single incident — and the incident belongs to cricket reporting, not to cricket.

Any serious cricket analysis runs in a fixed order: format first, then role, then metric, then benchmark. The order is not decoration. If the format is unresolved, the role cannot be fixed; if the role is unfixed, the metric means nothing; and a metric without a benchmark is just a digit that anyone can read any way they like.

The ICC keeps three separate ranking tables — Test, ODI, T20I. Three separate documents, three separate assessment systems. Adding them together is like adding a marathon time to a 100-metre time. Suppose a batter has a Test average of 45 and a T20I strike rate of 128. Those two figures measure different skills. The first measures patience, defensive technique and the capacity for a long innings; the second measures risk management, the speed of reading a bowler, and the ability to exploit fielding restrictions. In a report with no format marker, both get dropped into the same cell, and the reader is left believing they learned something.

Each of the eight dimensions in that table required at least one concrete object. For format, an explicit Test/ODI/T20I marker. For player, a name and a role. For team, one named side. For league, a league name and a currency figure. For governance, an official board or ICC decision. For risk, one line on bowling workload, injury history or contract status. For narrative, a single attributable claim. For transmission, one broadcast deal or investment report.

Three absences were loudest: a Source Quality grade, a Time Sensitivity assessment, and a publication date. The report itself stated that time sensitivity was 'not assessed in Stage 1.' That sentence says Stage 1 did not complete and return empty; it stopped early. The difference matters. Completing and finding nothing is a conclusion. Stopping is a fault. Presenting the two identically converts a fault into a conclusion.

That is where the real argument begins, and it is an argument about how we record cricket more than about cricket itself.

A null return is a finding in its own right, and its name is: the gate did not exist. One minimum check that costs nothing — at least one information point and at least one named entity — would have caught the entire failure at the door. Two fields. Just two. But in an industry that calls everything intelligence, the cheapest check is always the first to be removed.

And the dangerous sentence is this: what was never screened cannot be treated as cleared. An empty table does not mean risk is zero; it means risk was never examined. No injury column means the reader assumes fitness. No integrity-monitoring reference means the reader assumes clean. No financial assessment means the league looks safe. In cricket that is the costliest error of all — the gap between a workload-management story and a breakdown story is often just somebody deciding a column did not need filling.

In February 2026 a Hyderabad new-media startup paid me four thousand rupees to call the Indian Women's League final from a co-working room in Banjara Hills, off a laggy YouTube feed. Nine hundred concurrent viewers, a twelve-second delay, no spotter, and a colour commentator who had never watched a women's match. I misidentified two Manipuri midfielders and invented a formation that did not exist. I was squinting at 480 pixels when that final turned.

For three weeks afterwards I cold-called coaches in Imphal and Odisha until I could name every player in the league. I called 41 IWL matches for free the following season. I stopped writing about names and started writing about structures — who covers whom, who breaks the line. A 300-player reference file exists now, and I still update it.

That experience gave me the rule that applies to this entire report: nobody archives the games nobody thought to broadcast. And what is not in the archive never reaches the analytics layer. Women's cricket carries a doubled version of that hole — first thin coverage, then thin data about the coverage, then the thinnest analysis built on top of it. When a system returns N/A across eight dimensions, it is rarely one bad night. It is usually a twenty-year habit showing up disguised as a technical fault.

The second major hazard is format mixing. It is the commonest error in secondary cricket reporting — a T20 strike rate placed beside a Test average, or a career-wide blended figure printed as a single-format number. The error is not usually deliberate; it is a product of convenience. A blended number looks weightier, and a weighty number fits a headline more easily.

The third hazard is taxonomy. cricket_asia is a geography tag, not a format or subject tag. Such a label can route non-cricket material into a cricket template, and what comes out is a report that is genuinely about nothing while running to eight chapters. Filling the table does not fill the hole.

Here is the contrarian point, because the crisis the industry complains about is probably not the crisis it has.

Cricket analytics does not suffer from a shortage of data. It suffers from surplus — untagged, unformatted, ungraded data that looks like work. A blank report is honest; it says it has nothing. A filled report built on blended numbers is a lie with a spreadsheet attached, and it is far harder to catch because it looks like effort.

The second inversion: completeness gates are cheap, but they buy hygiene, not judgment. A gate can force a field to be non-empty. It cannot force a human being to have watched the match twice. The gate that actually matters is a person with a 300-player file and a poor memory for adjectives.

So the plain judgment is this: a report returning N/A on all eight dimensions should never have been published as analysis — it should have gone back to source with one line: send us the article.

The next ingestion cycle will arrive, and it will carry a title, a publisher, a date, three discrete information points and at least one named entity. On that day all eight dimensions go live and the argument becomes real — format, workload, what an auction price actually signals, where broadcast rights are heading.

Until then one job remains that no pipeline will do. Fill the women's archive. India was awarded the 2026 Women's ODI World Cup — the ICC confirmed it in July 2026 — and the WPL's first season was played in March 2026. Those two events built a structure that should have accelerated the flow of data. The question is not whether the flow arrives. The question is whether, the next time a table opens with all eight cells empty, the pipeline stops — or the column gets filed anyway.