An Empty Data Sheet in the Press Room: Notes from the End of the Bench

That night in Chicago, I opened the analysis file and found it empty. Not a single line of numbers. No player names. Not even team names. All that remained was a skeleton: nine sections, each with a line reading "insufficient information to assess", alongside table cells waiting to be filled.

I sat still in front of the screen for a long while. The radiator hummed steadily in the small apartment. Outside, the city kept running, and somewhere in newsrooms across the country, people were still pushing stories out by the minute.

I had four hours until deadline.

Four hours is enough to build something that sounds very solid. A tight headline. A few handsome numbers. A decisive conclusion. Four hours is also enough to convince myself that the skeleton was evidence, that filling it in was all that remained. I did not fill it in. But I understand why many people would.

Sports analytics now runs like an industrial assembly line. Data flows in from tracking cameras, from box scores, from statistics vendors, through software, and pours onto the writer's screen. At the far end of that line, everything looks firm. At this end, the writer receives only a pre-made file, along with the expectation that the file is correct.

That expectation is the most dangerous part.

My career began with an uncertain moment. In 2026, at seventeen, I was a commentary contributor for a community radio station in Chicago. During the Chicago Fire versus Toronto FC match, I mispronounced the name Bastian Schweinsteiger three times in a single half. Listeners called in to complain, repeatedly. After the match, I apologised to the programme director, then spent four weekends reviewing the recordings and building a pronunciation table for every player on both teams.

Since then I have carried a habit I cannot shake: before writing anything, I must know where my information comes from. Not to look careful. But to know what I am standing on.

The game taught me that in its own way. A possession becomes points not because the scorer is better than anyone else. It becomes points because someone set a screen in the right place half a second earlier. The screener's name never appears in the box score. The screener appears in almost no highlight reel either.

The real star is not the one who scores, but the one who makes scoring easier for his teammates.

I wrote that line not for style. I wrote it because it matches how I read a game. A defence switches its coverage. A wing pushes three metres higher. A midfielder drops deeper to open a passing lane. A pick-and-roll is broken by switching early. None of that lives in a basic box score. All of it decides games.

In 2026, as a first-year student, I wrote an analysis of France's 4-3 win over Argentina in the World Cup round of sixteen. Kylian Mbappé's two goals did not come from pace alone. They came from off-ball runs that stretched the defensive line and opened space for the deeper playmakers. With only the box score, I would have written something very tidy: France scored four, France won, Mbappé was good. That version is not wrong numerically. It simply skips almost the entire match.

Now imagine that box score is empty. No team. No player. And I still have to write.

That was precisely the situation I faced that night.

In 2026, at twenty-two, I had just finished a semester. Through a contact at the radio station, I reached an assistant coach at Leeds United. On the strength of those World Cup 2026 tactical pieces and the care in my working method, I was brought into a trusted circle of contacts. I followed the January 2026 transfer window closely and became the first to confirm the loan of midfielder Weston McKennie from Juventus to Leeds, including the detail that there was no purchase option.

What I remember most about that story is not the line itself. It is the five phone calls before publishing.

Five calls. Three independent sources. One contact in Italy. One in England. A third I only called because I still did not trust the first two. I published after the fifth call, not the first. The gap between the first call and the fifth was the longest stretch of that evening. It was also the stretch in which I learned the most.

Verification is not a step in the process. It is the process.

There is a common misreading: people assume verification exists to avoid being caught out. Not quite. Verification exists so you know what you are saying. A metric without a source is a metric without meaning. A skeleton without data is a skeleton without anything.

The smallest detail on the court is where the largest truth hides.

I trust details because I have seen them overturn conclusions many times. There was a game I watched and came away certain the winning side had controlled it completely. Then I rewound the tape and found that for twenty minutes of the second half, the winners barely touched the ball in the opponent's half, and the scoreline only leaned their way thanks to two set pieces. The box score said one thing. The tape said another.

