The Empty Report and the Art of Saying "Not Enough Data"

The Empty Report and the Art of Saying "Not Enough Data"

11:47 p.m., a Tuesday night in the middle of the transfer window. I open the report that just landed in my inbox. It follows the naming convention, it has section headers, it has tables, it even has ruled rows waiting to be filled. The structure is as tidy as an engineering blueprint. Then I scroll. Every cell is empty. No team name. No driver name. No lap count, no transfer fee, no timestamp. Just one line repeated across every section: not enough information to assess.

In a normal newsroom, that is a disaster. An editor will message back: "Is there anything we can run?". A young writer will type a few safe sentences, add a few plausible guesses, and the piece goes live before breakfast. But that empty file is telling a truer story than any of the number-filled bulletins published that week.

I have sat at more than one end of this information chain. From the reporter's desk, where I learned to call a team's press office twice before writing a line. To the data specialist's seat, where I hand-coded every single contest. And now to the strategy analyst's chair, where I have to read a number the way I read a contract — hunting for hidden clauses, not just admiring the signature. Those three role changes taught me the same thing: most of this job is saying "I don't know yet", and only a small slice of it is saying "I know".

Seen from that angle, the empty file is an honest piece of work.

Context: a summer built on rumour

The transfer window is the season in which sports convinces itself that silence equals falling behind. Across roughly six weeks, the volume of rumour grows exponentially while the volume of verifiable events stays almost flat. A club can be linked with seventeen names while genuinely negotiating two. That gap is not an error — it is a product. It is manufactured on purpose, because ambiguity sells better than clarity.

In the sport I have followed longest, the mechanism is more sophisticated. On the racing side, a driver-market rumour travels with a specific chain of interests: a manager needs leverage on a contract, a team needs to cool a sponsor's expectations, a manufacturer needs to inflate the value of a reserve driver. When an outlet reports "team X is eyeing driver Y", the real transaction may be nothing more than a wink between three parties. The reader is not in that room. Worse, the reader is usually not told that they are not in that room.

What readers actually need is very different from what they are served. They do not need another rumour. They are not hungry for another name. What they lack is a filter: a way to rank news by evidence rather than by volume. But a filter does not generate clicks. And in the economy of clicks, silence is treated as failure.

That is why I kept the empty file. It is a specimen. It proves that a system can receive nothing and still process it correctly — by stating plainly that it received nothing.

The Core: five layers of verification and the cost of a dropped letter

I write slowly. Long-time readers often note that, sometimes as a mild complaint. What they cannot see is that behind every number sit five verification layers. It began as a professional reflex after one mistake, and grew into a hard procedure.

The first layer is source matching. Where did this number come from? A press conference, an official supplier's dataset, another article, or a second-hand account? The quality of the source decides the value of everything downstream. An accurate but anonymous figure is worth less than a slightly off figure that can be traced.

The second layer is reviewing the tape. For me, this is the heaviest and most transparent layer. A stat sheet can be tidy, but video cannot hide context. A play logged as successful in the data can be a badly read play in reality, saved only by a covering teammate.

The third layer is counting twice. Here I am especially wary of figures too good to believe. When an indicator appears exactly as I want it to, that is when I must distrust it most.

The fourth layer is asking an expert. Not for approval, but to see whether my argument has a hole. The best person to ask is usually the one who does not care whether I am right.

The fifth layer is a thirty-minute pause before publishing. That sounds absurd for a Twitter thread that needs speed. But those thirty minutes have saved me more often than any data tool.

The mistake named Kanté

I retell my first failure because it is the anchor of everything I do now. In 2026, a local sports site in Liverpool asked me to write a prediction piece for the France–Croatia final. My piece had two errors. I misspelled a player's name, dropping a character, and I recorded three tackles when the real figure was four. The match ended 4-2, and the site was mocked by readers for a week.

I deleted the piece. Then I re-reviewed the tournament data, built the five-layer process, and set one rule: never publish a statistic that has not cleared all five layers. My mistake is named Kanté, and I do not want to forget it. I keep it the way one keeps a nail in a frame, to remember that a writer's biggest error is not being wrong — it is staying wrong while continuing to present as if nothing happened.

