When the Input Is Empty: The Discipline of Saying 'Insufficient Information' in Sports Analysis

A colleague sent me a nine-part analysis. Tables aligned, a colour-coded risk matrix, bolded value ratings, a tidy recommendation section at the end. I read it top to bottom and nodded along. Then I read the header again. First field: game title — none. Second field: patch version — none. Third field: team — none. Fourth field: player — none.

All nine parts of that report described a subject that never existed in the input data. A piece with wrong numbers can be caught. A flawless analytical framework with no subject is very hard to catch, because it asserts nothing that could be wrong.

This article is not about any particular game or match. It is about the thing standing behind every transfer item, every metrics table, every player profile that you and I read every day.

I work as a transfer market administrator in Busan. The daily job is reading reports, classifying them, and deciding which ones have enough grounding to enter my tracking board. Transfer season is the season when noise always outweighs signal. A player can be linked to five clubs in seven days; a deal can appear on twelve outlets before anyone confirms it.

My tracking experience shows that most broken analyses break not in the calculation stage. They break at the point where the brief was received. The writer receives an empty file but already has a story in his head. So he writes that story out and labels data on top of it.

In medical data work, this is called filling a gap with an assumption. In the transfer industry it has another name: "a source close to the situation." In sports analysis it usually lives in sections with impressive titles: projections, simulations, base case.

The rule I set for myself long ago: never publish an unconfirmed report as though it had happened, and never deny an unconfirmed report as though it had been ruled out. Those two errors mirror each other, and both come from a writer wanting a fast conclusion more than a correct process.

I reopened that nine-part report and read it differently. I read it as a list of things that had not been done.

The finance section said: sponsorship revenue, league distributions, salary bill, capital injection — all blank. The compliance section said: competitive integrity, transfer regulations, contract compliance, minor protection — all unscreened. The personnel section said: injuries, final contract years, burnout signals — unchecked.

This is where I want to stop longest. The heaviest risks in this industry — unpaid wages, match-fixing, an injury to a core player — are silent risks. They surface only when someone actively goes looking. Their absence from a dataset is not evidence that they do not exist.

I call it screening asymmetry. A club that looks clean on a spreadsheet may simply be a club nobody has audited. A roster that looks healthy may simply be a roster nobody has asked the medical room about. A deal that looks sound may simply be a deal whose release clause nobody has read carefully.

Every table is a cut, and every cut is a story. But a table with no knife cuts nothing, however neatly the grid is drawn.

From there, three layers of the problem appear.

The first layer is subject substitution. When the input lacks a game title, a team, a player, the writer has two options: write "insufficient information," or pick a plausible-sounding subject himself. The second option is always more attractive, because it yields a complete product. It is also the option that produces the highest-quality presentation of fabricated information.

The second layer is the illusion of framework completeness. A report with nine sections, tables, a star rating and a recommendation section looks more credible than a short paragraph reading "I have no data." But credibility lives in the data, not in the number of headings. A skilled presenter can make a blank page look like a blueprint.

The third layer is asymmetry in what gets published. A wrong positive result gets corrected. An honest null result gets published by no one. So in the information market, readers only ever see confident analyses, and gradually assume confidence is the standard and silence is a sign of weakness.

Method for this section: I re-scanned 210 transfer files from the last four windows that I tracked myself, classified by source tier — official club announcements, edited journalism, and aggregator pages with no attribution — and checked them against completed-deal announcements. Limits of the sample: these are personal notes, not random, skewed toward the Korean and Asian markets, and limited to deals that came within one person's tracking range. The result is not meant to generalise to the whole industry.

In that record, the share of rumours that became completed deals in the same window generally sat around one third, and it varied sharply by source tier. For tier-one sources — official club announcements, tournament organiser registration records — the rate was close to absolute. For tier-three sources, the hit rate was low enough that I stopped counting. The more interesting finding lies elsewhere: most of the wrong analyses I encountered did not cite the wrong source. They cited the right source but assigned it a weight that source did not have.

In a transfer file, the most readable part is usually the contract structure: the release clause, performance add-ons, the sell-on percentage to the previous club. That is where money actually moves, and it is where the fewest reports stop. A player's valuation is only an equation with missing unknowns. People typically solve one unknown and declare the whole problem solved.

In esports, the information lifecycle is even shorter than in football. A patch can reorder the strength ranking within two weeks; a roster can change three players in a single off-season. At that tempo, the pressure to conclude immediately grows, and the distance between "verified" and "heard" erodes faster. A fast tempo does not make inventing a subject less harmful. It only makes the consequences harder to trace.

The standard response to an empty analysis is to demand more data. That reflex is right but insufficient, and it sometimes points the wrong way.

The problem with that nine-part report lies elsewhere: it had too much structure. It had enough room to hold any conclusion, and precisely for that reason it invited the writer to stuff one in. Had that report been capped at one page with a single question, the writer might have been forced to answer that he had nothing.

Another counter-intuitive point: in transfer analysis, clean data can do more damage than dirty data that carries a label. A table footnoted "source unverified" makes the reader slow down. A table with no footnote makes the reader walk on, and walk into a place with no floor.

I have made this mistake. In 2026 I wrote about Korea against Germany in the World Cup group stage. Germany dominated possession, registered very few shots on target, and Korea counter-attacked quickly. I concluded the weaker side could win if the opponent lost focus late. The second goal came in the final minute of stoppage time, from a counter-attack that Son Heung-min finished. The result was right, the piece was shared, and I nearly learned the wrong lesson. What I actually took from it lies elsewhere: record the prediction date, the data source and the confidence level. The 2026 World Cup taught me that a 1% probability is still a datum. It did not teach me that I may ignore the other 99%.

The abacus never sleeps, but football does. And so should the analyst.

In this transfer window I am keeping one old rule and adding one new rule. The old rule: every player file must carry at least four comparable data columns, with the numbers and the inference kept separate. The new rule: every report must carry a field stating what has not been checked. That field will be blank in many reports, and I want it blank in public.

What I am waiting for in the next tracking cycle is not a bigger deal. It is an analysis willing to end on the sentence: not enough information.