When Tennis Data Goes Silent: The Line Between Analysis and Invention

My second monitor lit up at 1:40 a.m. Liverpool time. In the analysis file the system had sent back, the article title was blank. The source name was blank. The information-points field, the place that should have held every scrap of raw data from a tennis match, from first-serve percentage to break points won, was blank too. Nine analysis frames had been built, room for nine layers of conclusion, and not one line to fill them with.

I sat still for a long while before touching the keyboard. This trade taught me how to read second-serve points won, how to build an Elo model for hard courts, how to split a forehand into four separate variables. Nobody taught me what to do when the spreadsheet is empty and the editorial clock is still counting down.

That night I nearly wrote a very good piece. I had the structure, I had the voice, I had three opening lines strong enough to make a reader nod along. The only thing I lacked was the truth.

Empty data is not rare in tennis. A tour-level match generates thousands of data points across each rally: serve speed, return position, number of steps, time between serves. Hawk-Eye and the point-data providers pour all of it into a pipeline, and that pipeline hands it on to analytics firms, bookmakers, broadcasters, and writers like me.

Any pipeline can jam. A dead link, a paywall, a source that posts only images, a parsing error at midnight. Any small failure is enough to turn a match into a blank file. The problem is not that the pipeline jams. The problem is how people react when it does.

In tennis, that pressure is heavier than in most sports. Football gives you ninety unbroken minutes to tell a story. Tennis does not. Every point is a closed unit, every game a short essay, every set a chapter with a clear ending. That fragmented structure gives a writer the constant sense of holding enough pieces to assemble a verdict. That sense is very easy to be fooled by.

I have been a victim of that sense myself. In 2026, as an intern in Liverpool, I charted the entire knockout stage of the World Cup in Russia. In the Spain-Russia match, my team had 71.4% possession, completed 1,029 passes, and produced a mere 0.9 xG across 120 minutes. I predicted Spain would win. They lost the shootout 3-4. I was wrong, and it took me a week to understand that the possession figure was telling a very different story from expected goals.

What 2026 taught me is something I still carry to the desk: data does not speak for itself. It only answers the question it is asked. And when there is no data at all, it answers nothing.

When the input data is empty, every conclusion drawn from it is a product of imagination, not of analysis.

The frightening part is that the imagination of someone who has worked long enough always looks convincing. I know roughly what percentage of first-serve points a strong server wins in a deciding set. I know an indoor hard court dulls the effect of heavy topspin. Stitch those pieces together and I can write a thoroughly professional-sounding analysis of a match I never watched a single point of.

In 2026, when the pandemic emptied the stadiums, I worked for a tactics consultancy. In that June's Merseyside derby, Liverpool drew 0-0 with Everton. I compared Liverpool's PPDA before and after the crowds vanished: from 9.8 up to 11.5, meaning the attack was pressing far less effectively. The home side's high-intensity running dropped 4.3% in the noise-free environment.

I wrote a report showing that the crowd is a data variable, one that directly shapes fitness and pressing intensity. But it took me another two weeks to realise I had nearly made a bigger mistake: using the empty stands to explain everything, including things it cannot explain.

The empty stands taught me a cruel lesson: noise never appears in a spreadsheet, but it is always there in every heartbeat.

In 2026, I was assigned to analyse Leicester City's miserable run of fifteen matches. The club had seven injured centre-backs, Jonny Evans among them for twelve games, and their expected goals conceded rose 24%. Nobody wanted a system-based explanation. People wanted to hear that the club was unlucky. I refused that conclusion and dug into the defenders' running distances: 8.2 km per match on average, falling 12% after every game with less than 72 hours of rest.

An injury cluster is not a curse; it is a map that reveals the depth of a system being worn down.

The result was an index I proposed, called expected injury load. But the thing I remember most is not the index. It is the feeling of being allowed to say I did not know. Across those fifteen matches, there were games where the data was not enough to conclude anything. I wrote exactly that in the report, and it was the first time a client paid me to hear that I did not know.

Back to tennis. In the 2026 season, when the US Open was played in stands without a single soul, Dominic Thiem came back from two sets down against Alexander Zverev to win the title. Many commentaries afterwards called it a final of character. I do not dispute the label. But I wonder: with no crowd, what exactly did Thiem lean on to complete that comeback? With no roar to carry him, what kept him standing in the fifth set?

I have no data-driven answer, and I chose not to invent one.

This is where sports analysis writing is in danger. More data, more articles. More articles, more pressure to reach a verdict. And more pressure, less room for honest silence.

The betting industry has turned uncertainty into a product to sell. Every number I publish can be picked up by an algorithm and turned into a price. I cannot control that. But I can control whether I invent the number in the first place.

In meetings, I often remind colleagues: correlation is not causation, and an unvalidated model is just a hypothesis written in expensive ink. Some say I am pessimistic. I think otherwise.

Error is the most disagreeable friend I have, but the only one who never lies to me in the meeting room.

For tennis fans in Vietnam, the ones who stay up all night following the big tournaments, that honesty matters even more. You stayed awake to watch the real match. You deserve an analysis written from that match, not from the imagination of someone sitting six time zones away.

The blank analysis file was sent back to operations that night with a short note: source unretrievable, needs a re-run. No article was published. No conclusion was issued.

I do not think I lost that night. An analyst only truly loses when he issues a conclusion he has no basis to believe.

Every match is a hypothesis. I only write when I have enough data to disprove myself.