Empty Data Reports: When a Beautiful Analytical Framework Replaces Watching the Tape

Empty Data Reports: When a Beautiful Analytical Framework Replaces Watching the Tape

On the night of January 12, 2026, in a small community studio in the basement of an old building on Halsted Street, Chicago, I sat in the second chair on the left — the same seat I have occupied for seven years. On the control monitor, the game's analysis board was being built cell by cell: Attack, Execution, Personnel, Key Data, Risk, Market Sentiment, Ripple Effects, League Context, Officiating. Nine cells. Each one had a bold header, clean typography, thin grey dividers.

And each one was empty.

The lead host kept reading at an even pace, never missing a beat: "Tactically, the visiting side is showing real control over the tempo." I turned and looked at him. He looked at the screen. He kept reading. For two minutes and forty seconds the broadcast ran as though those nine cells were packed with data, when in truth they held two capital letters and a dash.

What chilled me that night was not the technical failure. The tracking feed had dropped somewhere between the arena cameras and the station's server. That happens a few times a season; anyone who lasts in this job has seen it. What chilled me was the familiarity. I had heard hundreds of reports that sounded exactly like that one, with nine cells full of numbers, and just as hollow inside. The only difference was that on this night the emptiness was exposed. On ordinary nights it gets polished with terminology.

The field never lies; we simply are not patient enough to hear it breathe. But the spreadsheet lies beautifully, and it lies in a language nobody dares argue with.

From a studio in Chicago

I entered this profession by mispronouncing a name. In 2026, at seventeen, a senior in high school in Chicago, I was taken on as a contributing commentator for a community radio station. Chicago Fire against Toronto FC at Toyota Park. In the first half I mispronounced midfielder Bastian Schweinsteiger's name three times. Not subtly. Listeners called in to complain repeatedly, and the programme director texted the booth: "Slow down. Read slower."

For the next four weekends I sat alone with the recordings, rewinding that match and several before it, building a phonetic reference sheet for every player on both teams — shirt numbers, positions, a note on how each name should sound. I also told the director I had got it wrong, though asking for that conversation was hard for me.

The lesson was not about pronunciation. It was this: I had gone on air without raw material. I had a programme, a time slot, an open microphone, and a match unfolding in front of me — but I had no baseline data with which to say anything true. The frame was full. The inside was empty.

Seven years later I sat in a different studio and saw the same diagram, this time rendered in software.

The three layers of any report

Every serious sports data report runs through three layers, and the order cannot be reversed.

Layer one is extraction. This is where the practitioner leaves the chair, goes to the floor, sits in front of the screen, makes calls, cross-checks, rewinds a clip until the thing that needs to be seen is seen. This layer is dirty, slow, and invisible.

Layer two is structuring. Raw material is filed into boxes: tactics, personnel, contracts, risk, league context. This layer is clean, attractive, and easily mistaken for the actual work.

Layer three is storytelling. This is what readers consume.

The problem is this: if layer one returns nothing, layers two and three still run. They do not stop themselves. A nine-cell frame with complete headers, complete dividers, complete technical vocabulary can still be exported and read aloud exactly like a real analysis. It is missing precisely one thing: information.

That is the definition of an empty report. A document with fully professional presentation, complete sections, complete jargon — containing not a single verifiable data point, not a single challengeable observation, not a single detail that would have required the writer to be physically present where the event happened.

A framework does not generate information

In basketball there is a category of possession I always show newcomers first: the scoreless possession.

The team runs the play correctly. The ball goes inside, comes back out, reverses sides, reverses again, two consecutive screens, spacing so good that a still frame of it belongs in a textbook. Then the ball reaches the last shooter, the shot misses, nobody is fouled, nobody grabs the offensive rebound. The box score reads: zero points.

On tape, that possession is beautiful. On the scoresheet, it is a zero. Both are true, and both are meaningless apart from each other.

An empty report operates in exactly the same way. It has a lovely formation, correctly placed terminology, a clear layered structure, bold headers. It scores nothing. And the danger in sports is that a beautiful possession is easily confused with a valuable one, because beauty is visible immediately while value has to wait.

The nine cells on January 12, 2026 were a beautiful possession. Nobody stood in the wrong place. Nobody used the wrong term. It was just that all five players were correctly positioned and the ball was never there.

The smallest detail on the floor is where the largest truth hides. But a framework does not go looking for detail. A framework only goes looking for somewhere to type.

