You Cannot File a Match Report From an Empty Notebook

In 2026, at Delhi's Ambedkar Stadium, I carried a 96-page notebook into the ONGC Nehru Cup final: India 1-1 Syria, 5-4 on penalties. I counted 23 throw-in sequences and 11 second-ball recoveries. That count was the report. Had the notebook stayed blank, I would have filed a colour piece the next morning, and I would have known it was a lie. That is why, when an analysis file was placed in front of me with N/A where the title should be, N/A for the source, and a completely empty information-points list, my first act was to put the pen down. The only solid item in the file was a domain label: cricket_world. That is a routing tag, not news. It tells you the system classified the matter as cricket; it does not tell you what happened in cricket that day. There is an old rule I learned in my first year at Mid-Day in 2026: you do not put a byline on something you did not see and cannot document. The notebook says one thing, the replay says another — and when neither exists, the question is not which to trust. The question is what to write. This is not performed caution. Before the 2026 Asian Cup I built a 54-page file on Bob Houghton's India: the direct 4-4-2, the set-piece routines, the 18 line-breaking passes India conceded per game. That file was careful but it was not empty. It held three scorelines and counted actions, so a conclusion was available and I drew one. Here the material is zero, so no conclusion is available. The two situations are not the same, and pretending otherwise is dishonest. An empty file is the most dangerous file, because emptiness leaves room, and deadline pressure fills room fastest. You guess, attribute it to 'sources', and three hours later the guess is another outlet's headline. This is the dirtiest layer of sports datafication: unverified numbers enter betting feeds and never come back out. When I do not have a count, my job is to ask for the count, not to invent one. So here is the gap, stated plainly. I need the match or series name, the date, the venue; both XIs or squad sheets; the scorecard or an over-by-over summary; and three to five hard facts rooted in an official source, a board release, or a named person's quote. The original article is best — I will re-read it myself, extract the facts and test the claims. Once that arrives, the order is fixed: normalise the entities, separate fact from quote from inference from evaluation, grade the sources, check the dates against today, and only then talk about the pitch — the length the ball landed on, seam position, which over the DRS review came in, and the moment the required rate turned. One more thing. If this empty output came from an automated pipeline, the pipeline needs repair first: a failed scrape, an unmatched parser, or a source so short it was only a headline. Until that is fixed, every downstream layer spins in air. Fix Stage-1 before discussing Stage-2. One page in my notebook has stayed blank since 2026. I do not write on it to fill space. It will fill on the day the right number arrives — because once a wrong figure is printed, the replay never forgives it.