From the Third Umpire's Chair: Asia's Review Ledger and the Verdict Written Late

Fourth ball of the thirtieth over. For two seconds after the ball struck the pad I wrote nothing, because there was no verdict to write. The on-field umpire did not raise his arm and did not shake his head. A section of the stands stood up, and the big screen rolled out three frames of ball-tracking. I noted a single figure in my ledger: seventy-one seconds. That is how long the third umpire took to arrive at a decision.

The number is data, not proof. The proof sits inside those seventy-one seconds, in the gap between what the screen showed and what the field was actually doing. Ball-tracking said the delivery would have hit the stumps. But the primary replay angle was set so low to the ground that the exact pitch point cannot be measured in that frame. Pitch point, impact and projected height — not one of the three is settled from that angle. The camera we were shown first was carrying the least information.

Every angle confesses something the first replay hid. So the work here is not to argue with the on-field verdict; it is to arrange the frames behind that verdict in sequence, so that the verdict writes itself before the tape runs out.

DRS is no new guest on subcontinental grounds. In July 2026, the system was used on trial in the Sri Lanka-India Test at the Sinhalese Sports Club in Colombo. The ICC rolled it out across every match of the 2026 World Cup. But the pace of adoption among Asian boards was never uniform. Sri Lanka and Pakistan accepted it comparatively early; India began using it in full from the Rajkot Test against England in November 2026. That uneven timeline is the first signal: a decision-review system walks through board politics before it walks onto the field.

The playing conditions deserve a look. Two reviews per team per innings in Tests; two in ODIs and T20Is as well. And here sits a phrase that shapes more outcomes in Asia than any other — umpire's call. If ball-tracking shows the ball would have struck the stumps, but not inside the clarity threshold required to overturn the on-field decision, the original call stands and the team keeps its review. Losing a review and losing a decision are two separate events, and that distinction is what scrambles a captain's arithmetic.

On subcontinental wickets the arithmetic tightens further. Ball-tracking predicts the ball's path after impact, and the two largest uncertainties in that prediction are bounce and spin. On a fourth-day Mirpur surface, where the ball is skidding below knee height, asking how high it would have struck the stumps means measuring a future nobody saw — not the umpire, not the crowd.

My ledger is blunt on this. During my VAR work in football I logged twenty-nine reviews across sixty-four matches, and the pattern was near identical. Asian teams do not lose more reviews; they spend their reviews in the wrong place. Twenty-nine reviews in sixty-four matches taught me that the pattern is the proof — a failed review never stands alone.

The spending happens in two ways. First, the catch review: often born of hope, sometimes simply of the urge to release pressure. Second, the spinner's wickets review, where the question is whether the ball would have hit the stumps — precisely the projection that is most unstable on a turning track. The opposite holds too: on full-length deliveries, impact-in-line reviews are the spinner's most profitable category in Asia. The ball does not deviate much off the pitch, so the impact point is far more reliable.

Ball-tracking essentially reconciles three points: pitch, impact and the projection into the stumps. The first two are measured; the third is estimated. The clarity threshold is calculated against the size of the ball — how much of it falls inside the outer stump zone. The finer the calculation, the more umpire's calls, and the fewer overturned decisions. On Asia's slow, turning surfaces those fine calculations are most frequent, because spin sends the ball skimming past the line of the stumps with the pad edge riding alongside it.

The review-retention rule has changed captaincy behaviour. Because a review is returned on umpire's call, challenging a marginal call is now cheaper in accounting terms. But a new risk has come with it: teams now dress doubt in the language of the rule. What was beyond doubt on the field becomes a matter of estimation once it reaches the review desk.

The wicketkeeper's position is sometimes more informative than the third umpire's. The instant a spinner releases, the keeper's ear catches both the line and the height. Weight inside a review huddle is built on experience — Mushfiqur Rahim can speak from the keeper's vantage, Shakib Al Hasan from the bowler's end, and two truths do not merge into one verdict. That is where the captain's real job sits: not gathering information, but selecting it.

