The Empty Report: Data Discipline in Esports Analysis

The nine-page report sat on the screen at two in the morning, Manila time. The first page covered the patch. The second covered the tournament format. The third covered the team and the players. And so on, down to the ninth page, which covered the flow of an entire industry. On every page, in the exact position where a number should have been, the same sentence repeated itself: insufficient information to assess.

I am used to decoding. At seventeen, during round twelve of the 2026 PFL season, I sat in front of a screen and rewound the fourteenth passage of play in the Kaya FC match. Striker Jordan Minta left the pitch in the twenty-eighth minute with hamstring pain, and the stands said only one word: cramp. I did not believe it. I drew the direction of his movement, measured his stride frequency, and cross-checked it against the way the opposing defence bent his line. That twelve-hundred-word piece reached a doctor on the Philippine national team. It was the first time I understood that a number like stride frequency could tell the whole story of an accident.

Tonight there is no passage of play to rewind. There is no hamstring to count. There is only an empty report and a very human temptation: fill in the blanks.

Context: an industry that lives on content and dies from data

Esports is a content-hungry industry in a way football has never been. A European football match lasts ninety minutes and leaves me roughly forty data points to hold on to: passes, pressing actions, heat maps, and most importantly the medical records that clubs are obliged to publish. An esports match lasts thirty-five minutes and leaves thousands of raw data points — yet almost none of them ever touch the human body sitting behind the keyboard.

I have watched esports matches in the Philippines and Southeast Asia for years, and what I learned did not come from tactics. It came from the gaps. When a player leaves the stage mid-series, the organiser issues a statement about "personal reasons". When a team substitutes at the tenth minute, nobody asks what state the replaced player's wrist is in. Football counts every hamstring tear; esports lives inside its own medical darkness.

This contrast is not a moral matter. It is a structural one. Football had a century to build team medical systems, a network of doctors, and a shared language for describing injury. Esports grew up in fifteen years, and it grew faster than its capacity to build infrastructure. The result is an industry with millions of fans, hundreds of tournaments, and thousands of broadcast hours — but no shared dictionary for naming pain.

And when an industry has no shared dictionary, it invents a private one. That is when empty reports are born.

Core analysis: the nine dimensions of a correct report

A decent esports analysis must pass through nine dimensions. I call them nine because nine is the minimum number for a conclusion not to collapse. Miss one, and the conclusion may still stand — but it stands on faith, not on data.

The first dimension is the patch. Before saying anything about a team, I must know which version they are playing on. A small change to an ability's damage can invert an entire tournament's priority order. If I cannot identify the game title and patch number, I cannot even select a framework — because the tournament systems, data metrics, and business logic of different titles differ so sharply that no single yardstick applies.

The second dimension is the tournament format. Format determines upset probability. A single-elimination bracket is a completely different beast from a best-of-three bracket. The same team, in the same form, produces a different expected result the moment the format changes. Without the format, I cannot say whether a strong team is stable.

The third dimension is the team and the players. This is where I am closest to my old trade. Paper strength, role fit, bench depth, and above all individual form over time. But I never compare a top-lane player to a bottom-lane player with the same number, because each role has a different resource allocation.

The fourth dimension is the regional landscape. Placing a region in the leading group or the fringe group is not about bragging; it is about positioning expectations. Which regions produce talent, which merely import it, which have a real academy pipeline — these are the decisive questions.

The fifth dimension is club finance. I do not care about the transfer number. I care about the revenue structure. A team living on sponsorship behaves differently from a team living on publisher distributions. The transfer market is where money buys back the forgetting of sports medicine.

The sixth dimension is rules and governance. Competitive integrity, transfer regulations, protection of underage players. This is the dimension where esports is weakest, and also the one empty reports love to skip most.

The seventh dimension is the risk profile. Seven standard risk groups: competitive, financial, personnel, rules, public opinion, systemic, and one that few notice — process risk. Process risk is when the analytical machine itself breaks, and every conclusion born from it is contaminated.

