The Empty Data Board in V.League and the Temptation to Fill the Gap

Minute 63, at Hang Day Stadium, the second monitor on my desk turned grey. The message appeared neatly: no data. The statistics feed from the Vietnamese provider had just dropped the connection. Twenty-two minutes later, the numbers returned — complete, rounded, without a single empty cell. Pass counts, sprint counts, distance covered, all of it as polished as a report prepared in advance. And during those twenty-two minutes, no one in the room checked what had been used to fill the missing section.

I read the match report before I read the news, because a match report does not lie. But an electronic match report does. It lies very politely: it fills the gap, then stays silent.

VAR arrived in V.League 1 from the 2026 season, and that was a genuine infrastructure step, not a slogan. Before that, every argument about offside, about a handball inside the box, about added time, was settled by the human eye and by the personal credibility of the person holding the whistle. After that, they were settled by the human eye, by personal credibility, plus a camera system and a closed room. The 2026-2026 V.League 1 season comprised 14 clubs and 26 rounds — a far shorter calendar than Ligue 1 in France, which runs 18 clubs and 34 rounds. But match density is not the most important variable here. The most important variable is the number of camera angles per incident, and the number of people patient enough to sit through all of them.

The difference between Hanoi and Marseille is not in the laws. Law 11 on offside, Law 12 on fouls and misconduct, Law 5 on the referee's authority, Law 10 on determining the outcome of a match — they are identical down to the word, because they come from the same book. The difference lies in this: when the book says "the referee decides on the basis of what is observed", then in a football culture with twelve camera angles, and in a football culture with four, the phrase "what is observed" carries two entirely different weights.

That is the visible part. The invisible part lies in the data stream behind it.

A data provider never hands over an empty cell. It hands over a number, along with a precision level that is never stated. During the twenty-two minutes the feed was down at Hang Day, three different mechanisms could have been operating to fill that gap, and all three are technically legitimate.

The first mechanism is automatic interpolation. The system registers the two endpoints before and after the outage, then draws a straight line between them. Mathematically, this is entirely standard practice, used everywhere from temperature sensors to stock data. But football is not a straight line. A player who slows down in the 65th minute because of a muscle strain, or who bursts in the 68th minute because his team is trailing, cannot be predicted by any interpolation algorithm. The number that appears will look good, and it will be wrong.

The second mechanism is an editor filling in by eye. A person sits and logs incidents by hand, based on what they see. This is the old method, honest in attitude, but wrong in arithmetic: human visual error in high-speed phases typically lands between 8 and 15 percent, depending on viewing position. The problem is not that the figure is large. The problem is that the figure is never annotated. On the board, it sits next to sensor data and looks equally credible.

The third mechanism is data generation by model. When the system detects a long gap, it uses the player's historical data to reconstruct the missing section. A player averaging 10.4 km per match will be assigned a distance in that range, regardless of whether he actually played out the second half.

What all three mechanisms share is this: they all produce a data board that looks more complete than reality, and none of them leaves any trace of what it did.

This is where I want to pause longer than the VAR stories, because VAR stories usually end at whether the referee was right or wrong. That question matters, but it is the question of a single incident. The question of a system is: when the data drops, who is allowed to know, and how long afterwards.

In V.League, when a VAR decision sparks controversy, the argument usually revolves around whether the referee looked at enough angles. It rarely revolves around whether the system logged who looked at which angle, for how long, and in what order. This is not a shortcoming unique to Vietnamese football. In Ligue 1, review-room protocol has also drawn criticism for a lack of transparency, and in 2026 I said on air that the review procedure in a World Cup group-stage match did not fully comply with the international law board's own regulations. I was called rigid then. But afterwards, a station in Paris still hired me to train 15 commentators in the laws for the following season. Rigidity, in the end, is teachable. Leniency is not.

Back to the empty data board. There is a wide gap between a system that fails and a system designed never to admit it failed. In the first case, the problem is technical and can be fixed with money. In the second, the problem is motive, and money does not fix motive.

Who benefits when an empty cell is filled instead of left empty? The data provider benefits, because their contract is almost always written around the number of matches with complete data, not the number with honest data. The broadcaster benefits, because on-screen graphics need a figure to display at minute 70, not a line reading "unknown". The club benefits, because an internal report to the board looks better when every metric is rounded. And the fans, in some corner of it, benefit too: a specific number is easier to argue about than a gap, and arguing is part of watching football.

Here I want to spend a paragraph making clear something colleagues often tell me I say too late. Fan emotion is valid data. When a stand in Vietnam reacts furiously to a decision, that is not noise to be filtered out of the analysis. It is a signal, structured, measurable, and it often reflects something the data board omitted: that the match is not felt through the same numbers. Fans are not wrong to feel a decision is unjust. They are simply using a different data source — one nobody is paid to make look complete.

