The Empty Field: Why 'N/A' Is Cricket's Most Expensive Data Point

The Empty Field: Why 'N/A' Is Cricket's Most Expensive Data Point

Across the 2026-94 Ranji Trophy season I charted 1,412 overs of nine Gujarat home matches at the Sardar Patel Stadium, Motera, in Ahmedabad. A wagon wheel for every innings, every leg-before appeal logged with the bowler's release point, the batter's stride length and the umpire's initials. Nobody ever asked to read the file. I kept adding to it for eleven more seasons.

That file did not contain a single blank row. The rule was simple: if it was not captured, write 'not captured' beside it and write the time. I came out of a scoring office where leaving a dash in place of a value was forbidden, because a dash and a zero look identical and mean opposite things. Thirty years later I sit at a review desk and watch the same error at scale, only now with broadcast-quality graphics. Cricket's most dangerous data point is not a wrong number; it is the field that was left empty and travelled down the chain as a zero.

The Indian game's record has carried one long structural crack — the distance between what happened and what was written down. The franchise-less career paths before 2026, the Ranji overs nobody televised, the women's matches with no full scorecard until the late 2010s. In that era the scorebook was the only source; the camera arrived and the distance became visible; ball-tracking arrived and the distance became measurable. The trouble stayed the same at every stage — the record never states which part of the record is missing.

The law book is perfectly clear about all of it. No-ball sits in Law 21, leg-before in Law 36, umpires in Law 3. The sixty-second over-rate provision sits in the playing conditions, and its breach is recorded under Article 2.22 of the code of conduct. The DRS procedure sits in an appendix to the playing conditions, with the fifteen-second decision clock and the umpire's-call band. On paper, every procedure has a number behind it. The difficulty is who fills those numbers in, and at what moment the filling stops.

March 2026, M. Chinnaswamy Stadium, Bengaluru. Steve Smith glanced toward the Australian dressing room over a DRS call, umpire Nigel Llong sent him back, India won by 75 runs, and Virat Kohli said he would not call opponents cheats. The papers argued about morality for a fortnight. I spent nine days building a 41-minute video on the review protocol, the fifteen-second clock and the umpire's-call band, then launched a channel purely to publish it. First-month views: 11,400. I answered roughly 300 comments myself.

That match's scorecard has no column recording which stage of the review failed. A DRS review has three elements — pitching, impact, wickets — tested separately, each failure meaning something different. The broadcast summary disposes of all three in one word: 'review lost.' In Bengaluru the decision took longer than the replay, yet the summary absorbed none of that delay. Three distinct failure modes, one word, and no field anywhere in which to record which mode it was.

The umpire's-call band is the cleanest illustration of the problem. It is a deliberate error tolerance in the tracking — an inner margin of roughly half the ball's width within which the tracking cannot overturn the on-field call. As design it is sound; few sports publicly concede their measurement error inside the decision itself. But when a broadcast puts 'umpire's call' and 'review lost' in the same sentence, the viewer is left with no way of knowing whether the system admitted its own error or the player made a bad appeal. Those are opposite events, and they have opposite consequences for the reviews a team has left.

The no-ball department is older and more desolate. Law 21 states that a no-ball adds a run to extras and the delivery is bowled again. That is where the counting splits. A bowler's card can read 10-0-48-1 while he actually delivered 66 balls — six extra deliveries that appear in no column. The tape counts 66, the card shows 60, and no tournament regulation provides a formal occasion for reconciling the two. I kept counting overs for years because the thesis could not be counted; today, when somebody tells me a bowler's economy was 4.80, my first question is which scorebook, and where the re-bowled deliveries went inside it.

Over rate is the only rule where the evidence and the sanction arrive from different places. The sixty-second provision is measurable from the tape, but the penalty is computed at the end of the innings, often from a team manager's sheet rather than a ball-by-ball timestamp log. Which means enforcement of that rule cannot be audited from the footage at all. After Hansie Cronje's confession in April 2026 and Mohammad Azharuddin's life ban that December, I re-watched 60 hours of 2026-2026 one-day internationals and logged 214 no-balls and 41 abnormally slow scoring overs into a private spreadsheet I called the anomaly log. It was never published. The reason was clean: per-over timestamps were not public, so the log was an observation, not evidence. A pattern is an argument and a clip is an anecdote, but a log without published timestamps is worth less than either.

Net run rate carries a convention that appears on no scorecard. A side bowled out is treated, for rate purposes, as having batted its full quota — a team dismissed in 43 overs is computed over 50. The choice is deliberate and has its own logic, but it is applied silently. Tournament qualification can therefore turn on a number whose governing assumption is printed nowhere official. The reader of the table believes he has seen everything.

This is where the media desk reproduces the error the old scorers were trained to avoid. A field is not captured, so it is left blank; the next process reads the blank as an assumption; the third stage produces a full, clean, entirely credible-looking report with every cell filled. That failure mode is hardest to catch precisely because the output looks complete. A missing over, an unstated review element, a wicket with no footage — these settle into the report as zeroes, and nobody interrogates them, because a zero is a number and questioning numbers is thought rude.

The attractive conclusion is that a blank field is a concealment. My own record argues for the suspicion: 60 hours of tape, 214 no-balls, 41 slow overs, and a year in which every argument about the game moved off procedure and onto character. A man who has covered hearings and fixings for decades develops the reflex of seeing design in discrepancy.

But suspicion deserves the same evidentiary bar I apply to praise. Most of the overs missing from India's domestic record were never televised — there was no tape to hide. The women's matches without full scorecards before the late 2010s were not suppressed; nobody was sent to score them. An empty field is usually a capture failure, not a decision to conceal, and conflating the two is the same carelessness I complain about in coverage.

One comparison does real work here. In tennis the Hawk-Eye decision goes on the stadium screen in three frames — where the ball came, where it struck, where it left. In rugby the TMO conversation is audible because the referee's microphone stays open; the crowd is made party to the reasoning, not merely handed the verdict. In cricket the third umpire is inaudible in most boards' broadcasts. The technology is of a similar class, the decision type is the same — the actual difference is the disclosure protocol. Cricket's problem is not measurement, it is publication. We have the tracking; we lack the structure for saying what the tracking found and where it fell silent.

The suggestion going forward is a rule rather than a verdict. Every field not captured should be published as 'not captured' with a timestamp. No zero, no dash, no apology. That is the admission check needed at every link from scorebook to broadcast graphic — no empty field may pass downstream as an assumption. The question that remains: if we can put a ball-tracking frame on a stadium wall in three seconds, what exactly prevents us from stating which of the three elements failed? The day that gets printed, the argument will move from character to procedure — and the anomaly log will probably still have something left in it.