The 48 Seconds of DRS: A Five-Point Audit of Bangladesh's Review Culture in Tournament Cricket

19th over, fourth ball. The batter on strike had already burned a review two overs earlier, challenging an LBW that ball-tracking showed pitching outside the line. Now there's a thud on the same batter's pad, the umpire's finger goes up, and nobody in the dugout raises a hand. There was no reason to. One review per team per innings, and it had already been spent.

Back at my desk in Dhaka that night, I wrote five rows into my log: ball number, umpire's original call, whether a review was taken, the tracking output, and the final verdict. Five lines in a table. But the story was singular — the review was not lost to a decision. It was lost to an assumption.

That night changed how I look at DRS. In tournament cricket, a review is not technology. It is a budget. And when you spend a budget from the wrong account, you pay it back with interest, usually in the last over.

The law is written; memory is not

DRS entered international cricket on trial in 2026, in a Test between Sri Lanka and India. Player referrals — where the players themselves demand a review — arrived the following year, in a Test between New Zealand and Pakistan. From the 2026 World Cup onwards, the system became standard in limited-overs cricket as well.

The rule is black and white. Two unsuccessful reviews per team per innings in Tests; one in ODIs and T20Is. A successful review is retained, an unsuccessful one is gone. The third umpire's threshold phrase is "clear and obvious error" — the on-field call must be overturned only if the evidence is beyond doubt.

Then there is the concept of umpire's call: if ball-tracking shows less than half the ball striking the stumps, the on-field decision stands. And this is the subtle rule most people in the stands miss: if a review lands on umpire's call, the review is not lost.

In my log, the first row is always reserved for this law. Over the years I have noticed that Dhaka's debates cite it least and the emotion most.

One review per innings: the arithmetic is brutal

Many T20 watchers in Dhaka treat a review as a lottery — right, you win; wrong, you are wounded. The arithmetic is not that simple. A T20 innings is 120 balls. A team gets exactly one unsuccessful review — essentially one attempt across the whole innings. Even with a thirty per cent success rate, the expected value of a review is so high that discarding it amounts to burning a chance with your own hands.

That raises the real question: when to spend it? An LBW challenge in the powerplay and one in the 19th over do not carry the same market price. In the powerplay, runs flow but wickets are not scarce. In the final over, one wicket means a set batter walking off, a cold new batter at the crease, and two to five runs of swing on the scoreboard.

The true value of a review is set by the over in which it is spent, not by whether the decision was right. This is the line I keep writing in my tracker.

What happens inside 48 seconds

The player on the field has very little time. Within fifteen seconds of the ball becoming dead, the fielding side must signal its decision — and in T20 cricket, where time-wasting rules bite harder, that window feels merciless. Then the TV umpire's process begins: replays, UltraEdge, ball-tracking, spin vision, and finally the announcement.

In 2026, covering Abahani Limited Dhaka against Sheikh Russel KC, I reviewed an 89th-minute penalty from six angles and logged the referee's initial call, the 48-second VAR check, and the final decision. That structure later became my cricket desk's standard template. The logic is simple: a long review does not mean more information; it means more guesswork. A protocol shortens the clock and slows the judgement.

I built the five-point log in Dhaka because memory is not a review protocol. When someone says after a match, "I thought the ball was going leg-side", they are quoting memory, not evidence.

Angles: six cameras, one truth

Ball-tracking is triangulation — multiple camera frames stitched together to reconstruct the ball's path. Vendors claim tracking error is in the millimetre range. Two things must be kept in mind while hearing that claim.

First, error is small but not zero. On a ball grazing the stump, a five-millimetre difference is the wall between out and not out. Second, the prediction segment — the ball's path after it strikes the pad — is extrapolation, not observation. The final step of any review rests on a model, not on a camera.

A referee's eye is not intuition; it is a habit built frame by frame. A coach who cannot read six angles treats a review as a lottery ticket. A coach who can, treats it as a probability calculation.

Umpire's call: the conservatism inside the machine

This rule is the most interesting to me, because it opens a strategic door. Say you challenge an LBW. Ball-tracking shows the ball hitting the stumps, but within the umpire's call margin. The on-field decision stands, and your review is returned to you.

In other words, on tight-line LBW scenarios, the marginal cost of reviewing is nearly zero — while the marginal gain is substantial. If the call flips, you take a wicket. If not, you lose nothing.