The lesson from 387 contests

A year earlier, at eighteen, I wrote a blog analysing U23 Liverpool's pressing model across twelve youth-league matches. I hand-coded 387 contests, cross-checking frame by frame. The result showed the right-back often drifting inside, and when he did, the team's possession share rose from roughly 52% to 58%. The piece predicted he would become a creative spearhead. Many dismissed me as "a kid in the computer room".

Six months later, that player recorded twelve assists in the national league, nearly double the other full-backs in his position. I do not retell this to boast about a call. I retell it to show that data can run ahead of prejudice — but only when the writer is willing to spend the time counting. The reward for that patience is not being right. The reward is having a system trustworthy enough to check yourself against.

When the stands emptied and the advantage question flipped

In 2026, when stadiums closed during the pandemic, I dived into a home-advantage dataset. For decades, analysts had assumed home advantage delivered a fixed percentage edge, a figure that was nearly constant. The no-fan season put that assumption into a laboratory.

The results showed home advantage falling sharply once the crowd disappeared — without vanishing entirely. Players change, the stands change, but the advantage equation stays intact. The residual edge came from things unrelated to chanting: travel distance, routine, a familiar pitch, and most importantly, the power to set the schedule. That was when I understood that home advantage had always been two stories folded into one: the crowd and the structure. Only when the crowd left did the two separate, and only then could we see which part truly belonged to the seat, and which part to the noise.

My entire writing career orbits that experience: the biggest shifts in sport often create no new data at all. They simply expose old data that had been hidden.

How to read a transfer rumour

If I had to pack eleven years of industry observation into one procedure, I would split it into four steps. Step one is source ranking. Step two is following the money. Step three is reading contract structure. Step four is tracking the agent's moves.

During the transfer window, noise always drowns the signal. A normal reader faces dozens of headlines at once, with no tool to tell which are credible. A writer can hand them that tool. Before trusting a transfer story, I ask four questions: Who reported it first? What do they gain if it spreads? Is there a trace of real money — fee, wages, clauses — or only desire? And does a release clause actually exist the way the story assumes?

The last question is the most overlooked. Fans tend to believe a transfer is simple addition: team A plus player B equals a stronger team. My experience says otherwise. A transfer is not addition, it is prediction. A contract is a hypothesis about the future, signed before the future happens. And every hypothesis must be tested by the season itself, not by the headline.

One contract type I watch closely is the loan with an obligation to buy. In accounting terms, it lets a small club push spending into next season and polish its current balance sheet. Structurally, though, it turns the small club into a transit station for semi-finished goods destined for a big club. They develop a player for two years, hand him over exactly when his value peaks, and receive a fee too small to reinvest proportionally. The flow of benefit runs one way, while the balance sheet looks balanced.

The way I express this view is simple: I choose the example. I do not declare the mechanism unjust. I take one specific case, set it beside a control case, and let the data speak. Readers are sharp enough to draw their own conclusion, and a conclusion they draw themselves lasts longer than one I hand them.

The counterintuitive angle: silence is a competitive edge

This is the least-discussed part of sports writing. In an environment that rewards speed, the person who says "I don't have enough data" is treated as inferior. Seen from the reader's side, the opposite is true. The strategy machine does not run on emotion; it runs on information. A system that can say "not enough data" is a more trustworthy system, because it can distinguish what it knows from what it wants.

The paradox is that the clearest pieces about a writer's own limits are often the most accurate about the world. When an analyst admits a model does not apply to a given case, they are protecting readers from an illusion of precision. The information market rewards that illusion, but readers pay for it in steadily eroded trust.

I once watched an editor demand that an empty table be filled with "reasonable estimates". That is the moment this profession is most tempted to betray itself. Reasonable estimates, multiplied across hundreds of pieces, become a sediment layer of numbers nobody can verify but everyone cites. That sediment is no different from the prejudices we imagine we have outgrown: it looks like data but is, in nature, belief.

