Empty Payload, Full Format: The Most Expensive Lie in Cricket Analysis Is 'N/A'

I froze the frame on the one cell where 'Entities Involved' was answered with — "identify from the information points above". There was no batter's name there, no venue, no series date. It was an instruction, filtered through the Stage-1 extractor and deposited in the output field where data should have been — the system had issued itself a directive and then passed that directive downstream as content. Above it stood a complete eight-dimension report: format and match analysis, player technique and data, team landscape and rankings, league and commercial ecosystem, rules and governance, a risk matrix, public narrative, and industry transmission. Every table was built. Every row carried risk flags. Every dimension ended with 'Analytical Conclusions'. And every cell said the same word — N/A.

That is the document that made me realise cricket coverage's biggest threat is not a wrong number. It is a document that arrives in perfect format and contains nothing at all.

Context: the desk economy has changed, and so has the audit question

Cricket news now runs on three layers. Retrieval comes first — a script or a sub-editor lifts raw material from a source. Extraction comes second — title, source, format, entities, date and a list of claims are pulled out of that raw material. Analysis comes third, where format logic, ranking snapshots, auction arithmetic and governance checklists are applied to that list.

For the first fifteen years of my working life, all three layers ran inside a human head. I carried them simultaneously while watching a match — reading the scorecard, holding the bowling spell in memory, and stitching the two together in the next morning's copy. When I began covering the Under-17 World Cup from the Jawaharlal Nehru Stadium press box in 2026, I understood I was not alone in this. Every man beside me was running his own extraction layer, and no two layers matched. One was measuring the depth of the back four; another was simply counting passes into the net.

Machines do that work now, which is good news. The bad news is that when a machine comes back empty-handed, it does not say 'I came back empty-handed'. It builds the eight-dimension scaffold and fills every field with N/A, because completing the format is in its programming and telling the truth is not in its priorities.

In cricket this lands in three places, and I have watched it land in all three.

First, the DRS inventory. A team has a limited number of reviews in an innings, and the man in the commentary box will tell you by the twentieth over whether the review has been preserved or burned. If one entry in his ledger is blank, the entire downstream read goes the wrong way — because the shot the batter played, or refused to play, was determined by whether a review was still available.

Second, NRR. One misread figure in a net run rate calculation reshapes an entire group, and teams chase that single decimal place to the last day of a tournament.

Third, the auction. Retention caps, the Right to Match, a player's base price — run that arithmetic on an incomplete list and the output is not merely wrong. It looks authoritative. That is the real trouble.

Core: N/A is not information, and it is never read as 'no information found'

That report carried three tells that, sitting together, said one thing. Blank title. Blank source. Article type 'Unclassified'. And an extractor instruction leaked into the entities field. Together these do not say the article contained no cricket information. They say the article's body text never reached the machine. A paywall, a JavaScript-rendered page, or a payload that was never text — any one of those would do it, and all three produce the same outcome: an extractor returning empty-handed, having disguised its failure as 'N/A'.

The first lesson is direct — format completeness and evidentiary completeness are two different things, and cricket desks treat them as one. A report with eight dimensions, seven risk categories and a five-star rating table persuades the reader that somebody worked hard. Somebody did. The work went into building the scaffold, not into gathering the material.

The second lesson costs more. One line in that report insisted that integrity and anti-corruption monitoring be logged as 'unassessed', not 'cleared'. That single sentence catches the largest blind spot in the entire cricket-media apparatus. No information on ACU monitoring, spot-fixing suspicion or unusual market movement does not mean the risk is absent. But when that report passes through an alerting dashboard or a newsroom filter, 'N/A' becomes 'zero' on its own, and zero becomes 'no story' on its own. Three steps, and an unassessed risk turns into a clean bill of health.

The third lesson is taxonomy. The payload's domain label read 'cricket_world', which sits outside the specified category 'Cricket'. It looks trivial, but in a data pipeline it is exactly what happens when a batter's name is entered in the scorebook under the wrong spelling — later, his innings gets credited to somebody else.

The fourth lesson is rankings. The report stated plainly that no team had been identified, so ICC ranking comparison was impossible. It also noted that even if a team were identified later, the currency of the ranking snapshot could not be proven without a date. This is the detail that trips every cricket desk, daily. ICC rankings move month to month. A sentence built on a stale table — 'they are the number two side' — can be technically accurate and entirely wrong at the same time.

The fifth lesson stings most, because it applies to my own trade. The report wrote about itself that its greatest risk was being mistaken for analysis by whoever read it. I read that line twice. We do this every day in cricket. A young batter plays one outstanding innings and ten outlets declare him 'the next big thing' by morning, with nobody checking the sample size behind the declaration. A team loses a series and the 'structure has collapsed' copy goes out, with nobody asking how much of it was the toss, DLS and one disputed DRS call.

That is the moment I had to fight my own reflex.

My first instinct was to fill the blanks. I know how far domestic cricket's media presence has shrunk in India — Ranji Trophy matches no longer get the space they got two decades ago, and the direct consequence is that zonal selection decisions happen without any public audit. I know that the BCCI's calendar, retention caps and broadcast deals are, in practice, bigger than the cricket visible on the field. I have twenty-seven years of material, and I could have filled every crack in that empty report from it.

I did not fill it. That is the only honest outcome of this whole exercise.

Contrarian: the empty report is the most trustworthy document in the batch, and that is what makes it dangerous

The conventional reading is that an empty report is a failure. My first reading was the same. Then I thought about the batch it arrived in.

Of the other reports in that batch, how many declared the tier of their source? This one stated plainly: 'Source Quality: not assessed'. That is the thing every cricket desk needs daily and rarely gets. Who is saying it? An official board statement, an ICC release, a seasoned reporter, general media, or a traffic account? Those five do not carry equal weight, yet as news they all look identical.

So the contrarian reading is this — the report that wrote N/A everywhere was the most honest document in that batch, because the rest shipped confident copy without any source tier at all. At least the empty report told you it was empty.

But here comes the second turn, and this is the actual danger. Honesty that looks like confidence stops being honesty and becomes branding. That document had seven risk categories, a five-star rating table and three scenario projections. Any reader seeing that much scaffolding assumes deep work behind it. The work was on the scaffolding.

This is the error cricket coverage commits daily. A team loses four matches and the desk produces a 'crisis' story without checking how much of those four was toss and weather. A player fails in two innings and the 'finished' headline writes itself, without asking which bowling he faced, at which position, off how many balls.

The defining habit of my trade is that we read absent evidence as a clean chit. Where the report said injury history was unavailable, it did not say the player was fit. Where it said venue information was unavailable, it did not say the pitch was neutral. The gap is small, and the entire copy stands on it.

And one last thing, the one that stung most. The report admitted internally that if it entered an automated system, 'N/A' would quietly convert to 'zero'. A document telling the truth can still become a lie downstream — because the system it enters has no separate word for an empty field.

Takeaway: next time a report looks clean, ask whether it was assessed or unassessed

Three things to watch in the next ingestion batch. First, the null rate — how many items out of the total returned an empty payload. If that ratio crosses an agreed threshold, the problem is the system, not one document. Second, the fetch logs — HTTP 401, 403, an empty DOM, or a payload that was never text. Third, domain label conformance, because a label like 'cricket_world' drops every downstream report into the wrong bin.

I have no instant fix for this, and I think that is the honest answer. What I have is a habit — whenever a table looks too clean, I will ask it one question. Is this clean because the evidence is clean, or clean because the space where evidence should be is empty? Ask that in the next match commentary, the next auction copy, the next rankings table, and half the desk's headlines might change.