Review Capital: The Asset No Auction Table Lists, But Every Series Turns On

Law 3.1 — Player Review. The clock stopped at 84.3 seconds.

The stump mic gain knob was turned to the right, so the sound of the edge reached my ears from the wrong direction — bat first, gloves two frames later. I had three tables open on the laptop: one for ball-tracking, one for review duration, one for umpire overrules. I did not get up from the chair, because the wicketkeeper was already raising both hands in the T-sign, and the big screen was burning with three words — pitch 2.9 metres, impact in line, wickets clipping. On a flat screen the word 'clipping' looks harmless. On the field it is not. The on-field call stood. The review was not retained. One of the innings' two had gone.

I froze that frame at 47. Had the ball taken the inner edge, or had it gone into the glove? On the UltraEdge waveform the difference is two milliseconds. Two milliseconds, and yet a review, an over's bowling plan, a captain's mental balance — everything stands on those two milliseconds. This piece is the arithmetic of that standing.

Frame 1 — The spreadsheet was my first whistle.

In November 2026, in the canteen of a coaching centre in Rajshahi, I logged all 41 reviews of the Bangladesh Premier League. The scene was ordinary: a cheap notebook, a cup of tea, and DRS arriving in Bangladeshi franchise cricket for the first time. I wrote four columns — ball-tracking frame, whether it was umpire's call, seconds between appeal and signal, and which umpire was overruled. By the final the numbers had settled into a table, and that table was my first published piece.

An instinct formed from that season onward: I do not write 'the umpire was wrong', I write 'Law 11, frame 47'. Because a wrong is an opinion; a frame is evidence. In a cricket culture that explains itself through stories, arriving with arithmetic means building ground under your own feet. The spreadsheet was my first whistle — nobody gave me the right to blow it, I picked it up myself.

Eight years later, I notice those review numbers have migrated from match reports to auction tables. Franchises now place a third column of money beside batters and bowlers — review capital. Nobody prints the name. Everybody pays the price.

Context 1 — How DRS entered Asia, and why it was late

Technology entered Asian cricket with suspicion and settled with trust; the distance between those two steps took roughly a decade. India agreed to use DRS in ODIs in the 2026-17 cycle; Sri Lanka and Pakistan had already used it in Tests; Bangladesh adopted it regularly from the late 2010s. Its arrival in the BPL in 2026 matters to me because it was the first time a T20 franchise league in Asia installed the system permanently, with no serious rehearsal window.

The oldest argument in Asia is not about accuracy but about authority. Who decides — the umpire in the middle, or three men in a room looking at a screen? During the 2026 Asia Cup that question arrived from two directions. One camp said ball-tracking was unreliable in our conditions. Another said that if the ball loses bounce travelling wicket to wicket, the gap between prediction and reality widens. Both are true. Both are unrealistic if you refuse to admit that tracking is a model, and that a model's error can itself be measured.

That is my professional centre. I do not argue against umpiring; I measure umpiring's boundary. Which frame can technology decide, and which frame can it only inform? That line was never drawn, and that is why so much anger has accumulated around reviews in Asian cricket.

Context 2 — What the law says, and what broadcast does not

The most widely misread fact: a review does not mean the umpire's decision is overturned. It means the decision is tested against clear evidence. Under international playing conditions each innings has two unsuccessful reviews; in Tests, two more are added after 80 overs. In ODIs and T20Is that number is the ceiling.

In LBW the tracking argument is split into stages. Where the ball pitched, where impact occurred, and how much of the stump the predicted path would strike. If an out decision is reviewed, the condition is that at least half the ball must be predicted to hit the stumps. Below that, the on-field call stands — what we call umpire's call. The reverse constraint exists too: if the ball pitches more than 3.5 metres from the stumps, overturning a not-out decision becomes difficult, because uncertainty in tracking is given the benefit of the doubt.

I logged the World Cup from a hostel room, one frame at a time — in 2026, twenty-four nights, four-hour sleep blocks, a stopwatch under the screen. Even then I saw that viewers rage in words like 'correct' or 'fake', while nobody states which frame produced the outcome. Nobody says the ball pitched 2.9 metres away, and that this was the centre of the decision. Without that sentence, argument stays at the level of emotion and never reaches the level of technology.

Context 3 — What is happening now: auction season

You may ask where reviews meet auctions. Directly. In franchise cricket the margin between winning and losing has narrowed so far that one review, one retention, one injury notice can decide a series. And those are exactly the three things decided at an auction table.

Every transfer rumour needs a timestamp and a source. Who said it, when, and what shape the contract takes — release clause, retention fee, match fee — without those, a report is incomplete to me. Across recent cycles I have noticed something: the franchise that finalises its retention list early also gains the time to build its review policy. Because the combination of wicketkeeper, captain and spinner is the capital of review capital.

