The Report Was Complete. The Match Was Missing.

On Wednesday afternoon, in the same Banjara Hills room from which a fourteen-minute recording went out in 2026, I opened an analysis report. Eight sections. A table in every section. An 'assessment' and a 'confidence tag' in every table. Format analysis, player technique, team landscape, league economics, governance, risk matrix, public narrative, industry transmission. Cleaner formatting than any press release, more disciplined layout than most match reports.

And not one cricket fact anywhere in it.

No match. No format. No player. No team. The title field read 'N/A'. The source field read 'N/A'. The 'Information Points' field was entirely empty. Yet the document called itself a 'Stage-2 Deep Analysis' and appended 'High Confidence' to every conclusion it did not reach.

My first reaction was laughter. My second was a question: is this a one-off, or is this the thing we read every day and fail to recognise? For thirty-six years I have made a living separating the scorecard from its flattery. Today I met a document with no scorecard at all — only its layout, and a caption claiming analysis.

So let us examine the thing properly.

Context: the real product of cricket coverage is no longer the match, it is the dashboard

The biggest change in Indian cricket coverage over the last fifteen years is that the match now arrives as data before it arrives as television. The rights sheet prices the fixture, the auction purse prices the player, and only then does the screen give you the powerplay graph, the death-over economy, the wagon wheel. That business has moved in the right direction. I am among those who think phase-wise data lifted a genuine burden off Indian cricket writing — the burden of guessing a captain's intent.

But every data product passes through a three-stage chain. Stage one: extract the facts from the match — format, venue, toss, players, overs, runs, wickets. Stage two: structure them. Stage three: draw meaning. In the document I opened, stage one returned empty, stage two returned empty, and stage three — the bit labelled 'Stage-2' — completed without complaint.

The consensus here is simple: more data, truer coverage. And the consensus missed this case entirely, because this was not a shortage of data. There were no facts. Those are different conditions, and cricket media blends them into one vessel every single day.

Core: the system broke in three places, and all three were upstream, not downstream

First wound: the missing format. This is not a cosmetic gap. The scorecard lied; the session rate told the truth — and when the format is undecided, a strike rate of 140 and a strike rate of 55 get weighed on the same scale, though they describe different skill sets entirely. In T20 the powerplay is the first six overs, and it is a game of fielding restrictions; in Test cricket the first morning is the new-ball phase, a game of movement and seam. Death-over economy means overs 16 to 20 in T20 and overs 41 to 50 in a one-day international. Without a format tag, joining any two of those numbers to each other is noise. That is precisely what happened: every row collapsed to 'N/A', because there was no benchmark to write beside any metric.

Second wound is more interesting, because it is a design failure rather than a data failure. The report carried an 'Entities Involved' field with the instruction 'identify from the information points above'. There were no information points above. The template stood on its own foundation. It is the poker-faced version of what we do in cricket all the time: naming the XI before watching the match. I chase the story, then make it show its receipts. Here the receipts never arrived and the invoice was printed anyway.

Third and most dangerous wound: converting 'unknown' into 'clean'. The governance section explicitly stated that integrity risk could not be assessed, and that the finding should be read as 'unknown', never as 'clean'. That single line tells you the document had a working conscience. It also tells you the fault sits not in the document but in the pipeline that forwarded it. Cricket does this constantly: no selection news means everything is fine, no workload report means the player is fit, no board minutes means no decision was taken. Thirty years on the board beat taught me one hard rule — the absence of news is never evidence of good news.

The fourth wound looks small and costs the most: the domain label. It read 'cricket_world' rather than 'Cricket' — outside the agreed specification. Anyone who has spent a day on a rights desk knows that bad metadata is the easiest way to leak money. One mislabelled file travels down one wrong route, and after that nobody knows which number belongs to which match. Names on an auction sheet are not a bowling plan, and the same rule governs every data sheet: names and numbers placed in the wrong column are decoration, not information.

All four wounds point the same way. The most honest thing in that report was its 'N/A'. What shocked me was its design. The system did its job and then succeeded in looking finished.

Where I could be wrong

My criticism may be aimed at the wrong address. Perhaps the fault is the market's, not the pipeline's. In 2026, when I wrote about that Eden Gardens Test — Laxman's 281, Dravid's 180, Harbhajan's 13 wickets, a 171-run win after the follow-on — my argument was only that the miracle was arithmetic: ninety overs of risk-free accumulation and bowling at the stumps. By Friday forty angry emails had arrived, one of them calling me a traitor to the team. That was never about readership; it was about taste. Twenty-five years on, the market still buys the shape of analysis rather than its weight. In such a market a beautifully formatted, fact-free report is not an accident. It is demand, delivered.

Second, I must be careful with my own memory. That 1990s press box, that February 2026 Mumbai auction where Symonds went for $1.35 million as the day's most expensive buy and Deccan Chargers finished last with two wins from fourteen — those are memories, not evidence. I may use them for texture, never to carry an argument. Third, and most important: perhaps that pipeline was right. A system that can say 'I do not know' is far more trustworthy than one that guesses. My quarrel is not with the null return. My quarrel is with the formatting that smuggles the null past the reader and past the next model in the chain. 'N/A' is honesty; eight headings wrapped around it is theatre.

The way forward

Next time a powerplay graph appears on screen, ask one question — which over does this graph begin at, and was there a match behind it? My estimate is that within this season, a report with a blank title will be cited as a source somewhere in the Hindi cricket content chain, and nobody will notice, because the layout was correct.

The fix will not come from better models. It will come from one line that every pipeline should carry: if the information points are zero, the analysis does not run. That is all. Cricket has done this for a century — when the toss does not happen, we do not write the score.