Manchester derby: the technology drew the right offside line, the officials missed the judgement layer

Minute 60 at the Etihad, and what the technology could not see

Michael Oliver's whistle cut through the singing at the Etihad in the 60th minute. He pointed to the centre circle: no goal, Erling Haaland offside. Less than a minute later, the semi-automated offside line appeared on the big screen inside the stadium. Haaland's shoulder sat a fraction below the last Manchester United defender. The decision was overturned, the goal was awarded, and by the initial account it was the winning goal of the Manchester derby.

I wrote the exact time in my notebook, as usual, and waited. In this trade I learned one thing: "I do not hunt for the moment, I wait for the moment to stand up on its own." The moment of this derby stood up in midweek, when Pro Ref, the Premier League's refereeing review body, published its findings.

Matt Donohue, the video assistant referee, and Blake Antrobus, the assistant VAR, were stood down. The Pro Ref conclusion was short and heavy: they failed to spot that a player in an offside position had influenced the play. In that situation, the correct procedure should have been an on-field review, after the technology had already confirmed Haaland was onside.

Those two facts do not contradict each other. Haaland was level with the defensive line, and another player still committed an offside offence in the same passage of play. They are two separate layers of the same law, and the gap between them is where the error was made.

The context of a derby and a decade of reform

A Manchester derby is the kind of match in which a refereeing error is multiplied many times over. A full stadium, a global broadcast, and two supporter bases already divided into two halves of the world. In matches like this I always take notes more slowly. Based on my experience covering Premier League fixtures across many seasons, most arguments do not sit with the event itself but with the fact that the two sides are arguing about two different events.

The Premier League introduced semi-automated offside technology with a very specific objective: to shorten the time spent drawing lines and to reduce errors at the geometric layer. On that measure, the system does its job. The line is fast, consistent, and far harder to attack than the manual method that came before. Complaints about a line being a hair's breadth out have largely disappeared from the coverage.

Pro Ref exists to answer a different question. Howard Webb and his department are publicly accountable for refereeing standards, release audio of in-game conversations when required, and accept that a procedural error will carry a specific name. That is a deliberate choice: to turn refereeing into an auditable profession.

The price of that model is that every time the system stops, it stops in public. This time it stopped immediately before an international break, the point at which personnel decisions disrupt the fixture list least, and also the point at which they are hardest for supporters to follow.

The geometric layer and the interpretive layer

The offside law contains two concepts that most spectators merge into one. The first is being in an offside position, a geometric state: a player nearer to the opponents' goal line than both the ball and the second-last opponent, inside the opponents' half. The second is committing an offside offence, a behaviour: from that position, the player becomes involved in active play, interferes with an opponent, or gains an advantage from the situation.

Semi-automated technology only answers the first concept. It draws positions. It does not read behaviour.

Once the technology confirmed Haaland was not in an offside position, the VAR team closed the entire offside file on that passage of play, while the next piece of work, checking whether the other player had interfered, was never opened at all. That is an error at the interpretive layer, not at the data layer.

In the laws, interference is not a vague idea. It covers specific situations: blocking a goalkeeper's line of sight, making an obvious action that impacts an opponent's ability to play the ball, or challenging an opponent at close range. Precisely because this category is subjective, the protocol requires the on-field referee to review the monitor rather than letting the VAR team decide alone.

The paradox is that the more precise technology becomes, the more it creates a sense of closure. When a line appears at centimetre resolution, the natural instinct of an operator is to treat the passage of play as settled. In the days of manual lines, the VAR was forced to review the whole sequence in order: position, then behaviour, then conclusion. A beautiful line can inadvertently cut that procedure short.

There is one more layer that is rarely mentioned: the intervention threshold. A VAR may only overturn a decision when there is a clear and obvious error. For objective decisions such as position, the VAR can reach its own conclusion. For subjective decisions such as the degree to which a player affects an opponent, the protocol demands an on-field review. That is why Pro Ref described this as a case that should have gone to an on-field review, rather than saying the VAR reached the wrong conclusion.

In other words, the mistake was not a wrong judgement about a specific behaviour. The mistake was a check that was never performed. In audit work, that is the most serious category of all: evidence that was never collected.

One point of identification deserves to be stated plainly. The account I cross-checked names Enzo Fernández as the player alleged to have been in an offside position and to have influenced the play. That name does not match the list of participants in a Manchester derby, nor does it match the club that player represents. Until there is official confirmation, I am keeping the structural analysis and leaving the identification blank. A wrong name can ruin a correct piece of analysis, and the cost of a wrong name is always higher than the cost of a blank space.

What the crowd is arguing about, and what it is missing

After the match, most of the debate circled around whether technology is stripping the humanity out of football. That is a comfortable debate, because it forces nobody to answer a specific question.

The more specific question sits in the procedure. If, every time the technology overturns an offside decision, the VAR team were required to run an additional checklist on interference, the error in this derby would be difficult to make. This is a design problem, not a question of professional ethics. Standing down two officials answers the accountability question, but it does not fix the design.

Here I am reminded of something I learned in Moscow: "a match can end, but its echo does not." The echo of the 60th-minute passage is not the goal that stood. It is the question of whether a procedural error can be repaired by replacing people.

One aspect that gets little attention is the human cost. The number of officials capable of running VAR in the Premier League is not large. Every time a VAR team is stood down, the system has to be patched with less experienced personnel or the schedule has to be compressed for everyone else. Over the past three seasons I have recorded the same pattern: VAR errors tend to cluster in the busiest stretches of the calendar, when the referee pool is rotated most heavily. That is a hypothesis that needs assignment data to test, but it deserves attention rather than silence.

And there is an economic layer to the data that spectators rarely see. The same player-tracking stream used to draw the offside line is the kind of data distributed with very low latency to in-play betting markets. That does not turn the error at the Etihad into a betting story. It simply means every second of the VAR process has commercial value, and that time pressure is part of the design, not an incident.

Signals to watch

After the international break, three signals will show whether the system really changes this time: whether Pro Ref publishes the audio of the VAR conversation from the 60th-minute passage or stops at a written statement; whether Donohue and Antrobus return to duty in the next round of fixtures, and in what role; and whether the protocol adds an interference check every time the technology overturns an offside decision.

"Every season is a cycle of rhythm, and I have learned to count the rests." The rest this time is not in the line. It sits in the interval between the line appearing and the VAR team delivering its conclusion, an interval in which a correct question was never asked.