The Slow-Motion Replay With Nothing In It: Confessions of a VAR Analyst

Sitting before a screen in a small apartment overlooking the Naviglio Grande in Milan, I opened a thirty-page report. Every cell was empty. Every field read the same phrase: "N/A — insufficient information." No title. No club. No manager. No players. No date. No source. I read all thirty pages in silence, then read them a second time, exactly the way I review any replay before blowing the whistle.

This time, the slow-motion replay had nothing to show. And I realized: this was the most honest document I had read in years.

To understand why a blank sheet kept me sitting there so long, you need to know the road that brought me here. In 2026, after graduating from journalism school, I began my career at a football newspaper while serving as a Madrid-based correspondent for an international sports publication. I was twenty, and I believed writing was a craft of storytelling, and that a good story always sits where you want it to sit. I was wrong. But it took me more than thirty years to understand exactly where.

In 2026, I hosted a late-night football program and worked as a producer. Eight years staring into an editing suite, watching how an event gets trimmed into fifteen gripping seconds, taught me something obsessive: most of what audiences call "the truth" is simply the most heavily edited version. Nobody watches a match. They watch a version of the match. And that version is usually chosen for them.

In November 2026, at San Siro, Milan hosted Juventus on matchday twelve of Serie A. I sat in the operations room as the VAR assistant. In the 56th minute, Higuaín scored to make it 2-0. The feed showed me that the Argentine striker had been 0.2 meters offside in the buildup. Twenty centimetres. The gap between a valid goal and a disallowed goal was shorter than the span of a hand.

I hesitated. I was afraid of being wrong. I did not recommend a review. The match ended 0-2. Afterwards, in the debrief, the referee supervisor criticized me in front of the whole team: "You were so afraid of being wrong that you let the wrong thing happen."

That night at home, I replayed the incident thirty-eight times. I was not looking for a justification. I was looking for why my eye faltered at the exact moment it needed to be sharpest. Over the following month, I reviewed forty-seven similar incidents across competitions. I built a checklist of thirty-seven criteria, from camera placement, frame rate, and the shoulder angle of the player to the ball's landing point and even the condition of the pitch. Not so a machine could decide for me. So that I would never again issue a judgment without a basis.

Since then, every piece I write runs like a decision tree. Set out the situation. List the data. Cross-check. Only then conclude. And the conclusion always stays open, to be contested. Before blowing the whistle, I review myself.

In 2026, at the World Cup in Russia, Sky Sport Italia invited me to commentate VAR for France against Argentina in the round of sixteen. Before kick-off, I built a model from Kylian Mbappé's fourteen most recent matches in Ligue 1 and the Champions League. His peak sprint speed reached 36.5 km/h. That was 2.8 km/h higher than the average speed of Argentina's defenders over the same span. I wrote a 1,200-word analysis concluding that Argentina's defensive structure would break when Mbappé accelerated around the 60th to 70th minute, once the back line had sagged under the volume of running.

The result: Mbappé won a penalty and scored twice. France won 4-3. The piece was shared more than five thousand times. Many called it a prediction. I dislike that word. It was not a prediction. It was simple arithmetic that people were too lazy to do.

Mbappé did not appear out of thin air. He was predicted by my model before the world knew his name. But my point is not that I am clever. My point is this: when the data is already there, surprise is usually just a prettier name for laziness.

In October 2026, Serie A returned in empty stadiums because of COVID-19. Milan went seven matches without a win. Public opinion blamed André Silva, who had just been sold to Monaco for thirty-five million euros. The story was told neatly: lose a striker, lose your attacking power. It sounded reasonable. And it was entirely wrong.

I analysed transition data from the previous fourteen matches. The result: Milan's defence lost 42% of its counter-attacking resilience once the crowd noise that drove the pressing lines was gone. The problem was not the scorer. The problem was the operating mechanism of the whole shape once an environmental variable nobody considered — the sound of the crowd — disappeared. I wrote a thirty-page report to the La Gazzetta dello Sport editor proposing a three-phase recovery plan. It was published in full.

Milan's collapse did not begin with the pandemic, but with the cracks the pandemic merely made visible.

