Vietnamese Youth Scouting Reports: Full Frames, Empty Data

Nine pages. Nine analytical sections. Twenty-three tables. Four risk levels. Every box was neatly ruled, every heading bolded, and in every slot where data should have stood, the author typed exactly two words: insufficient information. That file sat on my desk in Hai Phong for three weeks. I did not tear it up, because it taught me something nineteen years of watching youth football had never taught me clearly enough: an empty analytical framework is not honesty. It is a very polite way of refusing to work.

The man who sent it was a fresh graduate, assigned to cover a northern regional U19 tournament. He told me the truth: no footage sharp enough, no minutes-played table, no complete team sheets. So he returned exactly what he had — a complete skeleton with nothing inside. I understand the feeling. But that feeling is producing a generation of reports that say nothing about any player.

Vietnamese youth football runs on a short calendar: the national U19 championship, the national U21 championship, the Second Division, a few regional friendlies, plus overseas training camps whose public information usually stops at the scoreline. An 18-year-old can play twenty matches in a year, but the number with watchable footage can be counted on one hand. Big academies such as Viettel, PVF, Hanoi and HAGL have their own analysis rooms; the rest of the system does not. Scouting reports therefore get written from memory and a few notes taken from the touchline. I do not criticise that method. I criticise the way it is presented.

The first distinction that must be drawn: missing data is an event, while an empty framework is a device. When a scout writes "insufficient information" against one criterion, he is telling me there is a gap to be filled. When he writes those two words against all nine sections, he is telling me he was not at the match, or did not watch the footage back, or could not find a source. Those three possibilities demand three different responses. The framework cannot tell them apart, because a framework is only a rack to hang data on — it does not generate data itself.

In 2026 I built a tracking sheet with six secondary indicators for Tran Danh Trung at the national U19 championship: shots on target, aerial duels won, successful pressing actions, pass accuracy, successful dribbles, and output against the top four. He scored 12 goals in 18 matches, far above the tournament average. Had I simply filled in the "goals" box and closed the file, I would have had a beautiful report. Split by opponent, however, all of those goals came against bottom-half teams; against Hanoi and SLNA he barely produced a meaningful attempt. Numbers are only topsoil; I dig deeper for the groundwater. The groundwater here is that his goals were not distributed evenly by opponent quality.

In 2026, when the pandemic emptied the pitches, I lost access to Haiphong's youth training sessions and had to work remotely. Tracking three loaned players in the Second Division through statistical data, I found a 19-year-old defender named Nguyen Van Hop with a successful pressing rate roughly 23 percent above the division average. That figure was enough for plenty of people to write a eulogy. I added a line: the sample is seven matches, and after a five-month stoppage neither fitness nor mentality can be assessed. I advised the club not to promote him yet. At the end of the season he tore a ligament after being pushed into a congested schedule. A deliberate empty box, placed beside hundreds of filled ones — that is how it works. When the pitch is empty, I listen to the data. It lies more than I once believed.

In the 2026 World Cup quarter-final at Nizhny Novgorod, France beat Uruguay 2-0 through Varane's header and Griezmann's finish. The footage showed vast space behind full-back Diego Laxalt. The easiest reading is to blame the individual: the defender played badly. Yet Uruguay's pressing numbers at that tournament were among the highest. After re-watching their six previous matches, I realised that space was the consequence of a tactical choice, not an isolated error. One match does not make a talent, but it illuminates exactly where to dig. With only one match in hand and a framework to fill, I would have filled it wrongly.

In 2026 I was genuinely wrong. When Morocco reached the World Cup semi-finals, I doubted their data: low possession, few passes, not many chances created. My old evaluation framework concluded they were not good enough. After their round-of-16 tie with Spain, I sat down and watched all five of their matches, and found their rate of rapid transition was roughly three times the tournament average. I misread them because I looked at one cluster of metrics, and had to write a three-part self-critique. Belief only has value once it passes the qualifying round of evidence — including the writer's own belief.

Back to the nine-page file. The problem is not that it is empty. The problem is that it is presented as though it were full. The more detailed the structure, the easier it is to create the illusion that the work has been done. The scouting world has a blunt name for this: the compliance report. It exists to prove that somebody went to watch, not to answer whether this player can handle the first team.

The counter-intuitive view: the more boxes there are, the easier it is for the writer to hide. A report with only three questions — what does this player do, what can he not do, and in how many situations have I seen it — forces the writer to own every sentence. A report with nine sections and twenty-three tables lets responsibility scatter in all directions. The number of boxes does not measure analytical ability. It measures the reader's endurance.

People often assume an empty report is an honest act, because it admits ignorance. Honest it may be, but it is not the endpoint. If every metric is missing, the job is to phone for footage, hunt down team sheets, watch the match again. A file consisting entirely of "insufficient information" is procrastination in careful packaging.

People also say it is too early, too risky, to judge young players. I agree — mostly. But youth football does not need conclusions; it needs the right questions. I am not hunting a gemstone; I am sieving sand to understand the stratigraphy of youth football. A good report does not say "this player will be a star". It says: he shields the ball well when pressed from behind, he is slow to turn onto his left, and in twelve substitute appearances he arrived in the right spot inside the box nine times. Those three sentences are enough for a first-team coach to decide whether to bring him into full training.

Youth cohorts are a living archaeological layer; each season scrapes off another stratum, and I do not rush to conclude. But I am obliged to record the layer I just scraped, with dates, opponents, match conditions and sample limits. Without those four things, every conclusion is literature.

There is a young player in Haiphong I have tracked for nearly two years. He has no standout metric: not many goals, not many dribbles, absent from every statistical ranking. The only number that caught my eye was his distance covered without the ball, always about a fifth above the team average and stable across the whole season, including heavy defeats. Data is not innocent. It can be distorted by a team's tactics, by the quality of team-mates, and by media intent. But when one metric repeats across months, opponents and circumstances, it stops being coincidence.

He has not been promoted to the first team. I do not know whether he will be. I only know that in my file on him, not one box says "insufficient information" — even though it took me nearly two years to fill it in.

If you are holding a framework full of empty boxes, I am not asking you to invent data. I am asking you to put one true line in it: date, opponent, conditions, sample. An empty box is worth keeping only when at least one box beside it has been dug to the bottom.

The question I leave for myself, and for those who share this trade: in the most recent report you submitted, how many lines were about the player, and how many were only about you?