The Empty Report and the Whistle That Stayed Silent: When an Analyst Must Say "I Don't Know"

There is a moment in the VAR room that I have carried with me for years. November 2026, at San Siro, minute 56 of Milan against Juventus on matchday 12 of Serie A. Gonzalo Higuaín put the ball in the net, making it 2-0. The slow-motion replay showed him 0.2 metres offside. I sat in front of the screen, my hand resting on the communication button, and I did not press it. The fear of being wrong outweighed my trust in the data. After the match, the refereeing supervisor stood in front of the whole squad to point out my mistake. From that night on, I spent a full month reviewing 47 similar passages of play, and built a 37-point checklist to standardise every decision.

But what I want to discuss today is not the offside line. It is a question that seems far simpler: when is an analyst allowed to say that he does not have enough information to conclude?

In the modern football industry, that question is almost forbidden. Every finished match demands a finished verdict. Every report must have a score, a ranking, a name to praise or a name to blame. That pressure does not come from the pitch. It comes from the newsroom, from the feed, from the whirlpool of social media, where a gap in information is treated as a professional failure rather than a form of honesty.

I have seen this repeat itself many times. A club loses three matches in a row, and instantly there are ten explanations: the manager has lost the dressing room, a star wants out, the defence is too old. None of them is verified. They are conclusions offered simply because the audience needs a conclusion.

That is why I believe the greatest value of an analyst lies not in what he concludes, but in what he refuses to conclude.

Sitting in the VAR room, I learned that an honest empty report is worth more than a full but false one. An analysis sheet where every cell reads "insufficient information" is not a failure. It is a warning. It tells the reader: there is no data here yet, do not build a conclusion on sand.

Thinking of this, I remember the 2026 World Cup. Before France met Argentina in the round of 16, I sat in the Sky Sport Italia studio as a VAR commentator. I had spent days building a model from Kylian Mbappé's last 14 matches in Ligue 1 and the Champions League. His sprint speed reached 36.5 km/h, 2.8 km/h faster than the average Argentine defender. I wrote a 1,200-word analysis arguing that Argentina's defensive structure would break when Mbappé accelerated between minutes 60 and 70. The result: he won a penalty and scored twice, and France won 4-3.

I tell this story not to praise myself. I tell it because behind it lies a detail few people notice. Before I dared to publish that prediction, I checked my model three times. I asked myself: what if my data is wrong? What if Mbappé's speed is just noise? I only allow myself a conclusion when I can defend it before myself. I do not trust my eyes, I trust the slow-motion replay — but the slow-motion replay must itself be checked before I trust it.

This is where I part ways with most people in this profession. A new school of analysis is entering the dressing room: data scientists with spreadsheets, models and algorithms. They bring beautiful numbers. But those numbers are often detached from the real rhythm of a match — the breathing of a player in the 85th minute, the hesitation of a defender with his back turned, the noise of the crowd pushing a team back or lifting it forward. Data does not lie, but data does not speak on its own. It only speaks when placed in the right context.

That is why I always begin each report with a set of checking criteria, not with a conclusion. The order must be: context first, data second, and a conclusion last — if there is room for a conclusion at all.

In 2026, when Serie A returned in empty stadiums because of COVID-19, Milan went through a run of seven matches without a win. Public opinion blamed the attack, and the sale of André Silva to Monaco for 35 million euros. I did not believe that was the cause. I analysed the transition data from the last 14 matches and found that Milan's defence lost up to 42% of its counter-attacking resistance when the crowd noise that drives pressing was absent. The problem was not the striker. It was the system. I wrote a 30-page report for an editor at La Gazzetta dello Sport, proposing a three-stage recovery plan. It was published in full.

I place these two stories side by side because they taught me two different but complementary lessons. Mbappé taught me that good data can see the future. Milan taught me that good data only matters when it sits inside a system. But both taught me a third, most important thing: football is a game of errors, but the winner is the one who knows which errors are worth making.

And the errors worth making are never the errors of haste.

Now let us talk about the hardest part. When an empty analysis is presented, the public's first reaction is always disappointment. They want an answer. They want to know who is right, who is wrong, who will be champion, who will be relegated. The emptiness of information is mistaken for the emptiness of competence. But that confuses two entirely different things: having no answer, and refusing to invent one.

At 60, after more than four decades on the pitch and five years holding a pen, I have learned that professional honour does not lie in always having something to say. It lies in knowing when to stay silent.

Before I blow the whistle, I review myself. That is not a slogan. It is a procedure. When I read back an empty analysis, I do not see failure. I see someone who kept his discipline: who did not invent a club, did not pin a story onto a player, did not manufacture a narrative just to fill a page.

What worries me is that today's media ecosystem rewards the opposite. It rewards speed, certainty, a decisive tone. A bold headline always travels faster than a cautious one. A confident wrong prediction is remembered more than a correct admission that we do not yet know. This is a distortion of the information market, and it has real consequences.

But I remain optimistic, in the cautious way of a man whose trade is checking.

Every judgement deserves a second look, including the judgement of data. And the first thing to review is not the data. It is the motive of the person making the conclusion. If the motive is to fill a gap, then that conclusion was rotten before it was written.

So what will change? I think of a new generation of analysts, trained not to always have an answer, but to tell the difference between a gap that needs filling and a gap that deserves respect. I think of newsrooms that allow a report marked "insufficient data" to be published without treating it as a disgrace. I think of readers who understand that honesty sometimes looks like silence.

I reviewed 47 passages of play in one month only to build a 37-point checklist. Not because I enjoy complexity. Because I am afraid of becoming the man who offers a conclusion without a foundation. That empty analysis, with every cell reading "insufficient information", is not a meaningless page. It is a reminder that in a game shaped by errors, the one who knows he is not yet ready to judge has taken a step ahead of the one who blew the whistle too soon.