An Empty Report Is Not a Clean Chit: Auditing Cricket's DRS Evidence Chain

Nineteenth over, fourth ball. Left-arm spinner, on the batsman's pad line, the keeper goes up. The appeal goes up, the umpire shakes his head. The captain looks at me — that fifteen seconds. UltraEdge comes up flat on the screen, ball-tracking shows the ball grazing the outside of leg stump, and the third umpire says: "Not out, on-field decision stands." A wave of relief rolls around the ground, as though the batsman had been acquitted.

In my logbook the entry reads differently. I wrote: no evidence found. That sentence is not the same as "there was no evidence," and cricket — especially in these weeks of the transfer window — runs on treating the two as identical. The captain who burned that review will burn another one, because he was told that "nothing found" meant "nothing there." And the same sheet of paper sits on the table in the meeting where a retention list is decided: name filled in, numbers blank.

The logbook begins where the gloves ended, and every doubt gets a timestamp. My own logbook opened in Delhi in 2026, when a split finger took the gloves away and pushed me from the scorebook towards the camera. I did not know then that the skill I was learning — deciding from footage — would become the least audited part of cricket.

The law, and the story

The whole architecture of DRS rests on one sentence, and that sentence is not in the Laws. It is in the protocol: the on-field decision stands unless there is conclusive evidence to overturn it. Note what is being decided. Not truth. Whether there is evidence sufficient to change a call. Those are different questions.

The count is clear: two player reviews per innings in T20Is and ODIs; two per innings in Tests, replenished after eighty overs. That count quietly reveals something simple — a review is a resource, not a right. Something that expires in four overs is not something you spend with total confidence in any over.

The third umpire's toolkit is short and its limits are wide: UltraEdge (microphone-based spike detection), ball-tracking, split screen, real-time Snicko. Each tool answers one question and stays silent on the rest. UltraEdge tells you whether a sound arrived. It does not tell you whether the sound came from bat, pad, or the keys in a fielder's pocket behind the stumps.

In 2026 the ICC scrapped the soft signal for low catches. It reads like a small change. It moved the centre of gravity of the whole system. Under the soft signal, the field umpire offered a guess first and the third umpire hunted for evidence to overturn it. Now the third umpire has to reach the first conclusion himself — evidence replaced the guess, and the responsibility grew with it. A soft signal is just a story the field is still telling. The signal went; the story did not. It sits in the commentary box now.

My own fifteen-second tree grew out of exactly this spot. Three questions: what can you see? What was the on-field call? What does being wrong cost? If all three answer inside fifteen seconds, burn the review. If not, don't. Fifteen seconds is not a deadline; it is a shape for deciding.

Three states of evidence, one scoreboard

The real problem here is vocabulary, not technology. DRS has three entirely separate conditions, and the scoreboard folds all three into one word: not out.

First: evidence arrived and overturned the call. A clean case. Second: evidence arrived but was not enough to overturn — less than half the ball hitting the stumps, umpire's call. Third: no evidence arrived at all — flat UltraEdge, wrong angle, missing frame. The second and third produce the same outcome and mean opposite things. In the first, the umpire decided. In the second, the technology absorbed the decision. In the third, an absence of information rescued the call.

That is my central complaint, and it is about reporting format rather than machinery. The third umpire's announcement should carry three different sentences for three different states. Until it does, captains will keep learning that burning a review is cheap, because every burn returns the same answer they already heard.

The economics of an angle

A ball-tracking rig typically runs on six to eight cameras, at broadcast frame rates — often fifty frames per second. Do the arithmetic. A quick's delivery passes the bat at roughly 140 km/h, about 39 metres per second. At fifty frames per second, each frame is roughly 78 centimetres apart. How thick is the edge of a bat? Two or three centimetres.

The moment of contact can, in principle, fall between two frames. Now judge how much of "no evidence found" is a limit of the instrument and how much is genuine absence. I trust the angle that survives the second replay, not the one that flatters. The angle that says the same thing on the second viewing is evidence; the one that looks beautiful first time is usually the broadcaster's favourite shot.

So my logbook has three columns beside every review: number of angles, frame rate, and the frame the decision rested on. If the third column is empty, the review teaches nothing whatever its outcome. You do not learn from an incident when you do not know what you were looking at.

Umpire's call: the clipping that is not proof

This is the least understood rule in the game. When tracking shows the ball clipping the stumps, we all shout out. The law says that if less than half the ball is inside the stump line, it is umpire's call and the field decision stands.

That does not mean the technology failed. It means the technology declared its own margin — it will not bet below the accuracy it can deliver. I respect the honesty and I see the side effect: uncertainty has been given a language that makes it sound like a verdict. "Umpire's call" sounds to a crowd like a decision was reached. Nothing was settled there; what was settled is that there was nothing sufficient to settle it.