When cricket was played in empty stadiums in 2026, I began keeping an audio log across forty closed-door matches. That was where it first became clear that crowd noise does not merely mask language; it masks the limits of responsibility. Silence in an empty stadium can be louder than a crowd — the stump mic catches the captain's hesitation, the umpire's shortage of conviction, and the two long breaths taken before a decision is made. The crowds returned and that layer was buried again, but the data stayed in the ledger.

Field placement declares what the fielding side already believes, and it does so before the ball is bowled. A packed slip cordon with nobody at short leg is itself a statement. In review culture this is decisive, because whether the side genuinely believed on the field often settles the outcome. A review born before unanimous conviction is usually rejected on camera.

Since the soft signal was removed, catch decisions rest entirely with the TV umpire. That has added clarity; it has also placed all the responsibility on one chair. The question is no longer what the on-field umpire thought, but what threshold we require before calling something certain.

Domestic cricket is the real laboratory here. In the Dhaka leagues and the National Cricket League, the review system behaves like a patchy internet connection — it works intermittently, and there are never enough cameras. Players there learn to review on guesswork and come to believe that a decision and an appeal are the same thing. That habit surfaces later in a Test. What looks like a surprise on the international stage was already selected on a league ground in Mirpur or Bogura.

A major tournament compresses everything. In the short Asia Cup format, every review feels like the key to the match; the ledger says patience with reviews drops in tournaments, and that is the biggest shift. A side that keeps accounts from the third over in a league match often burns its first review in the first over of a crucial group game. It is easy to float on flags and storylines; the truth about squad depth lives on twenty-two yards of turf.

Process and outcome must be separated. The third umpire has fifteen seconds, not fifteen angles. The replay makes everything look simple in hindsight, but the decision has to be made on incomplete information under time pressure. The judgement should therefore fall on the process, not the result. An umpire who reconciles five angles and can say which is more reliable is dependable; one who simply announces quickly may be fast, but not certain.

Review accounts are usually read through the lens of win and loss. A losing side's reviews are remembered; a winning side's bad reviews are forgotten. Look at the two-reviews-per-innings arithmetic at the end of a match and it is clear that the winners often do not know why they were right, and the losers do not know why they were wrong. That is where the coaching staff belongs — letting the captain decide, not feeding him information.

The count of reviews does not measure skill; the type of review does. The sharpest Test side is not the one that has overturned the most decisions, but the one that settles before challenging what it is looking at and who is asking the question.

The easiest conclusion arrives right here: a bad review means incompetence. Eight years of ledgers do not fully support that. Most reviews are not taken with eyes shut but after calculation — except the calculation is built not on the team's best information, but on the loudest voice in the huddle. The keeper behind the camera says the pitch is outside leg, the slip fielder says it is inside; the captain picks a verdict between two truths, and no decision stands comfortably in that middle ground. This is not a personal failing but an organisational one — responsibility is undefined, and so the risk is uncounted.

Honesty is required, though. On some reviews the on-field call was simply correct, and what spoke last was patience, not a replay. There are matches where the system justified the outcome and the decision did not change — and changing it would have been the error. The low-angle first replay offered no information there, only false confidence; the correct call was to refuse it.

The second cost is more obscure because it is invisible. It is the review not taken — or, more precisely, the final review hoarded on a turning wicket. In Mirpur the price of that is a catch. What a player raised on domestic cricket learns early is that a review is a luxury, and luxuries should not be spent in a crisis. So on the fourth evening, when it matters most, there is nothing left in hand. Losing a mediocre review costs less than never taking a good one.

Two steps matter going forward. First, boards should publish a review audit at the end of each season — where the loss happened, which data was missing on the field, and why. Second, camera-based limited review should be introduced in domestic cricket, so the habit forms before a player reaches the international stage. A rulebook is a map, not a mirror; intent lives in the terrain.