Manchester Derby, the Night VAR Robbed Football: When the Error Was in the Protocol, Not in the Eye

I still keep a bad habit: opening three data tabs before a Manchester derby kicks off. One for possession, one for shot maps, one for the history of controversial derby decisions across the last five seasons. That night, the third tab was the one I kept returning to. A goal disallowed, then allowed by VAR, then an admission of error from the very body that runs English refereeing. I sat still for a few seconds, not out of shock, but because an old question came back to me: if the technology saw everything, why did the humans still choose not to look?

This match gave me no material for tactical dissection. It gave me a case file about protocol.

The Manchester derby between Manchester United and Manchester City has never been just three points. It is a local earthquake, the kind of fixture where every mistake is magnified under a national lens. Referee Michael Oliver - regarded as one of the steadiest officials in England - took charge, with VAR sitting behind him to do the job of 'correcting errors.' VAR's entire reason for existing is to rescue decisions that are clearly wrong. That night, VAR did the opposite: it rescued a goal that should have been struck out.

What made me sit back was not the goal itself. It was the fallout. First, the goal was disallowed on the pitch. Then VAR intervened. Then the goal was awarded. Then United's players reacted, the coaching staff reacted, and even the legends watching from the studio like Roy Keane and Gary Neville could not hold their composure. That night, the body that governs refereeing in English football issued a statement conceding that the goal should not have been given, and that VAR should have sent the referee to the monitor. An apology, condensed into a few lines, was enough to open a far longer argument.

This is where I pause, because there are two different levels of error here, and people tend to blur them together.

The first level is judgment. IFAB's offside law, in the clause on 'interfering with an opponent,' is one of the most uncomfortable grey zones in modern football. A player standing in an offside position without touching the ball can still be deemed to have intervened, if his action clearly affects an opponent's ability to play the ball. In this situation, the offside-position player was said to have dragged a United defender out of position, opening space at the far post for the finish. He did not touch the ball, but he may have changed the defender's decision. This is the kind of call the refereeing body itself admits is 'subjective.' You cannot measure it with a ruler. You can only read intent.

The second level - and this is the part I want to talk about - is protocol. The refereeing body conceded that VAR did not recognise the possible impact, and should have advised an on-field review. This is no longer a question of judgment being right or wrong. It is a question of whether procedure was followed. When a subjective decision is in doubt, standard protocol obliges VAR to send the referee to the monitor to assess it himself. Failing to do so is not 'not seeing clearly.' It is 'refusing to look.' And a protocol error is checkable, unlike a judgment error.

VAR's fatal mistake was not in the eye that watches the ball, but in the fact that it forgot it had to invite the referee to look himself.

I keep a black notebook, a habit from my early years in the job. In it I jot down small fragments I am not sure I will ever use. One line I wrote long ago: the most controversial VAR cases have never been the technically hardest ones. They are the cases where someone decided he knew better than the man holding the whistle. VAR was born to fix 'clear and obvious errors.' But when VAR itself turns into a judge instead of a gatekeeper, it oversteps its own limits. People do not need a second referee. They need a gatekeeper who knows when to call the homeowner out to look again.

And here, I have to be honest about something more uncomfortable.

There are talents buried under contemptuous glances, but there are also truths buried under eager glances. After the match, I reread the reports on this incident and noticed something few people did: many of the details did not match each other. Player names appeared at clubs they do not belong to. The name of the refereeing body was misstated. Figures were cited without sources. When I work with data, I learn one principle: if you cannot trace a detail to its origin, do not build a whole story on it. The core of the disputed goal is solid - the refereeing body itself conceded it. But the decoration around it was loose enough to become a story in itself.

That leads me to the counter-argument I want to aim at my own profession.

In the silence of an evening with no match, data has whispered things no one expected. But this time, the thing doing the whispering was the report itself. When a refereeing mistake happens in a Manchester derby, the default media response is to turn up the heat. Sensational headlines, the framing of 'VAR strangling football again,' accounts piling onto the individual referee. But my job is not to turn up the heat. My job is to separate what actually happened from what gets retold to please the crowd.

This time, the two overlapped at one surprising point: the refereeing body admitted the error itself. A public admission issued the same night is the sign of a mistake that internal review judged indefensible. But I still want to be careful. The phrase 'in our view, there was a refereeing error' is a way of speaking that keeps a margin of retreat. It is not the bare 'there was an error.' When language is filed down like that, it is an expectation-management move, not a full confession.

So where does the real problem lie?

It lies in the fact that VAR, as a system, has been pushed into a no-win position. Fans want it to fix every mistake. Leagues want it to shorten arguments. But no one wants it to touch the subjective part of the game - the part football's own laws admit cannot be measured absolutely. A system designed to handle clear facts has been forced to handle grey zones. And when it handles them wrong, everything - from the referee to the body to the fans - gets dragged through the mud together.

Tactics will fade, but the story of trust never will. And trust in VAR is the only asset this system has, something it cannot buy back with any apology.

I wonder what comes next. Will the refereeing body issue clearer guidance on the 'interference' grey zone? Will the VAR operator be reviewed for future appointments? Or will it all quiet down in a week, until the next scandal reactivates the same old argument?

My judgment, and I am ready to be proven wrong: this will become one of the classic examples used this season to push VAR reform. Not because the mistake was enormous - but because the protocol failure was conceded by the governing body itself, making it the perfect ammunition for those who want change. A judgment error is still up for debate. A conceded protocol error leaves only the fixing.

And as someone who has spent years reading data to the point of forgetting he was watching football, I want to add one more thing.

People call me the one who swims against the current, but I call myself the one who finds. This time I found something not on the pitch, but inside the story about the pitch. I found the truth lodged between the veneer of a report. And I found, once again, what I learned back in 2026: the difference between a knowing person and a prejudiced person is that the knowing one is still willing to look a second time.

Football does not belong to the winning side. And perhaps it does not belong to the technology designed to judge it either. It belongs to people - referees, players, and fans alike - who know that trust is the only thing that cannot be edited by a screen.

The derby is over. The scoreline is set. But the question remains: if VAR does not dare to call the referee over to look, then what was it born to do?