Half a Ball of Justice: How Cricket's Review Ledger Separates Big-Team Luck from Small-Team Fate

The Verdict of a Decimal

The ball struck the pad, on line, in front of the stumps. The on-field umpire shook his head — not out. The captain raised his arm for a review. On the monitor beside me, ball-tracking began to draw three bands: inner edge, outer edge, and the path of the ball between them. The prediction came down: the ball would have hit the stumps. But less than half the ball was inside the stump zone. The result was Umpire's Call. The decision stood, and the review was gone.

Twenty-seven minutes later, an edge carried low to slip and was grassed. The captain raised his arm again, but there was no review left. The replay showed the ball had touched the bat's edge — by about three millimetres. The match turned. Nobody wrote "no review left" on the scoreboard. The scorecard recorded only a dropped catch.

I do not count checks to find blame. I count them to find patterns. In 2026, from a student flat in Liverpool, I kept a ledger of all 380 Premier League matches, 92 penalties, and the 14 decisions I judged wrong. At Russia 2026 that became 455 VAR checks, 20 on-field reviews and a record 29 penalties, each intervention scored against a "clear and obvious" threshold I wrote myself. By June 2026 I was a junior performance analyst at Tranmere Rovers when League One was curtailed, and unweighted points per game sent the club down by 0.09 points per match. On 1 December 2026, in Qatar, 1.88 millimetres became a line that split a season.

In cricket I read the same kind of accounting, in a different unit. Football writes its threshold in millimetres. Cricket writes its threshold as half a ball. Both are conventions. Neither has a physical basis. And those conventions decide who reaches a final, who tops a table, and whose umpiring gets called weak.

How the Ledger Is Written

DRS entered Test cricket in 2026. In the sixteen years since, the system has split into three layers: the on-field umpire's decision, the tracking prediction, and the grey zone called Umpire's Call. The third layer gets the least attention and holds the most power.

For LBW, if ball-tracking shows the ball would have hit the stumps with half or more of its width inside the stump zone, the decision is overturned. Below half, the on-field call stands. Under the ICC's Men's Test Playing Conditions, that is Umpire's Call. Outside the law book, it means something blunter: the technology knows the ball would have hit the stumps, and the batsman is still not out.

Each side gets two reviews per innings in Tests, ODIs and T20Is. The old top-up after 80 overs was removed. A successful review is returned; an unsuccessful one — whether it was Umpire's Call or a plain error — is spent.

That is the first accounting trick. Umpire's Call is not a technical failure. It is an accounting decision. The fact that the ball would have hit the stumps is true, and that truth is worth nothing unless it clears half a ball. A side that keeps landing just outside that line is punished twice: the decision stays, and the review is lost.

From Mirpur I have watched this play out on slow-motion replays — the finger staying down, the prediction grazing the stumps, the captain hesitating with a hand half-raised. That one second of doubt is the product of sixteen years of convention.

The Stopwatch Ledger

Cricket's second ledger is not ball-tracking. It is a stopwatch. In the World Test Championship, a win is worth 12 points, a draw 4, a tie 6. But the table is ranked by percentage of points won, not by total points. That single line contains the politics of the whole cycle.

Take a side that plays twelve Tests in a cycle and another that plays twenty-two. The first can win a maximum of 144 points, the second 264. If both are docked one point for a slow over rate, the first loses roughly 0.69 per cent of its ceiling, the second 0.38 per cent. The same penalty lands about twice as hard on the smaller schedule.

Under ICC rules, a side can be docked one point per over it falls behind, with a five per cent match-fee fine per over as well. Since the 2026-25 cycle there is an in-match sanction too: once a fielding side is three overs behind, an extra fielder must go outside the 30-yard circle. The punishment now lives in two places — on the table and on the field.

I remember my four-day model at Tranmere. I was calculating relegation then; I calculate final qualification now. The same question sits underneath both: who set the denominator of the metric that delivers the verdict?

A Threshold Written on the Ball

Ball-tracking has a published margin of error. The manufacturers state accuracy within a few millimetres, and they publish the figure. The Umpire's Call threshold was never matched to that figure. It was matched to the width of a cricket ball — fifty per cent.

Football does the opposite. Goal-line technology decides in millimetres, and VAR offside lines are drawn to the exact measurement — inside 1.88 millimetres is a goal, outside is disallowed. In Qatar that fraction of a millimetre erased six months of a defender's work.

Cricket's threshold is half a ball because the ball is small and the stump area is fixed. The logic is clean and uncomfortable: the threshold did not come from the technology's accuracy. It came from the comfort of the decision-makers. Umpires needed the benefit of the doubt preserved, so a numerical threshold was invented that has nothing to do with the error of the tracking system.

I am not blaming umpires. I am describing a system that says "the technology knows the ball would have hit" and then says "but not out" in the same breath. Where the frame rate decides who stays, the frame rate is a moral position.

One Physics, Two Ledgers

The most uncomfortable part comes next. In the Indian Premier League, the rule was changed in 2026: if a review results in Umpire's Call, the side keeps the review. International cricket does not do this. Same technology, same tracking, same half-ball threshold — different accounting rule.