Those three stories — 2026, 2026, 2026 — share one structure. An event seen by public opinion through one layer. I looked through four: rules, data, context, and system. Not because I am smarter. Because I stand where nobody looks. From the whistle, you see the blind spots that players, coaches and terraces all miss.

And then, one day, I received a blank report. Every field N/A. Nothing to analyse. And I understood: this was the greatest test the profession could set for me.

The hardest thing for an analyst is not finding the answer, but recognizing when no question yet deserves one.

The report described a two-stage process. Stage one was supposed to deconstruct a source article into information points, entities, author stance, time sensitivity. But when stage two ran, every field was empty: no title, no source, no summary, an empty list of information points. In other words, stage one had failed silently. It did not throw an error. It just returned zero.

People assume explicit errors are what to fear. Wrong. In data systems, explicit errors are easy to catch. The danger is the silent failure, the one that returns a result that looks clean but holds nothing inside. A field reading "0" looks more professional than a red flagged cell. And because it looks professional, people start colouring it in.

The report did one thing I respect: it refused to fabricate.

It had a beautiful nine-part template in its hands. Tactical and technical analysis. Club finance and the transfer market. Results and public-opinion cycles. League landscape and team positioning. Rules and governance. Management and the dressing room. Risk profile. Media narrative and expectation. Football industry transmission. Nine boxes. Each could hold three thousand words. And into every box it typed the same sentence: insufficient information.

Do you know how hard that is? I have worked in this trade for forty-four years. I know the pressure of a blank page. I know the tingling of fingers on a keyboard, wanting to type a name, a number, a story, just to make the page look alive. In my industry, silence is treated as failure. To write nothing is to be nothing. And nothing does not get paid.

That is why most modern football analysis is rubbish, beautifully presented.

Look at how a match is retold. After every round you get hundreds of articles. They resemble each other strangely, because they are born of the same template and the same fear: the fear of saying "I do not have enough data to conclude." The writer picks a winner, assigns it an "identity," finds a few confirming numbers, and packages it as truth. That method always produces a product. It just does not produce a fact.

I have learned to recognize that kind of writing. It begins with an adjective. It uses "character," "desire," "class." It never states its sample size. It never asks: where does this data come from, how long did it take to gather, and is it large enough to say anything at all?

A data analyst can walk into a dressing room with a beautiful spreadsheet. But if that spreadsheet does not match the actual rhythm of the match on the pitch, it is just paper. Their conclusions often detach from fitness, fixtures, and the psychology of eleven men breathing hard. I have seen it. I have seen a model predict that Team A will press high, while Team A had played three matches in seven days and their legs were dead by the twentieth minute.

Every judgment needs a review, including the judgment of data.

There is a naive belief spreading through the analytical world: that with enough numbers, the truth will simply appear. More data, fewer arguments. That is wrong at a basic level of logic. Data is not truth. Data is raw material. Truth is what gets forged from that material through a verifiable process, and no process is immune to error.

I am one of the few in this trade who rarely uses the phrase "football intuition." Not because I despise feeling. Because I know my intuition has been wrong. It was wrong at San Siro in 2026, when I was afraid and stayed silent. Intuition is not a sense. It is an unverified memory.

I do not trust my eyes, I trust the slow-motion replay.

But this is where my story gets more complicated, and where I want to argue against my own camp. The camp of the data believers. The camp I belong to.

Because when you trust data absolutely, you commit a subtler error. You turn data into a judge, when it should only ever be a witness.

I have watched young colleagues build conclusions from tiny samples without blinking. Three matches. Five matches. A run of seven without a win is called a "systemic crisis." A player scoring in four consecutive games is called "in form." They speak with a confidence that makes you forget their foundation is paper-thin.

I learned this from Milan's collapse itself. I analysed fourteen matches and found a notable correlation between the loss of crowd noise and counter-attacking defensive capacity. But I know this well: correlation is not causation. Fourteen matches is still a small sample. There may be dozens of variables I did not measure. The only honest way is to state that in the piece, rather than hide it under a catchy headline.

The problem is that readers do not like caution. They want a statement. They want to know who is right and wrong, who is good and bad, who should be sold. And because they want that, the market supplies it. Not from the honest, but from the stubborn.

