The Match Without a Ball: When an Analyst Must Learn to Stay Silent

Opening

That night in Manchester, I opened a nine-page analytical dossier about a match that had never been identified. Every section in the file carried the same single line: "insufficient information to assess." No team name, no line-up, no score, not a single minute recorded. Only a label at the top of the document — football — and a large void behind it.

A newcomer to the trade would look at that dossier and feel frustrated. An analysis page must have something to analyse, mustn't it? And so many people fill the void with a story. They pick a familiar match, a familiar club, a familiar star, and retell it in the voice of someone who witnessed everything. That is how an empty analysis becomes a full article — and also how it becomes a lie.

I sat looking at that file for quite a while. Outside the window, Manchester rain fell as always. In me there was something resembling the feeling of watching a ball go into the net while nobody — not even the referee — understood what had just happened. Football has no VAR, only hidden angles waiting to be exposed. The problem was that this time, the hidden angle was not on the pitch. It was in the very way I was being asked to write.

Context

I have worked in this trade for nearly two decades, but only after the 2026 World Cup qualifier between England and Slovakia at Wembley did I truly take seriously the question: what must a football reporter do when there is nothing to report?

In 2026, I was twenty-six, a newly minted field reporter. I mispronounced the name of defender Kyle Walker — as "Wall-ker" — three times in a row, and my colleagues laughed. The editor-in-chief sent a reminder email. That night I opened the recording, watched the plays over and over, just to understand how a referee identifies offside. Not to write better, but to reassure myself that I was not the only one who made mistakes on the pitch.

From then on I wrote differently. I used referee reports, listed every minute of infraction, cross-checked against IFAB laws. I replaced emotional commentary with disciplinary data tables. A year later, when VAR first appeared at the 2026 World Cup, I was a data editor at an English football site. In France versus Australia, Antoine Griezmann's goal was confirmed after the VAR team reviewed Joshua Risdon's challenge. I sat for hours analysing camera angles, calculating foot speed and angle of contact, while colleagues told me I was spending too much time on a decision that took ninety seconds. But I was fascinated by the mechanism: who has the right to request a review, where the intervention threshold sits.

My trade has since been about finding mechanisms. The referee is the only person on the pitch not permitted to be led by emotion. But so is the writer. And I realised that in this trade, the hardest thing is not finding the truth, but admitting when I lack the data to say anything at all.

Those nine empty pages were exactly that test.

Analysis

When an upstream analytical layer extracts no information — no title, no source, no subject, no data point — then professionally, there is exactly one honest conclusion: it cannot be assessed. Analysts call this a "null result," and it is a legitimate outcome. The problem is that null results do not sell. They have no catchy headline, no controversy, no one to blame. And because they do not sell, there is enormous pressure — from the newsroom, from the algorithm, from readers themselves — to transform them into something.

I have spent a good deal of time tracing how that pressure operates. It does not come from an explicit order. It comes from small questions. "Got anything for today?" "Any new angle?" "What are the opponents saying?" None of them asks me to fabricate. But taken together, they form a frame in which an empty article counts as failure, while an article with a story — even a baseless one — counts as a job done.

This is the point I want to examine closely, because it mirrors exactly how a referee's decision gets distorted after the match ends. When the incident happens, only the referee sees the moment. When the match ends, millions watch the replay and each sees something different. No one is lying. But neither does anyone have enough data to state the whole truth. The viewer sees the incident, the referee sees the moment, I see the whole process. And that process is the only thing I am permitted to hold onto.

Take a concrete example. At the 2026 World Cup, the VAR team intervened in dozens of incidents across the tournament. When I analysed each one in the "Anatomy of VAR" series, what I found was not whether referees were right or wrong, but that the intervention threshold was inconsistent. The same level of contact was called a foul sometimes and not others. That is not a question of referee ethics. It is a question of process. And if I wrote "referee X favoured team Y," I would have ignored the data, ignored the process, to chase the mood of the crowd.

The same holds for that empty analysis. If I filled it with a story about some club, I would create something very convincing: numbers, names, arguments. But every number in it would be fabricated. And the most dangerous thing about fabricated writing is that it does not confess itself. It looks exactly like a genuine analysis, because it is built with the very grammar of a genuine analysis.

I remember a time during the 2026 shutdown. The Premier League was suspended and I had no match to report on. The anxiety grew so large that I retreated into data: I sat through all 380 matches of the 2026-20 season, focusing on Liverpool's tactical fouls under Jurgen Klopp. I counted that they fouled an average of 10.2 times per match, mostly in midfield, to stop counter-attacks. I sent the piece to an editor and was rejected, on the grounds that "no one reads when there is no football." I still wrote twenty pages of notes, because I had recognised a real pattern: how Klopp used tactical fouls as a language of spatial control. Two years later, those notes became the foundation of an e-book.

The point is this: those twenty pages might never have existed. Had I chosen that day to write a story just to fill the quota — that Liverpool were declining because of a leaky defence, say — I would have had an article and lost an understanding. I chose the second. And the price was that the article went unpublished.

