When Esports Must Learn to Say "Insufficient Data to Analyze"

On a Chicago morning I opened a nine-part analytical dossier on an esports event I was supposed to have mastered before going on air for my podcast. The first page said: title, none. Source, none. Article type, unclassified. The information-points field was empty. And in three cells that should have held team names, timestamps and source-quality notes, someone had pasted the instruction text meant for the person compiling the file: "identify from the information points above."

What woke me up was not the glitch. It was how the glitch was handled. That nine-section report, instead of inventing a story about an arena, a roster, a patch, wrote "insufficient information, cannot assess" in almost every cell. It chose silence. In a season where speed is measured in hours, silence is the hardest act there is.

There are matches that are not played on grass but deep inside people. This time the match was played inside a spreadsheet.

Context

Esports entered 2026 carrying more data than any sport has ever carried. A three-week international event generates thousands of games; every game generates hundreds of data points on gold, damage, item timings, pick-ban rates, fight duration. On the fan side those numbers flow through HLTV, VLR.gg, Liquipedia, Oracle's Elixir, and the stat pages publishers provide.

On the newsroom side, the pressure runs the other way. Analysis has to be published within hours of the final whistle. Nobody pays for a piece that appears two days late, however much truer it is. So most esports newsrooms have adopted semi-automated pipelines: one model reads sources and extracts facts, another builds the analytical skeleton. I use them every day to filter hundreds of matches. They are useful.

But there is a structural difference between esports and football, and it governs this entire story. Football has independent data providers, with contracts, with audits, with names standing behind every metric. In esports, the raw data sits mostly with the publisher — the same party that writes the rules, runs the tournaments, sells the tickets and holds the servers where the truth lives. Champion win rates, damage figures, the exact moment a patch goes live: all of it passes through a single gate. Independent verification, therefore, is not a stylistic choice. It is a condition of survival.

The Core

That empty file had nine sections. I read them as a list of questions this industry has never fully answered.

The first section concerned patches and meta. To claim that an update flipped the landscape, a writer needs win rates, pick-ban rates, average game length, and knowledge of whether the tournament server runs the same build as the public server. That last point has caused repeated controversy at international events: players practising on one version, competing on another. Without a version number, there is no claim to make. A patch changes the rules, and it also changes the market value of individual skills. A player can be the best in the world on one build and surplus to requirements on the next without losing a single point of ability. Anyone who has watched a team trapped in an old meta knows the feeling: they keep doing everything that used to win them games, and they keep losing.

The second section concerned format. BO1, BO3, BO5. This variable shapes upset probability more powerfully than any tactical factor. A strong team in a five-game series is a different animal from a strong team in a single game. Round robin, Swiss, upper and lower brackets, or accumulated points — each choice produces a different distribution of outcomes, and therefore a different definition of "strong". Organisers know this. They pick formats not for fairness but for broadcast slots and sponsorship windows.

The third section concerned teams and players. Average age, champion pool, injury history, final contract year. Among these, the most closely guarded and most consequential fact is injury. Carpal tunnel syndrome, tendinitis, back pain from twelve hours a day in the wrong chair — none of it shows up on a scoreboard, and all of it decides who can still play in October. Without player-level information, every form prediction is guesswork in make-up.

The fourth section concerned regions. The same region can dominate one title and finish last in another, because coaching ecosystems, academies and practice cultures differ. Who imports, who develops at home, where that flow goes — all of it requires data this industry publishes sparingly.

The fifth section concerned club finance. Revenue structure, dependence on publisher distributions, the salary-to-revenue ratio. No club discloses fully. So when a transfer is announced with a big number attached, outsiders have no way of knowing whether it is market price or money burned to reassure the fanbase.

The sixth section concerned rules and governance. In esports the publisher is simultaneously the lawmaker and a party with direct commercial interest, and no independent arbitration body sits above both roles. That is a structural feature of the industry, not the personal failing of anyone. But it means every claim of integrity requires stronger evidence than usual.

The remaining three sections covered risk profiling, public narrative, and the transmission chain from publisher to sponsor to mainstream market. Narrative is the one I care about most. The hype cycle in esports moves faster than in football because the audience is young, the content is short, the algorithm is impatient. A player is crowned over three weeks and dismantled over three days. The backlash — when a community turns on the very person it just worshipped — is almost always seeded by pieces that used numbers without samples, during the crowning phase.

All nine sections were blank. But their blankness points precisely at where this industry is thinnest.

Three Layers of Collapse

Reading it again, I saw three failures stacked on top of one another.

The collection layer: it never established which game was being discussed. That sounds trivial. It is not. Each title runs on its own metric system, and those systems are not interchangeable. In a MOBA you talk about KDA, gold-to-damage conversion, objective timing. In a shooter you talk about HLTV Rating, opening-kill success rate, kills traded per round. In a placement-based title you talk about placement points and the storm's path. Applying the wrong metric set to the wrong game is a category error. A sentence about "champion pick-ban rate" in a shooter is not misspelled. It is wrong in kind.

