When the Scouting Report Comes Back Empty: Why the Best Data Readers Are the Ones Who Know How to Refuse a Conclusion

On a January morning, I sat in front of my screen with a file I had waited two days to receive. It was the scouting report I had requested for a game I was about to call live. I opened it, and inside was a numbered skeleton — headers, table cells, sections labelled tactical analysis, player data, salary structure — but every one of them was empty. No team name. No player name. Not a single number. Only the faint residue of template instructions left inside the frame, lines like identify from the information points above, while above there were no information points at all.

I sat still for about five minutes. In this profession, the first reflex is always to fill the gap. You know the feeling: the mic is on, the feed is live, the producer is waiting, and you have to say something. And because I have watched basketball for thirty-six years, my memory will automatically supply material — a similar possession, a similar player, a similar game I once saw. The trap here is not ignorance. The trap is having too much knowledge, enough that you can construct a story that sounds perfectly reasonable out of thin air.

I closed the file and called the data team. Nothing at all? I asked. There was a pause on the other end, then: The source wouldn't load. The system ran but returned empty. Sorry.

I told them this might be the best thing that happened to me all week.

The context of a profession that lives on evidence

There is something outsiders rarely understand about professional sports analysis: it is much closer to auditing than to emotional commentary. In the Miami studio where I work, every pre-game analysis piece must pass a minimum process. First, identify the source. Then extract verifiable events. Then route them to the correct domain — basketball, football, athletics, swimming. Only then does the deep analysis begin, where I put pen to paper.

The third step, domain classification, was the only step that worked that day. The machine knew this was basketball. It knew nothing more. And that made me think about something that has haunted me for years: the difference between a routing system that runs correctly and content that actually exists.

When I entered the profession, I was a data sceptic. I used to think xG was meaningless, until it explained why we lost. In 2026, at forty-three, I publicly rejected the expected-goals model on Miami television. I called Josef Martinez a lucky ball-striker when he scored nineteen goals in twenty games for Atlanta United. A twenty-seven-year-old colleague opened a chart and showed me Martinez's xG reading of 0.85 expected goals per ninety minutes — the highest in MLS that year. I had no comeback.

But the real story of my career is not that I was wrong about xG. It is how I responded to being wrong. I began keeping a handwritten match diary: one page per game, with four columns — events on the pitch, player decisions, observed metrics, and my own judgement. From then on, every analysis piece I wrote had to contain a section I called weighing intuition against evidence.

And then 2026 arrived.

The Belgium mistake and the price of prophecy

I was forty-four, invited by a Vietnamese television network to commentate the World Cup in Russia. On the pre-match show before the quarter-final between Belgium and Brazil, I declared that manager Roberto Martinez's inverted full-back system would collapse under Brazilian pressure. I predicted Brazil would win 2-0. I said it decisively, with total confidence, in front of millions of viewers.

Kevin De Bruyne scored in the thirty-first minute, precisely from the advanced inverted full-back position I had just called a mistake. Belgium won 2-1.

Thirty days later, I sat at home and rewatched all seven of Belgium's matches at that tournament. Not to find excuses. I watched to understand what I had missed. And what I missed was not a tactical detail. What I missed was a larger truth: Belgium 2026 taught me that a golden generation does not automatically produce victory. A talented collective can win or lose for reasons that never appear in a box score. Belgium's fault was not in the attack; it was in heads already full of victories.

From then on I set myself a personal rule, and I tell young people entering the profession to treat it as a mantra: never speak unless you have rewatched the tape. My articles began with the line After rewatching the match tape, and I always recorded the exact minute an event occurred rather than writing from vague feeling.

I still remember the sensation of realising I had prophesied wrongly. Not shame. It was the feeling of a craftsman realising he had used the wrong tool of his trade. I do not prophesy. I had spoken like a prophet, and that is the thing I swore never to repeat.

The database built inside the storm

If you want to understand why an empty report made me stop cold, you have to understand how I built my database.

2026 was a strange year. The global pandemic suspended MLS for one hundred and eighteen days. Stadiums stood empty. I was pushed into a Miami studio and realised something painful: the thing that had saved me for twenty years — a tone of delivery built on crowd atmosphere — was entirely useless. An empty stadium removes the roar, and I had nothing left to lean on.