The consequence is direct: where a review is retained on Umpire's Call, the side does not carry the cost of the grey zone. Where it is not, the side is punished twice — in the decision and in the resource.

I am not alleging corruption. I am naming asymmetry. Franchise sides bank more reviews across a season than international sides do, and the difference comes from a paragraph in the playing conditions, not from a tracking error.

In 2026 the ICC scrapped the soft signal, removing the on-field umpire's initial hunch as the basis for a third umpire's catch decision. That was right, because a soft signal is habit, not evidence. Notice, though, that the reform arrived under pressure from visual controversy, not from any measurable principle. The grey zone of Umpire's Call is still waiting for that pressure.

Those the Cameras Do Not Reach

Ball-tracking is expensive. Cameras, operators, calibration, backup systems — a full setup runs into thousands of dollars per match, and more in a major series. Full Member fixtures carry the cost. Many regional qualifiers, Associate tournaments and domestic leagues have no DRS at all, or a token version of it.

This is where the border-crossing question sits. Ireland played their first Test in May 2026 against Pakistan at Malahide. Afghanistan played theirs in June 2026 against India in Bengaluru and lost inside two days. Both entered a system whose most expensive instrument was not part of their experience.

Consider Bangladesh. After gaining Test status in 2026, it took five years for a first win — 226 runs against Zimbabwe in Chittagong in January 2026. That side had no reviews and no tracking, only an umpire's eye and a crowd. Bangladesh has DRS now, but the system it uses was calibrated in its absence.

I say this with a specific vantage point: born in Bangladesh, working in the UK, I have moved through the cricket economies of both. Technology is never distributed neutrally. The richer the board, the more reviews its team takes, the more analysts it employs, the more tracking it installs in conditioning work. When a technology draws the boundary of a rule, the unequal distribution of that technology becomes a rule itself.

I was lucky enough to sit on a data floor in Qatar, watching four screens at once while operators traced ball paths. Outside that floor, at a regional match in a smaller country, having one of those four screens is a matter of fortune.

Stadium Aura

I have argued for years that inconsistent treatment of big clubs and small clubs is not a conspiracy theory; it is the real effect of stadium aura and media pressure. In cricket it works more subtly.

When eighty thousand people in Mirpur roar, and two thousand sit quietly in Southampton, the same LBW decision feels "natural" in two different ways. That cannot be measured, but it can be counted. In the VAR ledger, the rate at which on-field decisions are overturned against the home side differs by venue. Cricket has no public equivalent of that ledger, which is itself a finding.

Technology cannot wipe out aura, because technology is handled by people. Who mounts the cameras, who calibrates them, who picks the backup frame — all of it sits inside the host board's operations. Where the pitch, the ball, the outfield and the broadcast belong to the host, believing the tracking configuration is perfectly neutral asks for more faith than the evidence supplies.

I am not claiming anyone deliberately rules against anyone. I am saying that in a system with a blurred threshold, bias needs no conspiracy — only habit and environment. And the biggest beneficiary of a blurred threshold is always the side with the loudest voice.

The Error Nobody Counts

Now the counter-argument. Suppose Umpire's Call were abolished tomorrow and a ball hitting the stumps meant out. What happens?

The answer is not comfortable. The threshold would move to the tracking error margin, and every two-millimetre decision would write a match's fate. From Qatar's 1.88 millimetres we know how cruel that fate can be. Umpire's Call is a buffer — an artificial blanket over the limits of the technology.

But if a buffer must exist, it has to be the same buffer for everyone. That is where the real fault lies. The problem is not the technology's error. The problem is that the rule deciding who pays for that error was written unevenly.

The second counter-argument is that over-rate deductions punish the guilty. Partly true. But when the Test schedule is unequal — twenty-two matches for one side, twelve for another — the same deduction is not the same punishment. If the unit of punishment is a point, fairness requires the unit to be a percentage.

I know this reads as anti-technology. I am not against technology, and I am not against systems. I want the ledger kept open, because a ledger nobody reads holds the most power of all.

What the Next Cycle Should Change

First, transparency. The tracking error margin, and the number of decisions per Test that fell to Umpire's Call, should be published as public data. I see things on a data floor that spectators never see, while the verdict belongs to their team.

Second, one rule. Whether a review is retained on Umpire's Call should not differ between franchise and international cricket. Same physics, same ledger.

Third, proportional punishment. Over-rate deductions should be a percentage of a side's available points in the cycle, not a fixed number, so schedule inequality stops distorting the table.

Fourth, reach. A minimum ball-tracking standard should be mandatory at ICC qualifiers and major Associate tournaments. A side that never learns to use a review never learns to reach a final.

I began with a 455-check ledger and ended with a question about the watchers. The table is a verdict, not a story. Nine-hundredths of a point per match, half a ball, one over on a stopwatch — those three units decide whose song is sung next cycle and whose scorecard records only a dropped catch. The next time a prediction appears on the screen, take a second before the verdict: who drew the line, and who is standing outside it?