The interpretation layer: a number is a map, not the territory, and the person reading the map always gets to choose the scale. Chicago Fire taught me that football always knows how to trample the script. In 2026, while studying sociology at the University of Chicago, I wrote my first piece for a blog called "Third Half" about that club: the lowest passing accuracy in MLS, but the most goals from counterattacks. I pulled Opta data, built charts, and argued that direct play was a tactical manifesto rather than crudeness. A commentator on Twitter sneered: "Women like peering through tactics, huh?" I did not delete the post. I wrote a response, with charts.

The same 78 percent passing accuracy reads as dislocation beside a possession side, and as consistency beside a counterattacking side. The same opening-kill rate is a burden inside a slow roster and fuel inside a fast one. A patch says nothing about a team on its own. Someone speaks for it, and that someone always speaks in favour of the argument they picked in advance.

The publication layer: an empty document can travel through a system undetected because it looks correctly formatted. It has a title, a nine-part table of contents, tables, assertive verbs. Inside, not one verifiable fact.

I have received such briefs in my inbox — not from machines, from people. Transfer news with no source named. Match analysis with no match named. Predictions with no timeframe. Outwardly they look nothing like that empty file. In substance they are identical.

The first tell is the absence of proper nouns. A piece in which the protagonist is called by role rather than name, and the team by region rather than name, almost certainly means the writer had nothing specific to name. The second tell is numbers without samples: "a high win rate" with no count of games, no date range, no build number. The third is a conclusion placed before the evidence — the verdict in paragraph two, followed by ten paragraphs scrambling for something to lean on. The fourth is a complete absence of named data sources. And the fifth, subtlest of all: every sentence is true of every team. You can swap one team's name for another and the meaning does not shift. At that point the piece is a template waiting to be filled.

The third half of this story is not played on stage. It happens after publication. A wrong number enters an article; the article is cited in a video; the video is cut into three clips; the three clips harden into a prejudice about a twenty-year-old player. He has no way to answer convincingly, because to answer he would have to prove a negative — that he is not as bad as he has just been described. That cost is not recorded in any statistics table.

In the summer of 2026 the stands were empty, and sport had never been more honest. I was a production assistant at WSCR Chicago then. Everything broke apart; the calendar melted; the transfer market became a place where people traded panic rather than players. A Chicago Fire assistant coach told me the club was quietly negotiating a loan for striker Robert Berić from Saint-Étienne. I checked the numbers, called an agent to verify, and published despite the newsroom's scepticism. On 12 August 2026 the club confirmed the deal. What I kept from it was not "I was right". It was that a sourced file stands, while an unsourced file — even a correct one — stands only until the first challenge.

That is why the empty file left me lighter. A system that says "I do not know" is more trustworthy than a system that says everything with identical confidence.

The Contrarian Angle

But I have to argue against myself, because a piece that scolds carelessness while presenting itself as clean is just another template.

Where I may be wrong: my strictness about sources and numbers is a privilege. In Chicago I have time, a freelance contract, an assistant who checks figures. A writer in Hanoi or Ho Chi Minh City, running three deadlines in one evening, without paid access to statistics platforms, with nobody to cross-check, writes with whatever is within reach. Blaming them for missing sources blames the wrong party. The problem lives in the cost structure of the industry, not in individual ethics.

And there is something else. When you demand that every piece carry verifiable data, you quietly create a journalism so safe it becomes flavourless. The greatest matches I have watched were not recorded by metrics. They were recorded by a moment no table can measure. If I were only allowed to write what can be counted, I would have to delete from my professional memory the paragraph about Luka Modrić at the 2026 World Cup, where I wrote that he ran without stopping, as if fleeing something called memory. A former England international dismissed it as mixing emotion into expertise. That piece was shared two thousand three hundred times in its first day.

The balance is not a choice between numbers and emotion. It lies in saying clearly which is which. I can write about emotion, as long as I do not call it data. I can speculate, as long as I label it speculation. What I must never do is let a guess wear the coat of a fact.

Takeaway

I want something so simple it sounds banal: a provenance label on every piece of esports analysis. It does not need to be long. One line, stating where the data came from, how many games the sample covers, which build it belongs to, and which parts of the piece are the writer's inference. That one line would accomplish more than every declaration about professional standards this industry repeats whenever a scandal lands.

I wrote this piece to talk about esports, and it turned out to be about myself. About a Chicago morning when I opened an empty file and realised it was teaching me to do my job more seriously than any file stuffed with numbers ever had.

If an analytical system can say "I do not know", what exactly is stopping us?