When the Report Is Empty: A Lesson on Data and Verification in Football

Opening: the report that had nothing to say One night in 2026, when I was twenty and still a second-year student, I sat in a rented room in Saigon and wrote a preview analysis of Vietnam against Iraq in qualifying. I laid out a 4-1-4-1, drew arrows for a high press, and declared that Iraq's diamond midfield would be smothered. The match ended 1-1, but Iraq produced 23 shots — three times what I had imagined. Comments flooded in, and the line I remember most was only six words long: "Analyzing on paper is easy." I tell that story not to flagellate myself. I tell it because this week I received a deep football analysis, thousands of words long, split into nine sections, with tables, a "risk" section, even a "glossary of professional terms". But by the last line, the only thing it asserted with certainty was that it had nothing to say. A report full in form, empty in substance. In football, that is not rare. It is the most common occupational disease among analysts. Context: the frame comes before the data My job is to read matches. But reading a match is not like reading a bulletin. A football match contains thousands of events: passes, duels, off-ball runs, a defender turning his head to check a teammate for a split second before rotating. No one can watch all of it. So we build frames: formations, metrics, tables. The frame keeps us from drowning. But the frame can also deceive us. When there is no real data, the frame still stands. It still looks good. It still has a table of contents. It still has part one, part two, part three. The problem is that inside every cell there is only one word: insufficient information. I used to think that was the writer's fault. After many years, I understood it is the nature of analysis: a conclusion is only as trustworthy as the sample it rests on. Give me one match, and I can tell a story. Give me five, and I start to see a pattern. Give me twenty, and only then will I say "system". Below that threshold, everything is speculation in makeup. The worrying part is how easily the frame multiplies. Nine sections, three items each, a table per item — a few minutes to build. Real data is not like that. It demands dozens of hours of re-watching clips, cutting each phase, counting each touch. So when deadlines press, writers keep the frame and drop the data. The product still looks professional. The only difference is that it is no longer analysis; it is a sheet of graph paper. Search algorithms today reward what is called "information gain" — something the reader has never known. But most sports content runs the other way: it repeats what everyone has already heard, with different wording. A piece with no new data has no information gain. It is only an echo. The core: three times I had to relearn the lesson The first was Vietnam — Iraq in 2026. I was not short of data; I was short of the right data. I watched enough clips, but I watched what I wanted to see. I hunted for evidence of my pressing hypothesis, so every phase looked like evidence. The 2026 mistake never disappeared; it became the ruler for every prediction I make. Since then, before each piece, I force myself to answer one question: if this hypothesis is wrong, what will be the first sign on the pitch? The second was the 2026 World Cup final, France against Croatia. The whole cafe in Saigon chanted Kylian Mbappe's name. I kept my eye on Antoine Griezmann. He dropped deep, forming a near five-man plane with the midfield, leaving Croatia's centre with nothing to press. I look at a team like a blueprint, and the biggest surprise always comes from the attacking plane. But I had to watch that match a second time, only to watch Griezmann, before I dared to write. If I had watched once, I would have written about Mbappe like everyone else. The third was Euro 2026, Germany against Hungary. My editor wanted a headline like "Germany will crush them". I refused. Germany then left their defence far too open whenever they lost the ball, while Hungary were the most disciplined low-block side in the group. It finished 2-2, and Germany nearly went out. But what I keep is not that I got it right. What I keep is the discomfort of standing alone behind a conclusion the crowd disliked. Getting one match right does not prove I am good. It only proves I read the data instead of the mood of the crowd. The attacking plane and the trap of the star There is a habit I try to break: naming the best player. I no longer name the best player; I name the most effective gap. It sounds cold, but it has saved me from many wrong conclusions. Morocco at the 2026 World Cup is the clearest example. The media told a story of spirit, of warriors. That was true, but not enough to explain a semi-final place — the first time an African team had gone that far. What truly made the difference lay elsewhere: a side that shifted from a 4-3-3 in possession to a 5-4-1 out of it, with two full-backs — Achraf Hakimi and Noussair Mazraoui — no longer full-backs in the old sense. When opponents funnelled the ball wide, they turned the flank into a sealed corridor, while the middle was packed tight. What I learned from Morocco is not "spirit beats talent". What I learned is that a system can compensate for a gap in quality, but only when the system is measured in concrete numbers — how often opponents entered the box, how many transitions succeeded — not in emotion. And to count those numbers, you must re-watch the match. There is no shortcut. In the V.League, I have seen conclusions like "team X has found the formula" after three rounds. Three rounds is not enough to speak of a formula. Never mind that early-season fixtures are uneven: a team facing only weak opponents will look better than it is. The numbers are not wrong, but the context that produced them is forgotten. The counter-intuitive angle: even data can lie Many think the cure for "paper analysis" is more data. I am not sure. The heat map has become the new fortune-telling. It is pretty, it is colourful, it convinces viewers they are seeing the truth. But a heat map shows where a player was, not which chances he missed, which defender he dragged out of position, which gap he opened that a teammate never saw. A high number of touches in the box can signal a great striker, or a team that only knows how to funnel the ball into one spot. One number, two opposite stories. Data does not speak for itself. The one reading the data is the one speaking. The summer of 2026 gave me the answer: football without a crowd is only technique. When the Bundesliga returned to empty stands, home advantage all but vanished, and the away win rate rose markedly. That was a natural laboratory. It showed that much of what we call "home character" is really just crowd noise. But I also asked myself: will this recur under normal conditions? That question matters more than the answer, because it forces me to wait for more data instead of concluding at once. There is another example I use to remind myself: VAR review time. When a goal hangs in the air for two minutes on screen, the rhythm of the match cools, and that cooling appears in no metric table. A process designed to raise accuracy creates an effect it cannot itself measure. That is why I distrust conclusions built only on the final number. Load management is another. It sounds scientific: tracking minutes, sprints, rest days. But look closely at the calendar, and most "rest to recover" cases fall exactly on low-revenue friendlies, while players take the field where the money is. The numbers still look fine. But the story behind the numbers sits in no table at all. My rule: verify first, conclude later My work now boils down to one rule: set the falsification condition before drawing the conclusion. Like a scientist, I must state it plainly: this hypothesis collapses if the team presses below 30 metres next match, or if the central midfielder receives the ball fewer than 40 times. If I cannot state that condition, I do not understand enough to write. The passer always sees the ball before receiving it; I only try to re-read that thought. And re-reading someone else's thought demands humility, not certainty. Why an empty report is useful Back to that empty analysis. At first I found it useless. Then I changed my mind. It is useless as an analysis. But it is useful as a mirror. It shows what happens when we build the frame before we have the data: we produce something that looks complete, yet cannot survive the question "based on what?". In football, that is the death of credibility. A good piece is not the one with the most tables; it is the one where every claim can pay its debt. I no longer trust analyses that cite no source. I no longer trust conclusions that do not say how many matches the sample holds. And I no longer trust myself on days when I feel too certain. Defeat in a match usually begins when we start praying instead of adjusting. What I want you to carry away Every match is a small model; I only point to where the heat is if you are willing to look calmly. But to look calmly, you need something simpler than any algorithm: the habit of asking "where is the data?" before asking "what is the conclusion?". Next match, when someone tells you team A will surely beat team B, try one small question: how many matches are you basing that on? If the answer is "one", you are hearing a story, not an analysis. And if the answer is "I don't need data, I have a hunch", then you are hearing exactly the empty report I received this week — except it has not yet been framed to look pretty. I still keep the 2026 mistake in a drawer. Not to brood over, but to remind me that every time I forget to ask "based on what?", I am about to write a piece on paper.