The Review Ledger: What a Captain Decides in Fifteen Seconds — Reading the DRS Account Book

That afternoon near Gate Nine at Mirpur, the air held dust and the smear of heat. Inside the stadium it was the second day's session, the pitch slowly cracking, the spinner rolling his wrist over. The scoreboard read 142 for 4. Just then the ball was cut toward cover, and a fraction before the boundary line the umpire did not raise his finger. The captain went quiet for two seconds, looked at the keeper, the keeper nodded, and the captain shaped a 'T' with both hands. The review went up. Ball-tracking came back — missing off. Review gone.

It was that side's second review of the innings, and it had just been burned.

On the field nobody yet knew what was coming. Slowly the big screen unfolded three stages — pitch, impact, wickets. The ball had pitched on leg, struck the pad, and was travelling past the stumps. No Umpire's Call, just a plain miss. A murmur rose in the stands, but a row was added to my ledger: second review after the fourth over, outcome — unsuccessful.

I was sitting in the Rajshahi press box, writing in my notebook. In my notebook every match is a row and every review a cell. Those cells have piled up over years to form my real material — not the score of the game, but the habit of decision-making. Everyone reads the score after the match; only someone who counts what lies outside the camera frame learns to read the habit.

My argument is simple: a review is not a game, a review is a document. And anyone who knows how to read a document can see why one side repeats the same mistake while another, in the same crisis, decides coldly and correctly. This piece is an attempt to read that document.

What DRS Actually Is, and Where It Came From

The Player Review System was born in July 2026, in the Test between India and Sri Lanka at Colombo. From that first application to today, the system has rested on three pillars — ball-tracking, Snicko or UltraEdge, and Hot Spot — joined by stump microphones and a direct communication protocol between the on-field umpires and the third umpire.

But DRS is essentially a bureaucratic arrangement — an appeals court. The on-field umpire gives the primary ruling; a side gains the right to challenge it, but only a fixed number of times. In Tests each side gets two reviews per innings, returned if successful. In ODIs and T20Is each innings carries two reviews, and a successful review is not returned — and it is here that the strategic difference between the formats is born. In a Test a successful review means another chance; in an ODI a successful review merely erases a failure, it does not grant a new one. A captain who does not keep that arithmetic in his head is playing a lottery.

Bound up with this is the notion of 'Umpire's Call', the most mysterious thing in cricket to the ordinary viewer. If ball-tracking shows the ball striking the stumps, but only marginally — less than the margin needed to prove that the centre of the ball is inside the outer edge of the stump — then the on-field umpire's decision stands. Similarly, if the point of impact is more than three metres from the stumps, the on-field decision is final no matter what the tracking shows.

Viewers often read these two rules as a conspiracy to protect umpires. They are in fact an honest acknowledgement of the limits of the technology. Ball-tracking is itself a predictive model — it extrapolates the ball's path from camera frames and extends it to the stumps. Once the ball strikes the stumps and bounces, or changes direction off the seam, nobody can say with certainty how accurate that extrapolation is. So the decision inside the margin is left in human hands rather than handed to the machine.

The rule here is clear: technology does not make the decision; technology grants permission to challenge the decision. A captain who fails to grasp this difference believes he is asking for 'justice' when he is in fact asking for 'reconsideration' — and the gap between those two can turn a match.

The Fifteen-Second Problem

The real drama of a review does not happen on the field; it happens inside the captain's head, and it is given only fifteen seconds. From the moment the umpire rules, the captain must decide within that brief window. In those fifteen seconds the information available is this — a blurry view of his own eye, the keeper's shout, the nearest fielder's opinion, the bowler's emotion, and the weight of the scoreboard.

This is where my ledger first earns its keep. Over years I have noticed that the decision to review is almost never a single person's decision. In Test cricket it is largely an ad-hoc committee of three — the keeper, the nearest bowler, and the captain. In ODIs time is shorter, so the keeper's role grows. In T20Is the decision must be fastest, and there the error rate is highest.

Sides whose keeper carries the most weight in the decision tend to have the higher review-success rate — because the keeper's angle is the best. The keeper stands behind the wicket; no one reads the ball's line and length better than he does. My notebook holds many innings in which a captain ignored the keeper's signal and reviewed on the bowler's emotion, and the review failed. A side that can tell the bowler's emotion from the keeper's observation burns the fewest reviews.

