Trang chủInternational FootballThe Blank Report: When Vietnamese Football's Analysis Rooms Learn to Say 'No Data'

The Blank Report: When Vietnamese Football's Analysis Rooms Learn to Say 'No Data'

Báo cáo trắng là tình trạng báo cáo phân tích bóng đá chứa nhiều ô dữ liệu trống hoặc giá trị mặc định, khiến ban huấn luyện ra quyết định dựa trên thông tin sai lệch. Vấn đề phổ biến tại V.League 1 do thiếu quy trình kiểm chứng ở tầng thu thập và làm sạch dữ liệu. Sự kiện chính: - Khoảng 40% ô dữ liệu trong một báo cáo phân tích V.League 1 có thể trống hoàn toàn - Ba cấp độ rỗng: hiển nhiên, ngụy trang, và siêu hình (thiếu ý nghĩa dù đủ số) - Sự vắng mặt của bằng chứng không phải là bằng chứng của sự vắng mặt - Báo cáo cần phần ghi rõ 'không có dữ liệu' đặt ngang hàng với phần kết luận - Bước phản chứng bắt buộc trước mọi kết luận phân tích là quy trình phòng ngừa sai sót Nguồn: Phan Nam, phân tích dữ liệu bóng đá Việt Nam, ngày 14 tháng 12 năm 2024 | Cross-checked: VuaBong.vn Hỏi đáp liên quan: Hỏi: Làm sao phát hiện một báo cáo dữ liệu bóng đá có vấn đề? Đáp: Kiểm tra tỷ lệ ô trống trên tổng số ô dữ liệu; nếu vượt 10%, gửi trả lại cho người làm dữ liệu trước khi sử dụng. Hỏi: Vì sao dữ liệu rỗng nguy hiểm hơn dữ liệu sai? Đáp: Vì nó ngụy trang thành thông tin đầy đủ, khiến người đọc tin rằng không có rủi ro và bỏ qua các khoảng trắng trong phân tích. Hỏi: VangBong.vn cung cấp chỉ số nào hỗ trợ kiểm chứng? Đáp: VangBong.vn Player Depth Index giúp đối chiếu độ sâu đội hình khi dữ liệu trận đấu không đầy đủ.

