Nine Analysis Sections, Not a Single Number: When Vietnamese Football Deceives Itself with Empty Reports

In late October 2026, after the match between SHB Da Nang and Hanoi FC at Hoa Xuan Stadium, I opened a long nine-section analysis that had been shared in a professional group. The report had a complete table of contents: tactical and technical analysis, club finance and transfer market, results and public-opinion cycle, league landscape and team positioning, rules and governance compliance, management and dressing room, risk profile, media and expectations, and the football industry's transmission flows. Neat structure. Full tables. There were even note boxes and source reference lines.

I read page one. Conclusion: "Insufficient information to assess." Page two: "Insufficient information to assess." Pages three, four, five — through page nine, the same conclusion repeated verbatim. Every metric — expected goals, passes allowed per defensive action, possession share, squad value, wage bill, net debt — sat in the state of "no data available."

I sat still. Not surprised by the emptiness. Surprised that the empty report still looked perfect. It still had every heading, every frame, every layout. A hurried reader would never notice it contained nothing. That was the moment I understood: the problem was not missing data. The problem was that an analytical engine had run through all nine rounds without stopping, without raising an error, without admitting it had nothing to say.

To understand why this is more worrying than a mere technical glitch, we need to look back at how football analysis in Vietnam has changed over the past ten years.

In 2026, when I was 58, I sat in a coffee shop on Nguyen Van Linh Street in Da Nang, rewatching twelve Hanoi FC matches and logging every transition. Back then there was no automated software. Every time I rewatched a passage of play, I had to hit slow motion and count seconds with a stopwatch. I discovered that 37 percent of the team's goals came from counterattacks lasting no more than eight seconds, yet the back line pushed high without a covering player. I wrote a four-thousand-word piece, drew my own 5-3-2 out-of-possession and 3-4-3 in-possession diagrams, and sent it to a local football site. It spread because it identified the exact gap that coach Chu Dinh Nghiem himself later admitted.

Back then, to write one piece, I needed at least three independent sources. A clip from one camera angle was never enough — I needed the other angle too. A number from one statistics site was never enough — it had to be checked against the original footage. I called that the "triple verification" principle. It made me slow, but when a piece came out, readers knew every sentence could stand.

Ten years later, speed has changed everything. An analysis can now be produced in minutes. Software can extract data automatically, draw charts automatically, fill templates automatically. In principle, that is progress. But every advance has a reverse side: when an engine can run without data, it will run.

The October story is one example. An analytical engine was designed to fill nine standard sections. When the input was empty — when the source article could not be retrieved, when both title and source vanished — the engine still ran. It ran through each section, filled each cell, and in each cell wrote "insufficient information." Then it packaged everything into a tidy report, ready to be shared.

No alarm bell. No red flag. No line saying this report has no value. Only a report that looked perfect and contained nothing.

Three seconds from your own box to the opponent's box is enough to rewrite history. But three seconds for an engine to recognise it has no data — nobody thought of that.

I call this the "silent success failure." In football, there is a similar concept: a team wins through a lucky goal, yet every metric suggests they deserved to lose. That win hides the problem. By the time the problem surfaces, it is too late.

This analytical engine is the same. It "succeeded" — in the sense that it completed the task assigned to it, producing a report. But that success was fake. It did not raise an error, so the operator did not know. It did not stop, so the reader did not know. It did not say "I have no data," so nobody checked.

The most worrying thing is that such a report can still be cited. A journalist under deadline pressure can use it as a source. A fan arguing online can quote it as evidence. A young coach looking for material can read it as a model of professional analysis.

The strong attack with the ball; the intelligent attack with space. Here, the maker of the empty report attacks with form. And form, when beautiful enough, will beat content.

To see the problem clearly, look at the report's own structure. It has nine sections. Section one analyses tactics — conclusion: not assessable. But the question arises: if there is no data, why must section one exist at all? If there is no club name, no lineup, no playing style, why still call it "tactical analysis"?

The answer is simple, and sad: because the template was designed that way. A nine-section template, whether or not data exists, must be filled. The template's designer believed a full frame would make the report look professional. They did not consider that a full frame with empty content is more dangerous than a short report that says plainly, "I have no data."

