When the Machine Has Nothing to Say: Cricket's Null-Input Problem and the Verdict Nobody Admits To

The screen went white just as the biggest board in the ground lit up in front of a hundred thousand eyes.

The third umpire said something into his headset. His lips moved; no sound reached us. The ball-tracking graphic drew half the ball's path and stopped, then a small line appeared in the corner — technology unavailable at this venue.

In my hand: a notebook, a pen, a watch. The on-field umpire had given it out. The question was simple. Where is the evidence? The answer was simpler and far more uncomfortable: there is none, so the on-field call stands.

Nobody made that decision. It arrived out of an absence. And that absence is cricket's least examined, least written-about, most consequential verdict. The laws tell us in detail what happens when the machine says yes and what happens when it says no. What happens when the machine says nothing — that is where the law lowers its voice, and where all of us quietly agree that no decision was taken at all.

Thirty-six years of sitting between the field and the screen have taught me this: cricket shouts loudest about technology's errors and speaks least about its silences. The second happens far more often.

When the machine goes quiet, the verdict that results is the most unprotected verdict in the sport — because there is no reasoning behind it, only a default.

Context: the apparatus that taught cricket to judge

DRS was first used in a Test match in July 2026, at the Sinhalese Sports Club in Colombo, between Sri Lanka and India. Before that, an umpire's word ended the argument. In two decades cricket has built a parallel judiciary — ball tracking, UltraEdge, Snickometer, HotSpot (now retired), and now frame rates, live pitch maps, expected-run models.

The entire structure rests on one assumption: input will arrive. Cameras will turn, sensors will fire, feeds will not break.

Feeds break. Rain arrives, lenses bead with water. Some venues have no Snickometer at all because the host broadcaster's contract never included it. When the ball climbs high, the projection becomes uncertain. And when the graphics fail to load at the exact instant ball meets pad, a million people want an answer and the system holds zero.

The 2026 World Cup was played without DRS — a whole tournament of declared absence, known to everyone in advance. There was a kind of honesty in that. Today's problem is harder, because the machine is usually present. Its absence is no longer the rule but the exception, and nobody prepares for exceptions.

That exception needs a name. I call it null input. The question went to the machine; no answer came back.

Modern cricket journalism is bound by the same thread. Scorecards arrive from feeds, ball-by-ball from APIs, pitch maps from a supplier's server. Break one link and the reporter is holding an empty payload. And the easiest, most dangerous thing to do with an empty payload is to fill it.

1. Where the law falls silent, the default is the judge

ICC playing conditions limit the third umpire carefully. He may overturn only with conclusive evidence. Without it, the decision stands. The logic sounds generous — the benefit of doubt goes to the player, or to the umpire.

But ask whose side the default actually serves. Say fifty marginal lbw calls in a series. Twenty go to review. Eight of those produce no usable data. In all eight, the field call survives. The calls surrounded by the most doubt receive no new information at all. The default does not cancel error; it accumulates it, and it accumulates on one side, because an umpire's bias does not change within a match.

The calls the technology is least sure about are the calls that matter most — and that is precisely where the law goes quiet.

Umpire's call is the most attacked rule in the sport, yet it is the only clause that publicly admits a model has an error margin and that inside that margin a human verdict stands. Null input does not even grant that much. There is no declared margin, because no model is running — only a gap, which the letter of the law then fills.

2. Trent Bridge, 2026: the machine was fine, the wallet was broken

July 2026, first Ashes Test. Stuart Broad on 37 edged Ashton Agar to Michael Clarke at slip and stood his ground. Australia had no reviews left; they had spent them. HotSpot later showed the edge. Australia lost by 14 runs.

The usual reading is that Broad failed the spirit of the game. From the referee's chair the real event is different: the technology was present and working and held the correct answer. What was missing was the right to ask the question.

That day the machine was fine; what was broken was the human review budget.

This is the second form of null input, and nobody files it as a technology failure even though the outcome is identical. A review is a scarce resource. Two or three per innings means two or three corrections available per match. The question stops being what is true and becomes whether I still have the currency to find out.

Cricket never publishes that ledger. Football logs its VAR checks; across 64 matches in Russia in 2026 I charted 455 of them, purely so the answer would exist in my notebook if anyone ever asked. Cricket has no public register of which umpire has been overturned how often, or which venue has failed to deliver technology how many times. Where there is no ledger, there is no liability.

3. Bengaluru, 2026: when the machine speaks, who vouches for it