In Asia's franchise market, the price of those three has risen over five years, and I do not read that as coincidence.

Core 1 — What review capital actually is

Keep the definition simple. Review capital is a team's capacity to take the right decision at the moment of doubt. It is built from four inputs. One, the ability to gather information — which bowler gets which umpire's benefit, how often. Two, the speed of transmitting it — a one-second link between the captain in the middle and the analyst by the boundary rope. Three, the captain's tolerance for uncertainty. Four, the wicketkeeper's eye and voice, because the man behind the stumps often issues the instruction.

Those four inputs produce an outcome that appears in no column. At an auction you will count a keeper's runs and strike rate, and how quiet he stays behind the stumps. You will not count whether he can decide in five seconds. Yet the second number matters no less to the result than the first.

Core 2 — The keeper market: the auction's invisible column

The wicketkeeper's market is strange. His value is set by two kinds of work — what the camera sees and what it does not. Runs, stumpings, catches are visible. But the habit of talking line and length from beside slip in the first two overs, of warning a bowler about his rhythm, of raising a hand five seconds after an LBW probability appears — none of that reaches a scorecard.

Yet in Asia's franchise auctions I have seen a pattern: the side that spends heavily on a keeper tends also to lead in review retention two cycles later. Part of it is technical. From behind the stumps you see the ball's line from an angle unavailable at slip or point. When a spinner turns the ball both ways, the keeper often senses whether it is missing leg and hitting pad. If that read is accurate, four or five extra review wins arrive in the league stage.

In Asian Test cricket, a handful of names built this culture — Kumar Sangakkara, in his time, created a quiet dependence between slip fielding calls and review instructions behind the stumps, and later Nurul Hasan Sohan in the Bangladesh setup gradually took on that role. This continuity is not accidental. Buy a keeper as a keeper and he takes catches. Buy him as a decision-maker and he controls the match. Decision-making keepers often cost 20 to 30 per cent more, and no advertisement mentions it.

Core 3 — The captain's calibration

There is a calibration to taking reviews. When a captain hears 'it hit him high', two questions must switch on. First, is my bowler one who usually gets extra bounce? Second, is this a surface where the ball will be predicted to strike at least half the stump? Very few captains know the answer to the second. That ignorance is the largest cause of wasted reviews. Subcontinental pitches, especially in early winter or on day three of a Test, are low and slow. Under low bounce, tracking uncertainty grows. So the belief that the ball would hit often proves wrong, and a captain's two reviews vanish in the first two sessions of a series.

In my own logging I began splitting review decisions into two kinds — bounce-driven gambles and line-driven calculations. The second kind succeeds several times as often, and that ratio barely changes between teams. What changes is which captain takes which kind, and whether he does so consistently. Consistency means the captain is not merely making good decisions but making his mistakes in the same direction. An error with a pattern can be corrected. Random error cannot.

Core 4 — The analyst economy

Franchise budgets swell on stars, but matches are won on information flow. An analyst in a security box now does three jobs: read ball-tracking data, understand umpire tendencies, and keep time. The third is least discussed. Under law, a wicket triggers a defined window for a review; the bowling-end umpire controls DRS and the signal must come within it. On television the delay looks trivial. On the field it is an entire thought.

A simple sum. If a franchise adds one extra analyst for the full season, the cost usually sits within a few multiples of a bench player's match fee. If that analyst's work produces four extra review wins in a season, and each win saves 8 to 12 runs on average, the arithmetic closes quickly. A bench player's saves are probabilistic. A review win is an event.

In Asia's smaller leagues this post is often temporary, or absent. Where no referee-analyst sits outside the main group, the whole weight of review capital falls on the captain and keeper. That is a policy choice, and its results show in scorelines without ever being named.

Core 5 — Timestamps: making review duration a metric

One metric almost nobody in Asia's cricket media uses — review duration. The gap from appeal to signal, signal to screen announcement, announcement to restart. Read those three together and you can say a great deal about an innings' discipline. A long review is not always bad; sometimes the decision was genuinely hard. But frequent long reviews signal something — the captain is hesitating, or information is arriving late. And in T20, time is everything. The longer the delay, the harder to restore a cooled bowler's rhythm.

Nobody accounts for this cost. Five long reviews in an innings means roughly ten minutes lost, the equivalent of an over. In a rain-threatened match those ten minutes can shift a Duckworth-Lewis calculation. In Asian cricket this is rarely discussed, because nobody links those ten minutes to decision time.

An empty stadium taught me that silence has a data trail — in the recordings of 2026's behind-closed-doors matches I found that silence is an easy way to measure delay. No crowd, so the signal's speed is not buried under atmosphere. Revisiting those files, I understood that review duration is not a curiosity, it is an organisational indicator. The better organised the side, the shorter the time.

