Vietnamese Football and the Empty-Report Trap: When the Analysis Sheet Is Full of Frames and Empty of Facts

Da Nang, seven in the morning. I open the post-match report file again — the very frame I had built for it three weeks earlier. The heading is still there. Nine analytical sections are still there. More than forty indicator rows are still there.

But every content cell is empty. The row "Broadcasting revenue" has a trend column and no number. The section "Dressing-room health" has a field for "Manager–player relations" and no name. The section "On-pitch movement analysis" has explanatory notes on xG and PPDA and not a single recorded passage of play.

What I am holding is not a wrong report. It is a report that is formally correct and substantively hollow. And had I not asked myself "why is this happening", I could have signed it and sent it out — producing the most dangerous thing in analysis: a certainty with nothing behind it.

Why an empty sheet is scarier than a wrong one

Vietnamese football is at a stage where virtually every V.League club talks about data. Analysis departments are being set up. Motion-tracking software is being bought. Academies such as PVF, HAGL, Viettel and LPBank HAGL all keep indicator records for every youth cohort. In the coaching staff meeting room, heat maps, passing maps and indicator ranking tables appear more and more often.

But data infrastructure always has two layers, and people in the game usually only see one.

The first layer is collection and deconstruction: feeding raw material — a match, a video reel, a first-half observation log — in, and turning it into discrete information points with names, timestamps and numbers. The second layer is interpretation: taking those information points and building them into tactical, financial, form and risk analysis.

The problem is this: the second layer does not know that the first layer has died. It still runs. It still generates every heading, every sub-section, every blank to be filled. If nobody places a checkpoint in between, that frame still gets printed, still gets presented in the technical meeting, still gets shown to the board — except that every content cell carries the same three letters: insufficient information.

In the trade, I call that an empty report. It does not lie. It merely stays silent in a way that looks a great deal like the truth.

The mechanism: four roads to zero

Based on my experience tracking and running my own recording process across many seasons, data arrives at zero along four roads, and all four are common in Vietnamese football.

The first road: the raw material never reaches the deconstruction unit. A video file fails to encode, a stream drops at half-time, a log gets saved in the wrong folder. This is the easiest failure to diagnose, because you only need to check the length of the input — if the raw text or raw data has zero length, everything downstream is meaningless.

The second road: the deconstruction process still runs, but every extraction branch fails silently. No error message, no warning, only default values written into each cell. This type is the most dangerous, because the output looks entirely normal in structure.

The third road: the source is not text or numeric. A tactics clip online, an audio-only post-match interview, a photograph of a tactics board snapped in the dressing room. All are legitimate material to a human being, and invisible to a system that can only read words and numbers.

The fourth road: schema mismatch between the two layers. The lower layer names a data field "minute of goal", the upper layer looks for a field named "time of goal". Two different names, and the result is an empty cell — even though the real data is still sitting somewhere in the system.

The core point sits here: an empty report is not a poor report. It is a report that never existed yet was still issued a number, still published, and still generated decisions.

On the pitch, this phenomenon has an almost perfect twin. A motion-tracking camera system that fails in the first half can still output a complete heat map for the entire match, with one difference: every coordinate behind the failure defaults to the centre of the pitch. The coach looks at it and sees his team controlling the middle superbly. In reality the camera died in the tenth minute.

That is why I apply three mandatory checkpoints before allowing any conclusion to travel further.

The first checkpoint is raw-material length. If the input is empty, the entire chain downstream must stop, with no negotiation.

The second checkpoint is the count of information points and named entities. A valid deconstruction must return at least one concrete information point, and that point must be attached to at least one identifiable name — a player, a coach, a club, a competition, a number with a unit.

The third checkpoint is schema conformance between the two layers. Every field the interpretation layer requires must exist in the deconstruction layer, under a matching name.

If any checkpoint returns zero, my rule is simple: keep the frame intact, mark every position as insufficient information, and never infer to fill. No guessing a name, no inventing a club, no padding a number to make the page look better.

It sounds simple. In practice, the pressure to fill a blank is far greater than the pressure to leave it blank.

