Manchester Derby: Did VAR Fail in Judgment or in Process?

The ball came in from the left flank. A runner darted across to the far post, a centre-back was dragged out of position, and the net bulged. The assistant referee raised his flag. The stands erupted in two opposite directions of emotion. Then VAR intervened, and the on-field decision was overturned: the goal stood.

That was the central moment of the Manchester derby. But the part that made me sit back and rewind the footage again and again was not the move itself. It was the statement issued the same night: the English referees' governing body admitted the goal should not have stood, and that VAR should have advised the referee to review the incident on the pitchside monitor.

A public apology, on the same evening, in a derby. Refereeing bodies rarely slam the door on their own defence that quickly. When they do, it means the error did not sit in a grey zone of debate, but at a point that can actually be checked.

And that is where I want to linger longer than a news bulletin normally allows.

One derby, one goal, one admission

The Manchester derby is the kind of fixture where the margin for error is zero. The first recorded derby took place in 1881, between Newton Heath and St. Mark's. Nearly a century and a half of intra-city rivalry has taught supporters one thing: in this match, a controversial decision outlives the scoreline. That is the nature of a derby, and it is why I always record derbies to rewatch, instead of watching live and writing on emotion.

The match was tight and low-scoring. The flashpoint came from a move built on the left: a cross into the box, an attacker in an offside position, a defending centre-back drawn into the situation, and a finish at the far post. The assistant initially flagged for offside. After a VAR check, the goal was allowed. The score finished 0-1.

The reaction was immediate. Players and coaching staff of the aggrieved side voiced their frustration. Former greats of that club, now working as pundits, spoke forcefully. And then, overnight, the English referees' body issued a statement: in their view, there had been a refereeing error; VAR had not recognised the possible impact of the player in an offside position, and should have advised an on-field review; the incident would be evaluated internally.

Reading that last line, I stopped. "Will be evaluated" is the language of a process, not of an apology.

That night I read several different reports of the same passage of play. They did not fully match. One described the crosser as the attacking side's left-back. Another attributed the player in the offside position to a midfielder from an entirely different club, which is logically impossible. One report named the referees' body with a title that does not correspond to English football's organisation.

I raise this not to catch journalists out. I raise it because it is the first piece of data in this analysis: when reports of the same event disagree on verifiable details, the only usable foundation is the official statement of the party responsible. Everything else must be marked unverified.

And that official statement says something very specific.

Law 11: a grey zone built by hand

The law at the centre of this case is IFAB's Law 11, the offside law. The hardest part of that law is not determining an offside position. The hard part is determining when a player in an offside position is deemed to have "interfered with an opponent".

The law sets out three situations that can constitute interference: obstructing an opponent's line of sight, challenging an opponent for the ball, or making an obvious action that clearly impacts an opponent's ability to play the ball. Those three situations sound clear on paper. On the pitch, they are a grey zone.

Picture the specific situation. A player runs across to the far post. He does not touch the ball. But he runs across the path of a centre-back, forcing that defender to choose: follow him, or hold position to attack the cross? The defender follows. The far post is empty. The ball goes in.

The question the VAR team had to answer: was the player's offside position the reason the defender lost his position? If so, the goal must be disallowed. If the defender lost his position for another reason, the goal stands.

This is the kind of decision no metric can measure. No expected goals, no pressing index, no passing map answers it. It depends on reading intent and impact within roughly two seconds. The English referees' body itself conceded this when it described assessing an offside situation as potentially "a subjective decision".

But hold on. If it is all subjective, why did they publicly admit fault?

A judgment error, or a process error?

This is the point I consider most important in the whole affair, and the one most overlooked by coverage.

The VAR protocol operates on a threshold called "clear and obvious error". When a situation is subjective, such as judging interference with an opponent, the protocol requires VAR not to settle the decision on the referee's behalf. Instead, VAR must advise the referee to go to the pitchside monitor to review it himself, because the final decision belongs to the on-field referee.

