The N/A Trap: The Cricket Report That Knew Nothing and Still Read Like Reassurance

On a Wednesday afternoon in a Hyderabad studio, a twenty-two-page document opened on a screen. Title: 'Stage-2 Deep Professional Analysis — Cricket Domain'. Eight sections, three or four tables in each, five or six rows per table, a green badge in the header reading 'Confidence: High'. The formatting would embarrass a board's annual report.

Then you read the first column. Format: insufficient information. Match nature: insufficient information. Player: insufficient information. Venue: insufficient information. Governance: insufficient information. Risk: 'unassessable — note, this is not the same as low'. Zero of eleven expected inputs usable. And the list on which all eight sections rested — the Information Points array — was entirely empty.

Now find the most dangerous sentence in that document. It is not the one that says 'insufficient information'; that is honesty. It is this: 'Overall Risk Rating: cannot be assessed.' A tired sub-editor will read that as 'Risk: low'. Six months later the same line will sit in a selection committee's file rewritten as 'no red flags', and a player will lose his place on the strength of it.

To see how that happens, you have to see how such a report is built. A cricket article is first broken into small units — 'information points', meaning hard facts that can be quoted separately: who, where, how many overs, which format, who said what. That is stage one. In stage two, eight dimensions are erected on those points: format, technique, squad structure, league economics, governance, risk, public narrative, industry transmission. The frame is not a bad one. It is the same logic cricket has run on since 2026: scorecard, then data feed, then data desk, then broadcast graphic, then the franchise's auction model, then the selection deck.

I keep a handwritten ancestor of that chain in a drawer. Winter 2026, Lal Bahadur Shastri Stadium, Hyderabad's Ranji campaign. A twenty-eight-year-old research fellow coding every delivery — 2,140 balls, a thirty-two-sector field grid drawn by hand. I kept the pencil because the pencil remembers what the software forgets. The ledger worked because not one ball was missing from it. Arshad Ayub's figures came out clean: 1.9 an over with a slip and short leg in place, 3.7 with a sweeper. In March 2026 Hyderabad beat Delhi at the Kotla for the state's last Ranji title, and Venkatapathy Raju's left-arm angles were part of the same arithmetic. Had a single frame of those 2,140 balls gone blank, the difference would have been poetry, not science.

The ledger never lied. It just never told the whole truth.

The same rule applies to that empty report, in the opposite direction. When some columns are blank and others are full, the blankness is itself news. An article that names the teams, the players and the series but carries not one figure for money, broadcast rights or auction value is telling you it belongs to the ground, not the market. Selective absence is a signal. But when the title is blank, the source blank, the format unknown, and the event has no name at all, what you are holding is not an article that says nothing. It is an article that never arrived. A selective gap is information; a total gap is a fault.

An empty filing cabinet and a missing receipt are not the same offence. Naming the three probable faults is cheap, because each has a different cure. In fetch, the source page sat behind a paywall, was rendered in JavaScript, or was robots-blocked; the cure is source access. In extraction, the article existed as a photo caption, a video clip, a scorecard embed or a live-blog stub, none of which survives text decomposition — 'Rohit in the nets', four words, one photograph, zero information points, and the article entirely real; the cure is the decomposition method. In serialisation, the stage-one report was cut off mid-run; the cure is the pipeline. Naming them is cheap. Choosing between them is expensive, and the wrong cure leaves the pipeline unchanged and the trust gone.

The real damage, though, is not the fault but its translation. N/A does not mean clean. N/A does not mean low risk. N/A does not mean no news. Read 'insufficient data' in English and a man nods and says, fine, the data didn't come. Read 'अपर्याप्त जानकारी' in Hindi and the same man shakes his head and moves on. Same error, two accents.