I once took old footage and split it into fourteen frames to see how a review decision was made — at which second the captain looked at the keeper, at which second the bowler raised his hand, at which second the captain shaped the 'T'. Since that day I have kept a habit: I record not only the outcome of a review but the timeline of the decision. The outcome tells you what happened; the timeline tells you how — and foresight comes from the second.

The Economics of a Review

In Test cricket a review is a finite resource, and any finite resource breeds an economy. Two reviews mean two tokens. The question is when to spend them. Early in an innings against a possible opening batsman, or late in the final session against a tailender?

The answer is mathematical. The value of a review rests on three things — the value of the wicket, the probability the decision will be overturned, and the position in time. Early on, the value of a wicket is at its peak, because that batsman may play a long innings and set the match's tempo. Late on, against a tailender, the cost of burning a review is low, but so is the reward.

One pattern returns again and again in my ledger: captains who hear the word 'maybe' in fifteen seconds and review anyway burn more; captains who review only when they are utterly certain inside review less but succeed far more.

That lesson has not fully arrived in Bangladesh's domestic game. In National Cricket League matches I have often seen young captains use a review as a protest — reviewing because they dislike the umpire's decision. At the international level that mindset is self-destruction. A review is not a tool of protest; it is a tool of correction.

The Angle the First Replay Buries

Broadcast cameras show us one fixed view — usually front-on or from behind the stumps. But the decision rests on information that view does not capture. The side-on angle shows the ball's line; the stump camera shows the height of impact; ball-tracking shows the future path — which no camera can show directly, because it has not happened.

So when a viewer shouts 'that was obviously out', he is assembling in his head a composite picture built slowly, watched repeatedly, from an armchair. The umpire on the field never saw that picture.

Every angle confesses something the first replay hid. The front-on angle hides the pitching; the stump camera hides the line; UltraEdge catches only the sound of contact, not the line. No single angle ever tells the whole truth — truth is made from the combination of angles. And that is exactly why, at every disputed decision, I ask myself: which angle did the broadcast show me, and which did it withhold? The hidden angle usually holds the real story.

Domestic Cricket as My Control Group

I have worked inside Bangladesh's domestic system eight times, and my biggest lesson came from there. The National Cricket League and the Bangladesh Premier League are, to me, the 'control group' for international cricket — a laboratory. Here there is less money, fewer cameras, fewer reviews, but the people are the same. The same captain, the same keeper, the same bowler, the same pressure.

If a pattern appears in an international match, I first look for it in a domestic match. Because in domestic cricket the pressure of outcome is lower, so a player's true instinct shows. An example: when a captain suddenly makes an unusual decision in an international, I am certain he made the same decision six months earlier at Mirpur, where perhaps nobody noticed.

What is proven at Mirpur only surfaces on the big screen at the international level. I write this often because it is my firmest belief — the big stage creates nothing new; it merely enlarges the old habit.

Domestic cricket teaches one more thing that international broadcast loses — the role of language in a review decision. In the National Cricket League the umpire and the player often speak the same language; misunderstanding is lower. In an international match the umpire, the keeper, and the captain may be three people of three languages. Crossing that wall of language within fifteen seconds makes the decision harder still.

Umpire's Call: Humility, or Weakness

In 2026 the International Cricket Council considered abolishing Umpire's Call. The argument was that if the technology shows the ball striking the stumps, it should be out — no margin. In the end the system survived. Why?

Because of the technology's own doubt about its own accuracy. Ball-tracking is an estimate. Where the ball would bounce after striking the stumps is an estimate; whether it would deviate off seam or spin is an estimate. If the ball strikes half the stump and misses half, the decision is clear to nobody. Making the technology the final arbiter in such a case means making the technology's error the final truth.

Umpire's Call is therefore not weakness but humility — an acknowledgement that technology can err as humans do, only with greater confidence. A viewer who reads this humility as 'inconsistency' either does not know the technology's limits or refuses to accept them.

I say this from the vantage I occupy — beside the third umpire's chair, where every frame glows on the surrounding screens, and where you know that in real time the umpire had only one angle and fifteen seconds.