In this passage of play, VAR did not do that. The English referees' body stated plainly: VAR did not recognise the possible impact, and should have advised an on-field review.

Read that sentence closely and the problem is not that the on-field referee judged badly. The problem is that a process which should have been triggered was not triggered.

The difference between a judgment error and a process error is the difference between an excusable mistake and a checkable one. A referee on the pitch, at real speed, can misread a situation. People forgive that, because football is a sport of margins. But a VAR team sitting in a room, with monitors, with time, with the power to stop the match, failing to advise a review, is an error that cannot be blamed on speed or angle.

And that is why I say the apology came so fast. When an error sits in the grey zone of the law, refereeing bodies usually stay silent. When an error sits in process, they know silence will be read as a cover-up.

The far-post pattern: an unsolved problem

There is another layer to this passage of play that I think tactical analysts should discuss more.

The goal type featuring a far-post runner and a player in an offside position acting as a decoy is becoming a common attacking pattern. In the Netherlands, in Germany, and in leagues where teams build around crossing, the pattern appears more and more, not because coaches love it, but because the law struggles to catch it.

The mechanics are simple in concept. The attacking side places a player in the box in a position that may be offside. That player is not the main target. His job is to force a decision on the opposing defender: follow or not follow? Every second of hesitation is space at the far post.

The centre-back is placed in the hardest position in this kind of situation. If he leaves the runner, that player can receive the ball unmarked. If he tracks him, he abandons the zone he is meant to protect. And even when the centre-back does everything right, he can still be penalised for having been "interfered with".

From a systemic angle, this is an attacking pattern that exploits the ambiguity of the law itself. The attacking team does not need a player to touch the ball to have an impact. They only need to place a player in the right spot to force the opponent to think.

Players create moments, systems create players. And in this case, the system, meaning the law and the protocol that applies it, is running behind what happens on the pitch.

If I am wrong, where am I wrong?

I have to be blunt here, because that is the discipline I set for myself in 2026, after I wrote about Vietnam's U20 side on emotion and had to correct myself with a spreadsheet.

First, I could not access high-quality original footage of the passage of play at the time of writing. All my conclusions about player movement rest on second-hand descriptions from inconsistent sources. If the original footage shows the defender losing his position before the offside player moved, my entire "interference" argument collapses.

Second, I assumed the personnel details in the reports I read were accurate enough to frame the context. As noted, they do not match. I deliberately built no conclusion on specific player names, but there is still a risk I unwittingly inherited a false detail.

Third, and most importantly: I am describing an incident without access to the refereeing body's internal report. I am inferring only from their public language. If the internal report shows VAR did consider and decide against advising a review for some technical reason, then this is a judgment error, not a process error, and my central argument weakens considerably.

Every debate has a layer of data that has not been turned over. The unturned layer here is that internal report.

But I stand by the main conclusion, because it rests on the public wording: the English referees' body conceded that VAR should have advised an on-field review. That is a statement about process. And if I am wrong, I will be wrong in reading that sentence as an admission rather than a piece of diplomatic phrasing.

What I will be tracking

Over the coming weeks, three things are worth watching. First, referee and VAR assistant appointment lists for the following rounds. If this match's VAR team is pulled from major fixtures, that signals how seriously the governing body rates the incident internally. Second, whether any new guidance appears on the threshold for "interfering with an opponent". Third, and longer term, the momentum of debate around semi-automated offside technology.

Based on my experience following matches, incidents that the governing body itself acknowledges tend to produce procedural change within a season. But change only arrives when pressure is sustained, not from a single night.

When the stadium empties, the noise disappears and the data starts to speak. At this derby, the stadium was not empty. The noise was very loud. So the work is to separate the apology from the emotion, read it as a process data point, and then wait to see whether that body can actually fix the process.

Football does not need you to believe; it needs you to verify. And the only thing verifiable that night was how fast they admitted the error.