Core 6 — Asian conditions and the limits of tracking

Before entering the technology debate, accept the geography. Asia has three main playing environments, each with different tracking uncertainty. On dry, dusty subcontinental pitches the ball slows as it ages but turns more; greater turn means greater lateral curve in the prediction, and when curve combines with bounce, error grows. In Gulf venues — Dubai and Abu Dhabi especially — surfaces are smooth and bounce is true, so tracking accuracy is higher, yet that is where most controversy occurs, because the margin is one run on the scoreboard. On some wet, slow surfaces in Sri Lanka and Bangladesh the ball stays low; there, LBW uncertainty cuts both ways, against all-out and for not-out.

Remember this: tracking is a measured system, but its quality is measured differently across leagues. If each league published its own calibration data, argument would shrink. Nobody publishes. And where transparency is absent, trust cannot be born — the two are the same sentence.

Core 7 — Spin, the 3.5 metres, and a wasted review

I have watched this scene many times. A leg-spinner turns one in, it hits the pad, on-field not out. The keeper's hands go up, the captain reviews, the screen shows the ball pitched 3.6 metres away. Review gone. Was the review wrong? In one sense yes — the captain forgot the rule. In another no, because the ball would genuinely have hit. Two truths stated together make the reader intelligent, and that is where writing earns its keep.

The 3.5 metre rule exists because of a real limit. When a ball pitches far from the crease, the range of prediction error widens. It is not accidental; it is arithmetic. But nobody explains it, so in Asian cricket this rule hears the word 'unfair' more than any other — when it is a boundary, not an injustice.

My preferred proposal: do not scrap the whole review process. Separate the improbable review from the faulty review. The first is a team's policy decision, the second a process weakness. League analysts' reports should state what percentage of reviews were lost to rule boundaries and what percentage to bad information. In Asian cricket nobody separates those two numbers.

Core 8 — The real numbers on the auction table

Now to the market. A franchise auction is a bidding process, and price is set by demand and the number of alternatives. For keepers, both have risen in recent cycles, because the keeper's job description has widened: batter, de facto review director, bowling-change adviser, and sometimes the anchor of mid-innings calm.

One blunt point. When the market rises, not everything rises — some prices rise for a reason. Only the keeper who can demonstrate, in writing or in conversation, that he is fast in review decisions receives that premium. The rest receive general inflation. In my reading, the match impact gap between those two kinds of keeper is wider than the price gap. I have also noticed that sides adopting a pace-friendly review policy — those who review more for their quicks on LBW — stumble on spin-dominant surfaces. Spin carries higher tracking uncertainty, so the same policy does not work in two conditions. Assets can be bought. Policy cannot; it must be built, and that takes eight to ten weeks.

Four questions belong in every auction file. Is this keeper quiet or balanced? How often has this captain burned both reviews in one innings? What is the team's instruction on reviewing for this spinner? How accurate was this league's tracking over the last three seasons? Answer those and what remains is luck.

Core 9 — Contracts, clauses and the price of instability

There is amusement in the paperwork too. Retention fee, release clause, match-based payment — the player strategy hidden inside those three phrases influences dressing-room decisions as much as an injury list. If a player's contract carries match-linked bonuses, a coach hesitates to rest him, and a tired keeper's five-second decisiveness normally declines.

A 90-day plan is just a referee — meaning that without a year-round structure, every franchise repeats the same mistakes at the end of a season. A side that decides in advance which matches it will not review discovers that its review capacity lasts to the end of the season.

One more observation from several cycles: the money a side saves or wastes at retention often shows up clearly in the review decisions of its first three matches. A new fielding plan takes time to bed in, and the link between fielding plans and review appeals is direct. If the keeper does not sync with slip, he will not sync with the umpire.

Core 10 — Injury and the invisible review budget

Another cost that only insiders know. Injury management directly affects review decisions. A fielder carrying a finger injury cannot dive quickly at slip; he may be stationed at wide second, from where the camera angle makes judgement hard. A keeper with a knee problem, asked to stay behind the stumps for twenty straight overs, begins losing concentration in the final third of an innings. That is usually the window of review crisis. Reading an injury list therefore means knowing not only the XI but the probability of a review crisis. I did not think this way at first; a physio's decision changing everyone else's fate is something I learned from a colleague showing me a table on a phone after leaving the hostel room.

Core 11 — Bangladesh's review gap

