The Empty Data Package: When a Cricket Report Contains No Cricket

This report is not about a match. It is about the process in which the match's information went missing. The file that opened on the Sydney desk on Monday night had 'N/A' where a title should be, 'N/A' where a source should be, and a completely empty list of information points. Format undetermined. Team undetermined. Player undetermined. A document that should have separated Test from ODI from T20 could not name any of the three. Cricket produces such things. A not-out batter's scoreboard sometimes shows only an asterisk. But behind that board sit eleven people, forty-two overs and one captain's decision. Here the back half did not exist at all — no overs, no pitch, no weather, no DLS, not a single over I could watch again. Hand a package like this to an analyst and there are two roads. The first is to fill the template — average, strike rate, economy, bench depth, broadcast-rights value, all stamped 'not available'. The second is to fill those boxes from memory of some familiar match. The second road is faster and entirely wrong. There is a real risk here, and it sits not on the field but in the pipeline. If this empty package travels into an automated system, every 'N/A' can later be read as 'no risk present'. No injury information supplied does not mean the player is fit. Absence of evidence and evidence of absence are different things. In cricket, that difference decides series. I keep eleven diagrams beside me because the game always leaves a twelfth in the air. This time there was not even a first one. Next time the file arrives, let it carry a date, a format, and one over I can call by name. Until then this page is better left empty.