The Price of a Burned Review

A failed review does not merely waste a chance; it pushes a side into greater risk. Late in an innings, when the pitch breaks and the spinners turn it, that is when reviews are needed most. A side that has burned both reviews early plays with its hands tied. This pressure indirectly shapes how the batsmen play — they know that if they are wrongly given, there is no recourse.

The number of reviews is a strategic asset, and managing an asset means spending it at the right time. In my ledger I track this 'spending timeline'. I watch at what percentage of an innings a side spends its reviews. Sides that exhaust both reviews within the first thirty percent have far less capacity to survive the final session — one of the steadiest patterns in my notebook.

The Same Decision, Two Eyes

One thing has puzzled me for years in Bangladesh cricket. The same kind of decision — say, a ball striking the pad — one umpire gives out and another gives not out. The viewer then says, 'there is no rule'. But there is a rule, on the page, in the words, in the clauses. What is missing is consistency of application.

After an incident in 2026 I stopped writing adjectives and began writing clause numbers. Because a clause number is the only language that survives emotion. You can say 'that was out', but you cannot say 'clause eleven makes that out' — if it does not.

A rulebook is a map, not a mirror; intent lives in the terrain. The letter of a rule can be memorised, but how that rule applies in a given situation can be understood only by knowing the terrain — the rhythm of the game, the character of the pitch, the state of the match. An umpire who knows only the letter is a machine; an umpire who also knows the terrain is a judge.

The Battle of Emotion and Rule

The most painful moment for a viewer is when he realises the decision was 'correct by the rule' but his sense of justice cannot accept it. This is where most of my time goes — explaining that rule and justice are not the same thing.

A rule is an agreement everyone accepted in advance. Justice is a separate picture inside each person's head. When the two collide, what survives is the rule — because justice differs for everyone, while the rule is one for all. The umpire's job is not to do justice; the umpire's job is to apply the rule.

That sounds cruel, but it is the foundation of the game. The moment we tell an umpire 'rule according to your sense of justice', we lose the game's true beauty — because then no decision is predictable, and predictability is what makes a game a game.

There is a subtlety here I want to stress. Respect for the rule does not mean blind obedience. It means consistency of application — the same decision in the same situation, always, on every ground. The viewer's real complaint is never against the rule; it is against consistency. He wants to say, 'why was the opposite given for the same thing last match?' That question is the legitimate one, and it is the centre of my work.

What Was Unknowable in Real Time

In every disputed decision I follow a discipline. First I say what information the on-field umpire had. Then I say how much time he had. Then I say what the correct decision could have been with that information and that time.

This order matters because it builds a wall between outcome and process. Replays make everything look easy. In slow motion, from eight angles, repeatedly — yes, obviously. But the umpire must be judged on process, not outcome.

Judging an umpire now, with information he never had in real time, is unjust — because you are judging with data that was never in his hands. This is the most common injustice in cricket discussion, and I stand against it in every piece I write.

Technology Is Not Telling the Whole Truth

There is a myth about DRS — that technology sees everything. It does not. Technology sees certain things, and even those, in some cases, it estimates. Ball-tracking estimates the future path. UltraEdge catches only sound — it must distinguish the sound of air, of bat, of pad, and that distinction is not always clear. Hot Spot shows only where friction created heat, but whether that was bat or pad cannot always be separated.

In 2026, in the empty-stadium matches, I heard these limits anew. When the crowd noise went, what the broadcast microphones caught was something new — the tone of doubt between the umpire and the third umpire, the hesitation of the moment. How often an umpire has said 'wait, let me look once' and paused — the sound of that pause taught me what the threshold called 'clear and obvious error' actually sounds like.

Listening, I understood one thing — 'clear' and 'easily predictable' are not the same. What is easily predictable may not be clear. And that distinction is the root of every dispute.

How to Read My Ledger

In my notebook every match is a row; every review a cell. In that cell I record not only the outcome but — who decided, how long it took, the type of review (LBW, catch, pitching, boundary), and at what point of the innings the decision was made.

Reading these cells, I learned something no broadcast taught me — the decision to review is a mirror of personality. A captain aggressive on the field is aggressive in review — reviews more, burns more. A patient captain keeps patience in review, waits for the chance. Both styles can work, if there is a conscious system behind them.

