Evidence First, Template Later: Why Cricket Reporting Must Never Read 'N/A' as 'Low Risk'

An eight-dimension analysis report landed complete on my screen on Monday morning. Every heading in place, every table with its cells, every cell counted. And in each of them the same line repeated — N/A, insufficient information. Above, the title slot empty, the source slot empty, the list of information points flat. Of eleven mandatory inputs, nine had not arrived in any form. A document that looked finished and stood at zero in evidence. Cricket has been here before: the paper full, the case hollow.

The payload that reached me contained not one cricket name — no team, no player, no venue, no date, no format. Only a label saying the sport was cricket. Having watched this desk work for thirty-five years, I know that the correct answer to an empty file is not analysis but diagnosis. The first job was to establish which things were missing and, among them, which ones made any downstream conclusion dishonest.

Four things were missing at ground level. Format — Test, ODI, T20 or The Hundred. Venue and date. The player and his role. Source and time of publication. The first is the most damaging, because cricket's three formats do not share a scale. A Test batting average is a stronger signal than a T20 strike rate, and an ODI strike rate demands a third scale of its own. With format undetermined I cannot even say whether the sixth over of a powerplay matters or the eightieth over of a Test innings. Format is not a soft gap but a hard block — without it no figure can be read at all.

I pulled the first precedent ledger and found the hinge of the case. The Mike Denness file of 2026 had taught that the Code permits a match referee to decide some things and not others — that file did not settle the argument, it taught us where to look. Thirteen years later, the 2026 spot-fixing investigation made the two-column rule compulsory for me: on the left, what the charge sheet alleges; on the right, what the board's disciplinary committee is actually empowered to rule on. Two columns, one incident — the gap between them was the whole story.

The same two-column rule now applies to this empty report. Left: what is not recorded. Right: what I can derive from it. The right column answers — nothing. An absent information point and an absent risk look identical on the page, and that is the deepest flaw in this whole exercise. If a review records that no anti-corruption item surfaced, the reader will read 'low risk'. The truth is that the risk was never measured. After the Lodha Committee report of January 2026 I adopted a discipline in my own writing: never use the word 'guilty' in a board inquiry until the written order is published. By that same logic, a category may be marked low risk only if it has been measured. Otherwise the cell stays N/A.

The third absence was the date. Everything in cricket decays fast — form, rankings, auction prices, injury status. An undated analysis cannot be safely reused, however handsome its tables. I remember the summer of 2026-21, when the IPL moved to the UAE — sixty matches, no crowds, and a biosecure SOP that invented a category called 'protocol breach' with no precedent and no written appeal route. I first filed that SOP as administrative noise and had to correct myself in print. That same year the board cancelled the 2026-21 Ranji Trophy — the first season without one since 2026-35. One lost first-class season strips an entire layer off the evidence base for selection, and a report with no date is deprived in exactly the same way.

From my years of watching matches I have learned that the data desk's argument always begins before the field's argument. In 2026-18, when I moved from print to a digital desk, I logged the first IPL season with DRS — one review per innings, sixty matches. Every review recorded: who took it, on which mode of dismissal, and whether ball-tracking or the on-field umpire's call settled it. The finding was unglamorous — the hardware was sound; the outcome depended on the third umpire's console workflow. I audited the DRS trail and understood that discipline begins at the moment the finger reaches the pause button. Since then I keep a short paragraph in any story resting on technology — ball-tracking, Snicko, a broadcaster's super-slow replay — stating how reliable that evidence is. I stopped treating a broadcast graphic as a fact.

That discipline now splits my ledger into two parts — one for conduct, one for regulation. The regulation tab holds every playing-condition and auction-rule change, the date it took effect and the season it first bit. The Impact Player arrived in 2026, net run rate formulas have been revised more than once, DRS protocols amended. A writer who knows a rule by heart and does not stamp its version will miscite it without noticing. At the IPL 2026 mega auction in Jeddah on 24-25 November 2026 I wrote the hall's mechanics rather than its money — ten teams, an Rs 120 crore purse, the returning Right to Match card, the accelerated round, and the bid increments that let a side holding two RTM cards shape a market. Rishabh Pant went to Lucknow Super Giants for Rs 27 crore, Shreyas Iyer to Punjab Kings for Rs 26.75 crore. The rest of the hall wrote money; I wrote which clause made that money.

Back to the empty payload. Everyone will agree the problem is missing information. My reading is different. The real trouble is that the scaffolding survived. Eight dimensions, tables, categories — all standing intact, and that is the trap. A framework that renders cleanly on empty input will render even more cleanly on bad input. A fully populated template often creates the appearance of diligence while removing the space to probe. Refusing this file is the correct answer, and better than printing a provisional verdict.

The second counter-intuitive point is that Indian cricket's loudest debates were born not from missing data but from misread clauses. DRS, net run rate, the Impact Player — most of these rows are rule interpretation, not arithmetic. And when that same data chain travels forward into betting and fantasy markets, the most important thing on the page suddenly becomes the date. The digital desk changed the timestamp, not the standard of proof.

When the next report reaches my desk, my first questions will be unchanged — which format, what date, which source, and in what role. Give me those four and all eight dimensions will start speaking. Without them the tables stay full and the case stays empty. The question is this: if a report can look complete without a shred of evidence, how is a reader to tell which report has been read and which has merely been arranged?