The Screen as Second Referee: Cricket's Review-Power Ledger and the Invisible Accountability Gap

At twenty past six in the evening the floodlights had cut through the haze, and open on my laptop was the spreadsheet I have dragged along for seven years. Every review, every timestamp, every umpire's call, every failed challenge. The on-field umpire raised his finger and said not out. Five seconds later the ball-tracking settled onto the monitor, and the decision flipped. In those five seconds, power in cricket migrated from the field to the screen. I went back to the ledger, and the story changed. This is no longer a story about umpires. It is a story about frames, protocols, and a chain of custody in which responsibility passes through four hands and ends up in nobody's name. Let me begin with context, because anger must come after the law. In July 2026, at the SSC in Colombo, the player-review system was used for the first time in international cricket during the India-Sri Lanka series. It was still called the UDRS; ball-tracking was Hawk-Eye, UltraEdge was version one, and HotSpot cameras were limited. India was then the most rigid opponent, and their argument was never about accuracy alone but about ownership and procedural transparency. When the 2026 World Cup adopted the UDRS in part, India did not participate. Over the following eight years the BCCI moved step by step, first in England in 2026-17, then at home. Those eight years are a quiet ledger of cricket politics, in which acceptance of technology was determined by board interest, not by the laws of the game. Under the ICC playing conditions, each side now receives two reviews per innings; an umpire's call retains the review, anything else loses it. Umpire's call means ball-tracking shows the ball striking a specific portion of the stumps, up to half the wicket, which is not sufficient to overturn the on-field decision. UltraEdge version two now combines sound with visual, and in the third-umpire review room a dedicated review umpire and the match referee together construct the chain of decision. The problem is that the law is clear but the responsibility is not. The law says what happens; it does not say who keeps the record of the error. Now the core. Across recent ODIs and T20Is, one pattern is clean: roughly forty percent of all failed player reviews come not from umpire's call but from the players' own poor decisions, taken in moments where no review should have been burned. In other words, most of the shouting against technology is the fruit of human error. I went back to the ledger, and saw it plainly: the keeper-captain conversation, the bowler's request, and the review taken out of fear produce the highest failure rates. Technology carries no responsibility; it only displays evidence, and responsibility remains stranded in some empty step of the chain. That is the least discussed reality of modern cricket. I watched football's VAR debut from Russia, but cricket's DRS is the older and finer laboratory, because here the player himself makes the decision by spending his own review. In football the referee summons the technology; in cricket the player summons it. That difference alone shifts the balance of authority. My seven-year log holds another quiet truth. Average review time fluctuates between eighty-five and ninety seconds, reaching two minutes in complex caught-behind or stumping cases. That time has become part of the rhythm of the game, like a drinks break, except that a drinks break is scheduled and a review is not. Before the bowler releases, his body is already waiting, and the wait fractures the bowling rhythm. In conventional language I would say the game has slowed. But the ledger says something subtler: in second innings and especially in day-night matches, the run rate rises marginally in the over after a review, because the bowler shortens his length and becomes more cautious. Technology changes decisions, but rhythm changes in the bowler's head. Bangladesh enters here. In our administrative pipeline, review strategy still rests largely on umpiring experience, and the habit of keeping the chain of paperwork is thin. The reason for every failed review, the timing of the third umpire's decision, the review umpire's name: this data is stored, but it is not systematically analysed. If I speak of Bangladesh cricket specifically, our review success rate has hovered slightly below the competitive average over the past five years, and the main cause is not technology but the economics of communication. A captain has five to seven seconds to read the camera, and the second-economy of sending the right signal is something we have learned largely by erring. Then comes the human part that gets lost in the protocol. The third umpire sits in the review room and rarely takes the field's error onto his own shoulders, because the match cameras do not show his face. The on-field umpire becomes the only visible scapegoat; over-rates, ground noise and social media attack land on him. And yet his share of the decision chain is the smallest. When a match referee imposes a sanction under the ICC Code of Conduct, he does not watch ball-tracking; he reads the incident and the documented complaint. Studying that documentation year after year, I understood one thing. Discipline is a ledger, not a mood; but the one who keeps the ledger does not decide, and the one who decides does not keep the ledger. Here is my contrarian observation. Fans usually curse umpire's call as the cowardice of technology. Five years ago I argued the same. But my spreadsheet now says otherwise: if half the umpire's call margin were removed, then by the ledger of the last three seasons, twenty-eight percent of the overturned decisions would actually become more uncertain, because the visual certainty required for a definite verdict does not exist in that portion of the ball's path. The problem is not umpire's call; the problem is that players have never been taught which frame justifies a challenge. I found this only after charting the review discipline of batters. The second point is more uncomfortable. In the market of big names and big contracts, accounting is often dodged, and cricket's review policy carries something similar. When a major side loses three reviews in a row, no separate system tracks that loss; the board's interest lies in declaring the technology fine, because criticism raises the question of ownership. The company selling the technology: the ICC publishes its accuracy, but the commercial pressure never enters the open file. A small example, because one line of data is worth more than abstract theory. In a 2026 franchise match, a batter wasted two consecutive reviews, both caught-behind, both showing a flat line on UltraEdge. The scorebook says the technology was correct. The ledger says the first was an act of faith, and the second was forgotten fear. The captain took the review because that batter had been dropped in the previous over; the emotion of revenge overrode the rule that day. Such decisions do not exist in the rulebook, yet they change results. When I launched Bangladesh's first social commentary platform, I learned that the audience receives umpiring controversy through emotion, not statistics. Years later I do the reverse: I enter through statistics, then move towards people. Following the chain of a third umpire's decision, I have stopped again and again at the same place, where the question is not right or wrong but who writes the name of the decision. Accountability is not merely answerability; accountability is the recognition, at a fixed timestamp, of whose decision it was. That recognition is still missing. Now the future. I am eighty percent confident that within five years the ICC will introduce a public review audit system, in which the reason, the duration and the outcome of every review are archived, because as the screen's power grows, the demand for accountability grows with it, and sponsors do not enjoy quiet criticism. But my estimate will be falsified only if the technologies become so accurate that their accuracy conceals strategic error. Correct ball-tracking and correct decisions are not the same thing; one is the input of a frame, the other the output of a protocol. So long as one party decides and another displays the evidence, without the ledger we will know only the story, not the reason. If I am wrong, I need proof, and the proof must be timestamped, because I do not question a person; I question a protocol. That evening I did not close the ledger on my screen. I knew another review would come the next day, another frame, another five seconds. And in exactly those five seconds, cricket hides its weakest link. The question is not about an incomplete decision. The question is who, in the end, answers for it.