An analytical framework only matures after reality refutes it. I believe this enough to publish a piece whose most important part is a list of things I cannot assert. An honest sports writer is not one who is always right. An honest sports writer updates their model when reality supplies counter-evidence — and makes that update public.

At the system level, the empty file also teaches something about VAR and refereeing. For years I tracked contentious decisions and noticed that most fan anger comes not from the decision itself but from the absence of explanation. Referees lack a mechanism for on-pitch dialogue, leaving spectators as the forgotten party. Transparency in modern sport is usually a slogan until it is pushed to its limit. And that limit appears exactly when fans need it most: at the moment a decision changes the outcome.

The same logic applies to data. Tools do not create trust by themselves. Trust comes from people seeing the whole process by which a conclusion forms — including the places where no conclusion can form.

Why I write slowly, and why that is right

I have a habit colleagues like to tease: sometimes I spend an entire week on one small stat table. I promise a publication date, then delay, then delay again, because I want to adjust every number until it can withstand every question I can think of. Readers see the slowness. What they do not see is the price of speed.

I have watched a wrong statistic spread. It starts in one piece, gets cited in another, becomes a background assumption for a debate, and eventually nobody remembers where it came from. When the truth is corrected, it is usually smaller than the echo of the error, and always arrives later. In this profession, writing slowly is a form of collective self-defence, not personal perfectionism.

I learned this across three role changes. As a reporter, I learned that a good source can hide a motive. As a data specialist, I learned that an accurate number can be placed in the wrong context and lie without any arithmetic error. As a strategy analyst, I learned that what happened before the number is often more important than the number, and what the number leaves unsaid is often the most worth saying.

Those three lessons merge into one method: split the problem into five layers and clear none of them by skipping another. Match the source. Review the tape. Count twice. Ask someone with no stake. And wait. It is not fast. It is only trustworthy.

The equation has changed, and the old formula no longer holds

There is a line I have written again and again, because it holds in almost every period I have observed: Do not ask who plays well; ask which side the system is standing on. It is not a personal accusation. It is a way of seeing.

In every era of a sport, the system stands on the side of a certain group: those who control the calendar, those who hold the rules, those who set the flow of money. When the rules change, the beneficiaries change. Teams that succeeded under the old rulebook lose their edge under the new one — not because they got worse, but because the game changed the question.

This is why small teams often get a brief window right after a major rule change. They are not stronger; they are just faster to adapt. That window does not last, because big teams have more resources to relearn the question. The opportunity does not disappear — it narrows, and demands a higher degree of precision.

That is why I do not write about "luck". Luck, in my analysis, is not an explanation but the residual of probability: the part that happens outside any reasonable model. Blaming outcomes on luck is a way to dodge model-building. And dodging model-building is dodging the real work.

What remains after the empty file

Looking back at that Tuesday night, I understand why I did not panic at the empty cells. A system that received nothing and said so is doing exactly what my profession needs most: distinguishing "nothing there" from "not yet looked". Confusing those two states is the source of most misinformation in modern sport.

In the transfer window, noise will keep outgrowing signal. Hundreds of names will be called, thousands of fees quoted, and only a small fraction will exist when the window shuts. Readers do not need another voice joining the noisy race. They need a voice standing outside it, holding a ruler, and measuring.

I still keep the five-layer process. I still wait thirty minutes before publishing. I still keep Kanté in memory like a nail in a frame. And I still keep the empty analyses, because sometimes the most honest thing a writer can publish is a blank page — along with a proper explanation of why it is blank.

The question I leave readers is not which team will win the title. It is this: the last time you trusted a sports number, did you know how many verification layers it passed through? And if you never knew — perhaps it is time to demand that from the writers you read.

Method note

The illustrative figures in this piece reflect the author's personal workflow across three periods: the U23 Liverpool analysis blog (2026), the World Cup final prediction piece (2026), and the no-fan-season home-advantage dataset (2026). All conclusions about transfer-market mechanisms, refereeing transparency, and home advantage are presented as conditional hypotheses, open to revision when reality supplies new evidence. This document is for sports-information reference only and does not constitute any betting advice. Sporting outcomes are highly uncertain; read any prediction rationally and only after a valid data chain has been verified.