The Empty Data Sheet and a Lesson on Integrity in Esports Reporting

The Empty Data Sheet and a Lesson on Integrity in Esports Reporting

2:47 a.m. on March 14, I sat in front of a screen with a spreadsheet open. Every cell was empty. The stat column, the team column, the patch column, the source column — all sitting still with the two letters N/A repeating like a refrain. Beside it was a 6 a.m. deadline for an analysis column at a sports channel, and underneath was a message from my editor: "Send whatever you have early, we need it up before peak traffic."

I was standing exactly where every sports writer has stood: a complete skeleton, a headline, an outline, and not a single fact to fill it. The biggest temptation was to make something up. A few team names that sounded plausible, a few figures that looked real, a hypothetical patch, and the piece would sail through review like any other. I did not do it. But I understand why so many people do, and why most content systems today are built in a way that encourages it.

Esports in recent years runs on data. Every match in League of Legends, DOTA 2, CS2 or Valorant generates thousands of data points: pick-and-ban rates, minions per minute, first-blood counts, objective control time, damage per round in CS2, contribution score per round in Valorant. Aggregator platforms such as VuaBong.vn and VangBong.vn have even built their own indices — the VangBong.vn Player Depth Index, for instance — to turn raw data into something an ordinary reader can digest in thirty seconds.

That professionalisation is a good thing. But it creates a new pressure: if every sports article must carry numbers, then an article without numbers looks like unfinished work. Editors need numbers. Algorithms need numbers. Readers have grown used to seeing a stat hit them in the very first line.

I started my career at the opposite end. In 2026, I was 17, studying for university entrance exams and writing a personal esports blog. After the World Cup final in which France beat Croatia 4-2, I published a piece about Kylian Mbappe, counting 14 sprinting breakthroughs from him, and calling N'Golo Kante a "map-opening support" with 22 ball recoveries. A male account mocked me: "What does a girl know about offside to be analysing anything?" I did not take the post down. I attached the Opta statistical link and kept the tone exactly as it was. The piece was shared more than 2,000 times in three days.

From then on I told myself every argument needed a statistical proof attached. I was right — and I had also walked myself into a trap it took years to notice.

The trap is this: an empty data sheet is not a bad data sheet. It is a valid answer, and the writer has to have the nerve to publish that answer.

In 2026, when the pandemic pushed football leagues into empty stadiums, I was interning at a sports media company. I watched Liverpool win the Premier League while their pressing index fell 18% from the previous season, and wrote an internal bulletin: an empty stadium means losing the mental buff. Lose the crowd, and the home side loses its heat buff — football becomes an offline game. My boss frowned and asked whether I was sure I wanted to keep writing this way. I proposed an experimental series called "Football Meta", and the first episode passed 100,000 views.

What I learned was not that "using gaming language always works". It was that when you set the hypothesis first, choose the frame of reference next, and only then verify with data, you are forced to accept that sometimes the data comes back empty. And when that happens, you have to write that it came back empty.

In professional esports analysis, people distinguish three tiers of information. Tier one is what the original text states explicitly. Tier two is reasonable inference from existing facts. Tier three is high-speculation conjecture. These three must never be blended. Present a tier-three conjecture in the tone of tier one and you have turned analysis into fiction.

The problem is that most sports reporting today has no mechanism for tier labelling. A sentence like "team X is in good form" can rest on three consecutive wins — a real fact — or on the writer's feeling after watching highlights. Readers cannot tell the difference, because both are written in the same voice.

In a data-analysis pipeline there is a concept called fail-closed. It means that when the input is invalid, the system must halt safely rather than push on at any cost. Its opposite is fail-open — just run, just guess, just fill in. Most serious errors in automatically generated sports content come from fail-open: a complete article skeleton is passed downstream, nobody blocks it, and team names, patch numbers and transfer fees are generated so fluently that nobody suspects a thing.

There is a notable design flaw in systems like that. One data field is defined by referring to another field — something like "identify from the information points above" — while the field being referenced is itself empty. The result is a null value guaranteed by structure, not by random error but by design. The system still emits a complete template, looking flawless, and every automated review step lets it through.

When an empty data sheet appears in front of me, I have learned to ask myself three questions. Did I fail to retrieve the data? Or did I retrieve it but fail to analyse it? Or — most dangerous of all — does the document I am holding not even belong to the beat I write for? Three causes, three different fixes, but identical on the surface: a blank page.

