A Nine-Layer Report With Zero Data Points: Where Esports Analysis Verification Breaks Down

At eleven at night I opened the report that had just been dropped into the analysis group. Nine tables, nine dimensions, exactly the framework professional esports analysis teams still use: patch and meta, tournament format, roster and players, region, club finance, rules and governance, risk profile, public narrative, industry transmission chain. On the very first line, in bold: Input integrity — FAILED.

I scrolled down. Every cell read the same thing: N/A – insufficient information. No tournament name, no team name, no player name, not a single date anchor. The only usable field was a domain label: esports. The information-value table at the end had four entries, three of them scored one star out of five, the fourth blank. Number of information points: zero.

A nine-layer analysis that declares itself hollow on page one. In twenty years of watching sport and nearly a decade of writing about esports for Vietnamese readers, I have never seen a stranger document.

The nine-dimension framework exists for a thoroughly practical reason. Esports is a discipline in which almost everything can be measured: pick-and-ban rate, match duration, resource differential at minute fifteen, deaths before minute ten. The framework is only a scaffold that lets those facts talk to one another instead of talking past one another.

Each dimension answers a different question. The patch dimension asks which playstyle the current update is rewarding and how long the adaptation window lasts — Riot ships every two weeks, Valve far less often, so the same magnitude of change produces completely different competitive consequences. The format dimension asks whether a series is BO1 or BO5, because BO1 is the single largest lever on upset probability. The roster dimension asks who calls the plays mid-match, who holds up under late-game pressure, and whether a nineteen-year-old is being pushed into a twenty-six-year-old's competitive rhythm.

The finance dimension asks the hardest question: whether club revenue covers wages, given that the industry benchmark still has salary-to-revenue ratios above 80%. The governance dimension asks who writes the rules — and in esports the publisher is simultaneously rule-maker and commercial stakeholder, a dilemma no traditional sport has to face.

Three years ago I rebuilt the dataset of 90 Bundesliga matches after football returned to empty stadiums and found away wins had risen to 34%, more than 11 points above the pre-pandemic figure. Empty stands, but the numbers shout louder than any crowd. That only happened because I had the raw table in hand — every match, every round, every column.

The nine-layer report had no raw table. The patch dimension could not establish whether the subject was a patch note, a meta shift, or a discrepancy between tournament servers and live servers. The format dimension had no tournament name, so it could not assign a tier: world championship, mid-season event, regional league or second division. Without a tier there is no way to weight upset probability, no way to measure draw luck, no way to price schedule congestion.

An empty roster dimension means form curves, age curves and injury risk never start up. The finance dimension had not one data point, so the 80% benchmark sat out of reach, and there was no way to detect the kind of transfer that pays above competitive value — the mistake that has dismantled more than a few expensive rosters.

The governance dimension left behind one line I want framed: the absence of an integrity signal is missing evidence, not evidence of cleanliness. A report that finds no sign of match-fixing because it contains no match to examine is silence, not an acquittal.

The risk dimension graded itself. Of six risk categories, five were marked unassessable; the sixth — the risk of generating conclusions from an empty input — was rated high and recorded as already materialised. That is the only real finding in the entire document: a framework capable of producing nine layers of conclusion without a single data point is a framework built to protect the writer, not the reader.

The mechanics are far simpler. An unclassified article type, zero identifiable entities, an unnamed source — that combination usually points to something that is not an article at all: a clip, a stream segment, a screenshot of a scoreboard locked behind a paywall. The text extractor could not read it, and instead of raising an error, the system still emitted a report. Data does not create revolutions; it only exposes who is running on instinct.

Based on my experience tracking matches and analysis documents across many seasons, the real cost sits downstream of the report rather than inside it. A document like this gets read by scouts, by sponsorship managers, by content writers. If it is labelled analysis complete instead of extraction failed, every decision behind it stands on nothing.

At the end of the document there is a table of five signals to keep tracking: a successful re-extraction, identification of the game title, entity resolution, source attribution, a time anchor. Those five signals are in fact the five minimum conditions of a decent piece of analysis. That they appear as an appendix is the part worth talking about.

I could be wrong in two places. First, it is entirely possible this is a plumbing failure: the source was a video or a paywalled page, a re-run of the extractor with a different format recovers the data, and the nine-dimension framework is blameless.

Second, and more uncomfortable: it is possible this empty report is the most honest document published this week. In an environment where analysis has to be live 45 minutes after the final whistle, the pressure to fill blanks with a plausible-sounding name is enormous. In 2026, when I published the set-piece statistics of Vietnam's U23 side at the SEA Games in Malaysia, a national-team coach pushed back publicly; I held my position because I had a match-by-match comparison table. If I had not had that table, I would rather have published nothing.

But honesty does not erase a design flaw. A nine-layer pipeline that fails at extraction and still emits a report, still carries a recommendations section, still includes a signal-tracking table — that is a governance story, not merely a technical one. Their failure did not come from bad luck; it came from bad design. Glory is only the tip; the root is who takes responsibility.

I keep an old habit: when everything looks too stable, I start hunting for the crack. My prediction is specific enough to be checked: before the current annual season closes, at least one esports data platform in Vietnam will publish a verified-source label for every statistical table, and a separate label for tables that could not be verified. If a machine can write nine layers of analysis out of nothing, what makes readers trust analysis written by a human?