Three Minutes Forty-Seven Seconds: Reviews, Rhythm, and the Regular Season's Quiet Ledger

Eight fifty-two in the evening. Under the Mirpur floodlights the grass reads almost blue. I am in the commentary box, headphones on, a notebook open in front of me — bowler's name on the left page, a column on the right for how low the keeper's gloves travel. At the corner of the table sits a cup of tea that went cold a long time ago.

The delivery that over was a slower ball, a fraction wide of the length, and the batter drove at air. The keeper took it clean, snapped both gloves up in front of the stumps. The umpire's finger went up. The stadium began to rise — twenty-seven thousand people do not stand in the same instant, but the sound of standing had started.

Then two letters appeared on the big screen. REVIEW.

The bowler, who half a second earlier had been appealing, stopped at the edge of the pitch. Hands on hips. Fielders drifted toward their positions but did not take them; they simply stood. The keeper did not take his gloves off. The non-striker leaned on his bat at the boundary line. On the screen, one frame at a time: impact, wicket, ball tracking.

Three minutes forty-seven seconds.

What came back was Umpire's Call. Out stands. The celebration that had begun never completed its arc. The crowd applauded, but the applause had a delay inside it, as if permission had to be granted first. I said what needed saying on air in an even voice, holding the discomfort in. At home I wrote one line in the notebook: rhythm is a liquid thing. It can be stolen legally.

This piece is the accounting of that theft.

The review system entered cricket on 23 July 2026, at the Sinhalese Sports Club in Colombo, in a Test between India and Sri Lanka. Early on it behaved like a piece of jurisprudence — evidence, appeal, verdict. When it arrived in one-day internationals at the 2026 World Cup it turned into a product, because every broadcast now trained its cameras on those few seconds when everything stops. In October 2026 the ICC made it mandatory across all Twenty20 internationals, and from that point the game's tempo and the game's surveillance were tied into a single knot.

The rule is plain. Two reviews per innings in Tests, one per innings in one-day internationals and Twenty20 internationals. A successful review returns; a failed one burns. If more than half the ball hits the stumps the decision flips; if exactly half hits, the umpire's call stands. I have watched this rule from the edge of grounds for nine years, and every season the same thing shows up: spectators memorize the verdict of a review but never remember the rhythm, even though the rhythm is what gets damaged.

In 2026, at seventeen, calling France against Argentina for Radio Rangpur — a match France won 4-3 — I said "Pav-ard" instead of "Pavar" in the first half, along with two other names. That mistake taught me something I have never put down: pronunciation is also a review. I re-watched the tape for a month afterwards, writing a phonetic card and one aesthetic line beside every name. The habit has stayed — writing a name in the margin before the world learns to spell it.

In 2026, calling a goalless Bangladesh Premier League match between Bashundhara Kings and Sheikh Jamal Dhanmondi in an empty stadium, I understood something else. In an empty ground every touch produces an echo, but an umpire's decision produces none. Nobody applauds, nobody swears; there is a click and a vacancy. I wrote that essay as "The Silence That Speaks," and it became the seed of the Court Sage podcast, where I learned to read the small moments — breathing, whispers, the weight of a goalless draw.

In the regular season the arithmetic of rhythm changes. In the first two weeks of a tournament teams treat reviews casually, because individual matches still weigh little. Then the middle of the table compresses, and eight teams sit within four points of each other, and suddenly a single review is worth a match. That evening in the Bangladesh Premier League sat exactly in that band — fourth and sixth separated by two points, a thinner margin than net run rate. When Rangpur Riders won their first title in December 2026, it was this city's first real reach for something; every season since, the crowd here has learned one lesson — the pressure of a points table breaks on small things, not on big matches.

The central observation in this piece comes from the back pages of my notebook, where for three seasons I have logged review timings: how many seconds until the appeal, how many seconds until impact appears on screen, how many seconds until the verdict. A pattern emerges that nobody usually bothers to count.

A review does not break the rhythm of the game — the review hands the captain time to think, and that time is the actual damage.

Think of it this way. You are fielding. You need to save an over before the death, and you know which bowler will hold up at the back end and which one will not. Normally you make that call in twenty or twenty-five seconds, because the batter is standing there, the umpire is watching the clock, people are waiting. Then a review goes upstairs and you suddenly have three minutes. Nobody forbids anything. Nobody is hurrying you. The coach signals from outside the rope, the vice-captain walks in from fine leg to talk, and you reshape the field three times.

In other words, the largest effect of a review is not in the verdict at all but in the free timeout it hands the bowling side. The batting side does nothing with those minutes; it waits. And Twenty20 is a format where the quicker the previous delivery stays in a batter's memory, the better he is — three minutes cools the memory down.

This touches the most honest part of the game. The ball-tracking data built from those camera frames does not change during the review process — impact, pitch, wicket; once those three points are recorded, they cannot be rewritten. The closest thing cricket has to a blockchain is precisely this: each frame an entry, each review a block, a chain verified by the umpire's verdict rather than by pressure. But the protocol that is durable is also the protocol that is slow, and the loudest complaint against slow things always comes from the spectator who may have just watched ten dot balls in the previous over.