A comparison helps. Russia 2026 was the first World Cup with VAR, and it produced a record 29 penalties. I watched all 64 matches with a stopwatch and timed every review. Most overturned calls had been lost inside the first forty seconds, to the wrong camera angle. The 40-second rule taught me that delay is a kind of evidence. Haste is not neutrality; it is a one-sided decision whose bias nobody can see.

UltraEdge: whose sound was it

A microphone system's greatest strength and greatest weakness are the same thing: it hears sound, not context. Fifty thousand people, wind, helmet grille, glove leather, bat handle. A spike appears when a sound crosses a fixed threshold. A sound below that threshold exists and does not exist at the same time.

Which means a flat line sometimes reads "no contact" when it means "contact below our hearing floor." I don't name villains. I ask which frame was conclusive. When the answer is "none," the correct protocol entry is "none" — not "clean."

The review ledger

A review's true price is set after it is gone. One review left in the last five overs is worth more than any bowler, because it is the only tool the captain still owns when the next appeal goes up. The captain who burns a pointless review in the twentieth over is apologising to that same bowler in the eighteenth.

I added a column to my ledger — burn rate, reviews spent without evidence per innings. Teams with low burn rates appealed with more conviction at the death. That number does not measure talent. It measures discipline, and discipline is cheaper and more available than talent.

The data road and its dark stretch

From here the story leaves the field for the room where the live feed is built. Every ball, angle, speed and map travels to several places within seconds. Some of those places are broadcasters, some are fantasy platforms, and some never appear in the credits.

I am not delivering a sermon, only a ledger entry. The moment live data is tied to money, pressure lands on both its accuracy and its speed — and speed usually leaves accuracy behind. A frame that gets checked three times on the field is logged once in the feed and moves on. Cricket's biggest data risk is not that the data is wrong. It is that the data is fast and the checking is slow.

The retention ledger: pricing a blank column

Now to the transfer window, because this is where the whole thing gets expensive. The sheet on the table at a retention meeting often looks like my logbook: a player's name, age, caps, and beside them a set of empty columns — fitness, workload, injury history, record in big matches.

This is the least audited decision in the sport. A franchise rarely holds the full medical picture, and whoever does — board or medical staff — discloses only what suits them. The result is that a player's price is set less by performance than by the availability of information about him. The player whose injury record is public goes cheap; the one whose record is hidden sells high. The market pays for darkness, not for risk.

And this is where the pipeline problem lives. A report once reached me with every heading filled in — name, style, role — and every number blank. Someone marked it clean because no red flag appeared. That is the fatal error. An empty input is not a clean chit; it is a data gap. When a column is blank, the correct finding is not "no risk" but "risk could not be measured." Between those two sentences sits a player's career.

The format error

One more thing, because it can wreck any analysis. In cricket, format is a precondition, not a variable. A strike rate of 145 is elite in ODI middle overs, ordinary for a T20 finisher, irrelevant in Tests. An economy under seven is excellent in T20, respectable in ODI, close to meaningless in Tests. A report that does not say which format it is describing is not measuring; it is guessing.

So before any number I ask three things: format, home or away, and sample size. Without all three, numbers are just numbers. Home advantage in cricket is among the widest in professional sport, and an evaluation that omits the home-away split is not incomplete — it is invalid.

The contrarian read: technology relocated doubt

Here is the line that does not get said in the commentary box. We assume technology reduced controversy in cricket. My ledger says otherwise. Technology did not reduce the volume of dispute; it changed its address. The argument used to be about the umpire — why did he give it? Now it is about the frame — was that frame even there? The argument did not end. It moved one technical level down, where understanding it requires the viewer to become an engineer.

And the harder point: the most dangerous document is not the one that is wrong. It is the one that is blank and looks tidy. A torn, incomplete, handwritten note makes its reader wary. A report with every heading filled and every number empty looks trustworthy, and that is exactly why it does the most damage. Cricket's decisions today rest on such reports: retention, workload, selection.

The third gap is between emotion and rule. A crowd wants a verdict — someone blamed, someone cleared. Protocol offers a status, not a verdict. "Insufficient evidence" satisfies nobody because it defeats nobody. It is also the sentence that keeps the game honest. — Root: VAR protocol training and a referee's eye. Delhi taught me the appeal; the booth taught me the burden of proof.

Takeaway

Next time the flat line appears and the third umpire says not out, don't check the scoreboard. Don't ask what the decision was. Ask what the report recorded — "there was no evidence" or "no evidence was found." The whole of cricket sits between those two sentences. The team that learns the difference stops burning reviews; the league that writes the difference into its reports builds a market where risk is priced and darkness is not. The logbook opens where the gloves ended, and every doubt gets a timestamp.