The instinct of a disciplined, rigid person is to fall back on the old method. I rewatched all four hundred MLS matches from 2026 to 2026. I built individual profiles for two hundred and fifteen players across twelve criteria. Sitting in a quiet room watching stadiums with no one in them, I gradually realised that a crowdless arena is an experiment, and we were the lab rats. It revealed how fundamentally lonely basketball and football are once the human noise is stripped away.

From that database I found that the high-speed running distance of Nani — Orlando City's key player — had dropped thirty-two per cent. Based on that number, I accurately predicted his decline the following season. Not because I am good at reading people. Because I had counted.

This is where I have to state clearly something I believe with my whole career: data is only a map, and the match is the storm. A map never replaces the storm. But when the storm has not yet arrived, the map is the only thing you have to keep from walking into the whirlpool.

Weighing intuition against evidence

I know my writing sounds dry to some people. But let me explain why I write that way, with a concrete example.

When I was a young commentator, I built all my judgements on memory. I remember back then this team used to win by… — that was a sentence I used constantly. The problem is that memory is distorted by emotion. You remember the beautiful goals and forget the ninety tedious minutes before them. You remember the moment of brilliance and forget how the whole team ran to create that moment.

The day I understood this clearly was when I reconstructed a match from memory and then compared it with the tape. I remembered my team playing with blazing attack. The tape showed they had less possession, fewer shots, and won through a set piece. My memory had rewritten the match into the script I wanted.

Since then, my process has been a three-step investigation. Step one, put the numbers first. Step two, actively place a counter-example on the scale — find a match where the numbers contradict what I believe. Step three, only then conclude with a conditional proposition: the data suggests… but the match may still…

I rarely use exclamations in my work. Every number must be anchored to a specific moment on the court. If it cannot be anchored, that number has not earned the right to appear.

And I must also tell you about the time I changed my view entirely. It took me two weeks to believe in data, but it took twenty years to understand that it is still not enough. That is why I no longer write this team is certain to win the title. That sentence turns a data system into a horoscope. Timing is the one thing that never appears in a box score. You can know how strong a team is, but you never know whether they will be strong on that particular night.

The empty report and the trap called saying something anyway

Back to that January morning. I had a decision to make: what to say on a live broadcast when my scouting report was empty?

There is a version of me — the twenty-five-year-old version — who would have filled the gap with whatever memory supplied. He would have talked about this team's style, about that player, about a tactical system that sounded very convincing. And he would have been half right. The danger is that half right sounds like fully right, as long as you say it confidently enough.

But I had learned something else. In analysis, the most dangerous failure mode is not being wrong. The most dangerous failure mode is inventing a plausible-sounding story when there is no evidence, then placing it on the same table as conclusions that were verified. Readers cannot separate the two unless you separate them yourself.

I decided to say it straight on air: My report today is empty. The source would not load. I will only comment on what I see directly on screen, and I will not offer any prediction about the result.

You might think that made me look weak. But hear me out. An analyst who says I do not know when he genuinely does not know is protecting the value of the twenty-five times he previously said I do know. If you fabricate when you have no data, then your data-backed conclusions also lose value, because no one can trust that you verified anything at all.

This is the point I like to call the discipline of closing down when evidence is missing. In the world of people who build systems, this is called fail-closed behaviour. A good system must be able to say there is not enough data to answer rather than always returning an answer that sounds reasonable. Because a system that always answers is a system that is sometimes wrong without anyone knowing.

For someone in my line of work, this boundary matters more than any model. I do not have a machine running behind me telling me the data is empty. I have to build that machine myself.

The counter-intuitive angle: silence is a skill

We tend to praise people who always have something to say. In sports media, a good commentator is, by popular definition, someone who fills every silence with analysis. Silence is treated as failure. But after thirty-six years, I believe the opposite: the hardest skill of an analyst is not speaking, but knowing when not to speak.

Think about the transfer window. This is the season when noise completely drowns out signal. Hundreds of rumours appear every day. Release-clause structures and wage budgets are the real story, yet most fans give their attention to a single unsourced tweet. And our profession largely responds by pumping more noise, because that is what generates clicks.