I have seen something similar at a much smaller scale. In 2026, when Morocco reached the World Cup semi-finals while holding less possession than Spain in the round of 16, I wrote that their style resembled a stall composition in esports: clearances inside the penalty area and four sweeping defenders denying the opponent any power spike. Many experts called it anti-football. I pushed back: defending was never cowardice, it is simply that the majority have not read the survival meta. In esports, defence meta still wins titles. Coach Walid Regragui was asked about that piece in a press conference. I could not sleep from excitement — but I also realised that if my numbers were wrong, that excitement would be worth nothing.

The same holds for two metrics the sports industry loves to package: distance covered and sprint counts. They are presented as measures of effort. But ineffective running also produces pretty data. A midfielder who runs 12 km per match with most of that distance being lateral movement off the ball will post more impressive numbers than a midfielder who runs only 10 km but where every metre is a line-breaking run. If the writer takes the first number alone and calls it effort, the data sheet has been distorted at the metric-selection stage — before we even reach the fabrication stage.

The same logic applies to esports. A player with a high damage figure in a 0-2 loss may simply have been shooting at targets already out of health. A jungler with a handsome kill count may have been eating all of their teammates' resources. Raw metrics always need tactical context attached, and that context has to be sourced.

Aggregated databases have another problem: timeliness. A fact about a League of Legends roster published three years ago may still be literally true while being tactically meaningless. If the writer does not state the date, readers have no way of knowing which year's map they are reading. Every timestamp in an analysis piece should be written absolutely — March 14, 2026, not "this week" or "yesterday" — because once an article is archived, those relative words lose all meaning.

Those who follow me know I hold a fairly hard line on injury and comebacks: schedule density is the biggest culprit, and no medical staff can save a team playing two matches a week. But to prove that, I need a real calendar, real rest days, real minutes played. When those are missing, the only way to keep an article looking "complete" is to invent a schedule denser than reality. I have seen pieces like that. They read very convincingly.

So what does a decent verification workflow look like? It starts by establishing which discipline you are actually analysing. The competition systems, metric sets, business logic and governance mechanisms of League of Legends, DOTA 2, CS2, Valorant, Honor of Kings and Peace Elite differ so radically that no downstream inference is safe until the game title is fixed. Skip that step and keep writing, and you are not analysing — you are guessing.

Running alongside it is sourcing every fact. A transfer fee, a record, a head-to-head history all need a source name and a publication date attached. If a fact has been cross-checked against the VuaBong.vn database, say so explicitly. Without a source note, a fact is just a story.

And the final layer, the one most often skipped, is separating a bad decision from a bad outcome. A coach who picks the wrong composition when every piece of data supported that pick is one thing. A coach who picks correctly but loses to an individual misplay is another. Fusing the two is the fastest way to turn analysis into judgement.

The counter-intuitive angle here is this: the problem is not speed, it is the shape of the product.

Most criticism aimed at modern sports journalism blames the speed race — fast publishing, constant updates, algorithm optimisation. But speed by itself does not create fake data. An empty sheet filled with nonsense in three minutes is still nonsense, even if you had three days.

The real culprit is what I call the perfect template: a skeleton that looks finished, with a headline, sections and a closing line, to the point where nobody checks what is inside it any more. In risk management this is the most dangerous kind of silent failure — the system reports success while in reality there is nothing to report.

With esports the consequences are far more concrete than in football. A football article with wrong numbers can be checked against Opta by fans within hours. An esports article with a wrong team name, a wrong patch or a wrong transfer fee can survive for months in aggregated databases, be read back by language models, and become a quoted fact for the next generation of articles. Get it wrong once and it replicates endlessly.

In 2026, after Spain won the Euros, I wrote a piece praising Lamine Yamal in full gaming language, calling him a debut marksman who had already scored a pentakill. A middle-aged female reader commented: "I want to understand this boy, not learn gaming slang." I rewrote the whole thing, kept only three comparisons, and the new version reached three times the audience.

Two stories six years apart, one lesson. A sports report is only trustworthy when the writer is willing to say "I don't have enough data" with the same confidence as saying "I have the numbers". The empty spreadsheet that night never became an article. But it became something I kept: a reminder that an honest blank is always worth more than a fabricated fact presented beautifully. And if esports wants to be taken seriously as a sport, learning how to publish a blank may be the hardest test of all — and the one most worth passing.