This is the biggest blind spot of the entire modern football analytical industry: it rewards confidence, not accuracy.

A piece saying "I do not have enough data to conclude" will not be shared. A piece saying "this team will win the title" will be shared five thousand times, even when it is wrong, because people do not remember the times someone was wrong. They remember only the times someone dared to speak.

And I understand, more than anyone, the allure of daring to speak. I have lived it. In 2026, when my Mbappé piece was shared widely, I felt something dangerous: temptation. The temptation to conclude faster, harder, more certainly next time. The temptation to become a man who is always right.

But I am a referee. And a good referee is not the one who makes the most decisions. It is the one who knows when no decision is needed at all.

On the pitch, a bad referee is one who blows the whistle too often. He interferes with the game, breaks the rhythm, makes himself the centre of attention. A good referee is nearly invisible. The match flows through him without being stopped. Occasionally, when truly needed, he appears, resolves a situation, and disappears again.

An analyst's job is the same. But in my journalism, people are rewarded for blowing the whistle constantly. Every day must have a whistle. Every matchday must have a verdict. Silence is treated as emptiness.

The blank report I received was the only thing that day brave enough to stay silent.

Technology did not kill football; it killed blind faith.

VAR arrived promising something simple: the truth will appear when you watch it again. But anyone who has sat in an operations room knows that is not true. Technology does not remove controversy. It merely shifts controversy to another layer. Before, people argued over whether the referee had seen it. Now they argue over which frame is the right frame, which moment is the moment the ball left the foot, which line is the correct line, and who decides.

I have watched thousands of slow-motion incidents. And I can tell you something few want to hear: most incidents do not have a single truth. They have a grey zone, and inside that grey zone, someone must choose a convention. Technology does not make that choice. Humans make it. Then humans hide that choice behind a technical curtain and call it objective.

Here I differ from most of my colleagues. I do not think VAR simply makes football fairer. I think VAR makes football more transparent about its own fallibility. Previously, a refereeing mistake vanished inside the match. Now it is recorded, reviewed, and debated for three days. Whether that is good or bad does not matter. What matters is that it forces us to face a truth football long concealed: that judgments are never entirely clean. No goal is entirely clean under the laws, only goals that people agree not to review.

And for the same reason, I never defend my fellow referees unconditionally. I write with the eye of a supervisor, not the loyalty of a guild member. When my colleagues are wrong, I say they are wrong. Not to bring them down. Because if I defended them emotionally, I would betray the very thing I believe: that the laws stand above people, even when that person is my friend.

I will say something many in refereeing dislike hearing. In my career, most refereeing controversies did not stem from referees not knowing the laws. They stemmed from a refereeing management system with no consistent standard. An identical incident is whistled on matchday one and ignored on matchday thirty. Players do not go mad over a wrong decision. They go mad over inconsistency. People can accept a harsh law. They cannot accept a law that changes with whoever holds the whistle.

Diagnose the system, not the individual. I tell this to every young editor I have worked with. If you want to write about a mistake, write about forty-seven similar incidents and show that this one is a sample inside a larger pattern. A player missing a chance is not a story. A development system that fails to teach players how to decide in the final three-quarters of a second is a story.

In Italy I lived five years and wrote through all of them. An Englishman writing about Italian football for Italian readers. That position has a strange advantage: I do not belong. I have no childhood club to defend. I have no legend I dare not criticize. Every time I sit down to write, I must rebuild the context from scratch, like an outsider who must relearn the language before speaking.

But I also know my limits. Some things about Italian football I will never fully understand the way an Italian does. I cannot fully feel the weight of a derby when I did not grow up inside its noise. That is why I always leave a gap in my analysis, a space for what I do not know. Humility is not a virtue. It is a technical tool.

And this is where I want to return to that blank report.

There is a structural temptation in my trade: the temptation to fill. When you have a mould, you want to fill it. When you have nine boxes, you want nine boxes full. When you have a page, you want it no longer white. It is a natural reflex, and it is the enemy of truth. Because truth does not care about your mould. Truth does not care whether your page looks beautiful.

In football, there is a moment every analyst fears: the moment they look at a match and have nothing to say. And their instinct is to invent something. Invent a "tactical identity" when both teams played in a fog. Invent a "dressing-room crisis" when the only thing that happened was three unlucky defeats. Invent a "rising talent" after two assists.

