How Do You Analyse Cricket From an Empty Input? A Document-First Reporter on the Stage-1 Failure

In February 2026, in a hotel hall in Mumbai, I saw for the first time how an auction book speaks — not aloud, but waiting quietly for someone patient enough to read it. That day, from the Deccan Chronicle sports desk, I logged every sold lot against its base price and found that Hyderabad had paid roughly 38 per cent above the median for overseas all-rounders. The editor ran it as a graphic, not a story. But the lesson was clear: the real information lives on paper, not in the headline. Seventeen years later, this week, a document landed in front of me that inverts that lesson — a "deep analysis report" with eight analytical sections, tables, a risk matrix, and the same sentence written everywhere: "N/A – insufficient information." Let me set the context first. The report in front of me is not about a match, a player, a team or a league. It states plainly that its input — the Stage-1 deconstruction — was entirely empty. Article title blank, source blank, core viewpoints blank, entities blank, time sensitivity blank. Given that, what the report did is technically correct: it fabricated no facts. It invented no cricket story. It built an eight-dimension scaffold and wrote honestly in every cell that there was nothing there. From a journalistic standpoint this is unusual — a report that reports its own failure. And in my experience, such reports often teach the most, provided you read them as process rather than as scandal. Now let me open the scaffold the report built. Its first section is format and match analysis. It asks whether this is Test, ODI, T20 or The Hundred — because the tactical logic of these four is different and their conclusions can never be mixed. The report says the format cannot be determined, so no tactical interpretation is possible. The second section is player technique and data, demanding average, strike rate, economy and situational splits — and without a named player it can say nothing. The third is team landscape and ranking, resting on ICC rankings, home-away profile and squad depth — all empty. The fourth is league and commercial ecosystem, covering broadcast rights, franchise valuation and auctions — no figures. The fifth is rules and governance, the sixth a risk matrix, the seventh public narrative and expectation gap, and the eighth an industry transmission map. Every section reaches the same conclusion: no subject, therefore no risk, no narrative, no transmission. Here is the point where I had to stop and think. A reader could dismiss this as a "useless report" and close it. But I remembered what I learned on those Mumbai briefing calls in 2026 — when spot-fixing stories were breaking and everyone was writing the crime story, I deliberately stopped chasing the crime and started reading the paperwork: which clause voided a fee, which franchise owed what. At the time I thought I was falling behind. Later I understood that the people reading the documents were the ones ahead. In the same way, this empty report is also a document — and it tells us that the real bottleneck in cricket analysis is never a shortage of data, but the form in which data arrives. In my 34 years, every major mistake in cricket has followed one pattern: people write the story of the outcome first and read the document afterwards. Whether the 2026 match-fixing era or the 2026 IPL spot-fixing case, the headline always came first and the clause afterwards. This report did the reverse — it first looked at what was in the document, and when it found nothing, it did not invent a story. That is a discipline, and it is rare in cricket coverage. The default mode of Indian cricket coverage is: if there is no data, fill it with sources; if there is no player, fill it with star worship; if there is no format, fill it with generalities about "the development of cricket." This report refused all three. It wrote N/A. And writing N/A, in my experience, is the hardest thing for any cricket reporter to do. But I want to register an important objection while praising this report, because praise and analysis are not the same thing. At the end, the report offers a "minimum intake checklist" — title, source, date, format, entities, three to five discrete information points, core viewpoints, and time sensitivity. The list is good, but it does not touch the problem that actually occurred. The problem was not that Stage-1 had too little information; the problem was that Stage-2 never found out why Stage-1 came back empty. Was the source text never retrieved? Was it retrieved but the parser failed to read it? Was the article in a language the pipeline could not handle? The report asks none of these questions. It simply says: input empty, therefore output empty. That is technically correct but journalistically incomplete. A good reporter does not just write "the source did not respond"; they also write how many times they called, on which number, and when. This is where the contrarian angle that bothers me most emerges. The weakest link in this entire report is not any N/A cell — it is the "Preliminary Note on Input Quality," which says the Stage-1 output was "effectively empty." "Effectively empty" is a very vague phrase. It could mean the fields were blank, or that the fields contained "N/A," or that the fields contained something the parser failed to recognise. These three situations have different remedies. The first requires fixing the input pipeline; the second the Stage-1 prompt; the third the parsing logic. The report puts all three in one bag and says, "please supply valid Stage-1 content." This is the same mistake cricket coverage makes every day when someone says "according to sources" without saying who the source is, when they spoke, and who heard them. The first rule of document-first journalism is that the absence of a document is also a fact, and it must be recorded the same way as its presence. I want to add one more thing that strikes me most while reading this report. The report has a risk matrix, but the biggest risk is not recorded in it. That risk is that the next time Stage-1 arrives populated, Stage-2, in its hurry to fill this same empty scaffold, may produce conclusions that come from the demands of the framework rather than from the data. I have seen this happen. In the 2026 auction, when I logged every lot against its base price, I had a framework — "who paid how much extra." But the framework was not the story. The story emerged when I called agents at night and asked who had been outbid and why. If I had just kept filling the framework, I would have had a graphic, not a story. That is the danger in the next version of this report: eight sections, tables, and if two or three facts arrive tomorrow, there will be pressure to fill every cell — even where there is nothing worth filling. Test cricket conclusions will land in the T20 cell, home-ground advantage will be unadjusted while averages are quoted, and a career will be decided on a single-match sample. This is the same "auction sugar rush" I guard against in my own writing — one rule per auction story, traced to who benefits and who is quietly excluded. So my suggestion is that before this report is re-run, a new section be added to its framework, called "diagnosis of input failure." It should ask three questions: where is the raw Stage-1 output? which of its fields were empty and which were populated? and what kind of emptiness was it — absence, unreadability, or inconsistency? Without asking these three questions, Stage-2 will keep returning to where it is today: a beautiful empty scaffold, reporting on its own emptiness. I remember that in 2026, when eleven reporters across four cities shared documents, we made a rule — no scoop at the price of a source. That rule slowed us down, but it kept us from being proved wrong. This report needs the same rule: no conclusion at the price of a cell. What next? The most interesting question for me is not when this report will be filled. It is whether, when it is filled, the person or machine filling it will remember what the emptiness taught. In cricket we often remember the innings that were built, and forget the ones that ended without a ball bowled — to rain, bad light, or the toss. But sometimes that unfinished innings tells you most about what the pitch was like. This report is that unfinished innings. Reading it tells you nothing about cricket, but it does tell you what those who write about cricket should not do. And perhaps that is its greatest contribution.