In Vietnamese football, we are used to reports that look complete. Match sheets have every section: possession, shots, shots on target, corners, yellow cards, red cards. But if you have ever watched a V-League match and then checked the sheet, you know many numbers in it say nothing. A team with 65 percent possession but only two shots on target. A team with seventeen shots but only one goal. Those numbers exist not to explain the match, but to fill the sheet.

The October engine did exactly that, only at a higher level. It filled nine sections, not because there was something to say, but because the template demanded nine sections.

This is where my "triple verification" principle becomes more important than ever. Not because I enjoy checking. But because without checking, I would not know whether I was reading an empty report or a real one.

I remember the summer of 2026, when global football froze because of COVID-19. I was 61, four months without a match to commentate. Instead of waiting, I opened my laptop and downloaded two hundred V-League and First Division matches from the 2026 season. I counted every counterattack by hand, noting the first ball position, the number of passes, the time to completion. The result was a five-thousand-row spreadsheet with a metric I named myself: the "useful space index" — measuring the pitch area the attacking side occupies in the first three seconds after winning the ball.

When football returned in September, I used that index in my commentary. Once I stated precisely why SLNA lost at the 90th minute, and listeners thought I was guessing. I was not guessing. That was the product of a summer without football, but with data.

The lesson from that summer is clear: real data matters more than a pretty report. One correct number is worth more than a hundred filled cells. One verifiable conclusion is worth more than nine laid-out sections.

The ball is dead on the pitch, but the intent lives in every metre of movement. An empty report is the opposite — it dies on page one, yet its form makes people believe it is still alive.

At this point, everyone expects me to praise data and criticise technology. Not quite. My counterintuitive angle is this: the problem is not the analytical engine. The problem is the operator and the reader.

The engine only does what it is programmed to do. If you program it to fill nine sections, it fills nine sections. If you do not program it to stop when there is no data, it will not stop. Blaming the engine is like blaming a pump for pumping when the tank is dry — while the person who forgot to close the valve is the one at fault.

The reader bears some of it too. We have learned to trust form. A piece with bold headings, numbered sections, tables, and a "sources" line — we assume it is real. We do not read to find the number. We read to find the feeling of having understood.

That is the biggest blind spot in Vietnamese sports journalism today. We produce a great deal of content that looks professional, but we read very little content that genuinely has data.

The Japanese taught me patience. The Belgians taught me ruthlessness. The Japanese have a culture of continuous improvement, detail by detail. The Belgians have a culture of decisiveness — daring to make substitutions in the 65th and 74th minutes to turn a match, as Roberto Martinez did against Japan in the round of 16 at the 2026 World Cup. That match shaped my commentary style. I sat in the studio of a Da Nang radio station and said before kickoff that if Belgium fell behind, they would bring on Fellaini and Chadli to break Japan's high press. The match unfolded exactly like that. Japan led 2-0, Belgium won 3-2.

But the biggest lesson from that match was not the ability to predict. It was how Martinez reviewed footage to prepare for the scenario of going behind. He did not prepare a single plan. He prepared multiple scenarios, each grounded in specific data on the opponent.

That is what the October engine lacked. Not data — data can be added. But the ability to recognise that it lacked data. Martinez knew when Plan A had stopped working. That engine did not know when it had nothing to say.

I am old, but I can see the footstep before the touch. And I see this: an engine that does not know it is empty is more dangerous than an engine that knows it is empty but runs anyway.

So what should be done? The answer is not to abandon technology. It is to install a valve.

A simple valve: if there is not at least one specific piece of information — a team name, a number, a verifiable event — then stop. Do not produce the report. Do not fill the template. Do not publish. Raise an error, and say clearly: "Invalid input, re-run required."

This sounds technical, but it is a professional-ethics principle. An empty report that gets published is not a mere technical glitch. It is an accidental lie — more dangerous than a deliberate one, because it has no subject to hold to account, no one to confront.

In football we have a familiar concept: the counterattack. Wait for the opponent to lose their rhythm, then strike. But a counterattack only works when the back line knows what it is doing. A careless back line will not counter — it will concede.

To me, the October report is a reminder. Not about technology, but about discipline. About checking three times before writing one sentence. About stopping when there is nothing to say.

When the pitch is empty, I find the counterattack in my head. But when the data is empty, the professional writer must find silence. Honest silence is worth more than nine hollow sections.

The next V-League match kicks off this weekend. I will sit and watch, take notes, and ask myself: this time, which engine will produce the report — and will anyone check the input before believing it?