Zero Information Points: The Cricket Analytics Failure Nobody Audits

Eight dimensions. Forty-seven checklist items. Six risk categories. And information points: zero.

That is not a figure of speech. The Stage-2 cricket analysis report that landed on my desk last week had exactly one sentence repeated across every field. Article title: N/A. Source: N/A. Article type: Unclassified. Author stance: N/A. Information points: an empty list, zero items. The entities field carried an instruction — "identify from the information points above" — and above it there was nothing to identify.

All eight dimensions were filled in, every one of them with the same marker: N/A, insufficient information. Format undetermined, players unnamed, teams unnamed, league unidentified, no governance question raised, the risk matrix left blank, and the narrative heat-cycle impossible to place on any curve.

This report is not incomplete; it is honest. And in my trade, honesty has become a metric-defying event.

Context: the road from scorecard to dashboard, and its one junction

With data now touching every part of cricket coverage, the pipeline has to be understood. A source article first passes through Stage 1, which yields title, source, article type, information points, entities, time sensitivity and source quality. Stage 2 then builds an eight-dimension frame on those information points: format, player technique, team landscape, league commerce, governance, risk, narrative and industry transmission.

The entire structure rests on one brick — the information point. That is a single, separately verifiable fact with its source and its date attached. One ball in a scorecard, one bid at an auction, one board press release: these are information points. When that list arrives empty, the building above does not collapse. It was never built.

The irony here is that the domain label was present: cricket_world. The system knew the item belonged to the cricket vertical; it did not know what was written inside it. A taxonomy tag is not content. That distinction is not small. It is the line between reporting and guessing.

Core: an empty list is not a story, it is a supply-chain failure

Twenty-six years of reading scorecards have taught me that guessing is the easiest thing in cricket and the most expensive. Any writer can assemble a plausible match narrative inside an hour — who was under pressure, whose powerplay was slow, whose death overs leaked. The trouble is that nothing in that story can be cut. A claim that cannot be falsified is not analysis; it is decoration.

In this report the empty list delivered a very clear message: the fault sits one layer above the analysis. An article that has already been assigned a domain label normally yields at least one or two facts. Zero is a different signal altogether — something broke at extraction or parsing, or the input itself arrived unreadable. In technical language that is a data-supply-chain failure. In professional language: fix something before picking up the pen.

The one field that points at itself

Read the instruction in the entities box: "identify from the information points above." That sentence is the whole case. The schema survived, the instruction survived, and the data it pointed at was absent. It is the equivalent of finding a scorebook with blank pages and a header saying "count the runs from the previous page."

In cricket, this is a layer-by-layer collapse. No player identity means no role — opener, anchor, finisher, pace, spin, all-rounder, keeper, none of it can be assigned. No role means no way to know which metric is even relevant. Average serves one player, strike rate another, economy rate a third. Choosing a metric without a role is exactly the error we hear from the commentary box every night.

The team dimension is blunter still. Batting depth, bowling mix, bench strength, age structure — none can be measured without a named squad. Rankings are trickier, because the ICC's Test, ODI and T20 tables are three separate documents, not three sections of one. Any analyst who slides between them in a single line has already lost the argument.

Format is the field that can never be null

If this report produced one structural fix, it is this: make format mandatory and non-nullable in the schema. The reason is simple. A Test new-ball contest and a T20 powerplay look like the same passage of play and are not the same sport. In one, the price of risk is a wicket; in the other, it is a dot ball. In one, an average of forty is excellent; in the other, the same average ends a fast bowler's career.

I had to learn that discipline the hard way, back when my spreadsheet started as a cricket scorecard and became a football argument. I did not port the words; I ported the assumptions hiding inside them. Whenever a metric crosses from one sport into another, the first job is its visa check: what was it originally built to predict, and how much can the new setting's event structure actually support it.

Cricket is stricter than most, because it runs on discrete deliveries rather than a flowing current. Every ball is a closed unit with its own outcome. A model born in football's continuity loses its footing the moment it descends into cricket's missed deliveries. The metric here is not the offender — the assumptions travelling in its luggage are.

The Narine spreadsheet: a map of populated data

To see what a filled list looks like, 2026 is worth returning to. At a Kolkata digital cricket desk I spent four months building an Expected Runs Added model from 2026 IPL ball-by-ball data, then published a pre-season piece arguing KKR were wasting Sunil Narine in the middle order. That April, KKR opened with Narine; he finished IPL 2026 with 224 runs at a strike rate of 172.3. The piece drew roughly 400,000 reads and an unsolicited email from the franchise's analyst asking for the methodology sheet.

