Cricket's Blank Cell: When N/A in the Record Becomes Fact

Bengaluru, March 2026. A Test between India and Australia at the M. Chinnaswamy Stadium, and Steve Smith raised his hands for a review — then glanced towards the dressing room. Umpire Nigel Llong sent him back. India won by 75 runs. For the next ten days the television argument ran: was it cheating, what is a captain's duty, what did Virat Kohli say at the press conference.

Not one word of that sequence appears in the scorecard. The scorecard records who was out for how many, who bowled how many overs, who held how many catches. It does not record at which second the review was requested, which frames the third umpire examined, what the ball-tracking margin was. The thing the record does not hold is the thing the argument was entirely about. The scorebook says one thing; the tape says another — and here, nobody logged the tape at all.

To understand DRS you first have to understand what actually happens. A player gets 15 seconds to consult his partner on the field, the referral goes to the on-field umpire, and the third umpire checks three things in order: where the ball pitched, where the impact occurred, and whether the ball would have hit the stumps. In the third step the umpire's-call band applies — if less than half the ball clips the stump in the tracking projection, the on-field decision stands.

Where does that sequence enter the public record? Nowhere. What survives is a single line: review successful or review unsuccessful. A procedure containing three checks, a time limit and a margin collapses into a verdict. After that incident the ICC added a restriction barring players from seeking dressing-room input on reviews. The rule arrived. The blank cell in the record did not go anywhere.

Across the 2026-94 Ranji season I scored 1,412 overs ball-by-ball across nine Gujarat home matches at the Sardar Patel Stadium in Ahmedabad. I drew a wagon wheel for every innings, and logged every leg-before appeal 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. I kept counting overs because the thesis could not be counted.

That habit produced one conviction: a blank cell is never blank. Every downstream calculation reads it as zero, and that zero goes on to fix somebody's average, somebody's economy rate and somebody's net run rate.

Three places where this happens. First, scorecard columns. An empty catches field can mean three different things — a catch dropped, a catch never offered, or a fielder who never got a hand to it. All three look identical in the record. No-ball counts often never get a column of their own in domestic cards; they land in the bowler's figures or in nobody's. Not out and absent hurt are tallied the same way.

Second, over rates. The rule sits in the book, the equation exists, but enforcement is discretionary. The record does not tell you which match was actually counted and which was waved through. Information never captured cannot be reconstructed later. In rain-reduced matches the basis of the net run rate calculation itself changes, and that changed basis never travels with the published scorecard.

Third, and most telling — women's domestic cricket. Until the late 2010s, full scorecards did not exist for a large number of women's matches. This was not a conspiracy; it was a structural silence. Nobody judged it necessary to record. Researchers working that era still meet empty cells.

This is where the real problem sits. An N/A travels through every downstream system as a value. If a bowler's overs were never entered, his economy rate drops out of the calculation or comes out wrong. If a match result is missing from the record, a team's net run rate is built without it, and that same NRR later eliminates somebody. No system announces that the data was absent. It proceeds quietly, and the output looks complete. This is the hardest failure mode to trace, precisely because the finished product looks finished.

In Bengaluru the decision took longer than the replay, and the record carries no trace of it. The anomaly log began as a place to put what did not fit the official account. In 2026, when the fixing argument was at its peak, I watched 60 hours of tape and logged 214 no-balls and 41 abnormally slow scoring overs. That sheet was never published. It taught me that a pattern is an argument and a single clip is an anecdote — and that the record's silence is itself a pattern, not an accident.

Everyone in that March argument asked about intent. Whether Smith looked deliberately is not establishable from the tape, and ruling on what is not establishable would contradict the method. The real failure was not intent. The real failure was that at that moment no procedure was determining what was permitted, because a clear rule for that situation did not exist. The rule came afterwards. We spent ten days on a player's state of mind while the system carried an empty cell.

The same evidentiary bar applies to me. The habit of correcting the record becomes an identity, and identities start manufacturing corrections for their own sake. If the official account is right on the tape, that has to be said in print too — and the anomaly log records that as well.

The forward question is not who wanted what. It is whether cricket can publish a review log with timestamps — when the review was requested, who came to advise, which frames the third umpire saw. Until that log exists, every dispute will be fought in the language of intent. A referee's eye is just a habit of distrusting the first angle, even when the first angle is the official one.