Empty Extraction, Empty Story: A Beat Reporter's Lesson on the Cricket Beat

After twenty-seven years on the cricket beat, I have learned one thing above all: you cannot write a story that isn't there on paper. Last week an analysis report landed on my desk with a headline that said everything: the Stage-1 result is empty. No title, no source, no summary, and an empty list of information points — only a domain label survived, 'cricket_world'. My colleague read it and laughed. 'Sir, this isn't even a story.' I told him, no, that is the story — and perhaps one of the biggest lessons in today's cricket media. The report stated plainly, in five places, that there was no data. Article type undetermined, author stance undetermined, purpose undetermined, time sensitivity unassessed, source quality unassessable. Only one thing survived — the domain label. The report also made clear that inferring the cricket story from that single label would be a guess among thousands of possible stories, and it declined to do so. That honesty is what I liked. Back in the 1980s, when I started on the print desk, saying 'no story found' took courage few showed. The page had to be filled, so some story always got made. Now look at today. When I return to the IPL franchise beat these past months, the same problem appears in another form. On auction day every channel runs the same graphics — purse, retention, the ₹1.55 crore fee. And when you step out of that room, you know the real story was in the corridor outside. I remember my team-hotel diary — Johannesburg 2026, thirty-six days in the same hotel, and a signing already homesick before the medical. That story was in no scorecard. It was said quietly in the hotel lobby on day twenty-six, and it took thirty-two days of being there to catch it. Back to the analysis report, because the five empty fields it left are the five pillars of cricket reporting. First — title and source. Every big cricket story has a source behind it: a board press release, a franchise media note, a coach's phone call. Without a source a story is only rumour. Second — article type. A Test match report, a T20 analysis, auction coverage, an injury story — each has its own skeleton. Third — author stance. Is the reporter neutral, praising, or questioning? Fourth — time sensitivity. Every cricket story has a date; an injury story before a series is worthless after it. Fifth — source quality. A board's official statement and a WhatsApp forward are not the same thing. The report wrote 'N/A' in all five. Seeing it took me back to my old office days, when we had a teleprinter. Sometimes only half a story came through — 'India won the toss and...' — and the rest of the line broke. Then we had to decide whether to print that half story. The good editors held it back; the bad ones filled the rest from guesswork. The same lesson applies to today's analysis pipeline, except the teleprinter has been replaced by an extractor. The report went on to list five likely causes, and this part I liked most. First — the input never reached the extractor. Empty body, or the fetch returned a paywall, consent, or login page. Second — schema mismatch. The model emitted prose, the parser dropped it, fields fell to 'N/A'. Third — the input was never an article; it was a scorecard, live-commentary feed, video page, or listing page. These structurally have no stance, so the empty fields may be correct, and the pipeline should reject rather than escalate. Fourth — the domain label came from a fallback, not real classification. Fifth — source quality could not be assessed because there was nothing to assess. Of these five, the fourth frightens me most. If a label like 'cricket_world' comes from a default, the whole system stands on the very guess the report refused. In cricket, one label cannot tell us what a story is about. 'cricket_world' can say the story involves cricket, but not whether it is international cricket, domestic Ranji, the IPL, women's cricket, or a cricketer's private life. And that is why the report declined to guess. This attitude reminds me of my time at total-cricket.com in the early 2000s. We had no automated system. A human read every story, checked the source, and then decided whether to publish. Today, when an analysis pipeline refuses so cleanly, I feel it preserves the honesty of that human editor. Building a story from empty data is the easiest work — and the most dangerous, because no one challenges that story, no one checks the source, and the reader takes it as truth. Now the part I watch most in my own work — the report said that to proceed, at least one of three things was needed: raw article text, populated information points, or title, source and publish date. This is exactly what I demand before writing a match report. Someone tells me 'RCB made a big deal' — that isn't enough. I need the date, the fee, who the deal was with, and who confirmed it. Without these I cannot write, and even if I did, it would not be journalism. The report said one more thing that matters enormously for cricket reporting — it asked what the downstream consumer needs. Fact-check, summary, entity graph, or bias read — each purpose has a different analysis shape. I learned this through my career. In 2026, when I spent eleven weeks on the Karnataka team bus, my goal was one thing: the match story. But the three hundred words of unprintable detail I wrote before every match in my scene book served a different purpose. Editors cut most of it. Yet that habit paid off later, and it is why I was handed a franchise beat nine years on. In both places the question was the same — what story are you looking for, and what evidence do you have. Cricket has some famous examples of claims printed without evidence. The 2026 scandal, or retirement rumours about a player — it always happens the same way: someone prints 'sources say' and later the source vanishes. The empty analysis result is the opposite. It says — I have no evidence, so I make no claim. In twenty-seven years I have heard very few editors speak so clearly. But here is an interesting turn, and I want to pause on it. An empty result repeated again and again becomes a different story. The analysis report itself says the input may never have reached the extractor, or a paywall page appeared. If this keeps happening, the issue is not the cricket story but access to it. And that is a familiar topic for me. In 2026, when the IPL was suspended and I reported during lockdown on the two hundred-odd casual workers at Chinnaswamy — groundstaff, scorers, camerapersons — our real crisis was that the story was out of reach. I built a WhatsApp pool of forty beat reporters so shrinking access would not become shrinking information. The same lesson applies to the extractor — if access is gone, build new access, don't fill the empty space with guesswork. You may be wondering what all this has to do with one empty analysis report. In my view, everything. In recent years cricket media has adopted a habit — fast news, fast analysis, fast verdicts. Player-of-the-match analysis twenty minutes after the match, a 'winners and losers' list the day after the auction. What is missing in all of it is the ability to recognise empty space. The good news is that an empty result is also a statement — it says the system knows its limits. The bad news is that most media houses will not accept that limit, and fill it with guesswork. Recall the 1980s, when the print desk had a rule — 'when in doubt, don't write.' Today the rule is reversed — 'when in doubt, make it breaking news.' But one thing never changed. The reader always knows which story was written carefully and which in haste. Cricket readers especially are alert, because they watch every match. They know a story from the training ground differs from a press conference. Now the final question the report left open — if the Stage-1 pipeline itself is broken, send the raw extractor output and parsing code, and I will trace where the fields drop. This is not merely a technical request; it is a reporter's request. For twenty-seven years this is what I have done — from teleprinter to WhatsApp pool, I have always traced where the story fell. Sometimes it was bad language, sometimes source pressure, sometimes deadline hurry. Today that same work is called analysis. An old notebook still sits on my desk, holding more names than scorecards. Many of those names are in no record book — trainers, physios, bus drivers, scorers. That notebook feels truer to me than this empty report. Because it knows what should be written and what should not. And if one empty analysis can teach us that recognising empty space is itself a craft, then perhaps we should see it less as a failure and more as a lesson.