I do not write from the box score when that happens. I write from the tape, and I state plainly that the box score is telling a different story.

That method is slow. It does not give me the fastest posts. It gives me pieces I still dare to reread two years later.

Back to that night. Empty data file. Four hours to deadline.

I could have done what I call "writing for shape". Build the headline first. Pick an angle. Insert some terminology that sounds professional. Publish. Done that way, the piece would have looked entirely normal. It would have had an introduction, a body, a conclusion. It would have had every required section. It might even have been shared.

But it would have contained no information.

That is what stopped me. A piece that looks certain with nothing inside is the most dangerous kind of text, because the reader has no way to tell. They see the shape. They do not see the emptiness.

I remember a night a few years ago, watching a big game and hearing the commentator beside me assert, with total conviction, something I knew to be wrong. He spoke fluently. Confidently. Without a flicker of hesitation. No one in the room reacted. Afterwards I asked him privately what he was basing it on, and he said he had heard it from an acquaintance.

An acquaintance. No second source.

Some rescues no one ever sees, but the team remembers them for life.

In this profession, the rescue does not happen in the final minute. It happens in the moment you decide not to say what you have not verified. It happens in the decision to delete a paragraph because it sounded good but had no basis. It happens across five phone calls in one evening that no one will ever see.

Fans do not see those moments. They do not need to. If everything goes right, they will see only a trustworthy piece of information and a solid piece of writing. The work stays backstage, in decisions that never appear on the page.

In that spirit, I find myself thinking about something else — not quite the same subject, but the same root. In many sports, people talk endlessly about transparency. There is assistive technology. There are big screens. There are systems. Yet when a controversial decision lands, the spectators in the stands are usually the last to learn why. They look up at the screen, wait for an explanation, and typically get nothing.

Transparency that only flows one way is just a slogan. If the technology can speak, why is it not allowed to speak to the people in the stands?

I leave that question here, not to answer in this piece. But it grows from the same root as the empty data file: information flowing in only one direction, with no way for the receiving end to check it.

Back to that night one more time.

I could spend four hours writing a piece. Or spend four hours finding out why the data file was empty. I chose the second. I called the person in charge of the data. It turned out the file had been pulled from the wrong source from the very beginning. A small technical error — the kind that happens daily in hundreds of places.

What matters is this: had I not checked, I could have written a complete piece built on a wrong source. And no one would have known.

I sat down and wrote a note about that evening. The note is not an analysis. It is a reminder. It tells me that in this profession, the worst thing is not writing something wrong. The worst thing is writing something that looks right when you have no basis for it being right.

Every time the mic goes live, I remember how much I once trembled, so that I know how to slow down.

Slowing down sounds easy. But slowing down while the deadline runs and everyone around you has already published — that is a discipline. That discipline does not hand me handsome numbers to show off. It only gives me the feeling that I know what I am saying.

So what changed after that night?

I started keeping a separate file called "things not yet verified". Details I had heard but not confirmed. Metrics I had seen but whose source I did not know. Judgements I believed but could not yet support. The file has one rule: nothing in it enters an article until every item has at least two independent sources.

The file keeps growing. And my articles have grown smaller — in the sense that I make fewer claims, but every claim stands firmer.

Some people tell me I am missing opportunities. In an era when speed is measured in minutes, writing slowly is a disadvantage. I think that is true, and I accept it. Some advantages are not worth the trade. Speed is one of them.

The court never lies; we simply have not been patient enough to hear it breathe.

I have written that line many times, and each time it feels a little truer. The court does not lie. What lies is the skeleton we build and fill with guesswork. What lies is the box score we use without knowing its source. What lies is the feeling of certainty manufactured by the outer shape of a piece of writing.

The court only stays silent. And my job is to sit long enough to listen, rather than write fast enough to publish.

Four hours before deadline, I could have chosen the first path. I chose the second.

To this day, it remains one of the decisions in my career I am happiest with.