When Every Data Cell Comes Back Empty: The Line Between Analysis and Fabrication

Last Tuesday night in Beijing, I sat in front of two screens with a 94-minute match and a blank spreadsheet. The footage ran normally: the opening whistle, the stands rolling in waves, the touchline glowing white in the sun. But the tracking file I had waited two hours for came back with no rows, no columns, not a single event. Ninety minutes of football, and the page stayed white.

A football story never begins at the first minute. It begins where someone hands you an empty skeleton and waits for you to fill it with flesh.

Nineteen years ago, when I was still reading sports bulletins for a local radio station, I learned something that runs against the instinct of this trade: a commentator's job is knowing when to stay silent. Knowing you are holding nothing, and saying exactly that.

CONTEXT: A TWO-STAGE PIPELINE AND AN EMPTY INPUT

What I received that night was not a match. It was the output of the first stage of a two-layer analytical pipeline. The lower layer strips a source down: title, source, publication date, one-sentence summary, author stance, article purpose, the list of information points, the entities named, time sensitivity, and a source-quality grade. The upper layer builds eight deep analytical dimensions on that foundation: tactics and technique; club finance and the transfer market; results and the public-opinion cycle; league landscape and team positioning; rules and governance compliance; the dressing room and the coaching staff; the risk profile; industry transmission; and media narrative.

That night, the lower layer returned exactly one usable field: the domain label, two words, 'football'. No title. No source. Not one information point. Not one named entity, not even the competition.

If I had sat down and written on from that foundation, every sentence about pressing intensity, expected goals, wage structure, sell-on clauses, or pressure on the manager's chair would have been mine alone to invent. That is a novelist's work. Not an analyst's.

SIX SPINE LINES

Put those eight dimensions on the table and ask each one what it needs to live.

The tactical dimension needs a starting shape, a pressing scheme, a passing share, a measure of chance quality. The financial dimension needs revenue, wage bill, net debt, a deal with a concrete price. The results dimension needs a table, a run of form, process data deep enough to separate luck from strength. The landscape dimension needs to know which tier the team sits in and who it is measured against. The rules dimension needs a governing body and an alleged breach. The dressing-room dimension needs names. The risk dimension needs an event to attach risk to.

An analytical model cannot measure what it has no data to measure. No event, no names, no dates. Eight dimensions, eight null returns.

The minimum checklist to re-run has only six lines, and all six were absent: a title with a publication date; at least one information point with its own source; clearly identified entities; a specific event type; a source-quality grade; and a time-sensitivity assessment. Those six lines are the spine of any serious analysis. Without them, a writer has two options: stop, or invent.

In the report's risk matrix, every cell is empty except one, flagged at medium: process risk. The pipeline ran on an empty input. And if any downstream system silently auto-fills those blank cells, the result will be misinformation carefully packaged, with a headline, with numbers, with a professional format.

An empty result is not a low-risk finding. The two differ the way an empty stadium differs from a match nobody watched. A missed risk is also different from a risk that was never tested. If that report flows downstream without a label, the end reader will understand 'no risk detected' instead of 'never analysed'. The distance between those two sentences is the distance between a sports press with brakes and a sports press with only an accelerator.

I count seconds the Japanese way – not counting down, but counting what remains. What remained after that night was an old lesson, and this time it came from the very machine I trust. It reminded me of how I have worked for eight years: watching the footage at least twice, cross-checking player names against three sources, and never writing a single figure I cannot trace back to where it came from.

On 28 June 2026, in Rostov-on-Don, I sat in the press tribune and watched Japan lead Belgium by two goals, then lose 2-3. The third goal came from Japan's own corner: Thibaut Courtois caught the ball, released it quickly to Kevin De Bruyne, De Bruyne drove through midfield, Romelu Lukaku let it run with a dummy, and Nacer Chadli finished. Fourteen seconds. I have retold that move hundreds of times and never once needed to invent a detail. One true event is always stronger than ten imagined ones.

Every contract is a farewell written in advance. With transfer data, the same holds on another floor: every fee reported before a signature is a promise written down so it can later be withdrawn in silence. I have seen a transfer-fee column filled with an estimate, then watched that estimate become fact in a presenter's mouth, then become the basis for a financial comparison. Three steps, and not one of them had a source.

THE PARADOX: THIS INDUSTRY DOES NOT LACK DATA

The irony sits somewhere else entirely. Football analysis today does not lack data. It lacks the time to check data. Every match generates thousands of events, hundreds of metrics, dozens of forecasting models, and the editor has a few hours before publication.

In that environment, a blank table is more frightening than a wrong one. A wrong table still gives you something to say. A blank table gives nobody anything. So the pressure of the system always leans toward filling it in – with anything, as long as the gap is covered.

And here is the point I see missed most often: what made that night's report valuable was that it said plainly it had nothing to analyse. A machine that can return the word 'no' is a machine with brakes. A machine that always returns a conclusion has no brakes at all.

On the pitch, we are used to matches like this. A team wins 2-0 without creating a single clear chance, and the whole stand goes home feeling they watched a convincing performance. The result hides the void beneath it. My empty spreadsheet that Tuesday was the inverse image: a match with no result to read, and therefore nothing to hide.

An empty stadium, and yet I could still hear the applause of the people at home. Sometimes that applause is only your own, reassuring you that the job is done, that the blank page was somebody else's fault.

WHAT I CARRY OUT OF IT

I will not call that Tuesday a technical glitch to be wiped from memory. It was the first test this machine passed in the most honest way available: it stopped instead of performing.

The question I carried out of that night was not for the machine. It was for the person sitting in front of the screen, hands on the keyboard, knowing full well there is nothing in them. Next time, when every data cell comes back empty, will I choose to stop – or choose to fill the page?