In my own desk's log — and I want to be explicit that this is my log, not a broad global dataset — teams that operate well review these situations far more often. Teams that burn reviews on caught-behind hunches and UltraEdge noise retain their reviews less.

A log does not merely record events; it reveals patterns of decision-making. And a pattern means trainability.

Bangladesh's pattern: when it is spent, when it is not

Here I want to speak carefully, because in this section patriotism and data often speak through the same mouth. What I write is based on sequences I have seen, with medium-to-high confidence, because the sample is limited.

I divide Bangladesh's review behaviour into three types. One, the reactive review: the bowler appeals emotionally, the captain responds, the process starts. Two, the habitual review: a pre-set reaction to a specific bowler's specific line. Three, the calculated review: a decision taken after weighing over number, scoreboard state and match-up.

The first two dominate; the third is scarce — roughly four to one in my log. That gap is the most under-discussed operational deficiency in Bangladesh cricket. It is not technology that is missing. It is a protocol.

A live tracker taught me that chaos is just data waiting for a sequence. But the sequence must be built in the dugout, not inside the heat of the field.

Captain, keeper, bowler: the wrong apex of the triangle

Who takes the review decision? The reflex answer is "the captain". In practice the process circles three people: the captain, the wicketkeeper and the bowler.

The problem is that the bowler is the worst judge of the three, because he is emotionally invested. He believes the ball pitched outside leg. He heard a sound on UltraEdge. He wants it to be true. The gap between the tracking line and the bowler's feeling is the primary source of wasted reviews.

The keeper has the best vantage point, sitting closest to the line, particularly against spin. Yet in Bangladesh's case, the keeper's voice often reaches the captain late, because the communication is verbal, not signalled.

The fix is organisational, not technological: one designated person in the dugout, whose only job is to watch the monitor and send a single-word signal to the captain within fifteen seconds. Heavy noise, one word. That is what belief in a protocol looks like.

Powerplay versus death: the market price of an over

A review's strategic value varies across three phases of an innings.

In the powerplay, the field is up, the ball is new, seam movement is high. LBWs and caught-behinds occur most often, but the middle order is still intact. A successful review here removes a top-order batter — a big gain. A failed one leaves you naked for the rest of the innings.

In the middle overs — seven to fifteen — spin, changing bounce and a disciplined line arrive. LBW probability peaks, because the ball skids less and holds its line towards the stumps. In my log, the bulk of successful reviews fall in this window.

In the last four overs, one wicket is worth the most, but it is also the most fraught moment to spend a review — the captain is squeezed between pressure, crowd noise and strategy, with no time to balance them.

The review crisis is really a timing crisis, not an information crisis. Tracking data always existed. It simply did not reach the team's window in time.

Pitch and weather: the trap of subcontinental low bounce

Pitches at Mirpur do not offer much bounce. The point of impact on the pad is often below the knee. In these conditions, the prediction segment of ball-tracking becomes most uncertain, because when the ball keeps low, projecting its path towards the upper part of the stumps is harder.

This is where I have noticed something important: Bangladesh's review culture grew out of home conditions — low, slow pitches — but when a tournament moves abroad or to neutral venues, the pitch behaviour changes, and with it the review threshold.

That is not a failing of the tracking. It is a gap in preparation. If a team carries its own distance-map of successful reviews — which line, which height, what confidence level — decisions become fast. Trying to judge foreign pitches with domestic data is how reviews are wasted.

A referee's eye is not there to describe the weather, but to recognise the edge of the threshold. When the threshold shifts, the decision rule must shift too.

(Note: the paragraph above reflects my own observational logging, not an official statistical claim.)

A global benchmark: where comparison is due

How often a team asks for a review is not the point. What matters is how often it keeps one. Retention rate is the most honest indicator of a team's decision quality, because it is not directly tied to batting or bowling skill — only to process.

Watching the top sides, I separate three habits. One, they assign the review decision to one person, not to the whole team. Two, they rarely pass up tight-line LBWs, because the risk is low. Three, while batting, they hoard the review for the final overs instead of spending it on early emotion.

In Bangladesh's case, I have seen the opposite of the third habit most often. The review is frequently gone inside the first ten overs, leaving the team unarmed at the decisive moment. That is not merely a tactical failure; it is a failure of planning.

A contrarian angle: the problem is not the tracking

The most popular explanation goes like this — the technology is flawed, human judgement is being undermined, and Bangladesh is simply unlucky. I want to stand against that explanation, though with arithmetic rather than emotion.