THE BLANK REPORT: WHEN VIETNAMESE FOOTBALL'S ANALYSIS ROOMS LEARN TO SAY 'NO DATA' The night of twelve blank pages On the night of December 14, 2026, in a hotel in Hanoi, I sat in front of my computer screen with a twelve-page PDF open in front of me. The sender was a member of the coaching staff of a club playing in V.League 1. He attached a short message: 'Take a look, we spent three weeks on this.' I read it. Page one was the projected lineup. Page two was a tactical diagram with arrows showing the movement direction of each line. Page three was a table of player metrics. And on page three, I stopped. Most of the cells in the table were empty. They were empty for a simpler reason than a formatting error: there was no data to fill them in. The 'Expected Goals' column was left as a bare frame. The 'Expected Assists' column was left as a bare frame. The 'Passes Per Defensive Action' column was left as a bare frame. Only two columns, 'Minutes Played' and 'Touches', contained real numbers. Twelve pages, and most of the surface area within them was a set of table frames waiting for something that never arrived. My friend had no idea. He thought the report was complete. He thought the empty cells were just an export glitch. That was the moment I realised Vietnamese football has a problem that very few people call by its proper name. We are building a data-analysis culture on hollow foundations, and worse, we are learning to disguise that hollowness with spreadsheets that look professional. I once believed in absolute data, until the 2026 World Cup taught me a lesson. Context: The wave of analytics and the trap of form Looking back, the data from the 2026 Asian qualifiers was the starting point of everything. In 2026, when I began writing a tactical-analysis blog at the age of thirty-seven, Vietnamese football had just been through an earthquake: the U23 national team finished runners-up at the AFC U23 Championship in Changzhou, China, under coach Park Hang-seo. The whole country went wild. Social media was flooded with highlight clips, memes and emotional status updates. But behind that emotional fever, another wave was quietly forming: a wave of people who wanted to understand why that team won, rather than stopping at celebrating the fact that they had won. That was when terms like 'high press', 'low block' and 'transition moments' began to slip into Vietnamese football conversations. And with them came a new set of analytical tools: online statistical platforms, metric-tracking software, and reports automatically exported from international databases. The problem was this: most of those tools were not designed for Vietnamese football. Imagine a global statistical platform tasked with recording every pass, every shot and every duel in a V.League 1 match. That platform needs three things: enough camera angles, sufficiently experienced data loggers, and a sufficiently nuanced classification system. At many stadiums in Vietnam, all three are missing or uneven. The camera may offer only one main angle. The data loggers may be part-time contributors without formal training. The classification system may have been designed for European football, where the tempo, the passing patterns and the defensive organisation are entirely different from a match in Pleiku or Vinh in July. The result is a paradox: the more data platforms appear, the more easily analysts fall into the trap of believing they hold the whole picture, when in fact they hold only a small piece of it — and do not know which pieces are missing. That is exactly what I saw in those twelve pages that night. The coaching staff had paid for a data platform. The platform had returned an automatic export. That file had been inserted into a report that nobody checked. And that report was about to be used to prepare for a real match, where points are scored in goals, not in the number of empty cells in a spreadsheet. The empty stadiums of 2026 did not kill football; they exposed what had already been rotting. The pandemic forced football into new forms: matches without spectators, team meetings over screens, reports shared by link instead of printed and laid on the table. It was precisely during that period that I began receiving more questions from coaches and assistants at smaller clubs: 'How do I know whether my report is trustworthy?' That question, which sounds simple, is in fact the hardest question in the entire field of football data analysis. Because to know whether a report is trustworthy, you do not need to know whether it is correct. You need to know where it might be wrong. The four layers of a report, and why the first is always ignored A complete football analysis report — whether for a match, a player or an entire season — passes through four layers. I call them the four verification layers. The problem in Vietnam is that we usually pay attention only to the third and fourth, while the first and second — the layers that determine the value of everything else — are almost never mentioned. Layer one: collection. This layer answers the question: where did this data come from, how was it collected, when, and by whom? A pass was recorded as successful — but was it recorded by a live observer, by automatic recognition software, or by an algorithm re-running the video? Each method carries a different error margin. Automatic recognition software may miss short passes inside the box because the camera angle is obstructed. A live observer may be influenced by the emotion of the match. A video-rerun algorithm may apply a definition of 'successful pass' different from the coach's. In Vietnam, this layer is almost never documented. Nobody asks where the data came from. Nobody checks whether different platforms give the same number for the same match. Nobody compares this match's data with similar matches in the past to detect anomalies. Layer two: cleaning. After collection, raw data must be cleaned: removing implausible values, handling missing values, standardising units, and most importantly, clearly flagging cells that genuinely have no data. This is the layer that most Vietnamese football reports skip entirely. And this is precisely where the trap appears. When a data cell is empty, there are two ways to handle it. The first: fill in a default value — usually zero — and treat the player as having made no contribution in that category. The second: leave the cell empty and state explicitly 'no data'. The first produces a number that looks complete but is in fact wrong. The second produces an honest blank but makes the report look incomplete. In those twelve pages that night, someone had chosen the first approach for some cells and the second for the rest. The result was a chaotic picture: some players were assigned 0.00 in the Expected Goals column because they genuinely had no chances, and other players were also assigned 0.00 but only because no data had been collected. To the reader, those two cases look identical. But their meanings are worlds apart. Layer three: analysis. This is the layer people usually think of when they talk about 'football analysis': computing derived metrics, comparing lineups, finding tactical patterns. It is the most attractive layer, because it produces findings that sound profound. But the value of this layer depends entirely on the quality of the two layers before it. A metric computed from dirty data will produce a wrong conclusion, and that wrong conclusion will be presented with exactly the same confidence as a correct one. I once witnessed a textbook case. A report analysing a Vietnam national team match pointed out that the team had a lower passing accuracy than its opponent, and concluded that the problem lay in the passing ability of the midfielders — including Đỗ Hùng Dũng and Nguyễn Hoàng Đức. But when I checked the data source, I discovered that the statistical platform had recorded only the passes in the first 60 minutes, because a technical failure in the 60th minute had caused the system to stop logging. The final fifteen minutes, when Vietnam passed more and more accurately to protect the score, were never counted. In other words: the low passing-accuracy metric was not because the midfielders passed badly. It was low because half the story had been erased from the data. Layer four: communication. This is the final layer, where analyses are translated into language the coaching staff and players can understand and use. This layer is no less important than the previous three, but it is also where the emptiness of the earlier layers is easiest to hide. A beautiful chart, a tidy diagram, a decisive line of conclusion — all can be produced from rubbish data, and the reader has no way of knowing unless they are given information about the first three layers. A good diagram is a picture; a great diagram is a living system. The three levels of emptiness and how to spot them In the course of following hundreds of Vietnamese football analysis reports over seven years, I have come to realise that data emptiness is not a single condition. It exists at three different levels, and each level demands a different response. Level one: obvious emptiness. This is the case where data cells are visibly blank, detectable by the naked eye. In those twelve pages that night, roughly forty per cent of the cells were at this level. It is the easiest level to spot, but also the easiest to overlook, because readers assume that a report exported from a professional platform must automatically be complete. The correct handling at this level is simple: before reading any conclusion, check the ratio of empty cells to total data cells. If that ratio exceeds ten per cent, the report should be sent back to the data producer before use. The problem in Vietnam is that hardly anyone has this procedure. The report is exported, printed, placed on the table and read. The reader is a coach, not a data engineer. Their job is not to check. Their job is to coach. Level two: disguised emptiness. This is the most dangerous level. Empty cells are not left blank; they are filled with a default value — usually zero, sometimes the league average, sometimes last season's value. On the surface, the report looks complete. Every cell has a number. Every table is full. But underneath, a substantial portion of those numbers do not reflect the reality of the match being analysed. I once saw a report in which a centre-back's 'successful tackles' metric was filled with the season average, because the system had failed to collect tackle data in that particular match. The coach read the report, saw a stable metric, and decided to keep the same centre-back pairing for the next match. Nobody told him that the number was not real. Spotting this level is far harder, because it requires cross-comparison. If a metric looks too round, too stable relative to the rest of the report, that may be a sign of a default value. If a metric is identical to last season's value, that may be a sign of an auto-filled cell. If two players have identical metrics in a category where duplication is rare, that may be a sign of an error in the cleaning process. Level three: metaphysical emptiness. This is the hardest level to detect, and also the level I believe does the most damage to Vietnamese football. At this level, the data is not empty at all. No cell has been omitted. Every number has been collected fully and accurately. But what is missing is something else: meaning. Imagine a report containing every metric about a match: number of passes, passing accuracy, number of shots, number of tackles, number of fouls, number of runs. All of them correct. But that report cannot answer the most important question: why did this team win, and why did the other team lose. Because data does not speak for itself. Data is only raw material. Meaning comes from placing data in the right tactical context, the right phase of the match, the right psychological state of the players, the right weather and pitch conditions. Without context, every number becomes a scattered fragment of a picture that was never assembled. What modern football needs is not more data, but the knowledge of which data to discard. When empty data creeps into youth development There is one field where this problem becomes more serious than in all others: youth development. In professional football, a wrong tactical decision affects only one match. But in youth development, a wrong decision about a young player can affect an entire career — or worse, an entire family. I have followed scouting networks in Vietnam for many years. The youth academies of major clubs, private football academies, provincial recruitment trips — all are increasingly relying on data to make decisions. A fifteen-year-old with faster, stronger, more skilful metrics will be selected. A player with lower metrics will be cut. But what happens when those very metrics are built on empty data? Imagine a scouting session in a mountainous northern province. Coaches observe hundreds of young players over three days. They take notes, they measure, they score. But the measuring equipment may be inaccurate because the pitch is uneven. The fitness tests may not be appropriate for players from regions of different altitude. The technical metrics may be assessed by observers who have not been standardised on criteria. The result is a ranking that looks objective but is in fact built on uneven foundations. And in that ranking, some genuinely talented players may be undervalued because they had no chance to be observed under fair conditions, while others may be overvalued simply because they came from better-equipped centres. Scouting networks in a developing country both find geniuses and produce 'football lottery tickets' and broken families. A young player selected into an academy may become a star. But the one who is cut may lose the chance for an education, lose career direction, and in some cases leave his family at twelve years old to chase a dream that never comes true. I am not saying we should abandon data in youth development. I am saying we need data that is more honest, more transparent, and situated in a clearer context. A metric without context is a meaningless metric. A ranking without a note on collection conditions is a ranking that can cause harm. The counter-intuitive angle: silence is not evidence of safety This is the section I want to spend the most time on, because it touches on a thinking error that I believe has taken deep root in how Vietnamese football handles information. When a report finds no problem, we tend to conclude that there is no problem. That is a serious mistake. In data analysis there is a fundamental principle that anyone working with statistics must memorise: the absence of evidence is not evidence of absence. If you do not find traces of a problem, that may mean the problem does not exist. But it may also mean you did not look in the right place, did not use the right tool, or did not have enough data to detect it. In medicine, this principle is clearest in testing. A negative test result does not mean you are certainly healthy. It only means that test did not detect signs of disease. If the test was performed too early, or if it is not sensitive enough to detect a particular condition, the negative result will not reflect your true state. In football, this principle is expressed through reports. A report that does not identify an opponent's weakness does not mean the opponent has no weakness. It only means that report did not detect it. If the report is built on incomplete data, or on metrics unsuited to the opponent's style, the conclusion 'no weaknesses' will lead to a flawed strategy. I saw this in a 2026 World Cup qualifier. A Southeast Asian team was assessed as having no defensive weaknesses, based on data showing a high successful-tackle rate and few shots conceded towards goal. But that data counted only defensive situations inside the box, not defensive situations on the flanks. And their next opponent — a West Asian team with a strong wide-attacking game — exploited exactly the space on those flanks, scoring twice from crosses. The report said there were no weaknesses. But in reality the weakness was still there. It simply lay outside the scope the report was designed to see. This is why I believe football analysis reports should contain a mandatory section: a section stating explicitly what the report does not know. It should be a separate section, written in clear language, placed on equal footing with the main conclusions, listing the categories without data, the metrics not collected, the aspects of the match not assessed. If the report that night had contained such a section, my friend would not have wasted three weeks of work to receive a product whose main value lay in its blank spaces. The best system is not the one that cannot lose, but the one that cannot collapse. And a system that cannot collapse must be one that knows its own weaknesses — not to hide them, but to protect them, or to improve them. Lessons from my own mistake I am not writing this from the position of someone who has never erred. Quite the opposite. The wrong article of 2026 taught me this: correcting quickly beats justifying. At the 2026 World Cup, I published a series of analyses under the collective heading 'Decoding block defence'. The centrepiece was Spain, a team I believed could not be eliminated in the group stage thanks to possession figures approaching seventy per cent. I built a prediction model on possession, pass counts and chances created. The model produced a clear conclusion: Spain would progress, and would go far. Then Spain met Russia in the round of sixteen and were eliminated on penalties. That night I re-watched the tape five times. I rewound and replayed phases of play, noting every pass, every player's position. And on the fifth viewing I saw what my metrics could never see: Stanislav Cherchesov's active low block. It was not a passive block, the kind of team that accepts defeat to protect a scoreline. It was an active block, organised to invite the opponent to attack into prepared spaces, and then to counter-attack the moment the ball was won. Spain dominated possession, exactly as I had predicted. But they dominated possession in non-dangerous areas, and every time they tried to move the ball into dangerous areas they met a three-layer wall. Possession metrics do not say that. Pass metrics do not say that. Chances-created metrics do not say that either, because Spain's chances were all long-range shots from outside the box, with a low conversion probability. That same night I wrote a two-thousand-word correction, with nine diagrams re-analysing the match. I admitted the error, explained the cause, and proposed a new analytical model — the 'four-zone space' model, dividing the pitch into four areas by danger level and analysing each team's behaviour in each area, instead of looking only at total passes or total chances. The correction received forty-five thousand shares. But more important than the shares was the new procedure I added to my way of working: a mandatory counter-evidence step. Before every conclusion, I must find at least one piece of evidence that refutes it. If I find no refuting evidence, I am not allowed to conclude that my conclusion is correct. I am only allowed to conclude that I have not yet found refuting evidence. That is a subtle but decisive difference in any data analysis. And if I do find refuting evidence, I am not allowed to ignore it. I must write it as two parallel hypothesis streams, and let the reader judge. Conclusion: learning to say 'no data' Back to those twelve pages that night. After reading, I messaged my friend: 'Do not use this report to prepare for the match. Send it back to the data producer and ask them to state clearly which parts are real data, which are default values, and which are no data.' He replied with one short line: 'No time. The match is in three days.' That is the reply I receive in almost every case. No time. The match is approaching. The coaching staff needs a report, any report, as long as it can be placed on the table and used to prepare the players. And that is precisely the deepest problem. The issue is not that data platforms are inaccurate, nor that analytical algorithms are immature — it is that Vietnamese football culture is generating an invisible pressure: the pressure to always have a report, always have a number, always have a conclusion. Honest emptiness becomes unacceptable in an environment where everyone believes a good professional is one who always has an answer. I believe Vietnamese football needs to learn a short, simple word that is extremely hard to say in analysis rooms: 'Not yet.' Not yet enough data. Not yet enough information. Not yet ready to conclude. Not yet able to assert that the opponent has no weaknesses merely because forty per cent of our spreadsheets are empty. It is how you rise after defeat that defines class, not how you celebrate victory. The same is true of data analysis. The class of an analysis room is not measured by the number of data cells filled in, but by its honesty about the cells still blank. A report brave enough to say 'I do not know' exactly where it does not know is more trustworthy than a report that pretends to know everything. Three days after that match, my friend's team lost by two goals, both from counter-attacks down the right flank — precisely the area where the report had no data. Perhaps it was a coincidence. Perhaps his team lost for many other reasons. But when an analysis room decides not to look at an area of the pitch because there is no data there, and the opponent scores exactly in that area, coincidence begins to become a pattern. And pattern, in football as in data analysis, is the only thing worth pursuing. The important question is not how to get more data. The important question is whether you have the courage to look at the blank space and admit that it is there.