I know what that error looks like because I lived inside it for eleven months. In December 2026 Mohammad Azharuddin was banned for life — a batter I had charted ball by ball since 2026. I left the press box, sat at the Sports Authority of India desk in Hyderabad, and coded 1,180 one-day scorecards from 2026 to 2026, hunting a statistical fingerprint: run-rate stalls between overs 20 and 40, anomalous fields, abrupt strike rotation. I found nothing robust, and I said so, in 'The Unfixable Statistic' in Economic and Political Weekly. Somewhere in that winter, the statistic stopped obeying me. The lesson was not that fixing does not exist. It was that 'the pattern is not there' and 'my coding could not see it' are two different sentences, and confusing them is a form of dishonesty. Every column since carries a line on what the numbers cannot prove.

The reverse is just as true, and there the check is easy. April 2, 2026, Wankhede. Chasing 275, India were 114 for 2 in the 22nd over when Mahendra Singh Dhoni walked out ahead of Yuvraj Singh. I coded the innings live: 14 from his first 20 balls, then 77 from his last 59. India won by six wickets with ten balls left, and I filed within ninety minutes — not the score, the decision: three options in front of Dhoni, the field each demanded, and why the third held. 'Dhoni was promoted above Yuvraj' is a claim. '114 for 2, 22nd over, 14 off 20, then 77 off 59, long-on vacant' is a set of information points. A report with zero information points is the first kind of claim dressed in the clothes of the second.

From there the argument reaches cricket's money. Auction models do not read empty records; they convert them into percentiles. Suppose a domestic left-arm spinner's forty-wicket season never entered the feed on which a franchise's model was trained. The model will not print 'unknown'. It will print 'lower percentile', and that percentile will send the player home unsold. Every transfer is a bet wearing a spreadsheet. A model that cannot be wrong is not a model. It is a religion.

And here is the paragraph that has to be written every time: a number can only count what somebody upstream decided to record. The forty wickets taken on a ground with no camera are not in the history. The viewer whose language never appeared in the rights deal is not in the audience figure. And the surge in women's cricket after 2026 has no historical baseline to be measured against, because the feeds of the previous twenty years never counted it. The arithmetic runs out there, and it should be allowed to run out there.

The fix is technical and cheap. Three hard gates — a non-null title, at least one information point, and at least one named entity (team, player or competition). Any record failing all three gets quarantined before stage two is invoked. Two lines of code, and a thousand false reassurances never get made.

One thing the data desk will not enjoy hearing. In 2026 the crowd in the stand knew before I did that taking the sweeper off Ayub would make him expensive. I trust the crowd — because the crowd is the witness that saw every ball with its own eyes, while the dashboard saw only what somebody could be bothered to send it. That crowd now sits in the comments rather than on the terrace, and its right to argue is still intact. You cannot argue with a dashboard that does not know where its source document is. You can only believe it, and belief is not a substitute for verification.

State the consensus at full strength, because it is not wrong. Machines invent cricket stories: fake transfer fees, fake head-to-heads, fake quotations. That is a real cost with a real consequence — one false figure travels from a feed to a newspaper graphic overnight.

And yet this document invented nothing. It said nothing, and said plainly that it knew nothing. One hundred per cent accurate, zero per cent useful. The danger was not in its error but in its tidiness — twenty-two pages of it, ruled borders and green badges. Fabricated news is read with suspicion. A clean empty report is read without any, because it made no claim, and a thing that makes no claim cannot be caught lying.

My quarrel with the television box is old, but here is the case for it. The commentary box at least says what it saw — 'that went to long-on', 'that review was a mistake'. You can argue with it, because it files its own deposition. You cannot argue with a dashboard that shows 'lower percentile' and will not say which feed it came from.

The next time a selection deck lands in front of you with 'no red flags' on the cover, ask the desk the question we used to ask in 2026: how many information points is this built on? If the answer is 'we don't know', do not conclude that the risk is low. Conclude that nobody looked. The most useful number about that document appears in no report at all — its null-rate. And that number is not on any cricket dashboard today. Do we still have the standing to ask which records the model refused to read?