The Empty Dossier and the Data Paradox of Vietnamese Football

October 2026. A meeting room with no windows. On the table lay forty-three dossiers, each recording the movement of the opposing team's back four across every round of the season: the angle of their covering runs, the distance between adjacent positions, the moment the defensive line stepped up and dropped back. I opened the last dossier, round 26, and looked again at the number in the table. Sanna Khanh Hoa BVN finished V.League 1 with 21 points from 26 matches, bottom of the table, relegated. There were no tears in that room, only the sound of turning paper. When a team is relegated, I redraw the diagram of the pain.

What I found when I went back through those forty-three dossiers was not a bad player, and not a mistaken coach. It was a gap. Our defence exposed a gap on the left flank in 61% of the matches we lost. That number had been sitting quietly in the dossier since round 20. By the time I saw it and brought it to the coaching table, only six rounds remained. The decision came too late. The data was not missing. The moment of intervention was what was missing.

Context: a football nation that records by memory

Before the 2026 season, I had proposed to the coaching staff a geometric note-taking system to profile the movement of the opposing defence. The principle was simple: each match, I plotted the average coordinates of the opponent's four defenders at three moments — when they built up from their own half, when the ball crossed the halfway line, and when the ball entered the final third. From those three points I reconstructed a moving quadrilateral, measuring each defender's covering angle and the greatest distance between two adjacent positions. The goal was not to describe whether the opponent was beautiful or ugly, but to find where that quadrilateral was stretched beyond its threshold.

The coaching staff considered it a perfectionist idea. We postponed it. No one strongly objected, and no one defended it. It simply sat in a drawer, waiting for a better moment. And that better moment never came.

This story is not one club's story. It is the story of an entire football nation. V.League 1 has fourteen teams, roughly two hundred matches per season across all competitions. The number of matches recorded systematically — with coordinates, with thresholds, with moments of intervention — can probably be counted on the fingers of one hand. Most analysis in Vietnam still relies on the collective memory of the coaching staff, on the feeling after rewatching footage, on phrases like "the defence was loose that day" or "the midfield lost its shape." Those judgments are not wrong. They are simply unverifiable.

Based on my experience watching matches across many seasons, I have noticed something that repeats: when a team loses, the cause is usually assigned to individuals — a defender who made a mistake, a striker who finished poorly. But when I redraw the diagram, individual errors are mostly the consequence of a systemic gap that already existed. A player does not die because he is bad. He dies because the system left him alone in a dangerous place.

The biggest problem in Vietnamese football is not a lack of talent or a lack of tactics. It lies in the fact that we do not have a disciplined data pipeline. Every time we analyse, we start again from an empty dossier. And an empty dossier cannot feed a decision.

The sufficiency gate no one wants to walk through

In my analytical work, I set myself a principle I call the data sufficiency gate. Before concluding anything, I ask: how many information points do I have, and are they enough to hold this conclusion up? If not, I stop. I do not speculate. I do not fill the gaps with belief.

It sounds simple, but this is a gate Vietnamese football walks through every day without knowing it. A coach rewatches a match, sees his team concede two goals from two counterattacks, and concludes: "We pushed too high." That conclusion may be correct. But it rests on two data points. Two points. To assert a pattern, you need a whole sequence.

I distinguish two kinds of material in this profession. The first is the information point — an atomic factual statement, sourced, timestamped, countable. "In round 20, the defence exposed a left-flank gap during a counterattack in the 67th minute." That is an information point. The second is the feeling — a judgment without source, without timestamp, without verification. "Our team lacked concentration." That is a feeling.

Most tactical meetings in V.League live on the second kind. Not because the coaching staff is lazy, but because the first kind is never collected. No one sits down to plot the opponent's defender coordinates after each match. No one records the moment the defensive line steps up. No one stores the thresholds. When the season ends, all that remains is memory — and memory is always biased.

I remember another meeting, later, when the team was already in the danger zone. A member of the coaching staff said: "I have a feeling the opponent will attack down the flanks next match." The whole room nodded. No one asked: how many information points is that feeling based on? No one asked: in what percentage of recent matches has the opponent attacked down the flanks? The question was so simple that no one bothered to ask it. And because no one asked it, it was never answered.

The closed meeting room has no windows, so I write things down to see what I am saying. I began turning every feeling into a verifiable question. "The opponent attacks down the flanks a lot" became "in the last five matches, what percentage of the opponent's attacking moves went into the two wide corridors?" Simply turning a feeling into a question already carries you halfway. The other half is answering it — and that is the hardest part, because it demands data we never collected.

Entity resolution: when we cannot name the thing we are talking about

There is a concept in analysis that I learned late, called entity resolution. Put simply, it is the ability to correctly name the things being discussed. Which team? Which player? Which match? Which moment?

It sounds obvious, but listen again to an ordinary Vietnamese football conversation. "Our defence has not been playing well lately." Which defence — which four players, in which formation, in which match? "The midfield lacks creativity." Which midfield — who, in what role, with or without the ball? Most of these statements have no entity resolution. They float.

