Cricket's Laws, Jurisdiction and Data: Through a Referee's Eye

The moment I begin with does not appear on any scoreboard. June 18, 2026, The Oval, Champions Trophy final. Fakhar Zaman was on three, Jasprit Bumrah's delivery took the edge and flew to the keeper. The umpire raised his finger. Then the third umpire said: no-ball. No broadcaster had a clean frame of the landing foot. I stepped through the recording frame by frame on a borrowed laptop in Dadar until three in the morning and wrote nine hundred words on Law 21. Those words are still on my desk, not because they reached a conclusion, but because a question had opened up that changed the way I write: who had the authority to determine a delivery's legality, and to whom was that authority visible?

This article is not the story of one match. It is the story of the structure through which we watch cricket — the laws, the jurisdictions, the datasets, and the institutional pressure that decides which frame is seen and which is not. Fakhar's caught-behind-that-wasn't was just an event. Behind it lay the whole map of cricket's governance: who can appeal, who can review, and who bears the decision when the available evidence is insufficient.

Jurisdiction: who is allowed to look

Law 21 states that some part of the bowler's foot must be behind the crease at the point of delivery. In one line: a no-ball is a technical condition, not a moral verdict. But the real question is not what the condition is; the real question is who can see that it has been breached. In 2026 the broadcaster did not have the best frame, the third umpire had limited camera angles, and the on-field umpire had only an appeal. So the decision rested not on legality but on availability. This is my first strength: legality before merit.

Seen this way, DRS is not a neutral technology. It is a compound of three separate jurisdictions — the on-field umpire's, the third umpire's, and the ball-tracking software's. Whose opinion is the software? It measures, but it does not decide when the measurement is decisive. The concept of 'umpire's call' exists precisely because there is a grey zone between technical and human jurisdiction, and the boundary of that grey zone is drawn by the ICC. I coded every DRS review from ICC events between 2026 and 2026 into a spreadsheet: 1,240 reviews. The result: the largest share of failed reviews were umpire's call. In other words, the system held players wrong when the error lay within the technology's own limits.

Dataset before opinion

My second habit is that when someone states a number as a conclusion, I first read it as data, then as a result. Whether it is net run rate arithmetic, Impact Player usage, phase-wise strike rates, or auction-purse constraints — every number has a sample behind it, and every sample has an error bar. When someone proves a 'clutch gene' from five innings, I ask: how many times in those five innings did the same player repeat the same situation? The question sounds impolite, but it is the only honest way.

Apply the same logic to the IPL auction. The purse constraint, the retention arithmetic, and the reserve-price framework before a mega auction — all of this builds a market in which a player's price is set less by performance and more by team need. Franchise scouting has replaced zonal selectors, and that shift is not neutral. It determines which state's player gets a chance to be seen and which does not. Ranji Trophy coverage is thin, yet its structural function is enormous — and that is the contradiction. The system on which domestic cricket rests has almost no one watching it.

Systems are not neutral

Third pillar: systems are not neutral. I say this not as a grand conclusion but through small examples. Take the stop clock. It was introduced in the name of pace of play, but in practice, on whom does it land? On the team under pressure. On the team with less match practice. The law is the same, but its effect is unequal. Consider the pitch-rating framework — who rates, on what basis, and whose soil bears the consequence. That is not a technical question; it is a political one.

WPL deserves the same lens. Broadcast promises, player contracts, and the gap between them are a test of institutional will. When a league gives players contracts but does not give them the airtime it promised, the question is not whether the league is good or bad; the question is whom it was built to serve.

Contrarian: when the crowd reads the law correctly

My biggest habit — and biggest risk — is that when the crowd shouts, I first assume it is wrong. That reflex is dangerous. Sometimes the crowd reads the law properly. In the Cape Town affair of 2026, Cricket Australia banned Smith and Warner for twelve months each, and the ICC route ran through the match referee's code-of-conduct hearing. The question arose: why did two different courts hand down different sentences for the same incident? The crowd's anger was correct — the law had created two jurisdictions, and the boundaries of both were unclear. So I check the rule first, then check whether the outrage is right. Sometimes the outrage is more accurate than the rule.

By the same logic I compare VAR and DRS. In football the question is what 'clear and obvious' evidence means — who decides which frame is decisive. In cricket the question is who holds the right of review — the captain, the batter, or the umpire. In both places the real fight is not about technology but about jurisdiction. When someone says 'the technology got it wrong', I ask: which technology, to what limit, and who authorised it?

The files on my desk

I have a file with data on 1,240 reviews — umpire, format, wicket type, outcome. That file is my most reliable source and also my most limited. I posted its pivot table in a fourteen-tweet thread, it drew four hundred thousand impressions, and a Mumbai desk asked for the raw file. But I know how little a 2026–2026 sample says about today's game. Presenting a five-innings T20 sample with a decade's confidence is a mistake I could make myself. So in every piece I publish the error bar, and where needed I write 'sample too small to call' — and mean it.

There is another file — of code-of-conduct rulings. It is my most-quoted asset. It records the hearings where the match referee imposed a sanction and the question arose of how much power the referee holds. The BCCI's grip on the global calendar, or the silence of ICC media officers — all of it is noted in the margins of that file.

What comes next

The next time a no-ball, a DRS controversy, or a code-of-conduct sanction makes headlines, do not ask first whether the decision was right or wrong. Ask first: who had the authority to look at that decision, and which frame was available to them? The day spectators start asking that question, broadcasters will have to install better cameras, and institutions will have to publish the limits of their jurisdiction. This will not be a revolution; it will just be a better question. And a better question is the only thing that moves the game forward.