I measure my own country's cricket because the gap is clearest here. For a long time Bangladesh carried a hesitation about reviews — whether to trust the technology. Across cycles since the 2026 BPL logging, the pattern of reviews lost in Bangladesh innings has been broadly consistent, and that is not accidental. Two patterns stand out. First, a tendency to review pace bowlers' slanting deliveries on low-bounce surfaces, where tracking uncertainty is highest. Second, a shortage of review capacity at the very end of innings, when the best keeper and best batter are both tired — exactly when decisions go wrong.

The fix is quick. Four things produce a difference in six months. First, read the tracking accuracy notes before every home series, as far as the host shares them. Second, joint rehearsal for keeper and captain, twice within a week, measuring only decision speed. Third, log what percentage of LBW reviews are won in domestic matches. Fourth, keep review discussion inside the dressing room, framed in process language rather than blame.

What teaching taught me is this: tell a team not 'you made a mistake' but 'your third stage would have been right if you had filled the slot earlier'.

Core 12 — The women's numbers nobody writes

An admission of incomplete work. I did not initially log women's international reviews separately, because replays arrived less often. As scheduling expanded over the last two years I built a separate table, because I realised borrowing men's numbers for women's cricket is wrong — conditions, ball and lengths differ. What emerges is clear: in the shorter format there is less review capital but more decision risk, because innings are short. Here two reviews mean eight to ten runs. Sides arriving underprepared spend more time learning than playing.

Keep one proposal: write the gap down.

Core 13 — Replay and process: what esports teaches

It may sound odd, but part of my understanding of reviews came from esports. In esports the replay is the referee, because the data is integral — camera and sensor sit as close to perfect as possible. Watching how a call is recorded at frame precision shows that in real cricket the fault lies not in the technology but in the recording structure. In esports, two different outcomes for the same input is a case of manipulation. In cricket, two different outcomes is called 'insight'. The difference is procedural. Cricket has limits of speed and resolution; some people accept that and work within it, some do not. The patience came from the World Cup logging: admit the error and it can be corrected; turn it into farce and it cannot.

Contrarian — Why 'abolish umpire's call' is the wrong demand

The demand returns to Asian media again and again: abolish umpire's call because teams are punished. The argument is emotional, and emotion goes wrong exactly when it fails to reconcile technical thresholds with a difference in power. I say it is wrong for three reasons. First, umpire's call exists because tracking is a model, not proof. Second, if you refuse to accept the model's uncertainty, who decides then — the most influential? The side investing most in information wins. The side with no referee-analyst loses. The current arrangement protects the weak and constrains the strong — uncomfortable, but true. Third, the most practical: umpiring is a profession. If technology becomes final on every marginal LBW, field umpires become relay nodes, the umpiring pool weakens, smaller series suffer most, and eventually the foundation weakens. The counter-proposal: publish per-match what percentage of calls went to umpire's call, and how many of those occurred on a side's second review. Read together, you stop calling it luck and start calling it process.

Contrarian — Dubai, 6 November: law against emotion

One of Asia's most debated recent episodes was not about technology but about time — Angelo Mathews' timed-out dismissal at the 2026 ODI World Cup. Law 40.1.1 requires a batter to be ready within the stipulated time; under the 2026-24 playing conditions that is two minutes. The umpire's call and the captain's appeal were both lawful. I cite it often because it shows that the same law-versus-emotion conflict appears without technology. Much emotion was generated in Bangladesh and Sri Lanka. Reading both sides convinced me the argument froze at a structural question: who measures the delay — the field referee or the governing board? Measured by one, it is misfortune; by another, it is bias. That measurement must be written clearly before a series begins.

Contrarian — The empty stadium's lesson: silence is not emptiness

In 2026 stadiums were empty and my freelance income fell to nearly zero. Sitting at a canteen table with rebroadcasts running, I logged frame by frame. I worked on a library of more than 300 clips — whistle tones, crowd gaps, referee-mic bleed. Those files taught me one thing: silence carries data, but not all silence is the same. One silence means no noise; another means nobody is speaking. That distinction now adds texture to my writing. When a team says nothing about a review, it may be a lack of confidence, or it may be that they know exactly what they did. To tell the difference you must read further — other voices, third sources, statistics. Read silence alone and you get a story, not understanding.

Takeaway — Who leads the next cycle

Review capital now carries weight at the auction table, and in Asian cricket the shift is one-directional. Three things are coming. One, analyst posts become permanent rather than match-based; sides still treating them as per-match costs will fall behind. Two, keeper brackets will keep rising, and with the price will come scrutiny — only those who decide will remain. Three, tracking transparency will become a controversy, and leagues will either explain themselves or wait. I keep the last question to myself, because the answer is not in my hands. In a match where two of three reviews end in umpire's call, who is punished more — the tracking system, or the side that never learned to read it? I know what I will write. But first, think: in your team, who is the person who will decide, in the final second, to go or not to go? How much longer will that person's name stay unknown — frame 47?