When the Data Table Goes Blank: A Warning from a Disciplinary Reporter

Saturday night, I reopened the round-12 derby summary on my screen. The "cards" column was empty. The "minute" column held three rows that contradicted one another. In the notes field, the line I had typed six hours earlier was still there: "check again — something is wrong." In the 88th minute, the score stood at 1-1. The referee showed a red card to the visiting centre-back after a collision inside the penalty area. The stands erupted. But when I rewound three camera angles, I noticed something odd: no angle showed the player named in the official report. The match's official data table — the one thousands of people would later cite — was blank in the single most important cell. That was the moment I understood: a report with no data was never neutral. It is an error waiting to be copied. I have worked as a league disciplinary reporter for eleven years, seven of them tied to referee statistics. The job sounds dry: logging every card, every minute of stoppage time, every VAR decision, then cross-checking against the official report. But that supposedly mechanical work taught me the biggest lesson of the trade: data does not generate meaning on its own. People assign meaning to it — and people are also the ones who distort it. For fans, a match is emotion: goals, roars, heartbreak. For me, a match is a chain of verifiable decisions. Every referee call is a variable. And my job is simply the test. Professional football's data systems run on an unspoken assumption: every cell gets filled, every event gets recorded. When a blank appears, most people skip over it. They fill the gap with memory, with feeling, with what they believe they saw. I did exactly that once. And I was wrong. In 2026, as a second-year student, I covered the derby between the University of Manchester and the University of Liverpool. I wrote that the referee had shown a yellow card to defender Trent Alexander-Arnold in the 23rd minute. In fact, the card went to a teammate. One name placed in the wrong position in the report. My editor reprimanded me severely, and I had to write a letter of apology. My first mistake was not the red card awarded in error. It was believing I would never award one in error. After that, I spent six weeks memorising FIFA's card regulations and logging 189 card incidents from the 2026 World Cup as reference data. Not to become an expert. But to understand that a wrong number, repeated often enough, becomes a fact in the end-of-season report. There is another detail I always remind myself of: English readers and Vietnamese readers need two different layers of explanation. English readers grew up with VAR and semi-automated offside; they know the language of "on-field decision" or "clear and obvious error." Vietnamese readers need a quick gloss inside the piece — Hawk-Eye is the camera system that reconstructs the ball's trajectory, VAR is the video room that assists the referee — before any argument begins. Writing for both without explaining is the fastest way to lose half your audience. Three tiers of verification Facing that blank table that night, I did not rush to a conclusion. I moved through three tiers of verification — the process my editors once called "slow but sure." The first tier is the origin of the number. What does a blank "cards" cell mean? Perhaps the referee had not yet filed his report. Perhaps a data-entry clerk skipped it. Perhaps the automation failed to sync. Each possibility leads to a different conclusion. In tennis, I have seen the same problem with Hawk-Eye data: sensors can drift if the court is calibrated wrongly, and no one checks until a pivotal point is called incorrectly. The second tier is historical context. A card in the 88th minute does not stand alone. It sits inside a chain of decisions across the match. How many cards has this referee shown this season? Does he tend to soften in the second half? Does the away side have a history of clashes with the host? When I analysed Morocco at the 2026 World Cup, I found their defensive system relied on cutting off the man without the ball rather than direct tackling. They cleared the ball more than European sides, yet their average card rate was 32 percent lower. That number only means something beside the tactical context. The third tier is deviation from the norm. Three "minute" rows that disagree are not a trivial detail. They are a signal. If the official report says minute 88, one source says 85, and another says 90+2, then at least two of the three sources are wrong — or all three are wrong in different ways. In 2026, analysing 23 matches between 2026 and 2026, I found Portugal received cards 41 percent more often in matches officiated by French referees. That is a deviation. But a deviation only has value once you prove it is not random. These three tiers do not replace one another. They stack. And only when all three point the same way do I allow myself to write. The match table I work with has four main columns: card count, minute, carded player, and offence type. At a glance, it is just a spreadsheet. But every column is an assumption. The "carded player" column assumes the data-entry clerk can tell apart two players in identical shirts from a distant angle. The "minute" column assumes the referee's clock matches the broadcast clock. The "offence type" column assumes the recorder knows the line between a technical foul and unsporting behaviour. When one of those assumptions collapses, the whole table loses value. And the danger is that it loses value silently. I once built a comparison table for that match: three data sources, six cells, and only two that matched. Two out of six. That was the ratio I could work with. The rest, I was forced to leave blank rather than guess. What is telling is that no one at the organising body wanted to hide anything. They simply did not have enough people to check every cell. Data moves faster than humans can verify. And in that lag, small discrepancies accumulate into a wrong report. Back to the 88th minute. I reconstructed the situation from three angles: the main broadcast angle, the angle behind the goal, and the touchline angle. On the broadcast angle, the collision happens too fast to tell who touched the ball first. Behind the goal, I see the visiting centre-back stretch his leg late — but the ball had already changed direction before that. From the touchline, the man actually involved is a midfielder, not the centre-back named in the report. Three angles, three stories. Only one truth. That is why I rewrite the process rather than the conclusion. A misplaced card can change the course of a whole season. I was once the person who wrote it wrongly. In another sense, referee data resembles a player's running data. Distance covered and sprint counts are packaged as effort metrics. But ineffective running also produces pretty numbers. A player who covers 12 kilometres may simply be chasing a ball he never reaches. The 12-kilometre figure looks impressive until you ask: what was he running for? By the same logic, a referee who shows many cards is not necessarily strict — he may be losing control of the match. That is why I am never satisfied with a single number. A number, detached from its origin and context, is only one piece. Readers deserve the whole picture, including the parts that cannot yet be assembled. The trap of the gap Here is what I learned after years, and it runs against my own instinct: not every blank is an error. There are honest gaps — where an event truly did not happen, where the referee truly did not show a card, where a number does not exist because there was nothing to count. The problem is that the human eye always wants to fill the gap. We hate emptiness because it forces us to admit we do not know. The biggest trap of this trade is the belief that data is always available and always right. Fans see a full statistics table and assume it reflects the match. But a full table can be built from wrong numbers, while a blank table is more honest than any of them. I log every card, every minute of stoppage time. Because a wrong number repeated three times becomes a fact in the end-of-season report. When data contradicts the eye, trust the data — but never forget to check where it came from. VAR is not wrong. The people operating VAR are wrong. And that is exactly where my work begins. What I still keep I still make it a habit to rewind three angles before typing a single line. Sometimes I find the answer. Sometimes I find only a blank, and I learn to leave it blank. In a major tournament season, when millions of people believe the same number at the same moment, the person who writes the final report carries a heavier duty than the referee: not to show the right card, but to record what actually happened.