I have learned from my own mistakes that a transfer report without a source has no value. I am not a prophet, and I am not a spokesperson for rumours either. What I can do is rank the credibility of each piece of information by evidence, track the money, the contracts, and the movements of agents. That is unglamorous work, but it is real work.

There is a trap I set for myself here: over-generalisation. When you summarise a complex tactic or a long tournament, it is very easy to slide into sentences like the trend of the entire sport is changing without anything backing it. I force myself to anchor every claim to a specific match or a specific stretch of tape. If I cannot anchor it, I cut it.

The second trap is language inflated by the market. Transfer moves and emotional matches tempt us into words like redefining or revolution. I have to remind myself to replace those words with measurable metrics. A real impact metric never calls anyone a revolution. It just says how many expected points this player contributes per forty-eight minutes.

This is what I want to say to young people hoping to enter this profession. If you only have one skill, choose the skill of refusal. That skill will stay with you longer than any title. Titles come and go. Discipline stays.

A database proven right

So you can see that refusal is not only a moral posture, let me tell you about a time I chose the other way.

World Cup 2026 in Qatar. I was forty-eight. When every television network in the world treated Morocco as a doormat, I was the only person at the Miami station to predict they would reach the semi-finals. Colleagues called me a prophet. I only replied: I do not prophesy. I simply read the data correctly.

My basis was very specific. Across five group-stage matches, Morocco conceded exactly one goal. And that goal was an own goal by themselves in the match against Canada, not a goal conceded from an opponent's attacking effort. It was a small detail, and small details are where data lives.

When Morocco beat Spain on penalties in the round of sixteen, the database I built during those empty-stadium days in 2026 paid off. But I must be honest: that was not a supported prophecy. It was a conditional proposition. I said that if the data held, Morocco would likely go far. I did not say they were certain to reach the semi-finals. That is the difference between data and a horoscope.

You see? I did not become trusted because I was right about Morocco. I became trusted because I always state my level of certainty. And precisely for that reason, when the empty report appeared before me on that January morning, I was not afraid to say two words: I do not know.

The lesson of an empty skeleton

I still keep that file. I named it the empty report, and I use it as a test for myself every month.

Why? Because it embodies the greatest temptation in this profession. That temptation is not laziness. The temptation is intelligence without a stopping point. A person who reads a lot, watches a lot, remembers a lot can construct a complete story about any match, whether or not that match ever happened. And the frightening part is that the story will sound entirely real.

An empty stadium does not remove the shouting; it only reveals how fundamentally lonely football is. I learned that during the pandemic season, and the lesson came back to me when I looked at the empty report. When there is no crowd, you must rely on the content itself. When there is no data, you must rely on your own honesty.

I once thought a good analyst was someone who could talk about everything. Now I think differently. A good analyst is someone who can distinguish between what he remembers and what he has verified. A crowdless arena is an experiment, and we are the lab rats. And the lab rat that learns the most is not the one that runs fastest, but the one that realises it is inside an experiment.

There was one time I was challenged on air for daring to say I did not believe a transfer rumour. The host asked: So what do you suggest we report? I answered: Report that there is nothing to report yet. It was a boring-sounding answer, but it was honest. And later, when the rumour exploded in several different directions, my viewers were not abandoned by a false promise.

It took me two weeks to believe in data, but it took twenty years to understand that it is still not enough. And I will probably spend the rest of my career learning how to say there is not enough data without feeling like I have failed.

What I am watching next

Thirty-six years in this profession have taught me one thing: fans do not need another person who always has an opinion. They need someone who tells them when a story is not yet ripe enough to tell.

So if you follow me in the period ahead, you will see one common thread. Every time I offer a judgement, I will show you where the evidence is. Every time I withhold a judgement, I will say clearly why. And if either of those makes me seem less exciting than others, I accept that. I am not in the business of entertaining with predictions. I am in the business of reading data, and sometimes reading correctly simply means saying two words: not yet known.

The question I leave you with is not which team will win the title. The question is this: when your own report comes back empty, will you invent a story, or will you have the courage to wait until the match tells its own story?

I choose to wait. The map may be empty. But the storm always comes, and when it comes, you will find me ready to read it.