The Empty Dossier: When 'N/A' Is the Most Honest Answer

Nine tabs. Forty-seven rows. And one entry repeated two hundred and fourteen times — N/A: insufficient information, assessment not possible. This was not a scorecard. It was an analysis file that landed back on my desk early this season — title blank, source blank, summary blank, the list of information points bare. A tag sat on top: cricket_asia. Where the contract names the category “Cricket,” a geography tag had been substituted. That could be a routing fault; it could also be the half-finished edge of a story about an Asian board, an ACC event or the South Asian market. The difference matters, because one is a report and the other an inference. Behind the file was a person. A twenty-year-old uncapped left-arm spinner with a T20 economy of 7.9. One desk called him “excellent,” another “expensive.” Both looked at the same number; neither checked the format field, neither asked for the phase split. What his next auction is worth will rest on a sentence someone finalised at 11:40 pm. The dossier had a page missing. That page was the story. Cricket’s documentation ladder thins as it descends. The IPL records nearly everything — squad lists, trade windows, the forensic detail of broadcast contracts, the right-to-match clause. At international level the ICC publishes playing conditions, match-referee reports, the DRS protocol. In the Ranji Trophy the same space is empty: no traceable match report, no published method behind a pitch rating, no hearing record. The lower you go, the less the evidence and the more the explanation. The first gate in that entire structure is format. A strike rate of 145 is elite in ODI, ordinary in T20, and meaningless in Test, where the currency is survival rather than speed. The term itself hides a trap: for a batter it is runs per 100 balls, for a bowler it is balls per wicket. Printing the words without saying which is the most common analytical error in the trade. Bowling currency is format-specific too; in T20 an economy under 7 is generally read as excellent, and the two phases that decide those games are the powerplay (overs 1–6) and the death overs (16–20). When the format is not fixed, the five-pillar governance checklist goes inert. Power and revenue distribution cannot be framed without the Big Three; a playing-rule dispute needs a DLS or DRS reference; an integrity question needs an ACU signal; eligibility needs an NOC or residency question; politics needs a cross-border flashpoint. All five blank. I watched that replay forty-seven times — Newlands, March 2026. The hostel laptop was buffering and Cameron Bancroft’s hand held sandpaper. Opening Article 2.2.1 of the ICC Code of Conduct produced two scales: Steve Smith and David Warner took one Test each from the ICC and twelve months each from Cricket Australia; Bancroft collected three demerit points and nine months. Watching again did not change the finding. What the replay cannot show has to be written down. October 2026, Dubai — Kings XI Punjab against Delhi Capitals. A square-leg umpire called a short run on Mayank Agarwal’s second; Punjab finished level, lost the Super Over, and the table moved by a point. What got written that night about Law 18.3 came down to this: the on-field human estimate sits outside every review protocol. A replay loop is not verification; it is repetition. Then the role question. A finisher is judged on a strike rate north of 180, an anchor on average and balls faced. Assess without fixing the role and you have committed a category error. The batting peak is placed at 27–33 and the fast-bowling peak earlier, but no age curve applies without a named individual, an age and a career line. The home-away differential is cricket’s largest structural variable and here there is no venue at all. Stripping toss and DLS luck requires material that does not exist. Bench depth, age structure, the pace-spin ratio, NOC status, an auction right-to-match clause — the same empty cells. The most dangerous sentence in governance is: “no risk found.” An unassessed risk is not a low risk. Treating silence in an empty payload as a clean chit is exactly how integrity questions go unflagged. The absence of an ACU signal does not say nothing happened; it says the page never arrived. Which brings back the old argument about “average.” In February 2026 the third India-England Test at the Narendra Modi Stadium finished inside two days, seventeen wickets fell on day two, and match referee Javagal Srinath rated the pitch “average” — no demerit points, no published methodology. Where that rating is appealed remains undocumented. The issue is not the algorithm; it is the process. The pipeline-failure signature is visible — null title, zero points, “not assessed” everywhere. That happens when the source sits behind a paywall, the page is JavaScript-built, the content is image or video, or the extractor drops a non-Latin script. A file that looks filled in while every cell reads N/A is more dangerous than an outright failure, because someone will read it. A filled-in shape and an empty evidence base cannot be treated as the same fact. What survives is a list worth keeping. The Indian market’s share of global cricket revenue above seventy per cent, IPL owners spreading into SA20, MLC and ILT20, the stickiness of fantasy sports, the 2028 Los Angeles Olympics calendar squeeze. These are the framework, not conclusions drawn from this file. Printing them as conclusions is the same error as mistaking a geography tag for a category. The easy inference is that the machines do not understand cricket. Look the other way: this time the machine did what the human usually will not — it refused. The story was fabricated not by the pipeline but by the market. A filled template gets published; an N/A gets a phone call. Commission pressure rewards completeness over correctness, and the sub-editor who set the valuation at 11:40 pm sits inside that economics. There is a second trap. Treating every gap as concealment is as misleading as missing a real one. Three kinds exist: no record was ever made, the record exists and is withheld, the record exists and is boring. Writing all three the same way is a reporting failure, and the reader never learns which one they were handed. The gap in this file belonged to the first kind — a pipeline gap, not a cover-up. That distinction has to reach the reader, or the next genuinely withheld document will also be read as a technical glitch. The fix ahead is cheap. Make a format field mandatory before any metric is quoted; state whether a strike rate belongs to a batter or a bowler; and publish the method behind the “average” rating with a clause number, the way a charge sheet carries one. The question is not whether the rating should be harsher or softer. The question is: with no published methodology behind it, in which file does the appeal get logged?