The Empty Code Table: Verification Discipline in Football Analysis

The sheet had a title. It had columns. It had row numbers running from 01 to 47. It had a source note in the bottom corner. The body was empty: not a single situation coded, not a single arrow showing where the ball went.

I received that document on a June morning, while preparing a series for the mid-season transfer window. The analytical frame was intact, in the four layers I still use: data, space, decision, person. Correct formatting. Correct field order. The classification label clearly named football. Every cell of content was blank.

A newcomer to the trade might fill that space with a few smooth sentences. I sat still, read it a second time, then a third.

The hardest part of analysis is not reaching a conclusion. It is recognising when you do not yet have the grounds to reach one.

Where the break occurs

A professional football analysis pipeline runs through four stages: collection, extraction, verification, interpretation. The first pulls raw data, including GPS movement metrics, passing maps and event logs. The second turns them into structured information fields. The third cross-checks between sources. Only the fourth turns them into prose.

The document I received that morning had passed the first two stages, but returned empty. The frame survived; the interior was gone. Engineers call this a pipeline fault: data drops out at the joint between two systems, and what remains is a skeleton.

For a writer, this is the hardest trap to spot. A wholly blank document is obviously blank. A document with a headline, with section headings, with an industry label attached looks very much like a real document. The shell is handsome enough to deceive reader and writer alike.

Push that document into an automated scoring pipeline and the system will not flag an error. It will score. It will rank. It may generate fluent copy in the voice of an expert, backed by not one fragment of data.

The code table remembers who made it

In 2026, when global football stopped for the pandemic, I spent six months re-watching footage of 200 European matches from 2026 to 2026. The result was the 47-Situation Code Table. Code 23 is a counter-attack after losing the ball in the opponent's final third. Code 35 is offside-trap pressing in midfield. Each code is a story that has been given a name.

I re-watched 200 matches just to find one moment nobody saw.

What I did not expect was that the code table would react to the emptiness itself. Opening the blank document again, my eye read each empty row in order from 01 to 47, and behind each row an image still surfaced. The code table does not need to remember; it remembers the person who made it. It also remembers the person who left it blank.

Three checks and the price of the third

On 22 November 2026, Saudi Arabia beat Argentina 2-1. On the first viewing I concluded Argentina had collapsed mentally. On the second, I began to doubt myself. On the third, I counted nine occasions on which Argentina fell into the offside trap, with the Saudi back line pushing up to sit only nine metres from the halfway line. Saleh Al-Shehri's 48th-minute equaliser and Salem Al-Dawsari's 53rd-minute winner came from a defence that knew exactly where to stand.

The conclusion flipped entirely: a problem of distance, not a burst of inspiration.

Had I watched once and written immediately, readers would have received an explanation that was wrong but sounded entirely reasonable. That is the most common error in this trade: wrong without anyone noticing, because it is wrapped in confident language.

Before buying a player, I let him run three matches, and only then do I trust the offer.

In a transfer window, a data gap is more dangerous still. When information about a deal is missing, people fill it with rumour. The real story sits in contract structure: transfer fee, wages, release clause, sell-on percentage. In the V.League, a single release clause can decide the value of an entire domestic deal, while most social-media rumour circles only around wages. Fans drown in rumours; coaching staffs work with the wage bill.

Back in December 2026 I turned down an offer to analyse Sanna Khanh Hoa against Hanoi FC in V.League round 12, because I believed GPS data was a luxury that could not replace the naked eye. When the movement dataset for 22 players arrived, I was startled: Hanoi FC held 68 per cent of possession but managed only four shots on target, while Khanh Hoa won through 18 high presses funnelled at the opponent's left-back.

Possession share, separated from spatial context, becomes undeserved praise. A low PPDA, the number of passes allowed per defensive action, signals aggressive pressing, but only if you know which zone the pressing happened in. Expected goals measures the quality of a chance, not the nerve of the finisher. That is why I never cite a single metric on its own.

The blind spot: silence read as conclusion

There is a habit in sports writing: when there are no numbers, writers reach for adjectives. The match exploded. The defence was solid. The manager is conservative. Adjectives need no verification, so they are always available. And they always flow.

Silence in data does not mean nothing happened. It means nobody has measured yet. An empty analysis table does not say the team has no problem. It says the analyst has not yet seen the problem. Those are two very different statements, and confusing them is the source of most hasty conclusions in Vietnamese football coverage.

The life cycle of a media story runs through four phases: emergence, acceleration, peak, reversal. Most sports content is written in the second and third, when heat is highest and foundations are thinnest. If a writer does not build a verification gate before publishing, the reversal will be done by someone else, usually by dismissing the whole thing.

Data is a story told in numbers, but I still hear the runner.

A verification gate for the rest of the season

Three principles I set myself after that morning.

If there is no data, say plainly there is no data. That is an answer, not an evasion. An expert who says he does not know yet remains more useful than one who offers ten groundless conclusions.

Every metric must sit beside match context and the manager's decision. Hanoi FC's possession share in V.League round 12 of 2026 means something only when read alongside Khanh Hoa's 18 presses.

Small margins must be recorded. A 0.1-second error can change the colour of a trophy, but I still prefer to measure three times.

And one more principle, for the reader. GPS does not show you the winner; it shows you the one who dared to run one extra metre. Reading an analysis, the thing to look for is the metre the author actually measured.

The 2026 World Cup is approaching, and the transfer window before it will generate more rumour than any in years. Hundreds of analysis packs will reach newsrooms with full frames and thin interiors. The writer's job is not to fill them in. The writer's job is to keep the emptiness intact, until there is enough data for it to speak.