From Timed Out to DRS: Who Really Governs the Review Protocol in Asian Cricket

Angelo Mathews walked out at the Arun Jaitley Stadium in Delhi after Sri Lanka's fifth wicket fell. His helmet strap snapped. He signalled for a replacement. The clock kept moving. Two minutes passed. Bangladesh's captain appealed. Marais Erasmus and Richard Illingworth conferred, spoke to the third umpire, and came back with a verdict. For the first time in the history of international cricket, a batter was timed out. The date was 6 November 2026. Social feeds filled up with two sentences that night: a violation of the spirit of cricket, and a rule is a rule. At my desk I filled in three boxes instead: which law, which timestamp, which decision. There was no column allotted to outrage. I built the five-point review log in Dhaka because memory is not a review protocol. The law is clear. The MCC's October 2026 code trimmed timed out from three minutes to two. Under ICC playing conditions an incoming batter must be ready to receive the ball within two minutes, or be given out on appeal. That evening only one question mattered: did a broken helmet strap block a batter's readiness, or was it his own responsibility? Both umpires leaned toward responsibility, and their reasoning was never written down anywhere. That is why the moment carries weight beyond the result. Timed out has no DRS and never did. Yet in matches that do have DRS, exactly the same question keeps returning: who made the call, on what input, and can it be audited later? In Asian cricket the answer is usually missing, because the log behind the decision is not public. DRS was first used in July 2026 at the SSC in Colombo during the Sri Lanka-India Test series. The core structure has barely changed since: two reviews per innings, reset in Tests after 80 overs. The third umpire can overturn only with conclusive evidence. And if ball tracking does not predict more than half the ball striking the stump, it stays umpire's call, which means the on-field decision stands. Here sits Asia's structural gap. The ICC controls DRS technology centrally for its own events, but in bilateral series the host broadcaster provides it, which means ball tracking and UltraEdge run on the host board's money. Some series have dropped DRS entirely on cost grounds. When the feed of the same technology sits with the host, the neutrality question is not about the quality of the technology. It is about the architecture. So the incident in the 25th over is not isolated. The same question stands in two places at once: who decides, and can that decision be audited afterwards? A referee's eye is not intuition; it is a habit built frame by frame. In my five-point log the first box is always the law, the last is the final call, and the middle three are camera angle, physical contact or evidence, and threshold. Put the timed-out incident through that mould and the result becomes plain: Law 40.1.1, evidence being the helmet strap, a clear threshold, an adverse decision. There is no box for anger. Put anger in the log and it stops being a log. It becomes commentary. The real failure is not in the law but in the process. Nobody publicly records who holds the clock. If the two-minute calculation rests on personal perception, that is not officiating; that is a management gap. In football's VAR room the timing is documented and pushed to the screen, and arguments later run off the minute of the review. In cricket, where is the written record of the two minutes? There isn't one. The same gap runs through DRS. ICC playing conditions require a player to indicate a review within 15 seconds of the ball becoming dead. Those 15 seconds are the pressure point for all of Asian cricket. The wicketkeeper sees best from behind the stumps, slip offers a second angle, the captain makes the call. Three separate eyes, three separate risk appetites, and to date I have not seen a single written, published review protocol from an Asian side that pre-assigns who holds veto. My live tracker from Russia 2026 first exposed that difference. Across 64 matches I logged 29 penalties, 22 converted, 20 VAR overturns, each entry tagged with a minute mark and a camera angle. What the tracker taught me was simple. A live tracker taught me that chaos is just data waiting for a sequence. Cricket never builds that sequence because nobody keeps the data. Which delivery a side reviewed, how many seconds the third umpire spent, which camera angle decided the call - no board publishes any of it. So spectators judge by outcome rather than process. My own confidence score here is moderate, because avoiding a bias charge forces a two-frame rule on me: if you do not separate the third umpire's decision from the on-field umpire's decision, you cannot see the injustice. There is also a vocabulary trap. In DRS debates we borrow football's language - clear and obvious. Cricket does not use that threshold. Cricket's threshold is conclusive evidence. When a similar contact reads out in India and not out in Australia, that is not a faulty eye; it is two different databases, two different camera sets, two different frame rates. Argue outcomes without stating the quality of evidence and the argument never ends. Technology has not freed Asian cricket from indecision. It has relocated the controversy. The question used to be about the umpire's eye. Now it is about the host broadcaster's camera angle and calibration. Spectator feeling has not changed. Only the accused has. In the Mathews affair the real failure was neither Bangladesh's appeal nor the helmet. The gap was in the pre-match protocol: which timekeeper holds the clock, who writes it down, and where that record is published. Nobody at an Indian venue did this. Perhaps nobody thought it necessary. To a spectator a timed out feels cruel. To the law it is an arithmetic of time. In Asian cricket that gap between two pairs of eyes is durable, because our classroom teaches drama more often than it teaches the law. Remote VAR, same threshold. The protocol I built during the pandemic in Germany's empty stadiums - isolating referee audio inside 48 hours, mapping silent-stadium echoes, verifying offside with two independent angles - works for timed out and DRS alike. One difference remains: in football it is mandatory; in cricket it is optional. Looking ahead I want to see three things. First, a public review log for every match - which ball, which second, which decision, which reason. Second, a designated review officer in each side who tracks the quota, because loading the keeper's instinct and the captain's authority onto one pair of shoulders is a management error. Third, a central technology pool for bilateral series as well as ICC events, so that a host board's budget, camera angles and the quality of decisions are not tied together on one string. If a side runs out of reviews in the 49th over of the next major tournament, will we ask why it happened - or will we ask who decided it?