When the Data Table Comes Back Empty: A Sportswriter Learns to Slow the Story Down

On the night of July 10, 2026, in Saint Petersburg, I sat in the press room about forty metres from the pitch and wrote France's possession share as 61 percent when the official tracking sheet said 49. In the same bulletin I called France's left-back "Hernán" three times; his name is Lucas Hernandez. The piece went live at dawn, right after Samuel Umtiti's header in the 51st minute — the only goal of that semi-final. Seven hours later my editor called me up, put the printout in front of me, said nothing, circled two places in pencil and pushed the sheet back across the desk.

I went back to my seat, reopened the full ninety minutes, and did the thing I still regard as the turning point of my career: I spent an entire month rewatching the footage, logging every minute, every pass, every tackle into one notebook. From then on I set a rule with no exceptions — every figure must be verified through two independent sources before it goes into a sentence. The rule sounds simple on paper. It only becomes expensive when the story is racing the clock and everyone around you already has a draft that looks polished.

Sports analysis has moved from the notebook to the data pipeline, and that very speed has produced a new category of risk: the risk of an empty report being filled with speculation that sounds entirely reasonable. A typical newsroom now receives automated stat tables, positional heat maps, pressing metrics, distance covered, and machine-written summaries. When the pipeline works, everything is smooth. When it returns an empty file — blank title, blank source, blank list of facts — the writer faces two options: stop and say there is not enough information, or fill the gap with something plausible.

There is a technical detail I learned across years of working with data teams, and it is worth knowing for anyone who reads sports: an empty extraction does not mean "nothing happened". It means the pipeline broke somewhere between the source and the reader. The two common causes demand completely different remedies. The first sits at the retrieval stage — a dead link, a block, or a javascript shell with no real content. The second sits at the extraction stage — the text arrived, but the parser returned an empty object because of a field-mapping error. Re-running the same process in the first case will produce the same empty result once more. That is why the first question in every production meeting I run is always: has the raw source actually arrived.

In 2026, when every competition was suspended and I was twenty-six with an empty work calendar, I threw myself into a short documentary series about great teams that had been forgotten. The Liverpool 2026-20 episode was the clearest lesson in why data has to sit inside a structure. They took 99 points from 38 matches, scored 85, conceded 33. Stop there and the viewer never understands why that side was different. Their expected-goals figure ranged from 1.2 to 3.1 per match — a very wide band, showing they did not play one fixed way. Average distance covered was 112 km per match. Pressing duration after losing the ball was 7.2 seconds, about 1.5 seconds faster than the league average. Put those three together and they describe a linear system: lose the ball, close down within seven seconds, win it back in the opponent's half. In a year without football, I found the real pulse of this sport — and that pulse lived in the columns, not in the league table.

In the summer of 2026, assigned tactical analysis at the Euros, I chose Italy. In the final against England, Italy registered 61 touches in the opponent's box; England had 22. Italy's total passes were 847 at 92 percent accuracy. They made 25 deliberate slips to stretch the defensive line. Set those three side by side and the picture is unmistakable: Italy did not attack through explosions, they attacked by continuously shifting the opponent's defensive structure until a gap about a metre and a half wide appeared. That is the kind of conclusion you only reach when the writer is willing to place the columns next to each other rather than reading each one alone.

Then came 2026-2026, with the Euros and the Club World Cup back to back, and I wrote the "Eight Tactical Models" series, sorting teams into eight rigid frames. I labelled Manchester City "absolute control". The label was wrong, and wrong in a systematic way. I failed to anticipate that they would happily switch to fast counter-attacks through Erling Haaland, abandoning the control rhythm entirely. Readers pushed back bluntly: too mechanical, the hybrid variants were missing. The desk asked for a rewrite. I rebuilt the whole series on more open lines, adding a section on hybrid models built from each player's average position and minute-by-minute tracking data.

Here is where I part company with the crowd. Most sports analysis fails because data is used to confirm a story already written in advance, not because data is missing. xG is the clearest case. Expected goals has been abused to the point where it is asked to explain things it cannot explain: a coach's substitution decision, a player's true form in a specific week, or a referee's threshold in a single challenge. xG measures chance quality; it does not measure decision quality.

The same holds for taxonomies. A framework only earns its keep when it is tested through learning — when the writer accepts that one team can wear several shapes at different points in a match. After the Manchester City lesson I changed the rule: before labelling a team, you must be able to answer why they chose that shape in the seventieth minute. If you cannot answer, you do not label. Data only gives us the door, but the story is the one who turns the key.

In this trade, "not enough information to conclude" is usually read as weakness. Yet an honest report about emptiness is worth more than a complete report that is wrong. Readers do not need more noise; they need to know which parts are real data and which are blank space. When the live feed stumbles, I learn to slow the storytelling down — and that slow stretch is usually where the information nobody had time to record actually sits. Viewers remember the goal; filmmakers remember the silence before the goal.

If there is one thing sports readers should do for themselves next season, it is learn to spot the blank space inside the story they are reading. A good piece does not cover the blank space. It tells you where the gap is, why the writer could not fill it, and what would be needed to close it — a name, a publication date, a second independent source. That discipline does not make the writing slower. It makes it correct.