My notebook says something more. Review timing varies by team, but the line near the ball does not. The sides doing well in the regular season also burn more failed reviews, because they spend the review like capital, not like insurance. Getting the keeper to call it, checking fine leg, a second-second decision with a glance at slip — those small habits are really a scorecard of a team's internal authority. Where captain and keeper work as one, a review often survives; where they live in two different worlds, the review burns on the worst delivery of the whole innings.

I also have a plain interest in fielding geometry — the half-space. That was the name of my old page, Half-Space Rangpur, because what the middle of the court's three corners is in basketball is an invisible gap between slip and point in cricket. Those gaps do not stay the same before and after a review. Given three minutes, a captain will often pull out silly point and drop fine leg back, or shift gully one step across — and that one step turns up in the scorebook as an edge. It works like pick-and-roll spacing: change the distance and the passing lane changes; change the distance in cricket and the angle of a catch changes. My eye does not see the difference between sports; it sees the structure.

The most uncomfortable part of reviews sits in money and cameras, and I will say this directly rather than obliquely. In many bilateral women's series there is no DRS at all, or only ball-tracking without UltraEdge or Snicko, and with fewer slow-motion cameras. So the doubt a male player can erase with one review, a female player in the same situation cannot. My nine years of watching say this gap is not a cricketing decision but a budget decision — and budget decisions walk onto the field wearing the shape of unequal verdicts.

One short parallel is warranted here, just one, and then I return to cricket. In football I have watched broadcasters edit a goalkeeper's long kick and distribution with great care while the basic business of shot-stopping quietly erodes. Cricket does exactly the same with wicketkeepers. The keeper who stays low and takes the turning ball in Mirpur, whose footwork nobody counts, is invisible; if he makes thirty off twelve, his name goes into the highlight package. The market tilts toward the flashy thing; the regular-season points table holds on the fundamental thing.

Now I come to the place where I disagree with the popular reading.

The standard complaint is simple: reviews slow the game, kill the celebration, waste broadcast time. My log says video review cannot carry that charge alone. Because what eats the most time is something no player can call for, and against which nobody has a right of appeal — the compulsory frame-by-frame check of the front foot and the catch on every dismissal. That check predates video review entirely and is the real silent time-eater. So when a spectator curses the word REVIEW on the big screen, he is really cursing a mandatory third-umpire protocol that nobody wants to remove, because removing it would bring back the largest controversy of all.

A second disobedient observation: review has not made umpires more accountable; it has made them more evasive. An on-field decision is now a provisional proposal — everyone knows it can change five seconds later. Even after the soft signal was scrapped a few years ago, the mentality survives: the umpire now feels the decision is not his, and so the responsibility for being wrong is not his either. When a game's authority is delegated to video, the authority in the middle of the field begins to depend on camera frame rates.

A third and more uncomfortable corner is incentives. A Twenty20 innings has an eighty-five-minute time limit. If a side has already crossed it, adding another three minutes later in the innings is not a serious penalty, while the job of cooling a batter's memory is completed in full. Which means the side breaking the rule gains the most from breaking it. This asymmetry is an accounting that exists outside the scorebook, and it rings loudest deep in the regular season, because the schedule is dense — fewer chances to recover, more weight on every point.

So what do we do with this three-minute ledger?

The easy answer is to shorten the review clock. Where a Test ground lacks the capacity, cut it; don't ask the batter, the decision and the appellant's fate are mine. The umbrella is fine — but "give me a moment, I'm checking" should not sit in an umpire's vocabulary. On Bangladeshi grounds this phrase stretches past two minutes three or four times a match, and that stretch is the theft I feel most. I have written before that two minutes is enough to cool a celebration; beyond that it cools the game itself.

And this is where the technology cuts both ways for me. Ball-tracking data is immutable — that is its beauty, and that is its problem. A process as precise as a hash will look the same frame by frame forever, but cricket's blood pressure runs in seconds. We have built a system whose claim arrives with proof, not with beauty.

I keep returning to one thing. At the end of a regular season we will have the record of time, but spectators do not remember time. They remember the pace of a match, the sound of a cover drive, a celebration that stopped. Over the next month or two, where four or five teams sit within two points in the middle of the table, the thing to watch is not the number of reviews — it is which captain knows how to save one and which one throws it away. A side that never lets anyone see its use of that mined time will not be contradicted by the points table.

Before closing the notebook each night I draw a small pencil mark in the same place: name on the left, the tally of blank time on the right. At the end of the season it will show that of everything that truly changed, more than half happened in those ten seconds when nobody did anything.

Caustic aftertaste aside, that is only an accounting. The question remains: if a review really is a timeout in disguise, then the next time we change the rule, will we be arguing about the time limit — or about whose hand holds the clock?