The Ledger of Umpiring Decisions: What 118 Calls Taught Me About Cricket's Invisible Mechanics

Let me write the number down first: 118. On 7 May 2026, at Allianz Stadium in Sydney, the A-League Grand Final, Sydney FC versus Melbourne Victory, 120 minutes, 4-2 on penalties. That day I sat in the stands and coded every decision referee Jarred Gillett made — position, distance from play, signal clarity. A knee reconstruction at 19 had ended my NPL youth career at Blacktown City; I was studying media at UNSW and volunteering as a decision-logger for the Football NSW referee development panel. Somewhere in those 118 codes, a realisation settled: I did not actually want to know whether the decision was right. I wanted to know how it was produced.

From then on every piece I wrote opened with where the referee was standing, not what the law said. The 3,000-word blog post "The Anatomy of 120 Minutes" was read 4,000 times. Nobody paid me. But that piece fixed my method.

In cricket this method matters more. Cricket's decision architecture has more layers than football's. Football has one referee, two assistants, a VAR room. Cricket has on-field umpires, leg umpires, third umpire, match referee, ball-tracking, UltraEdge, Snicko, real-time stump microphones — each layer manufactures a decision independently, and each has its own failure mode.

By my count, the true duration of a DRS review depends more on the umpire's own signal delay than on the precision of the ball-tracking projection. When the third umpire gives a soft signal on a wicketkeeper's catch, the real question is not "did the ball hit the bat?" The real question is "how many seconds did the umpire delay raising the arm, and did that delay alter the review window?"

At the Russia World Cup I watched all 64 matches from a share house in Dulwich Hill, logging 29 penalties, every VAR intervention and each review's duration into a 41-column spreadsheet. 400 hours of work, one university unit forfeited. The 6,000-word breakdown "VAR Is Not the Problem" was republished by an Australian football site and earned my first paid byline — A$150.

But what stuck with me most was the two seconds between the referee's hand reaching the earpiece and the arm going up. In cricket those two seconds stretch longer, louder, more political.

On 30 August 2026, at an empty Bankwest Stadium, the A-League Grand Final, Sydney FC 1-0 Melbourne City. Headphones on, I transcribed referee Chris Beath's on-field voice: 412 verbal instructions in 90 minutes, from "no, no, no" to "green, green." That essay, "Ninety Minutes of Silence," became the desk's most-read football piece.

That experience does not transfer directly to cricket, but the framework does. Stump mics are not always live in cricket, yet when they are, I listen to what the umpire says and what he does not say. "Wait on, wait on" — what is that? It is not a ball-tracking wait; it is a coordination instruction. "Stay there, stay there" — a signal to the leg umpire. These words never reach the scorecard, yet they bend the match.

I do not trust a pattern until it survives three different angles.

First angle: positional. Where the umpire stood, what he saw, what light caught his eye. On an LBW call, the gap between the on-field umpire's view angle and the ball-tracking projection can often be measured in metres but not in decisions.

Second angle: audio-verbal. Whether the ball struck the bat's edge or the gloves, Snicko can say. But who said it first — the stump mic says that.

Third angle: temporal. Whether the pattern of decisions shifts around intervals. Drinks, tea, stumps, rain — these breaks are not just rest; they are re-settings of concentration. Session by session, my ledger shows the rate of "not out" calls in the first six overs of the second session runs marginally higher than in the last six overs of the first — the cause is not fatigue, it is recalibration.

No single angle is true alone. Sound without position deceives; position without sound is blind; and without both, temporal patterns are just coincidence.

Now the uncomfortable part. In cricket's decision debates we routinely translate emotion into the language of law. "That was clearly out" — from whose angle? "That was never out" — under which resolution? The path ball-tracking shows on the third umpire's monitor is a projection. The path the on-field umpire sees is reality. And the path the TV viewer sees is an edit.

I have watched cricket for 13 years, and I can say this: the decision we shout loudest against is usually the one where we skipped the positional question and went straight to the outcome question.

This is not a conspiracy. It is psychology. Outcomes arrive fast; positions arrive slowly. And slow answers do not hold an audience.

So what should be done? My suggestions are technical, not moral.

First, every review broadcast should include a graphic of the umpire's position — where he stood, at what height, at what angle to the ball. Then viewers would understand why the decision was hard, not merely that it was wrong.

Second, stump-mic audio should be part of the review process, not just broadcast garnish. What the umpire said, when he said it, how certain he sounded — this matters as much as the ball-tracker to assessing decision quality.

Third, intervals should be written into match reports. How many decisions per session, how many reviews, how many overthrows — these are not mere statistics; they are the match's hidden narrative.

Sixty-four matches taught me that one spreadsheet is never enough. One hundred and eighteen decisions taught me how much to trust my own knee.

And ninety minutes of silence taught me that sometimes a microphone tells more truth than a replay.

If a change comes to the DRS system next season, I want it to move toward transparency, not speed. Because cricket's real crisis is not the pace of decisions, it is the explanation of them.

— Root: Referee