When the Data File Comes Back Empty: The Discipline of Football Analysis

On a Saturday night I opened my match-tracking file as I do every weekend. Forty event rows, fourteen metric columns, one positional data block I had been waiting three hours for since the final whistle. The file came back empty. Not a single row. No error message, just dashes sitting quietly in every cell, evenly spaced like a form nobody had filled in.

I stayed another twenty minutes, reopened the source link, checked every data layer. Nothing was broken on my end. The break was upstream: a blocked page, a script that failed to load, a record lost somewhere inside the pipeline. In this trade we call it an extraction failure. It is not loud. It is quiet, and it is more dangerous than any other fault, because what it leaves behind looks exactly like a fact: a blank page.

And that blank page, if I am not careful, becomes an article.

Over the past decade, football writing has shifted its axis. Writers no longer wait for the printing press; we wait for data. Some evenings the job is genuinely just opening seventeen browser tabs, cross-checking minutes played against the wage bill, comparing the average positions of two full-backs, then asking why the home side is shooting less than last season despite controlling more of the ball.

That trade has a built-in weakness few people mention: it depends entirely on a pipeline the reader never sees. When the pipeline runs, the writer is praised as sharp. When it snaps, the writer faces two choices: state plainly that he has nothing in hand, or fill the gap with sentences that sound perfectly reasonable.

The second choice is always easier. It is also always the beginning of something worse than simply being wrong.

In recent years I have run into a particular kind of report that surfaces whenever a large story leaks out half-formed. It looks complete: section headings, tables, a conclusions page, a risk warning. But read cell by cell and most of them say "insufficient information". No team name, no player name, no date, no source. All that survives is a domain label: football.

Read quickly, such a report is understood to mean the story was not worth telling. That is the most serious mistake a reader can make, and the mistake a writer can unknowingly plant in their head.

An empty data file does not mean the event did not happen. It means the link to the event is broken. Those are worlds apart. The first is a conclusion. The second is a technical fault. Merging them is the crudest act in this profession, and also the most common.

I once wrote a piece nobody read. Three years later it became my lesson plan. That 2026 article analysed an AFC Champions League quarter-final between two Chinese clubs, showing how pushing both full-backs high in a back four tore open the defensive flank and led to a heavy first-leg defeat. Three days after publication it had seven views. A month later, when the same club won using a back three, forums began resharing it, and it reached twelve thousand reads.

I tell that story not to boast. I tell it for what it taught me: the value of a piece lies not in whether it is right on day one, but in whether it survives being checked again. A wrong conclusion can be corrected. A conclusion built on data that never existed cannot, because there is nothing to correct.

The three cases below all turn on one question: does the paper trail exist?

The first comes from the books. In February 2026 the Premier League published a list of financial rule charges against a Manchester club, spanning multiple seasons. In November of that year a Merseyside club was docked ten points for breaching permitted losses, later reduced to six on appeal. In March 2026 another club was docked four points.

What matters in all three is not the size of the sanction. What matters is how they were proven. None rested on a pundit's instinct or an expected-goals metric. All rested on ledgers: sponsorship contracts, payroll, payment receipts, internal correspondence. When the file is complete, the story stands on its own. When the file is sealed, the story vanishes from the front pages, and supporters are left with a vague sense that something is wrong and nobody can say what.

That is the false-null at its largest scale. People read nothing, and conclude there was nothing to read.

The next case happened on grass, and I was there in the literal sense. In 2026, as European leagues returned after suspension, football was played in front of empty stands. With a group of students I analysed hundreds of German top-flight matches, comparing home points rates before and after the gates closed.

The result made us re-check three times: home advantage almost evaporated. Home teams lost a substantial share of the points they normally collect with a crowd behind them. Our video series passed several hundred thousand views within two months.

If I had to name the real lesson of that project, it lies elsewhere. It lies in how close we came to a wrong conclusion, purely because one data column was missing in nearly a fifth of matches. Had we filled the blanks with averages and published, we would have released a clean, tidy, wrong result. In 2026 everything collapsed. I stood up and rebuilt from the rubble, and the rubble taught me that missing data may not be filled with guessed data.

The last case belongs to the transfer market, where I have worked most in recent years. It is the environment where empty files appear most often, and where people are easiest to fool.

A typical deal is told through three facts: fee, wage, contract length. Those three are rarely true and even more rarely disclosed in full. Most leaked information comes from the agent's side, meaning from the party with a direct interest in pushing the price up. When you have one source, and that source is paid to talk, you do not have data. You have an advertisement.

I read a transfer not through the fee but through where the player will stand in the system. My first question is never how good he is. It is whose place he takes, and where the displaced man goes. Answer those two and you have grounds to discuss price. Fail, and every figure is just noise.

Before the 2026 World Cup I published a piece arguing that the Balkan side were no flash in the pan, citing roughly 86 percent passing accuracy in qualifying and squad depth under captain Luka Modrić. I was mocked. In the semi-final, with the opponent ahead, I held the line. Mario Mandžukić's 109th-minute goal sent Croatia to the final, and I was right. But I also learned that being right does not license disrespect toward the reader.

Here I have to be blunt about a habit spreading through the trade: using expected goals as a crutch for every argument. That metric measures chance quality; it does not measure refereeing decisions, the true form of a player stuck in the wrong system, and certainly not whether a centre-back was out of position from the twelfth minute. As a former player, I do not need to watch tape to know who is running into the wrong place. I still open the tape, because an opinion with nothing behind it is only a slightly better opinion.

When the underlying data is missing, expected goals is worse than an opinion. It looks scientific, it carries a unit of measurement, and it is anchored to nothing at all.

Now the part I expect many will dislike.

The instinct of a football writer facing an information gap is to fill it with context. We call that experience, a nose for the game, the ability to read a match. I once believed it. I still believe experience has real value. The lesson from the tunnel: silence before kick-off says more than any press conference.

But there is a line experience may not cross: it may not substitute for missing data. It may only annotate the data that exists.

The reason is simple. When you fill a blank cell with judgement, you can no longer check yourself. Nobody knows what is fact and what is your inference, including you, a few months later. A blank file keeps its diagnostic value: it says something in the process broke. A file filled with guesses loses that value entirely. You have a table that looks fine and no remaining clue whether it is fine because it is right or fine because it was painted over.

The reverse also holds. Sometimes the silence is the information. A deal that leaves no paperwork, a player absent from any medical record, a club that misses its financial filing deadline. Those gaps are usually not accidents. They are the fingerprints of a way of working.

My job is to point out where the gap is, and to say clearly that it is there.

A serious analytical setup must separate two states that look identical from outside: no information, and no event. The first is a system fault. The second is a finding. Merging them is blinding yourself.

There is one more consequence, less related to the pitch. When an empty record enters an aggregation system, it does not disappear. It sits there, waiting to be read by a machine or another person, and it spreads. An empty record treated as a valid result breeds an empty conclusion, then an empty article, then an empty decision. The process is perfectly silent. In a chaotic season, what an analyst needs most is the clarity of an outsider, and that clarity begins with admitting he is holding nothing at all.

If you write about football, this is the minimum checklist I use before typing a word. A headline, a publication date, a publishing outlet, at least five facts traceable to a source sentence, at least one club and one named person. Miss any cell, and I do not write.

Not out of pride. But because I have been on the other side of a blank file, and I know how easily it becomes an article.

The 2026 World Cup taught me one thing: hesitation is what ruins every plan. But waiting for data is a different act from hesitating. That is discipline. What must be done immediately, and decisively, is to say that you have no basis for a conclusion, and to say it before the blank page gets filled in.