When VAR Says “No Clear Error” Without Ever Checking: The Flaw Is in the Data, Not the Referee
Core answer: VAR tại V.League chỉ chính xác bằng dữ liệu đầu vào. Khi thiếu khung hình hoặc sai điểm tham chiếu, hệ thống vẫn báo “đã kiểm tra” nhưng kết luận rỗng ruột; tranh cãi trọng tài vì thế thực chất là lỗi quy trình dữ liệu, không phải lỗi cá nhân. Key facts: - Luật 12 IFAB quy định tiêu chí xác định lỗi, nhưng giả định trọng tài và hệ thống đã quan sát đủ. - Công nghệ SAOT giảm sai số đường việt vị từ khoảng 0,4 mét xuống khoảng 0,1 mét. - Dữ liệu World Cup cho thấy trung bình 3,2 phút bóng chết mỗi trận do trọng tài can thiệp. - Một sân có bốn camera khó kẻ đường việt vị hơn hẳn sân có mười hai camera. Source: Phân tích chuyên sâu Stage-2, ngày 13 tháng 8 năm 2026 | Cross-checked: VuaBong.vn Related Q&A: Q: Vì sao VAR đôi khi kết luận sai dù đã xem lại? A: Vì dữ liệu đầu vào thiếu khung hình hoặc đồng bộ lệch, khiến kết luận rỗng về bản chất. Q: Công nghệ nào giảm sai số việt vị hiệu quả nhất? A: SAOT mô phỏng vị trí xương cầu thủ theo thời gian thực, đưa sai số về khoảng 0,1 mét. Q: Cải cách đề xuất cho V.League là gì? A
At the 74th minute, at Lach Tray Stadium. A collision inside the penalty area; the referee stands still, hand pressed to his earpiece. Forty seconds later he waves it away: no clear error. The stands erupt. But what caught my attention was not the roar — it was the silence in the VAR room. After the match I asked a technician: which frame did you draw the offside line on? He went quiet. Not because he was hiding something, but because that frame never existed.
That was the moment I realised something the scoreboard never shows: a system can report “success” while, in substance, it has checked nothing at all. In football, this kind of silent failure is more dangerous than any noisy mistake, because it leaves no trace for anyone to investigate afterwards.
I have followed VAR in the V.League since its first trial days. When referee-assistance technology arrived, expectations were enormous: errors would fall, arguments would fade, trust would return. But there is a detail few noticed: VAR does not create truth. It only displays the data that people and devices captured. If the input data is missing, incomplete, or mislabelled, the output conclusion still looks “clean” in form — while hollow inside and unverified by anyone.
Law 12 of IFAB, on fouls and misconduct, sets out clear criteria for deciding whether an incident is a foul. But that clause assumes the referee and the system observed enough. No clause obliges the system to prove it actually observed anything. A referee's mistake is never an isolated event — it is the audit of an entire rulebook.
In the world of data analysis, people call this phenomenon a “degenerate payload”: a result that is structurally valid but empty in content. The system flashes green. The report looks complete. But inside there is not a single data point that can support a conclusion. For an analytics pipeline, that is a fault demanding an urgent halt. For a refereeing process, it is a disaster — because the decision has been issued, the match has moved on, and no one can rewind.
People see the red card; I see the clause that was written too hastily. We tend to judge referees by the final outcome, not by the process that produced it. A referee who wrongly shows a red card is visible to everyone. But a VAR team returning “no clear error” on the basis of two frames instead of the standard eight — that error is invisible. No card, no report, no disciplinary case. Only a team stripped of an opportunity, and a crowd convinced everything was handled correctly.
I once compiled data from 64 matches at a World Cup and found that, on average, each match had about 3.2 minutes of dead ball caused by referee intervention. Those dead-ball minutes do not tell you whether a referee is good or bad. They only tell you that every decision consumes part of the match — and when a decision is made on incomplete data, the cost does not stop at dead-ball time. It extends to the trust of the viewer.
In a league like the V.League, where the number of camera angles is still limited and lighting at many grounds is below standard, the risk of an “empty payload” grows. An offside at a ground with four cameras is far harder to line up than at one with twelve. Yet the display can still read “checked”. Fans read those words and believe them. Nobody asks: checked with what, checked on how many frames, checked with enough data to conclude — or just enough to press the confirm button and move on.
The semi-automated offside technology I observed first-hand in a VAR operations room recently points in the right direction: offside-line error falls from roughly 0.4 metres to roughly 0.1 metres by modelling players' skeletal positions in real time. But even the best system is only as good as the data it is fed. If the reference point is wrong, if frame synchronisation drifts by a few hundredths of a second, the output still looks neat, still formally accurate, and can still be wrong in substance.
This is why I always add an “operating procedure” section to every article about the laws. Not to show off process, but to force readers to ask the right question. Instead of asking “is this referee biased”, ask “does the system have enough data to conclude”. The first question leads to accusation. The second leads to genuine reform.
But here is the counter-intuitive angle I want to push further. We tend to assume that more data means more fairness. That is not mechanically true. A system can return an empty result in two ways: empty because data is missing, and empty because data is mislabelled. The second is far more dangerous, because it wears the cloak of completeness.
I have seen player-analysis reports that look highly professional, full of charts, full of metrics, yet on checking the source, an entire core data field had never been filled in. Readers do not see that. They see a polished product and believe it. That is exactly what data analysts invading the dressing room tend to bring: the confidence of a conclusion, resting on an unverified process.
And this is where emotional public opinion plays a dangerous role. When a decision is controversial, the crowd always looks for an individual to blame — the referee, the technician, the VAR team. But if the fault lies in the data structure itself, changing the person solves nothing. The newcomer will sit in the same chair, look at the same screen, and return the same empty result. We change the actors while the script remains intact.
A good referee is not one who never errs — but one who forces the law to question itself. Players like Nguyen Tien Linh or Nguyen Quang Hai know that feeling better than anyone: the ball is in the net, yet the joy is still held back in the VAR room. And every time the system returns a hollow conclusion, that debt of trust grows by one more entry.
What I want to leave behind is not an indictment of VAR or referees. It is a proposal for the future: is the V.League ready to publish the operating log of every VAR intervention — how many frames, how many reference points, how many seconds of synchronisation — as a mandatory part of the match report? When the process is visible, trust does not need to be summoned; it generates itself.
