The Gahunje Ledger: 34 Review-Eligible Moments, 11 Never Checked — and the Question of Indian Cricket's Audit Culture

The 2026 IPL final in Hyderabad ended with Mumbai Indians beating Rising Pune Supergiant by one run. The ledger records that score as 128/6 chasing 129/8 — a one-run margin on which an entire season turned. But the real story is not on the stadium scoreboard; it is on an Excel sheet on my laptop. After that final I spent three weeks re-watching Gahunje's eight home games, over by over, ball by ball. The result: 34 review-eligible moments, of which 11 were never checked by either side. I verified that count twice against the match log before committing it to paper. Editors learned afterwards — ask for the ledger before the argument.

Indian cricket journalism carries an old habit: whatever is printed on the scorecard is the truth. The match referee's report arrives, and the case is closed. But the scorecard is a document, not the tape. And when you place that scorecard in front of over-by-over footage from eight matches, a gap appears between the two — sometimes narrow, sometimes wide, but always there.

The Maharashtra Cricket Association Stadium at Gahunje was Rising Pune Supergiant's home that season. The team reached the final, and I was there as a volunteer broadcast data logger — in the last semester of a master's in sports management. My job was to record ball-tracking frames, UltraEdge spikes and third-umpire decisions with timestamps. When the season ended I kept that log and used it for a different question: how many decisions were challengeable, and how many of them did a captain actually review?

The answer is 34 and 23. Which means 11 moments where DRS was available, where the tape carried a clear signal, and where nobody opened the file. This was not a failure of batting or bowling — it was a failure of review management, in a season where the team lost the final by one run.

First, understand the protocol in force at the time. DRS use in the IPL was limited before 2026, and in 2026 teams had one or two reviews per innings — the rule shifted repeatedly, so the exact number has to be matched against the match-specific referee report. What stayed constant was this: a review is an expense, and a captain spends it when he believes he will win. That belief is built inside the dressing room — the wicketkeeper's voice, the slip fielder's gesture, the bowler's confidence. From outside, the process is invisible. My ledger was the post-mortem of that invisible process.

Now the part that stings most: most of the 11 unchecked moments were cases where the fielding side had doubt, but the captain did not review. In three instances UltraEdge showed a faint spike — faint enough to drown in stadium noise, but recorded in my 60-frames-per-over log. In two, ball-tracking showed the pitching point clearly different from the umpire's estimate. Of the remaining six, four concerned LBW height, where the umpire's call was out and no review was taken.

There is a structural problem here, and it belongs to the system, not the teams. When the number of reviews is capped, a captain calculates — 'if I spend now and lose, what is left for the last over?' That logic is rational, but it is operating in a system where the technology exists and is going unused. Seen through a referee's eye, this is a failure of regulation design, not of the player. If you want correct decisions, stop making the review a currency.

I got a chance to understand this in 2026 when VAR arrived at the Russia World Cup — the first tournament to award 29 penalties, a record. Colleagues called it chaos. I saw a missing checklist. FIFA's four VAR trigger categories (goal/no-goal, penalty, direct red card, mistaken identity) were explicit, and the officiating protocol was written the way a circuit diagram is written. That same year I drafted a twelve-page internal memo, 'Review Protocol v0.1', mapping cricket's DRS against FIFA's four triggers, complete with a decision tree for the captain's challenge. My supervisor circulated it; two franchises requested copies before the season ended.

From that twelve-page document I learned one thing that remains the spine of every piece I write: a twelve-page protocol is not a suggestion; it is a checklist with consequences. Until somebody is penalised under it, it is paper. That is the gap in Indian cricket — rules are written, debated, and forgotten by the next season. In DRS, the gap shows at player level.

In 2026, when the IPL moved to the UAE and the stands emptied, a new layer was added. I ran a four-person remote review desk from Pune, syncing ball-tracking, UltraEdge and host feeds across 1.5 seconds of latency. There was no crowd noise, so an audio spike could no longer hide — and this is where my manual sync log earned its keep: 60 frames per over, timestamped by hand.

That work showed me another truth. Working across six time zones, I learned that a sync log is a second referee. When Gulf and India desks hand over to each other, the biggest risk is not technical but accountability — who is verifying, and at what timestamp. Live coverage forgets this constantly. Every missed check leaves a timestamp; every timestamp leaves a question.

Now the contrarian angle, which may not please everyone. You could argue the 11 reviews in 2026 were not taken because captains lacked information. That is half true. The real reason is that teams had no formal review-decision process at all. It was dressing-room oral tradition — if the keeper says take it, take it; otherwise let it go. No log, no audit, no post-match review of where we guessed wrong. Every aspect of player performance is measured in cricket — strike rate, economy, catch percentage — yet review-decision accuracy is never recorded.

It is the same habit visible in the BCCI's regulatory culture. There are fines for slow over rates, code of conduct hearings, auction purse and retention rules — but enforcement has been selective, and Indian cricket journalism has historically chosen access over enforcement. My argument is direct: a rule is only real when somebody is penalised under it. In the case of review decisions, the need is not punishment but transparency — every team should publish, at season's end, how many reviews it took, how many were right, and how many chances it let go.

Here I owe a clarification, because I am writing against the habit of treating the scorecard as truth and that habit lives in me too. My figure of 34 is also a document, and documents can be wrong. That is why I checked it twice against the match log, and why I also state what it is not: it is not the cause of any team's defeat. A one-run loss contained many things — a run-out, dot balls, the pressure of the final over. The 11 unchecked reviews are one layer of that, not the whole story. But it is the layer nobody measured, and what is not measured does not improve.

At this point in the match thread, let me make the sequence clear. The first entry was the hook: 34 and 11. The second was context: the protocol, its limits, and the 2026 DRS framework. The third was the core: what those 11 moments were and why they were missed. The fourth was the contrarian angle: the error belonged to the process, not the captain. And this final entry looks forward.

In the 2026 tournament cycle, when every decision is taken amid multiple cameras, ball-tracking and the immediacy of social media, the question is not whether the technology is accurate. The question is whether we are keeping account of how it is used. Until every team maintains a public review ledger — how many taken, how many right, how many let go — DRS will remain a tool, not a system. And without a system, the same 11 questions will return every season, unanswered.