The alternative explanation is simple: Bangladesh's review crisis is procedural, not technological. The same technology, the same umpire panel, the same ball-tracking — yet some teams keep reviews again and again, and we lose them again and again. The difference is created by dugout communication, pre-agreed thresholds, and the speed of the captain's decision.

One more rare fact deserves mention: there is no simple relationship between the wave of review controversy and a team's performance. If losing a review automatically meant losing a match, only teams using tracking would win. In reality, a review sometimes saves twenty-five to thirty runs and sometimes flips a session — but only when the decision was made thoughtfully.

Our debate is about technology; our problem is about the clock. The event happens in the fifteen seconds after the ball goes dead, and the preparation for those fifteen seconds happens long before, in the dugout, on paper.

The ledger of emotion versus the ledger of operations

After a match, the picture is familiar. One frame goes viral on social media, captioned "robbery". Someone posts a tracking screenshot; someone else points at umpire's call. The discussion happens in the ledger of emotion, while the match belongs to the ledger of operations.

I do not disrespect spectator emotion — it keeps the game alive. But to assess decision quality, the emotional ledger has to be closed. Whether a review succeeded is a blunt fact; why it was taken or not taken is the working fact.

There is a larger cultural debate here, bigger than Bangladesh: should technology be treated as final, or should room be kept for human judgement? My position is clear — umpire's call should not be abolished. Automated prediction carries its own error, and on a ball grazing the stumps, the rule protects the decision from that error. The debate should be about the rule's effectiveness, not about a match result.

Emotion can give birth to every decision, but only a protocol can test every decision. That is exactly what my five-point log does — not to remove emotion, but to freeze it under a timestamp.

The mathematical honesty inside the protocol

Someone may ask why so much arithmetic. Cricket is a game of umpires, bowlers and batters. My answer: arithmetic does not change cricket; it makes cricket's errors visible.

Consider the scale. A Test match runs around 240 overs across five days. An ODI is 300 balls. A T20 is 240 balls. Within that volume, the review window is a handful of balls, a handful of seconds. When so much rests on so little time, preparation is the only controllable variable.

My log has a column I call silence. Ball speed, pitch mark, camera angle — with all the data present, some decisions remain where the evidence is inconclusive. In that cell I write a confidence score: low, medium, high. When confidence is medium, not reviewing is the correct decision, because burning a limited resource on the unknown is a mistake.

Chaos is not always explicable, and admitting that is the first condition of good analysis. A piece that finds a perfect reason behind every ball is not a working log; it is a story.

Tournament pressure: where the shift happens

Tournament cricket differs from a bilateral series not only in stakes but in the structure of pressure. In a bilateral series, a defeat is absorbable; in a tournament, it means elimination. That pressure slows a captain's decision-making — and in reviews, slowness is a direct loss.

At a T20 World Cup, every match from the Super Eight to the knockouts feels like a knockout. Teams commit two kinds of error here: spending a review too fast, or leaving a possible review unclaimed out of caution. Both grow from the same root — insufficient preparation.

At the 2026 World Cup in Russia, I tracked 23 penalties and 20 VAR overturns in my live spreadsheet, flagging clear and obvious errors by minute and camera angle. One lesson travelled with me to cricket: the teams that did well in tournament football were good not only at playing; they were good at deciding. In cricket the difference is no smaller.

What must change: five proposals

First, a designated review coordinator in the dugout, watching the monitor and sending a one-word signal within fifteen seconds.

Second, a pre-built threshold policy: which line, which height, which pace should trigger a review — decided at the planning table, not in the captain's gut.

Third, reduce the bowler's weight in the decision and increase the keeper's, especially against spin. The keeper's angle is the most underused asset in the review process.

Fourth, a review audit after every match — how many were taken, how many were retained, in which over, with what consequence. If a team can manage a death over ball by ball, it cannot fail a review audit.

Fifth, decision training from domestic cricket up. Reviewing is a skill, not an inheritance; it can be taught and sharpened.

Final word

Sitting at a desk in Dhaka, I keep seeing one thing again and again — our conversations usually start after the match, almost never before it. The shift in review culture can begin exactly there: on a sheet of paper before walking onto the field, listing which situations are worth a gamble and how big.

My five-point log will never win a match. But it can give a captain one extra second in the next one. And in a T20 death over, anyone who has played knows what one extra second is worth.

The question, then, is not about the opposition. It is about our own process: if a team cannot bank a single review, how will it ever dream of banking five days of a Test match?