The Field's Ledger: Evidence, Margins and Whose Testimony Cricket Believes

I was there that night. On 17 June 2026, with the pandemic's empty stands as a backdrop, the English Premier League was restarting, and I was covering its first fixtures as a junior reporter for a London sports wire. Aston Villa versus Sheffield United. In the 42nd minute, Oliver Norwood's free-kick brushed the crossbar, dropped inside the goal line, and spun back out. The referee waved play on. The match ended 0-0. Hawk-Eye stayed silent.

By nightfall it was clear the ball had crossed the line. The technology's error was 1.2 centimetres. I got hold of the 92-page return-to-play protocol and wrote a 3,000-word audit, mapping every technology checkpoint and interviewing three independent officials. Hawk-Eye issued a public apology.

That 1.2 centimetres is not just a measurement to me. It is a confession — a statement of which errors a system tolerates and whose errors it forgives. The margin was one pixel; the argument was everything. And that same confession returns in cricket every week, on every series, on the DRS screen — only in the language of ball-tracking, UltraEdge and 'umpire's call'.

I was born in Bangladesh, I live in London, and for 13 years I have watched one thing closely: cricket fans often think they are arguing about results. In truth they are arguing about evidence — who submitted it, who verified it, and how durable it is. Just as the offside line in football is not really a line, the DRS line in cricket is not a line either; it is a confession.

To see this, recall the DRS rules. The Decision Review System was introduced to protect players — to correct clear errors. But cricket has its own safety valve: 'umpire's call'. If ball-tracking shows more than 50 per cent of the ball hitting the stumps, the on-field decision stands. In other words, the system itself admits there is uncertainty in its measurement — and then places the blame for that uncertainty on the on-field umpire's shoulders. The same logic governs edge detection: if the UltraEdge graph shows a spike, whether it is bat or pad or strap remains contested — and doubt means 'not out'.

This is where the most useful lesson of my reporting life lives. In 2026, while studying at City, University of London, a 78th-minute red card in an Isthmian League match between Billericay Town and Leatherhead was rescinded on appeal. I built a spreadsheet of 120 FA disciplinary cases, coded each by rule violated, and published a 12-minute video. The 'The Offside Line' channel gained 2,400 followers in three weeks.

That experience taught me a habit that returns in every report I write: cite the exact rule number in every paragraph. A claim, a clause, a timestamp — when those three sit together, writing stops being commentary and becomes evidence. To me, every DRS review is a block, and every match is a ledger.

Consider this: if every contentious cricket decision were recorded like a block — holding the timestamp, the applicable playing condition, the ball-tracking confidence level, the frame rate, and the final call. The greatest property of a block is that it cannot be quietly altered; change one and the whole chain tears. Cricket's ledger lacks exactly that property. We see ball-tracking and snicko graphs, but not the confidence thresholds, the camera calibrations, or what was said on the 'umpire's call' phone line. I trust the replay, but I audit the frame rate.

In 2026, covering the first VAR World Cup in Russia, I teamed up with a data-science student to log all 22 VAR reviews. In Kazan, in France versus Australia, referee Andrés Cunha awarded the first-ever World Cup VAR penalty — Josh Risdon's handball, converted by Antoine Griezmann in the 58th minute, France winning 2-1. I built a decision-tree framework and published a 5,000-word analysis that a London referee association later cited.

What I learned there applies directly to cricket: technology does not change decisions, it forces decisions to answer for themselves. Who answers is the real question. In my decision log, every row carried a timestamp, a rule citation and an outcome — and the same pattern surfaced every time: big teams, big stars, big broadcasters get more replays, more debate; a small team's equally contentious decision disappears quietly.

In cricket this inequality is subtler. Who has the courage to take a review? A newcomer who knows that burning a review will burden a senior teammate next over will hesitate. A senior star reviews freely, because he carries more credit and more patience for his team. So the DRS, meant to be a tool of equal opportunity, becomes a mirror of power.

The real scorecard of that power sits off the pitch, in paper. The ICC Code of Conduct, slow over-rate fines, match referees' reports — read these and you see who gets punished and who gets protected. The difference in the language used to sanction Bangladesh, Afghanistan or Ireland for the same offence, and to excuse the big boards, is cricket's true ledger.

Now it is the transfer window. And a transfer window is a courtroom with no bailiff — every transfer window is a courtroom with no bailiff. The line between rumour and information is drawn at the same question: where is the evidence? The release-clause structure, the wage bill, the agent's commission — that is the real story, not the headline name. I tell fans: before believing a story, ask who said it, what they stand to gain, and whether there is a written basis, as there is for a match referee's report. That filter is what fans need most, because they are drowning in rumour.

Now to the uncomfortable part. I want to steelman the fan's grievance, because I believe anger does not appear from nowhere. The fan's logic is simple: if ball-tracking is truly accurate, why does 'umpire's call' exist as a separate verdict? Either the technology knows, or it does not. If it knows, why does the on-field error stand? If it does not know, why blame the umpire? The most uncomfortable discovery in my decision log is this: technology speaks when it is certain, and falls silent when it is in doubt. That silence unsettles fans, because the match turns in that very gap.

I am not dismissing the fan's anger. I am saying the difference between admitting technology's limits and hiding technology's gaps is the most important distinction of all. The first is honesty; the second is a breach of trust. Cricket still confuses the two.

And here is the central discovery of this piece: cricket's real DRS problem is not the absence of a perfect machine, but that the frames, confidence and conversations behind a machine's decision are written nowhere. Hawk-Eye's error could be admitted because there was a written protocol and a measured error. The third umpire's room has no such written, durable, publishable ledger — only a few moments in front of a camera, and countless decisions behind it.

So the question is not how accurate the technology is. The question is who submits the evidence, who verifies it, and whether that verification is durable. A ledger is trustworthy only when each block is inseparably bound to the last — and cricket's decision system needs exactly that.

I have watched children play on the streets of Bangladesh and professionals on English county grounds. Both need the same thing: whoever makes the call, let the evidence sit behind it. There is no need to hate the DRS; there is a need to audit it. Technology is the eye, but accountability is its ear — without both, there is no justice.

If the ICC does one thing in the coming years — keep a public decision log for every contentious call, with frame-by-frame timestamps, so fans can cross-check too — cricket's controversies will not disappear, but their tone will change. And a change of tone is the real change, because a game that distributes evidence remains a game; the day it distributes only power, it stops being one.

So the next time ball-tracking appears on screen and you feel 'that is plainly out, yet umpire's call!' — you are asking the right question. You are just looking in the wrong place. The margin is not in the machine; the margin is in the ledger. And if the ledger is not public, the margin belongs to everyone, but the blame belongs to no one.