The eighth dimension is the public narrative. A story told without a basis will dissolve within weeks. A story with a basis will outlive the tournament that produced it. My job is to measure the gap between market expectation and on-stage reality.

The ninth dimension is industry transmission. From publisher, through clubs and streaming platforms, down to sponsorship and derivative markets. A change upstream can take eighteen months to reach downstream.

These nine dimensions are the skeleton. But a skeleton only means something when it has flesh. And the flesh is data.

When the skeleton has no flesh

Tonight's report has all nine dimensions. It has titles, tables, boxes. But in every box, instead of a number, there is a slash. No game title is named. No patch number. No tournament, no team, no player, no region, no financial event, no rules issue, no public narrative, no industry signal.

The interesting part is not that the report is empty. The interesting part is that it is empty with discipline. Its author refused to fill the blanks. Its author chose nine blank pages over nine fabricated ones.

I once did the opposite. In June 2026, when European football returned after three months of lockdown, I took the dataset from five major leagues, scanned the first two hundred and eighty-seven matches, and counted forty-one muscle tears, against twenty-eight in the same number of matches the previous season. A thirty-two percent rise. I wrote a long piece, and I was not certain. I sent it to five experts. They replied differently, and I was glad when they attacked it, because being attacked meant I had put forward a hypothesis concrete enough to shoot at. I revised the draft and published it as an open hypothesis.

The lesson I drew was not "don't write when unsure". It was "write with your own uncertainty attached". Europe closed its pitches, and I opened the archive — counting every muscle tear in the dark. But I only dared to count when I knew what I was counting.

Tonight's report does exactly that. It knows that it does not know. And it admits it.

The player's body is writing a dictionary of injury that the coaching world has not agreed to open. In football, that dictionary has thickened over a century. In esports, it has only a few pages, and the first pages are being torn out by the very people responsible for writing the next ones.

The contrarian angle: the market pays for fabrication, not for emptiness

This is what keeps me up at night. An empty report is the most honest product an analyst can deliver. It is also the hardest to sell.

Imagine two analysts given the same brief. The first delivers a nine-page report where every box is a slash, plus a recommendation: re-run the data-extraction process, check whether the source document was successfully ingested. The second delivers a nine-page report packed with detail: a game title, a patch number, a team, a player, a transfer. The second gets praised. The first gets asked why they worked so inefficiently.

But if I read the second report closely and discover that the game title does not exist, the patch number is fictional, and the player never played for that team — then the full report becomes a debt. A debt the reader will pay with their trust.

In my industry, this debt has a politer name: an operational incident. But its essence is fabrication. And fabrication in esports analysis is more dangerous than in football, because here there is no team doctor to stand up and correct the record.

There is a psychological mechanism that makes this happen often. When an analyst receives an empty input, they do not see emptiness. They see a blank space that needs filling. And the human brain hates a blank. It will automatically generate the most plausible hypothesis to fill it, and the most plausible hypothesis always looks the most like the truth. That is why an empty report, if not written carefully, will be turned by its own author into a fabricated report within thirty seconds.

The author of tonight's report resisted that mechanism. They wrote a warning line at the top of the document: fabricating entities at this stage would violate the principle of transparent sourcing, and would produce a plausible-looking but entirely unsourced report — the most dangerous failure mode in esports analysis.

I agree with that line so much that I want to hang it on my wall. But I also know that within the next twelve months, there will be at least one more report as empty as this one, and someone will fill it with a name that sounds very real.

Counter-evidence: when emptiness is a fault, not a virtue

I do not want to turn honesty into a shield against accountability. Because there is another version of this story, and it is far more uncomfortable.

Suppose the source document did contain content. Suppose the game title, patch, tournament, team, and players were all in it, but the extraction process at the prior step failed. Then the empty report is no longer an act of discipline. It becomes an operational fault presented as a virtue.

The difference between these two cases comes down to a single question: did the source document exist and contain content? Tonight's report admits it cannot answer that question. And that admission is its strength — and simultaneously its blind spot.