I have invented. Not by saying something false, but by saying too much. Speaking when I should have stayed silent. Concluding when I should have waited. Decorating with language when I should have posed a single question. And I learned that this, though no one detects it, is still a betrayal. Not of the reader. Of the trade I chose.

I am not sure I have become a better writer after nearly half a century in the trade. But I am sure I have become a more honest one. And in this trade those two things are not the same. Many fine writers lie every day, in a smooth voice and with eye-catching headlines. They are not punished, because readers have no time to verify. But the truth has time. The truth is only slow, it does not forget.

I have learned to read a spreadsheet the way I read a slow-motion replay. Not trusting my feelings. Not trusting my first impression. Rewinding. Cross-checking. And only when three independent layers of data point the same way do I allow myself a declarative sentence. If not, I write a question. An honest question is worth more than a dishonest answer.

The problem with modern football analysis is not a lack of data. We have more data than any generation before. We have xG, PPDA, progressive passes, pressures, heat maps, sprint speeds, and thousands of other metrics. The problem is that we lack a culture that knows when to be silent.

I read new analyses every day. They are longer, prettier, more data-rich. But they are not more honest. Because honesty does not lie in the volume of data. It lies in what you dare to say when the data is insufficient. It lies in the pause between two sentences. It lies in the space you leave empty.

Football is a game of errors, but the winner is the one who knows which errors are worth making.

And here is the last paradox I want to leave with you.

In life, silence is often treated as weakness. In analysis, silence is power. A writer can say anything. That is easy. The hard thing is to stay silent when you have nothing to say, and to hold that silence against the pressure of a blank page, of an editor waiting, of a reader needing a name to believe or to hate.

That blank report taught me something forty-four years of experience had never fully taught. It did not teach me with an argument. It taught me with a refusal. It refused to invent a title. It refused to fill a cell. It refused to turn emptiness into a product. And that very refusal produced a different product: trust.

I trust a report brave enough to say "I do not know" more than one brave enough to say everything.

At sixty, living in a city far from home, doing a job most colleagues treat as a technical tool, I have reached a simple conclusion. My job is not to deliver answers. My job is to protect the quality of the question. When the question is right, the answer usually becomes less important. When the question is wrong, every answer is a lie, whether it is right or wrong.

I reviewed the blank report one last time. Thirty pages. Not a name. Not a number. Not a conclusion. I printed it, stamped the date, and filed it in a drawer of its own. Not for storage. To remind myself. Whenever I sit before a big match and feel my fingers tingling to type a declarative sentence, I open that drawer and look at thirty white pages.

And I think of the only thing I know for certain after nearly half a century of watching football run across a screen: truth does not need to be defended with beautiful language. It only needs to be treated fairly enough to dare to appear. And sometimes the fairest way to treat truth is to give it a pause in which it can say for itself that, tonight, it has not yet arrived.

Before blowing the whistle, I review myself. This time, I looked at the blank replay, and I blew the final whistle. There was nothing to review. And that was the most honest thing I could do as an analyst — and the most honest thing any of us can do when asked about something we do not know.

When the slow-motion replay ends and nothing remains on the screen but the grey of an empty frame, people usually switch off. I stayed a few minutes longer, in my apartment in Milan, listening to the street drift in through the window. And I understood that honesty is not a moral gift handed to the well-intentioned. It is a skill forged through thousands of hesitations, thousands of chances to lie and a refusal to take them, thousands of times you look at an empty cell and let it stay empty.

My career began with a mistake at San Siro. It may end with an empty space in Milan. Between those two moments lies a whole life of learning to tell the difference between what I want to see and what is actually in front of me. And if there is one lesson I would leave to anyone still sitting before numbers, it is this: when you are unsure, do not write a declarative sentence just to make the page less white. Write a question. Let the reader look with you into that empty space. Because readers do not need someone who is always right. They need someone who does not deceive them.

And so the thirty-page blank report became the greatest lesson the trade ever taught me — taught by refusal, taught by silence, taught by the very thing I always claimed to pursue: the truth, reviewed many times over, and left untouched when it is not yet ready to speak.