What does not work is the absence of a system. A side with no pre-set rule for reviewing decides anew at every review — in fifteen seconds, on the shove of emotion. These are the sides that own the most failed reviews in my ledger.

Big Squads, Deep Benches, and Review Pressure

When a tournament's tempo rises, one thing becomes clear. Sides with deep squads survive the final session, because they have more options. In cricket the analogue is review management. A side that plays more matches, faces more situations, has a richer memory-bank of review decisions. And that memory-bank is what saves a side in the final session.

Under tournament pressure captains err more, because every match feels like a knockout. But for that very reason, a tournament demands more discipline. A side that assigns the responsibility for review decisions before the tournament — usually to the keeper or a designated senior — errs less during it.

Tournament pressure compresses emotion, and that compressed emotion is the most dangerous kind — because the man believes he is deciding with reason when he is deciding with fear.

The Other Side: When the Obvious Call Is Right

I am always careful that my analysis does not become a habit — the habit of always finding the reverse. That is a trap. If you say in every piece 'the first angle lies', the reader learns what to expect every time, and then the reversal stops surprising.

So I concede this too: often the obvious decision is the right one. Often the on-field umpire correctly gives it out, and the captain's doubt was only regret. Often the first angle tells the truth, and the angle we hunt for hides nothing.

A pattern is credible only when it sometimes has the courage to deny itself. An analyst who finds a conspiracy in every match is not an analyst but a storyteller, who plants the same character at the end of every tale. I do not want to be that.

Language, Culture, and Fifteen Seconds

One thing I have seen in Bangladesh cricket and nowhere else. Here there is a cultural closeness among players, umpires, and coaches that is rarer elsewhere. This closeness sometimes helps — a player reads an umpire's mood, reads when a review might pay. And sometimes it hurts, because personal relationships influence decisions.

I return to an example. In a National Cricket League match I watched a young captain decline a review on an LBW decision when ball-tracking suggested the odds of out were high. Asked afterwards, he said he knew the umpire was ruling correctly that day, so he did not challenge. That is not review strategy; that is relationship arithmetic. And that arithmetic is the hardest cell in my ledger — invisible to any number, yet it shapes the decision.

The Viewer's Psychology

Viewers love reviews because a review grants them power. They are no longer merely spectators but assistants to the judge — they watch three balls tracked on screen and believe they too are part of the decision. That feeling of participation is what made DRS so popular.

But that participation creates a problem. When a viewer joins the decision, he binds himself to its outcome. A failed review leaves him not merely disappointed but humiliated — as if he had been cheated. And that feeling of humiliation shouts loudest on social media.

The viewer's complaint is never against the rule; it is always against transparency — he wants to know how the decision was made, not only what was made. And that demand is legitimate. If the broadcast showed the viewer the decision's journey — what was seen at which stage, where doubt arose — half the disputes would never be born.

The Path Forward: What Could Be Done

Three proposals from my ledger ring loudest in my head.

First, broadcasts should show the journey of a review decision, not only the final outcome. If viewers knew at which stage the technology estimates and at which it measures, much needless dispute would fade.

Second, sides must bring more discipline to review decisions. In fifteen seconds, process must work instead of emotion. Some sides already do this — by assigning one person a defined responsibility. That proves a review is not only reaction; a review is planning.

Third, umpire training must state the limits of technology more loudly. If an umpire knows where ball-tracking estimates, he will be more confident in deciding situations where technology should not intervene.

Toward the End

I think of that afternoon at Mirpur. The captain burned a review, the match result did not change, but the innings' course did — in the final session the side played with its hands tied, having lost the chance to protest a clear out.

From that first India–Sri Lanka review to today, the system is built more on human decisions than on technology. Technology has added only a new angle, and that angle has taught us that every angle is incomplete.

Let the tape finish before the verdict writes itself. Because the decision we now call obvious may be only the angle we watched most — not the most true.

Next season a new row will join my ledger. And I know those rows may again show — the side that yields its emotion in fifteen seconds pays for those fifteen seconds in the final session. The only question is whether our cricket is ready to stop paying that price.