I learned to tell these two kinds of fault apart from a transfer case. In January 2026, I checked the details of striker Kevin Tabora's move from Stallion Laguna to Muangthong United. There were reports the deal had collapsed after a second failed medical. I read the injury report from the clinic and noticed an old meniscus tear in his right knee from 2026. I called Stallion's doctor, ran the numbers against similar cases in the J-League, and wrote that Tabora's recovery index was better than eighty-two percent of players in the same position. As a result, Muangthong sent additional doctors to Manila to re-examine him.

The lesson from that case was not in the conclusion. It was that I was forced to separate two things I had initially merged: medical risk and transfer risk. Medical risk is a scientific question. Transfer risk is a business question. A player can have low medical risk and high transfer risk, or the reverse. Merging them is the fastest way to get it wrong.

Applied to tonight's report: the subject-level risk — the risk of the tournament, team, or player named — cannot be scored because no subject is named. But the process-level risk — the risk of the analytical machine itself — can be scored, and it is high. This is what a poorly written empty report would miss. It would say "no risk detected", and the reader would understand it as "everything is fine".

I once misread in exactly that way. After writing about goalkeeper Beiranvand's concussion, I earned a spot as a reporter for a Southeast Asian transfer news site. I was so excited that for months, whenever I found no evidence for a rumour, I wrote that "no abnormal signs have appeared". Only later did I understand: finding no evidence is not evidence of calm. It is just another blank space.

What needs to change

From the Eriksen case, I drew a principle I apply to every piece I write, including esports pieces. On 12 June 2026, at the Denmark versus Finland match, Christian Eriksen collapsed from cardiac arrest. I was watching live in Manila. While many spoke of a miracle, I opened a spreadsheet and sketched a timeline: zero seconds to detection, twenty-two seconds for the captain to signal, thirty-eight seconds for medical staff to begin chest compressions, seventy-eight seconds for the defibrillator to be applied. I wrote a twenty-eight-hundred-word piece, emphasising the forty-five drills run by the Copenhagen medical team.

Then a doctor in Denmark emailed me to correct three terms. I thought I had understood Eriksen's ninety seconds. The email from Copenhagen showed I had only read the cover.

Those three terms did not change my conclusion. But they changed how I write. Since then, I never care only about which minute. I care about every second. And I never publish a piece about injury without contacting at least one local expert.

Applying that principle to esports analysis, I see three tasks.

The first is to build a mandatory data field for every extraction process. That field must contain the game title, patch number, tournament name, team name, player name, region, and timestamp. If any field is empty, the process must halt and report an error, instead of running on and producing an empty report. An empty report should only exist when a human actively decides it is empty, not when a lazy machine produces it.

The second is to ban any data field defined by reference to another field. In tonight's report, there are two such fields: the entity field and the source-quality field. Both instruct the reader to derive their value from other fields — which are themselves empty. That is a loop with no exit. A good analytical system never ties itself in such a knot.

The third is to teach readers how to recognise an empty report. Esports fans today are trained to read full reports. They are not yet trained to read empty ones. And an empty report that is misread is more dangerous than a full report that is misread, because it wears the appearance of objectivity.

Takeaway

I do not write about injury. I write about what the body screams when language is not enough. Tonight, that body is an entire industry. It is screaming that it does not yet have enough vocabulary to describe itself. And its response, in many cases, is to invent vocabulary.

The nine-page report with the slashes is not a failure. It is a confession. It says: I have nothing to say yet, and I will not pretend otherwise. In an industry where everyone is talking, the person who stays silent at the right moment is the most trustworthy.

The body does not lie — it only speaks a language the medical room has not yet translated. The analytical machine is the same. It does not lie. It returns exactly what was loaded into it. If the input is empty, the output is empty, and everything in between is just noise.

The question I leave for the industry is not how to write more. It is: when the machine returns a zero, who among us has the courage to publish that zero?