March 2026, second Test. Steve Smith lbw to Umesh Yadav for 28 in the second innings, reviewed, ball tracking upheld the call. Australia's anger was not aimed at technology but at the projection — whether the modelled path after impact was true or inferred.

That is the honest crux. The part of ball tracking people trust most is the part least observed. Up to impact, cameras watch. From impact to the stumps, a model draws.

Ball tracking is a model, not a photograph — and a model that will not publish its uncertainty earns suspicion that is not ignorance but reasonable distrust.

Cricket has never printed those error bars. Football's goal-line technology answers in centimetres; cricket's ball tracking says "hitting" without saying how far inside, at what margin. So the argument leaves the data and settles into tribe — India against Australia, batter against umpire.

Russia taught me this. In 2026 the replay did not argue; it showed me my blind spot. One angle I could not have had from the field, and it wounded my confidence. Cricket gets that angle sometimes and not others, and we deliver the verdict with identical certainty either way.

4. Lord's, 2026: the letter of the law against the feel of the ground

14 July 2026, World Cup final. England 241, New Zealand 241. Super Over tied. England champions on boundary count, 26 to 17.

The most argued moment is the fourth ball of the fiftieth over. Ben Stokes dives; Martin Guptill's throw deflects off his bat to the boundary. Six runs — two run, four boundary. The letter of Law 19.8 was correct. The feeling was not. MCC amended the law effective 1 October 2026: an unintentional deflection to the boundary now yields five, not six.

The amendment is right. It arrived three years late. That lag is the point. Cricket's law-making is reactive but it exists, because a law has a text and a text can be rewritten.

A law can be amended because its text is written. Null input has no text, so the question of amendment never arises.

Nobody has ever written: where Snickometer is unavailable, the following procedure applies to caught-behind reviews. Nobody has ever published: this many reviews failed on technological grounds last season. A rule that was never written cannot be appealed against.

5. Arnos Vale, 2026: an unfinished match, a complete result

24 June 2026, T20 World Cup. Afghanistan 115 for 5. Bangladesh 105 for 5 in 17.5 overs. Rain.

The match never finished. The result was perfectly complete: Afghanistan by 8 runs on DLS. The scorecard looks like a finished match.

An unfinished match can still yield a complete result — if somebody decided in advance how incompleteness would be calculated.

I am not arguing against DLS, which is an extraordinary model. I am arguing about transparency. The live screen shows the par score; the match report shows only the final number. In May 2026 I called Borussia Dortmund 4-0 Schalke from Delhi into an empty Signal Iduna Park, referee Deniz Aytekin's whistle echoing, and I logged 22 fouls and 4 yellow cards simply because the sound needed recording. The empty stadium taught me that silence can be the loudest decision. Cricket's silences do not look like empty stadiums.

6. When the feed breaks, the reporting breaks

Every modern cricket desk sits on a pipeline. When it fails, there are two paths: write that the information is unavailable, or fill the gap with inference. The second is easier because readers cannot tell. An empty payload and a full one look nearly identical on the page.

An empty payload and a full one look the same — and that resemblance is the biggest trap in sports journalism.

I have fallen into it. In 2026 in Delhi I called all 52 matches of the Under-17 World Cup live — England 5-2 Spain in Kolkata, Rhian Brewster's eight goals, Phil Foden's Golden Ball, Sergio Gómez in the tenth minute, Brewster's equaliser in the forty-fourth, 1.1 million views. I thought I knew the whistle until Delhi hummed in binary. And under that success I shelved a follow-up on referee Enrique Cáceres' appointment, because I did not have the material. The next year in Russia I began timestamping every check.

The most important sentence in journalism is "I do not know." A report that admits the gap can be verified later. A report that fills it reads convincingly once and collapses on the second reading.

The contrarian angle: more technology is the wrong question

The reflex is to demand better machines. The real gain from 500 frames to 1,000 is small, because the problem is procedural. Most of the damaging errors I have seen were process errors — the wrong person reviewing, the wrong question asked, the wrong time budget, nobody confirming the venue's equipment was live.

And the unpopular second point: umpire's call is the most honest two centimetres in the sport, the one place where the system publicly concedes its answer is not perfect. A system that cannot admit uncertainty can become more precise without becoming more trustworthy.

Takeaway: who writes down the silence

Publish a null-input register after every international match — over, umpire, type of technological failure, and the default applied. Aviation publishes every instrument failure because the industry learned that hidden failures repeat. Cricket has not learned it yet.

The machines will improve. The silence will remain. The whistle does not tell us who wins; it only asks who is keeping the record of what was never said.