The Empty Packet: Eight N/As and the Lesson of Missing Evidence in Cricket's Data Chain

Two-forty in the morning. An eight-section sheet sat open on the monitor — format and match analysis, player technique and data, team landscape and ranking, league and commercial ecosystem, rules and governance, risk matrix, public narrative, industry transmission. Every section had a table. Every table had columns — metric, benchmark, assessment, direction, magnitude, likelihood, impact. And under every column, one entry: N/A — insufficient information.

The title was blank. The source was blank. The article type read 'unclassified'. The information-point list contained zero rows. The material that was supposed to be analysed had never arrived. What arrived was a frame — a building with every door hung and no floor poured.

In 2026, at the Nehru Stadium square in Pune, I hand-coded 1,412 deliveries of a Ranji season — length, line, footwork, scoring zone. Every column was full then, in pencil, by mud-stained fingers. One opposition left-hander that season made 78 percent of his runs square of the wicket; Maharashtra opened with a 7-2 off-side field and a deep sweeper, and he made 41 off 96 balls. The coach called the chart a fluke and I charted the next eleven matches anyway. The lesson of that decade was that an empty column is a matter of shame. Twenty-four years later a machine taught me the reverse: if an empty column says plainly that it is empty, that is not shame, it is honesty. And nobody in that room was equipped to recognise the honesty.

Cricket coverage in 2026 runs on three things — the live score feed, the broadcast clip, and the template. The first two are visible. The third is not, and it decides the most. Any match report, transfer analysis or auction note travels through four stages: source, deconstruction of the source, dimensional analysis, publication. Deconstruction is where only facts are pulled — title, outlet, article type, format token, entities (player, team, league, board), time sensitivity, and the list of information points. This time that stage returned empty. The stage below opened its eight-dimension frame, recorded the preconditions each dimension requires, and marked all eight 'insufficient information'.

A format token is not a formality. A Test batting average and a T20 strike rate answer different questions; one measures patience, the other speed. The powerplay scoring rate (overs 1 to 6 in T20) is not a proxy for overall batting strength. Economy rate and bowling strike rate have to be read together, never apart. DLS revises a target after rain and leaves a residue of doubt over the legitimacy of a result. An NOC is the key document in any league-versus-country dispute. If not one of these is pinned, no tactical sentence can be completed. This time none was pinned.

The eight N/As are not emptiness. They are a dependency map. The first dimension says that without format and match identity, nothing can be read out of the powerplay, the middle overs, the death overs, or a Test session milestone; and without venue, pitch character, dew, cloud cover and DLS, the gap between result and process cannot be demonstrated either. The second says that with no named player, no role can be assigned — opener, middle-order anchor, finisher, seamer, spinner, all-rounder, wicketkeeper. With no role, no benchmark. Without a benchmark, a metric is a number, not a meaning. The third says that home-versus-away is the single most consequential variable in cricket, and it cannot be measured without a team and a venue. The fourth says that a high auction price does not equal international strength — and that distinction cannot even be applied here, because neither a price nor a player exists in the material. The fifth is the most delicate: where no party is named, raising any integrity or spot-fixing signal is simply defamation. The correct posture is this one — no name, no allegation, only 'unassessable'.

The most important warning in this entire frame sits in a single line: never record 'unassessable' as 'low risk'. A bowler with no data is not a cheap bowler; he is an unknown bowler, and being unknown is a separate risk, not zero risk. Absence of evidence is not evidence of absence. That is why injury, schedule overload, cross-format transfer, positional drop-off and the financial fragility of smaller boards were all marked 'unassessable' rather than 'low'.

The real hazard is not the analysis. It is the template. A populated template looks like a low-signal but valid analysis. Eight headings, eight tables, clean formatting, competent vocabulary — and zero evidence inside. A downstream reader can cite it, because nothing in it raises a hand. The chart rarely shows the pass that changes the room, and the template never shows the ball that actually takes the wicket.

One consequence of the blank source is permanent. If the outlet and the journalist are not recorded, their reliability can never be graded again — not even if the material is later recovered. The platforms that hold up today, databases like CricSultan, are built on exactly this question: who made the claim, on what date, and can it be checked again. An item with no source can never clear that bar.

April 2, 2026, Wankhede. India were chasing 275. Virat Kohli's dismissal left them 114 for three, with Yuvraj Singh in form. Mahendra Singh Dhoni walked in at number five — a promotion almost nobody in the press box had written down. Dhoni made 91 not out off 79 balls, Gautam Gambhir made 97, and the winning six off Nuwan Kulasekara came with ten balls left. I filed at 1:40 a.m. arguing that the promotion was the story and the six was only the receipt. Had only the scorecard been recorded that night, the sheet would carry 91 not out and a six — and the promotion, the decision that made the match, would appear nowhere. That is the template's disease: it collects receipts, not decisions.

So the one useful thing that came out of that blank sheet is a remediation list. For any item to be fully analysable, the mandatory fields are: title; source (outlet and URL); article type; a format token — Test, ODI, T20, The Hundred, or non-match; at least three information points, each traceable to the source text; at least one named entity from the team or player class, plus the competition name; and time sensitivity, meaning the date of the event against the date of publication. If it is a match report, add scoreline, venue, toss and innings state. If it is an auction or transfer item, add price, franchise, and retention or right-to-match status. If it is a governance item, add the specific rule, the deciding body and the ruling date. If any of this is missing, the correct answer is 'insufficient information' — not an estimate.

Why empty packets form is an economic question more than a technical one. Content volume rises every season, per-piece rates do not, and the speed of aggregation is such that the deconstruction step is often the one that gets squeezed — a paywall, a login, a geo-block, or a source that was never text at all (video, photo post, live-scorecard widget); any one of these is enough. Even so, the most honest work that night was the work that happened — writing 'insufficient information' against all eight dimensions, because that option contains not one false claim about any player, team or board.

This is where I see the strangest thing about my own trade. People in cricket tell me the data desk won the tactical argument years ago. In this case it conceded — and conceded honestly. For me that is worth more than a win, because an empty packet is the only artefact that cannot later turn out to be wrong. An analysis that says 'we don't know' never has to be retracted.

But the real risk is not the sheet. It is the room where four hundred words are needed at eleven at night. An empty sheet is a problem there, and there will always be someone to fill it — a sub-editor, an aggregator, or a model told to just write it. The real lapse is not the blank sheet. The real lapse is handing the blank sheet to a man who was never at the ground. I have always read the game in that gap — between what a coach says and what the bench does, between what the scorecard records and what the captain chooses. Machines cannot measure that gap. They try to fill it, and that is where the biggest lapse happens.

The next item entering this pipeline should be watched for three things. The information-point array must be longer than zero. One named entity — team or player — must be present. And a format token must be recorded. If all three arrive, all eight dimensions open; if not, the sheet stays blank however elegant it looks. The question is not where the data is. The question is whose hand holds the pen when that blank gets filled — and whether, when it fills, it can name the ball that actually took the wicket.