When entity resolution is low, every analysis becomes meaningless because no one can refute or confirm it. "The defence is not playing well" cannot be wrong, because it does not speak about anything specific. And a statement that cannot be wrong also cannot be right. It simply exists.

In my 2026 geometric dossier, everything had high entity resolution. I did not write "the defence is weak." I wrote: "In round 14, minute 63, the left-back, number 3, exposed a gap of 18 metres from the left centre-back during a counterattack, leading to the second goal conceded." A sentence like that can be contested. Someone else can open the footage, check minute 63, re-measure the distance, and say: "No, it was only 12 metres." That is data. That is what can feed a decision.

I realised that most of what is called "analysis" in V.League is actually narration — retelling a story in tactical language. Narration has its own value. It helps fans understand the match. But it does not help the coaching staff decide. To decide, you must raise entity resolution to the level where a statement can be proven wrong.

Once, after a defeat, a colleague told me: "We lost the midfield." I asked back: "Lost it in which zone, for how many minutes, under pressure from how many players?" He was silent for a moment, then said: "I just felt it." I did not mock that feeling. Feeling is a good starting point. But it must be translated into a question with high entity resolution. Otherwise it is just a cloud.

The sufficiency gate in practice: three cases

To see how the sufficiency gate operates, I want to recount three cases I lived through.

The first is the 2026 season. We had forty-three matches of data but no moment of intervention. This is the most dangerous kind of failure: data that is complete but arrives late. The sufficiency gate had opened, but that door opened when the season was almost over. The lesson: data only has value when it comes with a moment of intervention.

The second is the Russia 2026 World Cup. In early 2026, a Vietnamese football outlet discovered my geometric dossier through a former colleague and invited me to write analysis during the tournament. Russia beat Egypt 3-1, and I wrote about how Russia operated a 5-4-1 but pressed in six-second bursts in midfield. I pointed out that Mohamed Salah was isolated, touching the ball only four times in the opponent's penalty area across ninety minutes. This is the reverse kind of failure: complete data, a good moment of intervention, but low human resolution. The editor called to praise the piece, then gave me a line I never forgot: "You wrote it too correctly, but readers need to see a face, not just lines."

I understood that correct data is not enough. It needs a face for readers to hold on to. From then on, every piece of mine opened with a specific person — a shirt number, a nickname, a moment of error — before moving into the diagram and the space. I kept the data's accuracy but arranged it behind the human story. I record every passage of play as a witness, not a fan.

The third is the summer of empty stadiums in 2026. In March that year, global football shut down. I was fifty-three, doing tactical research for a First Division club. Empty stadiums made the concept of home advantage, which I had used for twenty years, meaningless. I spent six months rewatching one hundred and twenty European matches played in front of empty stands, measuring the average distance between centre-back and goalkeeper when the home side was trailing. The result showed the home team pushed its line up 18% higher than usual, creating more dangerous counterattacks for the opponent.

The empty-stadium summer taught me that applause is only a coat of paint. When there are no fans, that coat peels off, and you see the naked professional substance. I realised I had believed an old assumption for twenty years without verifying it. That is the third kind of failure: complete data, a good moment of intervention, high human resolution — but the founding assumption was wrong. Since then, I have made a habit of noting the founding assumption at the end of every piece.

The trap of over-analysis

There is a trap that analysts like me easily fall into. It is over-decoding. When you have data, you want to squeeze it dry. You build more layers, more charts, more metrics. And gradually, the analysis becomes a giant chart no one reads to the end.

I have fallen into this trap many times. After each layer of analysis, I force myself to step back and ask: what does the reader need here? The answer is almost always: one thing they did not know, said in one sentence they can remember. Not twelve charts. Not thirty metrics.

There is a paradox in this profession. The more data you have, the more likely you are to postpone conclusions out of fear that verification is not yet enough. I once fell into that spiral: collect more, measure more, wait more. But the season waits for no one. The ball rolls. The team gets relegated while I am still perfecting my dataset.

The way I escaped was to set a time limit for data collection. When the deadline arrives, I write the conclusion with what I have, with a line warning about reliability. A provisional conclusion delivered on time is worth more than a perfect conclusion delivered too late. Tactics cannot save a team, but they help us know where we died.

Emotion is not the enemy of data

The empty-stadium experience taught me one more thing: do not deny emotion. For a time, I thought emotion was something to be removed from analysis. I wanted everything cold, precise, unbiased. But then I realised emotion is not the enemy of data. It is the coat of paint, not the foundation.

When I write about a player who made a mistake in the 89th minute, I cannot — and should not — write like a machine. I must write like someone who sat in the stands, who saw those legs tremble, who saw those eyes look down at the grass. That emotion does not distort the data. It makes the data have a reader.

But I always keep a boundary. After every cold judgment, I trace back to a human story. And after every human story, I force myself to have an information point holding it up. Emotion is not allowed to replace data. It is only allowed to dress data.

The empty-stadium summer taught me that applause is only a coat of paint. But it also taught me that this coat, used in the right place, helps people see the wall. The problem is not the coat. The problem is whether we use it to hide the cracks.

