The N/A Report: A Cricket Data Desk's Most Dangerous Output Is a Perfectly Filled Format

That file had eight chapters. Each chapter had a table, each table had measured columns, and almost every column held the same two characters — N/A. Format: N/A. Match nature: N/A. Player and team: N/A. League, governance, crowd mood, market signal — the same. The title field held it too. An analysis report commissioned to deliver a verdict on a cricket match spent eight chapters explaining that it had nothing to say. And while explaining that, it still graded itself: sporting value one star, industry value one star, timeliness value one star, and process risk: High.

I did not find that report incomplete. I found it complete, and that was the unsettling part. In cricket we fear missing data, while the real damage comes from data that looks filled in neat columns and is hollow underneath. The machine assumed the job was done because the boxes were filled.

In 2026 I coded Rising Pune Supergiant's home season for a Mumbai digital desk — MCA Stadium, Gahunje. Fourteen league matches and the final, which Mumbai Indians won by one run in Hyderabad. I logged every powerplay field change by hand, because I had understood early that the franchise needed a memory, not a dashboard. Washington Sundar took eight wickets at 6.16 that season, and that became my case study for how a finger-spinner's release angle dictates a captain's ring field. I banned the word “momentum” from my own drafts and began every column with a field map, a three-number geometry box — ring radius in metres, catcher depth, release angle — and one falsifiable claim. Editors started asking me for diagrams instead of quotes.

So when I read that Stage-2 report, I recognised an old malfunction, only outside cricket. A system reads a source text, extracts title, format, entities and numeric points, then weighs them across eight dimensions. This time Stage-1 came back empty — title N/A, the information-point list at zero, entities unpopulated. What did the system do? It printed the full skeleton of every dimension, wrote “insufficient information” into every cell of every table, and closed with an honest verdict: this is not a cricket judgment, it is a pipeline failure.

The real question is not why the data did not arrive. The real question is why, with no data, the system wrote eight chapters.

Two different kinds of page exist, and one extractor was run on both. A scorecard or live-score page carries format, venue, toss, innings state, the DLS situation. An editorial page carries argument, author stance, a central claim. Feed a score page into an editorial extractor and every useful score line slips past the parser, leaving a shell that looks like an article. The most expensive error in cricket data is not a shortage of data; it is the confidence of the wrong extractor.

The cricket translation is simple. The most useful information in a match often sits on the page we dismiss as boring — toss, pitch moisture, the hour dew arrives, boundary dimensions. In 2026, when stadiums shut, I logged all 7,200 deliveries of the sixty IPL matches staged in the UAE, 19 September to 10 November, to test whether captaincy changes without a crowd. Attacking fields rose; captains hunted wickets earlier in the middle overs because there was no crowd to punish them. That finding came from exactly the material no editorial extractor ever captures.

The second malfunction sits in the report's format. Eight chapters, a risk matrix in each, five columns per matrix, and “unassessable” across all five. A report that fills every cell of every question usually answers none of them. It is the same disease I have watched in commentary boxes: a full rundown, a talking point for every segment, and three hours later nobody remembers what the match actually decided. In that Pune studio during the 2026 World Cup, filing all sixty-four matches, I learned that football and esports share the same panic — and the first symptom of that panic is that we start filling. Belgium's fourteen-second counter off Japan's 94th-minute corner, Chadli's winner in Rostov, only made sense after I broke it into six stills. By then I had already written three paragraphs on it that were entirely useless.

The third and quietest malfunction is the empty time-sensitivity field. No date was recorded anywhere in that report — not the source's, not the analysis's. Data without a date does not rot; it returns. That lesson arrived for me on 19 December 2026, hours after India were bowled out for 36 in Adelaide. I did not file that night. I held the column twelve hours and re-watched the footage, then argued the collapse was technical — seam movement, front-foot press — and the series was recoverable. A finding recorded without a date is not institutional memory; it is institutional waste. That is why every crisis column of mine now carries a standing recovery-path section: three named variables, a date by which each will be proven right or wrong, and a public error log.

The fourth point is procedural, and here the report wrote its most valuable sentence. It said: take no downstream decision on this output; re-run Stage-1 first. It also proposed the cheapest gate — Stage-2 should not execute unless the title is non-null and at least one information point is recorded. That suggestion is the only actionable line in the whole document, and it is equally true that most cricket organisations reject exactly this suggestion. Dashboards photograph well; gates do not.

The real tension is this: when a system has nothing to say, its instinct is to fill, and cricket's filling material is cheap. A “bottler” narrative, a momentum swing, a young batsman buckling under pressure — all writable without a single data point. The gap between the commentary box and the selection room is the same gap as between the data desk and the editorial desk: on one side what is known, on the other what is being said. What was known in this file was clear — nothing arrived. Eight chapters were written anyway. I will not call the report dishonest. I will say it fell into the trap every experienced desk falls into: the blank space is visible, and the hand starts filling it by itself.

The straight read would have been more accurate: the pipeline broke, write it in one line and stop. Instead we got eight dimension skeletons, each proving that it could not be proven. This is the digital form of an old cricket habit — the scorecard filled to the brim with runs, balls, fours, sixes, economy, and no record anywhere of release angle, ring radius or catcher depth. The paper looks finished. The match is not in it.

One thing in that report I liked. It rated its own process risk High, stating that issuing a cricket judgment on an empty evidence base was the only genuine risk in the run. Institutions rarely write that. Its lapse was wrapping the honesty in an eight-chapter format instead of daring to write the truth short. Calling a blank a blank and stopping there are two different skills, and the second is harder.

Next time a cricket desk produces a report that looks complete and polished, ask it one question: how many cells here record the absence of information rather than the information itself. My guess is the answer will surprise you. If it does not surprise you, that is the bigger story — because then your desk has normalised the format. In my next column I will watch one thing: when the first gate goes onto that pipeline, and whether anyone puts a date on it. I trust patterns, but only after I have walked the pattern myself.