The VAR blunder in the Manchester derby was a case of team dysfunction caused by "the one person who couldn't speak up"
Share this column
Inside the tunnel, someone failed to speak up
In football, judgments are always linked in a chain.
One decision creates the next phase of play, and that phase demands another judgment. This happens not only on the pitch, but in exactly the same way inside the video room where officials stare at the monitors.
The Manchester derby of September 2026. In this match at Old Trafford, Erling Haaland's goal in the 60th minute was reviewed by VAR and allowed to stand. Manchester City won 1-0, and the match ended there.
But afterward, the events took on a different meaning.
Every time the match is revisited, what actually happened in that moment comes into sharper focus, little by little.
Why something that should have been visible went unseen
In "Match Officials Mic'd Up," the first such release from the Premier League's refereeing body this season, the audio from inside the VAR room during that moment was made public.
The VAR's words were focused solely on confirming whether Haaland was offside. Semi-automated offside technology showed Haaland to be onside by 3 centimeters. Upon seeing this, the VAR moved rapidly toward confirming the goal.
"Go, go, go" — "That's a goal" — these are the kinds of words that appear in the audio record.
Meanwhile, where Enzo Fernández was positioned, why he was there, and how that affected the defensive line, were never evaluated at all.
Whether Fernández had touched the ball was checked. But whether he was in an offside position was never even brought up for consideration.
Howard Webb, the Premier League's head of refereeing, described this situation as "tunnel vision." He said that the focus on tracking Haaland caused the wider field of view to be lost. And at the same time, he acknowledged that the assistant VAR, whose job was to pull that focus back from outside, failed to do so in this instance.
The voice that should have pulled it back, but didn't
What Webb emphasized was not simply an individual failure, but a breakdown of the team as a whole.
VAR is not a system in which one person makes the decision alone. There is also the assistant VAR, whose role is to speak up from a different angle when the lead official's field of view narrows.
But in that moment, that voice was barely heard.
When one person is deeply absorbed in something, can another say, "Wait, let's look a little wider"? That is precisely the point on which functioning as a team hinges.
This is not a story confined to the world of refereeing.
When a group is making a decision, if one person starts running toward a particular answer, others can easily get swept along in that current. Speaking up within a group to say "maybe we should wait a little" is harder than it seems.
The "gap in standard" between Foden and Fernandes
In this match, aside from the controversy over the goal decision, another ruling also sparked debate.
Manchester City's Phil Foden was sent off in the 23rd minute for a kick to the upper body of Bruno Fernandes.
But just before that, Fernandes himself had also put his foot out toward Foden.
While supporting Foden's red card, Webb assessed Fernandes's action as "a spiteful reaction, not violent." His judgment was that classifying it as violent conduct would require excessive force or brutality, which this incident lacked.
As a result, two players who had each extended a foot in a similar way received different sanctions.
This difference in judgment shows once again that football's laws of the game are not black and white, but are interpreted according to degree and context.
Former England international Wayne Rooney said of the missed offside on Fernandes, "Anyone who has played football at any level should be able to see that that's offside."
Something didn't line up between intuition born of experience and a verification process carried out through a system.
What lies between "speed" and "accuracy"
This season, it is said that VAR teams were instructed to streamline the checking process and avoid spending excessive time on it.
This policy itself is meaningful in its own right, for preserving the tempo of the match, both for spectators and for players.
But the mindset of "finish it quickly" may have eaten into the time needed to think about what actually needs to be checked.
Efficiency and precision shouldn't be a trade-off, but under time pressure, once an answer appears, it becomes easy for an atmosphere of "no need to check further" to take hold.
When verifying something, the room to pause and ask "is this enough?" disappears quickly unless it is consciously protected.
This happens not only inside the video room, but on the bench during a match, and in the minds of coaches building out their training plans as well.
Preparing to restart is what decides the next match
Following this misjudgment, Webb said the officials would "reflect and take the lessons forward." It is also reported that the officials involved will not take charge of matches until after the international break.
Whether that interval functions less as a punishment and more as time to stop and think is the real question.
What happens after a failure matters just as much as the failure itself in determining what comes next.
Someone steps out of that tunnel
Players on the pitch, officials in front of the monitor, coaches on the bench — all of them can lose sight of something else while concentrating too hard on one thing.
What matters is not concentration itself, but knowing, even while concentrating, where your own attention is currently directed.
What happened at this derby will likely be filed away as a technical error. The decision won't change. The result won't change.
But if someone in that video room had spoken up and said, "Wait a second, where was Fernandes?" — this story would have taken an entirely different shape.
I suspect that whoever swallowed that one word is, at this very moment, thinking about it more deeply than anyone else.
What gets lost when we call it a breakdown
I understand the assessment that frames this misjudgment as a breakdown of the team as a whole. Still, the phrase "failed to speak up" may flatten out the sheer speed of that moment a bit too much.
The audio from the video room shows the words "go, go, go" following one after another, and the decision accelerated rapidly. How much room the AVAR actually had to interject from a different angle is hard to gauge from the outside.
Still, since Webb himself stated clearly that "the AVAR was responsible for pulling that focus back," it is a fact that this function was not fulfilled. The possibility that the policy of finishing quickly cut into the time needed for verification needs to be reexamined going forward in how the system is designed.
What's being questioned around that decision
I still sometimes recall, in the back of my mind, the 22-year-old version of myself who had to leave football without making it as a professional. Back then, I felt something similar in moments that demanded a decision. Once you're pulled toward the one answer right in front of you, the idea of checking one step further can slip entirely out of your mind. I think that happens not only on the pitch, but in any setting.
The difficulty of speaking up has nothing to do with how much knowledge or experience you have. It comes down to whether you're in a position to say "wait" when someone starts moving in a certain direction. In that moment, do you think you could have gotten that one word out?
- Geographic offside and the gray zones of football — how should we face decisions that keep shifting?
- Learning from the Premier League's "hard-to-read handball" calls: what Mbeumo's controversial incident teaches players and coaches about engaging with officiating decisions
- What Arsenal v West Ham United's VAR-overturned goal teaches us: how players and coaches can make the standards on 'goalkeeper protection' and set pieces their own