What I argue against is not that emotion. What I argue against is using that emotion as raw material to invent a number.

In 2026, when stadiums in the Marseille region stood empty because of the pandemic, I was tasked with building a procedure for matches without spectators. I led the creation of a 38-point checklist for referees, from how to respond to artificial crowd noise to how to time the ball being out of play. It was applied to 23 friendly matches, and the number of disputes over decisions fell 18 percent compared with the previous season. A 38-point checklist did not save the season, but it saved the referee's good name.

The lesson from that checklist is simple, and it applies directly to the data question: when error cannot be eliminated, declare it by rule. In my checklist, criterion 34 stated that any stoppage the referee could not explain to both captains had to be logged with a reason, including when the reason was "unclear". The word "unclear" was permitted. The phrase "nothing happened" was not.

Vietnamese football is standing at exactly this crossroads, and the crossroads has three branches. The first branch: accept that data will always be incomplete, and mark the gap. The second branch: keep filling, and accept that every analysis downstream — form, fitness, tactics — rests on an unverified foundation. The third branch: fill, but fill with an annotation, and publish that annotation to all parties.

Only the first and third branches are viable long term. The second looks cheapest, and in reality it is the most expensive; the invoice simply arrives a few seasons late.

Meanwhile, in esports, this problem takes a different and harder shape. A patch in a competitive title is an invisible referee with the power to decide a championship, but it signs no match report and holds no press conference. A mid-season balance change can turn a champion into a fourth-place team, and all that remains is a four-hundred-word technical note most viewers never read. When that happens, meta adaptation gets mistaken for genuine strength, and a team that wins because it read the patch faster gets praised as a team that won because it played better.

In Vietnamese esports, from major leagues such as VCS down to grassroots tournament systems, disputes over the validity of a match are usually handled by administrative decision rather than by publishing data. My principle here is consistent: a decision unaccompanied by verifiable data is not a decision, it is a notice. A notice may be correct, but it cannot be checked, and what cannot be checked cannot become precedent.

In France, Ligue 1 runs with 18 clubs and 34 rounds per season, with a data system built over more than two decades and an independent refereeing oversight body. In Vietnam, V.League 1 runs with 14 clubs and 26 rounds, with VAR only introduced from 2026. Looking at those two figures, the easiest conclusion is that Vietnamese football is still young. That conclusion is correct, but it is useless, because it does not say what to do tomorrow.

A more useful conclusion is this: a younger football culture has an advantage an older one does not. In France, hundreds of protocols have been written, baked into legacy systems, and changing them requires persuading dozens of parties with different interests. In Vietnam, most of those protocols are still at the stage where they can be written fresh. Writing new is cheaper than fixing old. This is the kind of advantage that exists only in a short window, and that window is open right now.

The offside line has never been straight, it is only today that I can see it bend. This holds for the line on the pitch and the line on the data chart. No line is absolutely straight, but it is precisely by placing two lines side by side that the curvature of each becomes visible.

So what is the concrete proposal, written in the exact format of a clause that could enter a tournament rulebook?

Clause one, on declaring gaps. Any party supplying match data for a match in a professional league system must publish, within two hours of the final whistle, a list of the time windows in which automated data dropped, with duration and the method used to handle it. This disclosure is published publicly; it need not be pretty, only correct.

Clause two, on data labels. Any metric produced by interpolation, manual logging, or reconstruction from historical data must carry a label displayed on every public chart. No label, no display. The cost of this clause is close to zero: it is one extra character in a database.

Clause three, on unverifiable data. If a gap exceeds five minutes and cannot be handled by any method, that cell must be left empty and display an unknown marker. In all professional reporting, leaving a cell empty is treated as correct procedure, not as a shortcoming to be criticised.

These three clauses require no new technology, no large budget, and no wholesale overhaul of the oversight apparatus. They require exactly one thing: agreement that a wrong number is worse than an empty cell.

VAR is not wrong. The people operating VAR are, after all, only people. And so are the people operating data. The only difference between the two groups is this: a referee's error gets replayed in slow motion on television, while the error inside a number gets replayed by no one.

A disallowed penalty can be fixed, a gap in the laws cannot. In V.League, in VCS, and in every league where I have sat reading match reports, what always gets fixed is the decision. What never gets fixed is the empty cell that no one admits to filling.

A match does not end with the whistle, it ends when people finish reading the report. For Vietnamese football, this season's report is still being written. The only remaining question is whether the writer will dare to leave a few lines blank, or will fill them with a number pretty enough that no one asks again.