Metrics have no obligation to explain

There is a widespread belief in this industry that more metrics mean deeper understanding. I have watched the sports content markets in Vietnam and the United States long enough to see that belief fail in a very specific way.

The metrics we lean on most — true shooting percentage, usage rate, net rating per 100 possessions, composite impact models, and expected-goals models in football — are designed to describe outcomes, not to explain decisions. They answer "what happened, and how often". They do not answer "why did the coach choose that option in the sixty-eighth minute".

That gap is not the fault of the metrics. It is the fault of the people using them, who assign a descriptive tool an explanatory job.

One example I still use with interns: France beating Argentina 4-3 in the round of 16 at the 2026 World Cup, on June 30, 2026, at Kazan Arena. Kylian Mbappé scored twice, in the 64th and 68th minutes. Antoine Griezmann opened the scoring from the penalty spot in the 13th. Benjamin Pavard scored in the 57th. For Argentina, Ángel Di María scored in the 41st, Gabriel Mercado in the 48th, and Sergio Agüero pulled it back to 4-3 in the third minute of stoppage time.

Read only the goal column and the story is: Mbappé is fast.

Watch the tape and the story is different. Both Mbappé goals came from off-ball runs that stretched Argentina's back line, opening space for Griezmann to drop deep and orchestrate, and giving France's midfield time to change state. Argentina's defence was pulled out of its block by movement without the ball, not by raw speed. Mbappé's goals were the result. The cause sat two seconds before the ball arrived at his feet.

The real star is not the scorer but the player who makes his teammates' scoring easier. And metrics never say that on their own. Someone has to sit down and watch.

Extraction is the entire job

In January 2026 I covered Leeds United's mid-season transfer window closely. Through an old radio contact I reached an assistant coach at the club and entered a reliable relationship network. I was the first to confirm Weston McKennie's move from Juventus to Leeds on loan, with one important detail: no option to buy.

I made five verification calls. I published only after three independent sources. Three sources, not one source heard twice.

The "no option to buy" detail is the one I have remembered longest, not because it is dramatic, but because it separates a report from an empty report. Anyone can write that a player is being linked with a club. Only someone who made the calls can write that the deal carries no purchase clause, and what that says about how the club views the player in the medium term.

If layer one returns nothing, the entire chain behind it must be stopped. That is the only principle I have kept intact for ten years.

Our industry has no such gate. No automated control rejects an analysis whose raw-material section is blank. No editor receives a red alert for a two-thousand-word piece containing no observational detail. Everything keeps running, because the frame was already beautiful.

Language that is true of every team

There is a category of sentence I learned to delete from my drafts first, once I recognised it as the fingerprint of an empty report.

"They need to improve their transition defence."

"They have to be more clinical with their chances."

"The back line must concentrate better in the closing minutes."

"The team needs to maintain psychological stability."

Every one of those sentences is true of every team, every match, every season, every decade. A sentence true in all cases carries zero information. It is not wrong. It simply says nothing.

Descriptive language is what gets generated to fill gaps in a frame. When extraction fails, the inexperienced writer does not drop the assignment. They fill it with sentences everyone nods at, so the piece still has length, still has sections, still looks like a finished job.

An empty report does not look like laziness. It looks like diligence applied to the wrong layer.

Thirty seconds to spot an empty report

This is the part I want readers to keep, because readers are the ones who pay for an empty analysis.

Four questions. No tools required. Thirty seconds.

One: does the piece recount a specific on-field moment? Not "the team controlled the game", but a possession, a sequence, a decision at an identified minute.

Two: do the numbers cited have a source? Not a prestigious source — just one that can be traced back.

Three: does the piece contain a claim that could be proven wrong? A claim that cannot be wrong is a claim that cannot be used.

Four: is there any trace that the writer actually watched the match, rather than reading the post-game summary? That trace usually appears as a detail meaningless to everyone else but meaningful to someone who was there: a player changing shoes in the thirtieth minute, a coach standing for the entire second half, a referee saying something to a captain.

Without all four, what remains is a beautiful spreadsheet.

What a real report looks like

I have no intention of dismissing the value of metrics. I object to using metrics to avoid watching.

A real report starts with an observation others missed. Take pick-and-roll coverage — drop versus switch. The point is not "this team defends solidly". The point is: when the big man drops, the opposing ball handler is forced to navigate a second layer of screening; if that second layer does not arrive on time, an open jumper appears. And that is only visible when the tape is rewound possession by possession, not when a summary table is read.