But that price is cheap. The expensive price is when an analytical platform is filled with conclusions that are empty yet fluent, and readers start believing them. Once trust in data is eroded, then when real data arrives, no one believes it either.

I noticed one detail at a very technical layer of that empty analysis: the fields "entities involved" and "source quality" were defined by relying on the information points — while the information points themselves were empty. In other words, what needed to be extracted depended on what had not been extracted. This is a design flaw, and it mirrors exactly the flaw in a bad VAR system: if the VAR team depends on a camera angle that does not exist, there is no clear signal with which to correct it. In both cases, the problem lies not with the final decision-maker, but with the designer of the input.

There is a basic distinction I always stress to younger colleagues. An analysis can fail in two very different ways: it can fail because the data is insufficient, or it can fail because the writer filled the data with inference. The first is a professional failure — it can be fixed by gathering more. The second is an ethical failure — it cannot be fixed, because it has introduced something that does not exist, and once introduced, it is very hard to remove. In my trade, people often confuse the two. They think a fluent article is a successful one, and an empty article a failed one. In reality it is the reverse: a fluent but empty article is a failure, while an article brave enough to be empty is honest.

At a deeper level, every football controversy turns on a process question: who has the right to decide, at what threshold, and on what data? When I analyse a contentious incident, I do not ask "was the referee right or wrong." I ask: was the referee permitted to review it? Did the VAR team have enough camera angles? Is the intervention threshold here the same as in a previous incident in the same competition? Only when I can answer those questions do I have a basis to say anything. If I cannot answer them, I have no basis. And with no basis, I must stay silent.

This is a discipline I learned from referees themselves — although I have never held a whistle. A good referee is not one who is always right. A good referee is one who knows he is not permitted to guess. If he did not see it, he does not blow. If he is not sure, he does not give it. The same principle applies to the writer: if there is no data, I draw no conclusion. And if I must write, I write exactly what I see — even when what I see is a void.

Every foul is a question about intent; data only gives us answers about consequence. I use this line often in pieces on disciplinary play, and it holds for the fabrication trap too. When a writer fills a void with a story, he is answering a question about consequence — why the team lost, why the referee erred — without data about intent or context. He pretends to understand what he cannot observe. And that is something I am not permitted to do, because once I do it, I keep doing it.

The Counter-Intuitive Angle

Here I want to say something not everyone in the trade wants to hear: honesty in analysis is not a virtue, it is a competitive disadvantage.

Look at how content operates online. An article saying "I don't know because I have no data" gets low engagement. An article saying "this is exactly why this club failed" spreads. Both may be equally accurate in informational terms — in fact the second is usually less accurate — but the second wins on every metric the platform measures. That is why the fabrication trap is not an individual mistake; it is a structural consequence.

What is even more counter-intuitive is this: readers do not want to be deceived. They merely want a tidy answer. And the gap between those two desires is filled by the writer — by people like me. The responsibility does not lie with the algorithm. The algorithm only reflects people. The responsibility lies in whether a writer has the courage to say "insufficient data," even when that sentence earns him nothing.

In the Euro 2026 final, I was assigned to analyse the penalty shootout between Italy and England. Three young English players — Bukayo Saka, Jadon Sancho, Marcus Rashford — missed in succession. The media was flooded with psychological stories: they were too young, they lacked nerve, they were under pressure. Those are easy stories to write. But when I dug into the mechanism, I saw something else. Goalkeeper Gianluigi Donnarumma chose the right direction on the majority of attempts, thanks to studying opponents' habits. The distance from the penalty spot to the goal is eleven metres, the average ball flight around 0.3 seconds. In that interval, the goalkeeper can rely only on prior data and the micro-expression of the standing foot.

I wrote three thousand words on that mechanism, citing data from fourteen recent shootouts. The editor cut it to five hundred words as "too specialised." The psychological story was kept intact. I do not resent anyone. I merely record a fact: the easily understood story beats the correct story, and any writer who chooses the correct one must accept living on the margins.

This brings me back to the empty dossier. If I wanted, I could turn it into a very smooth analysis. I could pick a big match, a big club, a controversy hot enough to click. But in doing so, I would betray the very trade I have pursued for nineteen years. And I would become exactly what I criticise: a commentator who says everything about everything, never noticing that he is staring into a void.

There is a paradox I keep turning over. The most careful readers — those who genuinely want to understand the mechanism of a decision — are the least served. They need detail, context, precedent. But the market does not measure that demand, because it generates no engagement. So writers tend to write for the skimming reader. And when writing for the skimming reader, story replaces data — because story skims faster. This is not a football-only problem. But in football it is more dangerous, because what is being replaced is not merely numbers, but fairness in judging the people who make decisions on the pitch.

Closing

A null result is not a sign of weakness. It is a sign of a process that has not fully run, and a serious writer must be able to tell the two apart.

If there is one lesson I want to keep after all of this, it is this: the value of an analysis lies not in how much it says, but in whether it dares to say "I don't know." Football will keep giving us controversies, wrong decisions, compelling stories. But readers deserve a writer willing to stand before a blank page and let it stay blank. The laws never stand outside the match; they are the second match running in parallel. And that second match is sometimes won by saying nothing at all.