The Empty Report: The Discipline of a Sports Data Analyst

In June 2026, I received a nine-section report from the analysis department. All nine sections carried the same line: insufficient information. No tournament was named, no player identified, no game version mentioned. A colleague laughed and called it a useless document. I kept it and read it from top to bottom, because in twelve years of watching this industry it was the most honest report I had ever received.

That honesty comes at a price. Most of the sports analysis I read each week is packed with numbers, packed with charts, and packed with conclusions that have nothing holding them up. A line like "this team has found a winning formula" gets written from three matches. A pressing metric gets celebrated without anyone asking how many minutes it was measured over. The empty report, by refusing to guess, did exactly what my trade needs most.

I started out as an esports player, moved into tournament organisation, then into media. In 2026, as a first-year student in Busan, I built my own dataset for Asan Mugunghwa's matches in K League 2. There was no paid feed. I rewatched the footage of every match, marked the position of every shot myself, converted chance quality into xG myself. Each match took about two hours.

The league table said Asan were strong. My xG-per-match column said otherwise: 1.02, below Busan IPark's 1.48 and below both teams sitting just beneath them. Six penalties in six consecutive matches was the clearest signal. The leaders were not creating chances; they were living off situations that do not repeat. I wrote it up and said Asan would slide in the second half of the season. They finished fourth and lost in the play-offs. Two thousand views on a student blog was enough to convince me that data can say what the table hides.

From then on I set myself a rule: every claim carries a number, and every number carries its measurement context. When it was recorded, how many minutes were played, who came on, what the legs looked like at minute 75 — all of it is part of the data. Strip it out and the number becomes a label stuck onto a feeling.

In June 2026, in Kazan, South Korea beat Germany 2-0. Germany's PPDA was 5.8, meaning they pressed ferociously and made life miserable for anyone trying to hold the ball. Many analysts used that number to belittle Shin Tae-yong's approach: a win built on luck, on an opponent's slip. I split the data into fifteen-minute windows and saw something else. Germany ran hardest between minutes 60 and 75, exactly when their pressing system should have been holding its highest intensity. After Kim Young-gwon came on, Germany's lines began to open. South Korea needed three shots on target to score twice.

I wrote the rebuttal, published it on an Asian football forum, and got attacked for it. Three weeks later FIFA published a technical report confirming precisely what I had said. A PPDA of 5.8 sounds frightening, but a team out of gas at minute 75 is the genuinely frightening thing. That metric measures average intensity across a match; it cannot measure the moment a system collapses.

In 2026 the pandemic forced domestic leagues to play in empty stadiums. I was a master's student, and I realised this was a rare natural experiment: for the first time in modern history, the crowd factor could be separated from the home factor. I tracked 214 matches in the Bundesliga and K League 1 from May to August. Home win rate in the Bundesliga fell from 43.2% to 37.8%. Average goals rose from 2.79 to 3.12. That sample covers only two leagues and a short window, so I do not call it a law. I call it a measurement.

Those 214 empty-stadium matches taught me that home advantage is data, not just atmosphere. With the noise gone, referees still leaned slightly toward the home side, but home players lost part of their confidence and away players lost part of their pressure. Goals went up because the game opened out, not because somebody's defence got worse.

I published the small study on Medium. An editor at a sports analysis outlet got in touch and invited me to write pieces drawing on GPS data from Korean clubs. It was the first time I had access to a paid data feed, and the first time I had to standardise how I presented things: comparison tables, sourced footnotes, neutral language.

In June 2026, working as a transfer market administrator for a K League 1 club, I proposed signing Lee Kang-in from Mallorca for eight million euros. My data showed him in La Liga's top ten for chances created per 90 minutes, at 2.8, above Isco. The board turned it down on the grounds that he did not show enough defensive ability. Six months later Lee Kang-in shone, helped Mallorca stay up, and my club finished eighth.

I did not write a piece attacking anyone. I gathered every email, data report and meeting minute, then wrote a fifteen-page internal analysis showing where our process had failed: we compared metrics across different leagues without standardising them, and we let a qualitative criterion override an entire chain of quantitative evidence. A transfer fee is the number one party is willing to pay. True value is the number that data does not have to negotiate.

At this point the story is usually told one way: data is always right, trust the numbers. That is not how I tell it.

My trade has a trap bigger than ignoring data: trusting your own data too quickly. Numbers have blind spots too. The table tells the past, data tells the future — but only when the sample is big enough and the context similar enough. A seven-match sample cannot support a claim that a playing style works. A metric imported from football into esports is not automatically valid, because esports runs on meta, on patches, on balance cycles — things that shift far faster than a football season. A metric has to be localised before it is quoted.

And there is one thing I learned from that empty report, something very few analysts will admit: an empty data cell is a gap in knowledge, not a clean bill of health. Finding no sign of unpaid wages does not mean a club is healthy. Finding no sign of match-fixing does not mean a match was clean. Having no injury data does not mean a squad is fit. Silence in the data and cleanliness of the data are two different things, and confusing them is the most serious error an analyst can make.

I was once attacked for daring to question PPDA. FIFA confirmed it. But I do not use that to feel proud. I use it to remind myself that a doubted metric can still be useful, and a celebrated metric can still be meaningless. What decides the matter is whether you are willing to check its context.

For the coming round I am watching three signals. Teams with high xG and low goals, because they are creating good chances and the table has not caught up. Teams winning consecutively through penalties or a man advantage, because those runs break, we just do not know which round. And new metrics that appear in the press with no stated method, because before believing them you have to ask how many minutes and how many matches they were calculated over.

The empty report is still in my drawer. I keep it as a reminder that the real discipline of a data person lies in knowing when to stay quiet, not in how much they can say.