No 'Analysis' on Empty Input: An Audit Report from a Cricket Data Desk

On Tuesday afternoon, at my desk in Liverpool, I opened the Stage-1 output. Article Title: N/A. Article Source: N/A. Article Type: Unclassified. Information Points: an empty list. The Entities Involved field said 'from the information points above' — and there were no information points above. I stopped the stopwatch, opened the ruled notebook, and wrote the first line: there is not a single fact on this sheet that I can reconcile against a scorecard, a press release or a committee minute. This is an audit entry, and it is not about a match. It is about the reporting chain itself. I have been lifting the paper trail of this game for 41 years. I began at The Indian Express in Chandigarh in 2026, covering Punjab through the years of militancy, and the lesson from those years still applies: what survives on paper is what is true; what travels by word of mouth is somebody else's truth. March 2026, Eden Gardens — I was 27, on my first subcontinent assignment, for a Manchester news agency. India chased 252 and slid from 98/1 to 120/8. The press box filed fury; I sat with a stopwatch logging run rate by five-over block — 5.4 down to 2.1 — and tagging every dismissal by delivery type. Since that day I keep a private dismissal ledger for every match I attend, and no report leaves my desk without a phase-wise number. Sub-editors learned to leave space for my table. Now back to the empty sheet. I have one label: cricket_asia. That is all. If I sit down to write a 'deep analysis' now, the only route available is to guess from that label — maybe the Asia Cup, maybe the ACC, maybe some match — and then invent tournament names, teams, scores and quotes. That would not be inference; it would be fabrication. The damage is direct: Stage-2 and Stage-3 would treat the invented entity as established input and carry the error forward, and the mistake would belong to the chain, not to one step. If the output goes public, readers get a cricket analysis that looks sensible and is hollow on facts. Since the 2026 match-fixing crisis I have worked on one hard rule: no allegation without a paper trail. The other face of that rule is this — no analysis without a source either. Because an analysis with no source is also a kind of allegation: against the reader's intelligence. The real problem shows up in the Stage-1 Entities Involved field. It says entities are to be identified 'from the information points above', when that list is empty. The field contradicts itself from the inside. My ledger has a separate column for such cases — this is not 'analyst error', it is 'upstream extraction failure'. The difference matters. If I assume I missed something, I will try to fill in what never existed and then put my name under it. If I diagnose correctly, the fix goes where the fault is — at the input layer. I choose the second route. All my working life I have wanted my byline read as a fact-check, not a hot take. Today that byline rests on an empty sheet, and I will not stuff it with counterfeit goods. What is the minimum input, then. My ledger has three tiers, in order of priority. First and best: the original text. Give me the body copy and I can do the full breakdown straight from it — fact and opinion separated, a checklist of claims, source tier, time sensitivity, slant detection, entity graph. Second: at least three information points, each with what was said, by whom, and when. Third, the floor: title, source outlet, publication time, and a one-line subject. Any one of these and I can begin real work on the standard cricket_asia dimensions: source-tier ranking of ACC/ICC official versus member board versus wire agency versus self-media; time sensitivity against schedule nodes and windows; host-country slant, association politics and broadcast commercial interest; and a relationship graph of players and institutions. That is the work I have done since 2026, and it does not happen without input. There is one lesson here that speaks directly to the cricket data desk. Cricket keeps saying 'data-driven', and most of the time it means a table that looks good. Being data-driven actually means refusing to write when there is no data. That is the same discipline I learned in 2026, when after Hansie Cronje's confessions I spent five months building a database of 340 one-day internationals from 2026 onward — no-ball counts, toss-to-result clusters, collapses in dead rubbers — and then published only the twelve cases backed by a board report or court filing. Thirty-one were spiked for lack of paper. The same rule applies to this empty sheet. The only difference is that there the paper was missing; here the input is. In both places the outcome is identical: publication stops, and it stops for the right reason. There is an alternative route, and I want to state it plainly so there is no confusion. If the original text cannot be obtained right now, I can supply a cricket_asia 'analysis skeleton' or checklist — clearly labelled as a template, not presented as an analysis of any article. It would carry the dimensions I apply to any Asian cricket report: claim separation, source tier, time sensitivity, institutional slant, entity map, and the places where numbers usually go missing. That I can do. What I will not do is present that template as the analysis of a particular match or tournament. Doing so would mean failing my own audit, and I keep a written list of forecasts I got wrong — I am in no hurry to add a new name to it. So the choice is yours. Route A: send the original text or three clean information points, and I will do the real analysis on the standard cricket_asia dimensions — the claims checklist, source-tier ranking, time sensitivity, slant detection and entity graph. Route B: if the text is not available yet, I will give the template, clearly labelled, and fill it when the text arrives. Pick either. What I will not do is write 'analysis' on an empty sheet and call it true. The cricket paper trail teaches me that the most valuable thing is not what got printed but what got held back — and why. Today's hold is my most honest entry. The next line in my notebook is waiting: date, source, and the number that proves the point. When it comes, I will write — late, but right. And if it does not come, this empty sheet will also be a record: the day the data desk refused, because it had nothing to prove. One question for the reader: when you read a piece of cricket 'analysis', do you look for the source list underneath — or only for the shine of the numbers? Because the day readers start asking for sources, the word 'analysis' written on an empty sheet will quietly stop being written at all.