From Pitch to Review Room: Cricket Moved the Controversy, It Did Not Remove It

From Pitch to Review Room: Cricket Moved the Controversy, It Did Not Remove It

July 14, 2026, Lord's. It was nearly half past eleven at night and I was sitting in front of a television in a small Delhi flat, a notebook beside me on which I was logging every over of the innings and the line and length of each bowler. In the final over, Ben Stokes was taking a second run alongside Adil Rashid. Martin Guptill's throw from deep midwicket struck Stokes's diving bat and rolled away to the boundary rope. The on-field umpire signalled six — the two runs were completed, plus four overthrows.

Most of what was written about those six runs afterwards was not about cricket. People produced paper and pen to work out whether Stokes and Rashid had crossed before the second run was taken. Others quoted a clause from the laws and wrote an interpretation. Some argued that a boundary created by a deflection off the bat should not be credited to the batsman at all. New Zealand lost the match — on boundary count after a tied Super Over. Yet the centre of the debate was not the ground. It was a grey margin where the rulebook does not say what is fair, only what is permissible.

That night it struck me that cricket's biggest arguments no longer begin on the pitch. They begin in the camera frame hanging above it, on the monitor in the review room, and at the unprinted edge of the rulebook.

Context: A system that changed in seventeen years

The technology at the centre of all this argument is only seventeen years old. In July 2026, the Decision Review System — DRS — was first used in a Test match in Colombo. In the beginning, a major side like India did not embrace it easily; the reasoning was that an umpire knows his own decision best. Within two years the reasoning changed, because broadcasting had changed. The number of cameras rose, frame rates rose, and the viewer at home could see what the umpire on the field could not.

DRS is easier to understand as the joining of three separate technologies. Ball tracking reports where the ball pitched, where it rose to, and how likely it is to connect with the stumps. Systems of the Snicko-Wilkins variety search for the edge of the bat through sound and vibration. UltraEdge reports whether the ball touched bat, touched pad, or struck neither. Three technologies, three different kinds of uncertainty — and one decision.

In 2026, the ICC removed the soft signal. Earlier, when there was doubt over a catch, the on-field umpire would give a soft indication, and the third umpire's decision would revolve around that indication. After the soft signal was scrapped, the burden shifted entirely into the review room. The question changed then — who is making the decision is no longer the important question; what information the decision is based on is the important question.

That is precisely my working ground. When I crossed from the court to the pitch, I packed the same questions and a new geometry. The grey margin that travel and block-charge inhabit in basketball is the direct cousin of cricket's umpire's call. In both, technology measures the event, but somebody else makes the call, using their own judgement. I opened the tape of the 2026 Finals expecting a coronation and found a chess match. The same thing happens in the review room — someone wins on an invisible board, where pieces cannot be moved, only explanations can.

Core analysis: the geometry of uncertainty

The rule runs roughly like this: if ball tracking shows the ball striking the stumps, but the point of impact is not more than half a ball's width inside the outer edge of the stump, the on-field decision stands. That is umpire's call. One thing needs to be said plainly here: umpire's call is not a measure of truth, it is a measure of uncertainty. The review room is not saying the batsman is not out; it is saying our information cannot establish it, so the on-field decision remains final. Two very different sentences, yet commentary collapses them into one.

Why that distinction matters becomes clear through an ordinary number. In limited-overs cricket each side has two reviews, in Tests three, and a successful review is returned. A review is therefore an asset — it can be spent, and it can be saved. Where there is an asset, strategy is born. And where there is strategy, data walks in.

Over the past few seasons I have noticed that the decision to review is no longer the cricketer's decision. An analyst sitting behind the dugout runs the ball-tracking feed, the umpire's historical decision patterns and the bowler's line and length through a probability calculation. The message then travels past the helmet. This does not break the laws of the game, but it changes the character of the game.

The box score told me who won; the tracking data told me who was afraid. In review arithmetic, fear shows up this way — a side in good rhythm on the pitch takes fewer challenges, because it does not need them. A side losing its rhythm takes more risk, and one bad challenge takes the second one out of its hands. The review system does not merely correct decisions; it builds a new kind of pressure on how teams behave.

There is a second layer here that is almost never discussed. Cricket now extracts enormous quantities of data from players' bodies — release angle, knee load, sprint speed, sleep, heart-rate variability. Much of it is used in broadcast, in markets, in forecasting. The question is unavoidable: who owns this data? The player, who produced it with his body, or the board and broadcaster, who installed the camera and swept it up?

The technological answer is easy — a distributed ledger can record consent, usage and royalty today, and this is no longer a research problem but an implementation problem. A blockchain-based consent registry is something sports institutions could run if they chose. The obstacle is not technical but contractual. The party collecting the data will not voluntarily open the account book.

Read together, the two layers form one picture. On the field, review is a process of correcting error; off the field, review is a process of delegated responsibility. Viewers are aware of the first. Almost nobody is aware of the second.

At an out-of-town net session once, I sat and watched a reserve batsman simulate ball-tracking outcomes on his phone — what the probability was if he reviewed a particular delivery. That half hour, outside the construction of the match, was like an empty arena: no noise, only room to measure response. The empty arena became my laboratory, and silence became my control group. My most reliable ideas about review were formed in exactly those low-stakes matches and net sessions, not in live crowds.

IPL innings are the great evidence of this. On April 15, 2026, in Bengaluru, Sunrisers Hyderabad posted 287, the highest team total in IPL history. Behind it was not only weak bowling; there was the Impact Player rule, short boundaries, and data-driven arithmetic about bowling changes. In a format that does not weaken bowlers so much as hand batsmen extra advantage, the only survival route is calculation — who bowls which over, who sits out which matchup.

The contrarian angle: the technology is not the culprit

The popular complaint is that DRS has slowed the game, reduced the umpire's authority, and spoiled the crowd's excitement. I see something different. Technology is not creating the controversy; a rulebook that cannot plainly call a binary decision binary is creating it. Where the law is clear — no-ball, boundary, review connectivity — technology has settled the matter quietly, and nobody protests. Arguments survive only in those places where what is written on paper cannot be shown on screen.

Second, spectators usually blame the third umpire. In reality the third umpire is often applying a rule written when ball tracking did not exist. If someone interprets the language of a two-decade-old law with the precision of modern cameras, the decision will look inconsistent — but the problem is not the person, it is the language.

Third, data-driven review strategy is building its own trap. When an analyst decides according to a pattern — this umpire gives this decision on this kind of delivery — he is measuring probability, not the ball. Call it a confirmation loop. The better the model, the more courage a team has to take a bad challenge, because the numbers reassure them. Here lies the limit of analysis: a model cannot read the rhythm of a match, only the sample that came before it.

And a final point about institutions. Everyone says technology reduces corruption. The real picture has been the reverse — technology has moved the argument off the pitch and into the review room and the contract file, where the pressure of accountability is lightest. The grey margin has not shrunk; it has grown. Because the doubt used to live on the field, in front of the crowd; now it hides inside a standard of proof called 'conclusive evidence'.

Takeaway

The next big change will come from automated LBW — like the automated no-ball check, where the on-field umpire is no longer at the centre of the decision. The question then will not be whether we use the technology. The question will be whether the umpire's authority can survive it. And a bigger question still — who keeps the accounts of the review that corrected the error? The answer to that leads to data ownership, not to cameras.