A real report ends with a variable for the next game. If my read is right, the next game will show this signal. If it is wrong, I will say so on the next broadcast.

There are rescues nobody sees, but the team remembers them to the end. The screen set on time at the third beat of a possession never reaches the box score. Yet the outcome of that possession depends on it. And if I have not watched, I have no standing to speak about it.

The counterintuitive angle: the machine is not the culprit

Over the past two years, each time an empty report appears, the instinctive reaction is to blame machines. I think that assignment of blame is wrong, and wrong in a direction that benefits everyone except the reader.

What produces empty reports is not a machine. What produces them is a reward system. Readers share a beautiful table. Nobody shares a paragraph stating that the writer does not yet have enough data to conclude. A piece with complete sections feels credible at first glance, before the second sentence is read. Form is rewarded before substance, and when form is rewarded long enough, it becomes the objective.

A second belief to dismantle: more metrics means more understanding. Over the past decade, the volume of indicators inserted into sports coverage has risen sharply. Whether understanding of how games actually work has risen correspondingly, I am not certain. I have read pieces containing twenty metrics and not one sentence that made me reconsider what I thought.

A third belief, and the costliest: that the parties harmed by empty reports are the clubs. They are not. Clubs do not read us. Those harmed are young readers and young writers. A young writer reads an empty report, finds it professional-looking, and concludes that this profession runs on building frames. They learn to build frames before they learn to sit and watch tape. Three years later they can produce a complete nine-cell report in forty minutes and cannot say one specific thing about any match they have ever watched.

The most counterintuitive point, to me, is that an empty report is more dangerous than silence. Silence leaves a gap for someone else to find the truth. An empty report occupies that gap, frames it, labels it as expertise, and makes nobody want to dig into it again.

One more thing, from a field I still track: transparency in officiating. We now have decision-support technology, lines drawn on screens, movement charts accurate to the centimetre. Spectators in the stadium still receive no explanation on the spot. The technology advanced; the mechanism for explaining to the audience barely moved. That too is a beautiful spreadsheet: the form of transparency is immaculate, while the part that helps people understand is absent.

What is true of every team belongs to no team

Let me return to something already touched on, because it sits at the centre of all of this.

When a claim cannot be wrong, it does not describe the thing. It describes the writer. The phrase "they need to concentrate better" tells us nothing about the team. It tells us the writer ran out of material and needed more length.

Serious practitioners have another sentence available: I have not watched enough tape, I do not have the data, I will answer next week. At twenty-six I learned that this sentence does not cost credibility. It preserves it.

There is one moment in this profession I remember more clearly than any smooth night on air. It was an afternoon in May 2026, when the pandemic had halted every league and my university's community football club in Chicago faced dissolution after losing its main sponsor. I told nobody. I drafted more than forty fundraising appeals, contacted alumni, and organised a charity livestream that raised eight thousand five hundred dollars. I declined to be named, letting the club's leadership thank the community on its behalf.

I do not tell that story to talk about myself. I tell it because it taught me something that applies directly to writing: the work that genuinely keeps a system running almost never appears on the board. Forty fundraising appeals have no cell in an analysis grid. Three verification calls have no cell. Four weekends rewinding recordings to fix how a name is pronounced have no cell. Remove them and everything collapses.

That summer, we did not save a club. We saved a belief.

What comes next

I am not proposing that we abandon analytical frameworks. Frameworks organise thinking, help readers follow, help editors check. I am proposing a gate at the lowest layer: if the raw-material section is empty, the report is blocked and returned to the writer.

For readers, I propose a small habit. Next time you read an analysis, underline the most specific sentence in it — the sentence that could only have been written by someone who was there. If you reach the end without underlining anything, you know what you have been reading.

For writers, I propose a different standard for self-assessment. Not word count, not number of metrics, not number of shares. One question: if the next game turns out completely differently from what I wrote, will I know exactly where I was wrong? Anyone who cannot answer that is not yet writing analysis. They are building frames.

At twenty-six, I understand that commentary is not for asserting myself; it is for lighting the way for the viewer. That night of January 12, 2026 in the studio on Halsted Street taught me something simple: a nine-cell frame can hold an entire game, or it can hold nothing at all. The only thing separating those two cases is whether somebody actually sat down and listened to the field breathe.

The next game will answer.