The counter-intuitive angle: the problem is not a lack of data

Here I want to say something that may annoy many people. Vietnamese football does not lack data. We lack something else.

Look at the reality. Every V.League match is filmed. Every goal, every pass, every foul exists on tape. International statistics platforms have covered V.League for years. The data is there. It is simply not turned into decisions.

What we lack is a pipeline — a process that turns observation into information points, information points into thresholds, and thresholds into moments of intervention. We have raw material but no factory. We have ore but no furnace.

And here is the most counter-intuitive part. Many people think the solution is to buy more tools, hire more analysts, install more software. I do not believe that is the root. The solution lies in the discipline of note-taking and the courage to act. Neither costs money. They cost habits.

A club can have the most expensive analytics software in Southeast Asia and still be relegated, if no one turns the data into decisions. Conversely, a club with a notebook and a pencil can survive, if the person holding the notebook knows what he is looking for and knows when to act.

I once witnessed a coaching staff with complete footage, complete numbers, whose every meeting ended with the sentence: "Let's just see next match." That is not a data problem. It is a courage problem. A tactical diagram is like a map of a landslide zone — it shows you where not to stand. But if you know where not to stand and stand there anyway, the map is useless.

When the empty dossier appears in the meeting room

There is one image I will never forget. It is a tactical meeting where everything on the table was empty. No dossier on the opponent, no movement data, no threshold measured. Only feelings and memory. One member said: "I think the opponent is strong on the flanks." Another said: "I think we should play tighter." No one asked: strong on which flank, with whom, in how many recent matches. The meeting ended with a decision based on two feelings.

I call that an empty dossier. It is not a blank sheet of paper. It is a sheet full of words but with no information point at all. Full of words yet empty.

An empty dossier is more dangerous than a blank one. A blank sheet is obviously blank to everyone. An empty dossier looks full — it has judgments, conclusions, recommendations. But none of them have a source, a timestamp, or verifiability. It creates the illusion that we have analysed, when in fact we have only told stories.

I realised an entire football nation can operate on empty dossiers. And it operates quite smoothly, because no one has to take responsibility for a feeling. The person who says "I think the opponent is strong on the flanks" is never wrong, because he is only speaking about his own thought. But the team is still relegated.

The line between humility and self-doubt

There is one thing I have had to learn over many years. It is to distinguish humility from self-doubt.

Humility is an attitude in how you communicate. I am willing to hear others argue back. I am willing to say: "My data may be wrong." I am willing to note the founding assumption at the end of a piece so readers know what I based it on.

But humility in communication does not mean doubt in conclusion. Once verification is sufficient, I must state clearly what I believe. A coach cannot walk into the dressing room and say: "I think maybe we should play like this, but I am not sure." Players need certainty. They need to know what to do.

I once made the opposite mistake. I was so humble that decisions became vague. I offered too many options, too many warnings, until the coaching staff did not know what to believe. That was another form of postponement, dressed as caution.

At 59, I understand that winning matters less than explaining why we won. But I also understand that explanation without decision is only commentary. And commentary does not keep a team up.

Refereeing and the sufficiency gate in the dark

There is one field where the data sufficiency gate is especially hard to apply: refereeing and VAR.

In modern football, VAR is designed to correct clear and obvious errors. But that phrase itself is an ambiguous clause. What is clear? What is obvious? Two referees can look at the same incident and give two different answers, both within the permitted range.

The space for subjective judgment in VAR is larger than people think. When we draw a line on screen to determine offside, we choose a frame, we choose a point on the player's shoulder, we choose the moment the ball leaves the foot. Each of those choices is an information point — but an information point placed by a human, not measured by a machine. And when a human places the information point, entity resolution becomes a problem again.

I am not saying VAR is wrong. I am saying that even in the field considered most objective, we still pass through the sufficiency gate. And that gate, in the darkness of a decisive moment, is often not wide enough.

What I want to hand over

I began my writing career in 2026, at a local newspaper, where I learned the discipline of writing from observation. After that, I went through eight Olympic Games, eight World Cups, and many editions of the major cycling tours. Those experiences taught me that data is the same in principle everywhere, differing only in its thresholds.

What I want to hand over to young coaches and new analysts is not a set of tools. I have no set of tools to hand over. I have only one habit: before concluding, count how many information points you have.

If you have only two points, do not conclude. Go and collect more. If you have enough points but do not know when to act, set a time limit. If you have acted and the team still loses, reopen the diagram and find where the gap lies.

When a team is relegated, I redraw the diagram of the pain. And I realised that pain, drawn as a diagram, becomes a structure. A structure can be fixed. A feeling cannot.

What remains after the season

Every season has a champion and a relegated team. But what remains after the season is not the table. It is what we learned about how we make decisions.

The question I want to leave is not which team will win this season. That question is too easy, and its answer lies in the future. The question I want to leave is: when the season ends, do you have a dossier full of information points, or a dossier full of feelings?

Because in the end, tactics cannot save a team. They only help us know where we died. And knowing where we died is the first step to not dying there again.