From DRS to DLS: Cricket's Decision Chain When the Data Goes Blank

Three minutes and thirty seconds. Players stand in the middle, the scoreboard has frozen, and in the third umpire's room three screens loop the same frame—the flat UltraEdge line, the ball-tracking pitch map, the percentage of ball striking the stumps. Then the verdict: on-field decision stands, umpire's call. The crowd roars, the social feed fills with clips, and the next morning every outlet carries the same sentence—DRS has created another controversy.

I have spent years watching matches and I am used to this scene. That is exactly where my real question begins, and it is not a hot-take question. The question is this: when an entire decision chain stands on data, what does the system do if that data is incomplete? And what if the data is entirely blank?

In 2026 I made a decision—I launched The Referee. Watching Milorad Mazic's four-minute VAR review in Chile vs Cameroon, I understood that controversy is not born on the pitch; it is born in the review room and in the grey zones of the law. I forgot the result, spent 72 hours cross-referencing IFAB's 2026 VAR protocol, and wrote a 4,200-word timeline that became the foundation of my writing. In 2026 my second major project was the 2026 World Cup final handball and intent: after that handball penalty in the 38th minute of France vs Croatia in Russia, I re-watched all 64 matches over 11 days and logged 29 VAR reviews and 20 changed decisions. In 2026, during the empty-stadium, five-substitution era, I built the 2026 spreadsheet and INTP personality method, coding 500 referee decisions under the relevant Law clauses. In 2026 in Qatar, semi-automated offside fascinated me, because there the speed came from the accuracy of the data, not from human confidence.

That habit taught me one thing. Technology does not reduce controversy; it moves controversy off the pitch into the review room and into the clause-level language of the law. In cricket that review room is called DRS, and beside it sit DLS, ball-tracking, UltraEdge, the Anti-Corruption Unit's protocols, and a living library of Playing Conditions.

The ICC's Playing Conditions are amended before every series—the umpire's-call margin, the no-ball height, obstruction in the field, the sequence of ball-on-body in a caught-behind, the application of the spirit-of-cricket clause. The precise wording of all of it lives there. DLS was born in 2026 in the hands of Frank Duckworth and Tony Lewis, and was refined by Steven Stern's revision in 2026. Put the two examples side by side and the pattern is clear: cricket has progressively handed its decisions to a model, and the more reliable the model's input, the fewer the controversies.

First, a structural truth has to be accepted, one most discussion avoids. Test, ODI and T20 statistics are not comparable with one another. Placing a batter's Test average beside a T20 strike rate mixes the rules of two different games. In Tests the ball ages, field restrictions differ, and light, breeze and pitch wear play a large role; in T20 the per-over fielding restrictions and the wicket-preservation calculation create an entirely different equation. Analysis that ignores this distinction and reaches conclusions through averages and strike rates is not analysis—it is decoration with numbers.

One example. DRS was first used in July 2026, in the India–Sri Lanka Test series. Initially it was optional, with a fixed number of reviews per team and a limit on unsuccessful reviews. Over the years that framework has changed—the number of reviews per innings, the retention of a review after a successful one, and the ball-tracking thresholds. Behind every change there is a single logic: balancing the pace of the game against the reliability of the decision.

The arithmetic behind umpire's call deserves attention. If ball-tracking shows the ball would have struck the stumps but the amount of contact falls below a specified percentage, the decision goes in favour of the on-field umpire. The logic is simple: if the technology's certainty is limited, the human decision takes precedence. But this simple logic has a side effect—it converts an absence of evidence into a decision, and that decision is not always the commentator's favourite.

The second layer is process. When a review reaches the third umpire, he must pass several gates at once: where the ball pitched, whether impact was inside or outside the line, whether bat or pad came first at impact, and what percentage of the ball struck the stumps. Every gate has a threshold, and those thresholds are the real law. Whether the wicket fell is merely its outcome. This is where a habit of mine earns its keep—when I write a data brief, I attach a timestamp and a clause reference to every decision, because explaining a decision without a clause means filling the reader's head with emotion alone.

The third layer is the least discussed and the most important. When data is insufficient, a system can take one of two paths—suspend the decision, or fall back to a default. Cricket has deliberately chosen the second: when evidence is insufficient, the on-field decision survives. This protects the flow of the game, but it leaves an uncomfortable question hanging. Why does insufficient evidence always favour the person who made the first call? The default is the rule of the game, but its design is a choice—and behind every design sits a distribution of power.

That distribution of power is not only technological but institutional. The 2026 Big Three model gave three major boards disproportionate advantage in power and revenue distribution, and the 2026–17 revision partly reversed it. The NOC system for players determines who can play in which league; the conflict between leagues and national teams creates new problems of scheduling and injury management; the political freeze in India–Pakistan bilateral series shows that cricket's calendar was never a purely sporting calendar. Put together, one truth stands: cricket's decision chain is technological and political—the combined product of two layers.

The fourth layer is integrity. The Anti-Corruption Unit's job is not only punishment; it is to identify suspicion by analysing data—abnormal movement in betting markets, abnormal over-rates, abnormal patterns. The biggest lesson here is that when suspicion appears in data, the decision must wait for evidence, not for publicity. I remember how, in the empty stadiums of 2026, the absence of sound changed the tempo of referees' decisions—there was no crowd roar, so decisions took longer. With data, decisions come faster; with bad data, decisions come faster and wrong—both at once.

This is my central observation. Cricket's technology governance is really a pipeline: talent arrives from youth and domestic cricket, national teams and leagues give it a stage, and then broadcast, advertising and betting markets convert it into money. At every layer decisions are made with data, and at every layer one blank input can weaken the whole chain. If who is good in which format is measured wrongly, then team selection, auction prices, even broadcast commentary go wrong too. Confident decisions from blank input—that is the biggest risk in cricket analysis today.

The broadcast and commercial layer is no simpler. A league's broadcast-rights value, a franchise's valuation, a player's salary—these three numbers are related to one another but not identical. A high price in a league does not always mean strength on the international stage. Commercial value measures audience appeal; sporting quality measures depth of competition. Commercial value and sporting quality are two separate calculations, and conflating them is the most common error.

Now comes the uncomfortable part, where rule and emotion face each other. The roar of the crowd, the social-media clip, the television commentary—all say the same thing: this is against the spirit of cricket. But I ask: under which clause? In which section of the Playing Conditions? When a sentence cannot cite a clause behind it, it is not law; it is feeling. Feeling is not a bad thing, but explaining a decision with feeling means leaving the decision to an individual.

My experience says the loudest shout usually arrives with the least protocol knowledge. And yet the number of controversies has not fallen. It has risen—because every review creates a new object: the replay. And once the replay is in everyone's hands, everyone can judge it again, by their own law. Hence my second observation: VAR and DRS did not kill debate; they gave debate a replay, and gave everyone their own law alongside it.

The bigger lesson for me has come from my own work. In the analytical pipeline I have seen how dangerous the temptation is to fill a template when the input is blank. If someone builds a confident analysis on empty input, that is not a wrong decision—it is the pretence of a decision. And in cricket the price of pretence is high, because a decision there touches not only a match but a career, a contract, a nation's feelings.

Looking ahead, I offer a proposal. If the umpire's-call default and the DLS model are both system decisions, then every review decision should carry an immutable record: which frame, which threshold, which clause, whose approval. A tamper-proof, ledger-style audit trail—one where no one can change the explanation of the same incident next season. Cricket today is as much about its record as about its play. And if that record is blank, then no matter how fast the decision comes, trust will not.

I leave the question open: before the next review, will we read the law, or will we just stare at the screen?