When VAR Outputs an Empty Verdict: The Silence of Process in Kazan

The third minute of stoppage time, Kazan, June 27, 2026. Kim Young-gwon puts the ball into Germany's net. The assistant referee raises his flag for offside, then lowers it after the VAR team confirms. The goal stands. Son Heung-min seals the 2-0 in the sixth minute of stoppage time, and the reigning World Cup champions leave the tournament in the group stage. But seconds earlier, inside Germany's penalty area, the ball had struck the hand of a defender in white. That is exactly the kind of situation VAR was created to catch. No signal. No monitor leaving its case. Not a single voice rising from the sealed room. What I remember is not the shock. What I remember is the silence.

Before VAR spoke, I had already seen the data whispering since the 2026 season. That year, while working as the dedicated discipline reporter for the K League Classic, I stayed behind after the season and counted all 47 red cards. The total said nothing. What said something was the split: home teams received 16 cards, away teams received 31, a gap of 38 percent. A gap like that cannot be explained by playing style. It forced me to look elsewhere: the referee's position, the timing of the card, the match report. I published the investigation "The Silent Bias" in Busan Ilbo. A referee threatened to sue. The league then quietly changed its monitoring process. Since then, every judgment I make about referees has to come with statistics attached.

Kazan was the second time I witnessed the same kind of silence, but on a larger stage. VAR was introduced at the 2026 World Cup with a promise: technology would not let clear errors pass. And yet in Kazan, a handball in the penalty area, precisely the kind of situation VAR exists to handle, slipped by as if nothing had happened. After the match I sat for six hours, reviewing fourteen camera angles. Not one showed the referee being called to the monitor. The VAR team issued no recommendation. The process did not collapse because someone looked wrong. It collapsed because no one looked at all.

A system never collapses starting from someone's error; it starts from the silence of those entrusted to hold the scales. In VAR operations there is a layer the audience almost never sees: the process layer. A VAR team runs a fixed sequence, observation, cross-checking, recommendation. When that sequence runs correctly, the audience sees only the result. When that sequence runs empty, the audience also sees only the result. The difference lies where no one is looking. In Kazan, that sequence ran empty: the steps still existed on paper, still printed in the guidance documents, but they were never filled in with any real signal. That is the most dangerous kind of failure. The system does not report an error. It simply outputs an empty verdict.

A proper match report has mandatory fields: time, position, line of sight, decision. When a field is left blank, the report remains formally valid. But it has lost the most important thing, the capacity for reconstruction. In Kazan, that blank field was the question of the hand. No one filled it in. And because no one filled it in, no one had to answer for it. This is the point I want the reader to grasp firmly: in modern football, the most serious error is usually not a wrong decision, but a decision that was never made.

The mistake is not in the referee's eye, but in where he chooses to look. I have spent many seasons verifying this. When analyzing a controversial situation, I do not ask whether the referee has eyes. I ask where he was placed, what he chose to look at, and which space he left uncovered. In Kazan, the referee stood in a reasonable position. The problem was not his position. The problem was the line of sight of the whole system, a line of sight programmed to focus on the final touch, while the crucial signal lay a few seconds earlier in the move.

I call it the "third eye." It differs from the referee's eye and the spectator's eye. The third eye does not judge; it asks about design. Who sets the order of the camera angles? Who decides when the VAR team is allowed to intervene? Who defines what counts as a "clear error"? These questions have no answers in the match report. They live in meeting rooms, in referee training sessions, in documents the audience never reads. But they are what determine whether a goal gets reviewed at all.

Based on my experience following matches, most VAR controversies do not come from outdated technology. They come from the gaps between process steps, where a signal that should have been passed on was instead stopped. An assistant VAR sees something, but the intervention criteria are too narrow for him to speak. The referee hesitates, but no one on the team is confident enough to ask him to step outside. Everyone does his own job correctly, and the result is that the whole system falls silent together. This is the paradox of process: it can be followed perfectly and still produce an empty verdict.

This explains why adding more cameras does not automatically solve the problem. After Kazan, major tournaments added cameras, added semi-automated offside technology, added more layers of checks. But an angle only has value when someone decides to look at it at the right moment. Technology widens the field of view; it does not widen judgment. If the process design still leaves blank fields, then the more data there is, the easier those fields are to overlook amid a sea of signals.

This is where I have to be most careful, because the greatest temptation is to assign blame. That night in Kazan, Korean fans cheered. I cheered too. That goal was deserved by a generation of players who had endured so much. But within the cheering, one question was drowned out: what about the hand in the penalty area? No one asked, because the answer might spoil the joy. The emotion of the crowd filled the blank field the process had left. And that frightens me more than a wrong decision, a crowd content with an empty verdict.

The applause fades, but the cry of the law remains intact on the empty pitch. I write this sentence not for effect. I write it because the matches played without spectators during the pandemic gave me a rare laboratory. When the roaring stops, people hear the law clearly. And what I heard was this: the law is not at all ambiguous about a hand in the penalty area. The ambiguity lies on the human side, in the decision whether to review. The law cries out loudly. It is only we who do not listen.

There is another temptation I must always remind myself to avoid: the voice of the prophet. I do not want to sit here and say I knew in advance. I did not know. I have only a small dataset from one domestic season, a few dozen red cards, and a belief that repetition can be measured. What I saw in Kazan was not a prophecy fulfilled, but a familiar pattern reappearing on a larger stage. That is why I write in the language of probability, not the language of verdict.

It should also be made clear what I do not do: I do not name referees. For many years, I have never written a piece to pin responsibility on an individual holding the whistle. Not out of deference, but because framing it that way is structurally wrong. If a refereeing team of many people, many cameras, many layers of checks still lets a clear situation slip, then the fault does not lie in a single pair of eyes. It lies in the design. Finding a scapegoat is the fastest way to avoid having to fix the system.

I have no power to punish, but I have a duty to see what the man with the whistle does not want to see. The problem with VAR has never been technology. The problem is that we have built a system capable of outputting an empty verdict for which no one is accountable. Years after Kazan, tournaments have added cameras, added process steps, added even artificial intelligence to the VAR room. But a camera does not fill a blank field by itself. People do. And as long as we accept letting emotion fill those blank fields, VAR will still occasionally output a verdict no one reads. If a system never reports an error, how do we know it is running correctly?