The Unwritten Match Report: When Match Data Comes Back Empty

On the night of September 14, 2026, at Groupama Stadium in Lyon. I sat in the section reserved for disciplinary observers, a 47-code error sheet in hand, eyes fixed on every challenge between Lyon and Marseille. By half-time, I had recorded midfielder Dimitri Payet committing three fouls. At the 90th minute, I closed my notebook and sent the disciplinary report to the Ligue 1 organizers. Three days later, the reply came back, short and cold: an error. Payet had committed four fouls, not three. The entire report was returned, and I spent the following four weeks reviewing footage of twelve Marseille matches, cross-checking every incident the referee had whistled. That mistake was not large in number. It was large in principle. A data table wrong in a single cell can trigger a wrong sanction, an unjust suspension, or the opposite — a dangerous challenge slipping through the net and repeating the following round. Over a long season, the smallest error can become a precedent. In modern football, every match leaves behind an enormous data trail. Multi-angle footage, VAR logs, referee reports, distance-covered tables, sprint counts, foul counts, yellow cards. Fans look at all of it as a fair verdict. But those of us in the trade know: a trail does not automatically become the truth. In Ligue 1, a disciplinary report must pass through at least three verification layers before entering the system. The on-site observer records directly. The data center cross-checks against footage. The disciplinary board cross-checks against precedent. If one layer returns an empty result — no data, or mismatched data — the whole chain stops. That is the rule. But the rule only holds when someone is willing to stop. Deadline pressure always pushes the other way. A newspaper needs copy before the page goes to press. A broadcaster needs graphics before kickoff. A pundit needs a conclusion before the audience changes the channel. That gap breeds the most dangerous thing in analysis: the temptation to fill an empty cell with a guess. I once received such a data table. It came from an automated feed, full of columns, full of numbers, but when I checked it against footage, I found an entire half mislabeled. The figures looked clean, looked complete, and were entirely meaningless. Had I pushed it into print that day, I would have created a conclusion that was not true, complete with a source citation that looked highly credible. What is worth noting is that empty-data incidents are not rare exceptions. They are everyday occurrences in any system that runs on numbers — from referee reports and VAR logs to the performance metrics media publish each round. Three main causes turn a data table empty or skewed. First, transmission failure. Match data is typically collected by several different providers, each with its own format. When one mesh in that chain breaks — a dead camera, a hung connection, a truncated file — the rest keeps running, and the system still outputs a table that looks complete. The gap is covered with a default value, usually zero. And zero, in football, is a perfect lie: it is not data, it is the mark of lost data. Second, labeling failure. The same incident, one person records as a foul, another as a fair challenge. The line sits in the grey zone of the law — where the eye sees contact, but the law sees a touch. If the labelers are not trained consistently, the same act produces two different numbers. That was precisely my error at Groupama: I saw three, the footage saw four, because I had ignored a challenge on the edge of the box that I judged insignificant. Third, confirmation bias. An analyst tends to find the number he wants to find. If before the match I believe the away side defends hard, I will more readily record their fouls than reality warrants. Conversely, if I admire a player, I will unconsciously soften his challenges. Data does not generate bias by itself; the person reading the data is the one who installs it. These three causes do not exclude each other. They compound. And when they compound, they produce a particularly dangerous product: an analysis that is wrong but looks rigorous, with numbers, with sources, and therefore hard to question. With VAR, the problem is subtler still. When a VAR team concludes that there is insufficient evidence to overturn the decision, they are speaking the exact language of an honest empty report. But public opinion often hears that phrase as a refusal of responsibility. In reality, admitting a lack of evidence is the hardest decision, because it hands no one a conclusion to hold onto. In 2026, when the World Cup was held in Russia, I was assigned a feature on yellow-card sanctions. I decided not to chase blockbusters like France — Argentina, but instead to follow all fourteen group-stage matches with the fewest goals, to analyze tactical fouling behavior. My method for tracking World Cup 2026 was a net: small mesh, no fish missed. I combed through every fifth touch, every counter-attack-stopping situation, rather than only recording the thunderous tackles. The result surprised me. Iran, under coach Carlos Queiroz, had the tournament's highest rate of counter-attack-stopping fouls: 23 in 3 matches. Not loud challenges, but small, quiet contacts in midfield, at the exact moment the opponent shifted from defense to attack. Those incidents barely appeared in the major bulletins. Yet they were the soul of how Iran played. The article was later cited by the European Referees' Council, and I received an invitation to collaborate with So Foot magazine. But the real reward was not there. It was this: had I been lazy with cross-checking that day, I would have missed 23 tactical fouls — and an entire tactical story worth telling. From then on, I began building a personal error-code sheet of 47 codes, and every article had to carry a data-source note. This is the point most easily misunderstood. Many assume empty data is a failure — a sign of a broken system in urgent need of repair. In my experience, the opposite is true: an empty table is more honest than a full one that is wrong. In football analysis, we live in a culture that rewards completeness. The more numbers, the more graphics, the more a piece is treated as deep. But that completeness is often just paint. A center-back running 11 km a match sounds impressive, until you realize most of that distance is jogging back into position after losing the ball. Distance covered and sprint counts are packaged as effort metrics, but ineffective running also produces pretty numbers. A pretty number is not the same as a real contribution. I have seen counter-attack-stopping fouls omitted from statistical tables because they were too small for the coarse mesh. And I have seen harmless challenges magnified, only because the player was a star. When data is filled with prejudice, the empty cell is the most honest friend you have. This holds true in a neighboring field too: esports. Betting is eroding competitive integrity in esports faster than in traditional sport, simply because the regulatory system there lags behind the speed of data and money. When capital flows faster than law, data tables get bent to serve the odds before anyone can verify. A system with no room for an empty cell is a system with no room for the truth. The error in the 2026 World Cup qualifiers taught me: the report is not written in advance. The job of the referee, like the report-writer, is not to predict the outcome, but to let the final whistle confirm the truth. I never write a statistical figure without checking it myself at least twice. Perhaps football should learn to respect empty cells. A report that admits it lacks enough data is more credible than a confident report that is hollow. And if one day you see a match-analysis table come back empty, try asking: is that a failure of data, or the first time data dared to tell the truth?