That is what I call a populated dataset: defined competition, defined role, defined sample, defined window. Every number stood on a definition, and every definition stood on a source. Against it, this report's empty list proves something else — cricket does not lack data; it lacks the provenance that should travel with the data. A file that will not say which format, which season and which sample an average belongs to is not a fact file. It is a file of orphan numbers.

And one necessary caveat, which I regard as my most honest line: that year my call landed, and landing is not proof. KKR's team management changed their mind; that my model caused it is something I cannot demonstrate. A single decision matching a single model is correlation. Calling it cause is the same self-deception as valuing a match by its run count — and the century itself is a counting convention inherited from print-era scorecards, not a measure of match value.

The circular sin of source grading

One more finding here is technical and utterly basic. The source-quality field said: "judge from the source fields." The source field was empty. It is the equivalent of asking the third umpire to rule on a replay that was never recorded because the camera was not switched on.

In cricket media that gap is the gap between life and death. A board press release, an ICC published ranking table, a senior reporter's file and a traffic-chasing account cannot share one scale, because if they do, the weight of your whole report hangs on an anonymous handle. Without a source, information is a claim; with a source, it is a fact. The distance between them is not a matter of quotation marks but of legal liability.

The auction as selector, and its limit

The league-commerce dimension returned empty because the input carried no transaction, no retention, no bid. But one point deserves recording now, because it is the thing most likely to be misread the next time this report arrives with populated data.

IPL purse arithmetic, retention calls and franchise scouting have quietly replaced the zonal selector. That is the most honest public signal of what Indian cricket actually values. The data has a limit that is routinely ignored: an auction price is not evidence of a player's international strength. Market value is commercial; format-specific performance is sporting; merging the two in one column is the metric imperialism I criticise every week. The transfer market is not a market; it is a vocabulary under pressure — and in cricket that vocabulary snaps faster still, because every bid carries a format condition with it.

Contrarian: "an analyst must always deliver" — in its strongest form, then its rebuttal

I put this argument at maximum strength, because beating a weak version is not a win. The argument runs: an analyst is hired to say what happened and what comes next. Filing "insufficient information" after a match is a failure of craft dressed as a moral victory. A good writer builds a path for the reader out of half the facts — because the reader wants understanding, not excuses. That argument is correct. And it does not apply here.

The difference is not the amount of input but its shape. Half the facts means: format known, teams known, score known, a couple of performances known, a few things missing. You can stand on that partial ground and mark its edges clearly. Here there was not partiality; there was zero. A building on zero has no foundation, and therefore any cricket claim written from it could not be cut. And a claim that cannot be cut is not journalism; it is a press release in verse.

One more thing belongs in the record, and it is against my own account. My first instinct — an ENTJ's instinct — says the meeting should end with a ruling. This entire report runs against that instinct. The ruling here is that no ruling is possible. When you can file a claim, file it; when it can be cut, cut it; and when all you have left is a tone of voice, the truth is that you have nothing.

One admission must be made: here the data and the commentary box are on the same side. Neither has anything to say. In my experience that is the one moment both fall silent — nobody's panel heats up over a match whose feed never arrived. The problem is that the dashboard stays warm, and in the hurry to fill it we patch that emptiness with counterfeit numbers.

Takeaway: what to watch in the next round

The next time a cricket analysis report reaches you, do not look for the match story. Look for five fields. An information-point count of at least five to eight, every item separately checkable, format clearly tagged, entities named, date recorded. A desk that cannot produce those five has not read the match — it has read a scorecard template.

Installing a gate is cheap; writing a correction is expensive. Every clean dashboard begins with a dirty question nobody wanted to ask — and this report is a photograph of that question. The day the pipeline is fixed, all eight dimensions will fill and the same frame will deliver a real verdict. Until then the honest output is zero. The question is not how much data we have. The question is whose testimony our data is giving.

---

Disclosure: This piece rests on an internal Stage-2 cricket analysis audit document and my own 2026-17 IPL ball-by-ball work. I hold no internal data from any franchise, board or broadcaster, and I cannot say anything about the contents of a source article I never received. This is sports-information content only and forms no part of any betting advice.