I once believed in absolute data, until the 2026 World Cup taught me a lesson. Back then I declared that Spain could not be eliminated because they controlled 68 percent of possession, and then Russia eliminated them on penalties. The problem was not that the possession data was wrong. The problem was that I used a correct indicator to answer a wrong question, and I had no checkpoint forcing me to stop and look for a counter-argument.

That night I watched the tape five more times. What I found was not a new number, but a deliberately organised defensive block that willingly conceded the ball to seal off the middle. A completely different indicator model. The two-thousand-word correction with nine diagrams that I published publicly afterwards was not to atone, but to install one more checkpoint into my own process.

The wrong article of 2026 taught me that correcting fast beats justifying. But it also taught me something later: most analysis errors do not come from misreading the numbers, but from nobody checking whether the numbers actually exist.

In hindsight, the data from the 2026 Asian qualifiers was the starting point of everything in how I work. In the Vietnam – Cambodia match in the 2026 Asian Cup qualifiers, I sat and logged every build-up phase using a five-colour spatial coding system, noticed the opposing back line drifting toward the right flank between the 60th and 70th minutes because of fading stamina, and correctly predicted Nguyen Van Toan's decisive goal in the 64th minute. The piece ran three thousand words with four hand-drawn diagrams.

But what I rarely tell people is this: that evening, I nearly had no video. The source I was using failed for roughly the first fifteen minutes of the first half. Had I not checked the length of the recording and caught the missing segment, I could still have written three thousand persuasive words — except that the entire opening phase would have been described from my hazy memory rather than from data. And because it sounded plausible, nobody would have caught it. Including me.

The only difference between a serious analyst and a gifted fabulist is one line in a verification log.

The execution blind spot: the industry invests in what is visible

Looking at how Vietnamese clubs spend on data, I see a repeating pattern. Money flows into the visible parts. Big screens in the meeting room. Software that renders three-dimensional charts. Presentations to the board. Scouting reports with player portraits and a composite score that looks very professional.

Almost nothing flows into the invisible part: input-data checkpoints, error logs, refusal-to-publish procedures. Simply because a checkpoint produces no attractive slide.

A good diagram is a painting; a great diagram is a living system. A living system knows to stop when it loses its source. A painting knows nothing — it just hangs there, beautiful, waiting for someone to believe in it.

This is where the transfer window makes everything worse. In a transfer cycle, speed is rewarded. Whoever breaks a story first gets read first. A deconstruction that returns empty in mid-July is treated as a delay, not as a signal to stop. And so people fill the blanks with speculation — with rumours, with the agent's word, with gut feeling.

When a deconstruction returns zero, the reflex of the majority is to go find alternative data. The correct reflex is to stop the chain, repair the source, and run it again from the beginning. What modern football needs is not more data, but the knowledge of which data to throw away.

An empty report still produces real decisions

This is the least-discussed part. An empty report does not end where it is empty. It travels on into the meeting room, and there it is no longer empty — it gets filled with memory, with feeling, with the reader's prejudice. A coach looks at an empty indicator sheet and fills it in with impressions from the latest training session. A technical director looks at a scouting assessment missing data and fills it in with what the agent said on the phone.

An empty report is an empty mould, and human beings always tend to fill moulds. The problem is that what gets poured in carries no label. It looks exactly like an evidence-backed conclusion, because it sits precisely where the evidence was supposed to sit.

For me, the only countermeasure is to say out loud that the cell is empty. Not a soft sentence. Not "more data is needed before concluding". Write it plainly: this position has insufficient information, it cannot be assessed. Nine sections, forty rows, all carrying the same mark.

The empty stadiums of 2026 did not kill football, they exposed what had already rotted. An empty analysis sheet does the same. It does not create the gap. It simply shows the gap that was already sitting in the process, waiting for a fine day to surface.

So, a question to leave behind

If next season your club could keep only one of two things — a sophisticated prediction model that can speak about every opponent, or an input-data checkpoint that answers a single question: is this source real — which one would you keep on the desk?

I made my choice back in 2026. And that choice has never once forced me to write another correction.