The Empty Spreadsheet in F1: When Data Stays Silent but Conclusions Still Get Issued

November, London, three in the morning. Four screens in front of me broadcast four different races, the commentary tracks overlapping like an orchestra out of time. To my left, on an old laptop, sits a nine-page spreadsheet formatted neatly: bold headings, ruled tables, every sub-section with its own bullet points. I hit refresh. The central column — the one that should hold the raw information points — returns zero. It is not a network failure, not a server crash. The spreadsheet is open, the cells are lit, but inside them there is nothing. Every row repeats the same sentence: "N/A — insufficient information." What stopped me was not the emptiness, but its form. That document looked perfect. It contained all nine analytical dimensions: car technicalities, race strategy, team and driver status, competitive landscape, governance and rules, the driver market, risk profile, public narrative, and the industry transmission chain. It had tables, text-based charts, a "conclusion" section and "recommendations." Anyone skimming it without reading closely would assume it was a complete deep analysis. Yet not a single line held real information. The whole nine pages said one thing: someone handed me an empty input, and I built a skeleton waiting for content to pour in — and the content never arrived. I sat staring at it for a long time. At sixty, I have seen enough data incidents not to be surprised by a wrong number. But this was the first time I saw a system return a result that was perfect in form, hollow in content, and still walk forward confidently as if it had just done something useful. It felt like receiving a medical report printed on fine paper, with a red stamp and a signature, but the diagnosis section left blank. You cannot sue anyone over pretty paper. You can only ask yourself: how many times have I, and this entire sports world, read a pretty document and forgotten to check what was inside. Data is never in a hurry, but people always are. That empty spreadsheet is the clearest proof of it. It was not rushing. It was simply silent. It was people who rushed to assign that silence a meaning, a conclusion, a prediction. To understand why an empty spreadsheet is more dangerous than a wrong one, one must talk about how the sports world has built data over the past fifteen years. When I started as a transfer market administrator at a London sports consultancy, my job was far simpler: watch tapes, call scouts, and trust my eyes. Today, every major club runs at least three parallel data streams — match event data, positional tracking data, and physical data from wearables. Those three streams flow into one pipeline, are processed across several stages, and become reports for the coaching staff, the sporting director, the owners. That multi-stage structure is precisely where incidents are born. A typical analytical pipeline splits into two tiers. The first tier reads raw documents — an article, a scouting report, meeting minutes — and breaks them into atomic information points: who, did what, when, at what number. The second tier takes those information points and goes deep: technical, strategic, market, and risk analysis. The iron rule is that the second tier can only reason from what the first tier has supplied. No information points, no analysis. That is a correct principle, and it is also the principle my system just violated in a strange way: it still produced nine pages of output even though the first tier returned zero. I call this "pretty spreadsheet syndrome." In sports analytics, we are used to being wary of bad data — a miscalculated xG, a skewed speed measurement, too small a statistical sample. But we are almost never wary of empty data. Because empty data does not produce a wrong number for us to catch. It leaves only a blank, and a blank is more easily filled by guesswork than by an admission. I remember 2026, when I spent three months tracking Brentford — a Championship club famous for using data to sign cheap players. I analyzed 1,247 players from 15 European leagues, filtering down to 38 potential targets based on xG, PPDA, and chance creation. Every one of those 1,247 rows had a clear provenance: a specific match, a specific minute, a specific play. When Brentford signed Ollie Watkins from Exeter for £1.8 million and later sold him to Aston Villa for £28 million, I realized data was not merely an auxiliary tool but a strategic weapon. But the bigger lesson lay elsewhere: Brentford never acts on an empty cell. They wait until that row is filled, verified, and cross-checked against at least two independent sources. Brentford does not read the future; they simply read data more carefully than everyone else. Back to the empty spreadsheet that night. The frightening part was not that it was empty. The frightening part was that it was empty yet still confident. Had I been a young editor, an impatient investor, or a fan looking for a reason to believe, I would have read those nine pages, found them tidy, and assumed a serious analytical process lay behind them. Tidiness of form had become a kind of counterfeit guarantee. And in a sport where belief is priced in money, a counterfeit guarantee can cause real damage. Let me be clear to avoid misunderstanding. My problem that night was not a single technical glitch. A pipeline can fail for hundreds of reasons: a blank source document, a parser hitting a syntax error, a broken hand-off between two tiers. But what every incident of this kind shares is that it passed through a door that should have had a guard: the door checking the completeness of the input. My system had no such guard. It allowed an empty input to pass straight into the deep-analysis tier, and that tier still tried to do its job by building an empty frame. In other words, the system chose to look useful rather than admit it was useless in that moment. That is a very human choice. And a very harmful one. In football, we are all too familiar with a team short on data but still taking the field. A center-back with a slight knock, a midfielder not yet match-fit, an opponent without video analysis — and the team still has to play. A coach cannot tell the referee: "Sorry, I lack information today, so I request a postponement." They must decide under imperfect conditions. But there is a big difference between a human and a system. When a coach lacks data, he knows he lacks it. He decides with an awareness of uncertainty. A system programmed to always produce output has no such awareness. It does not know it is blind. It only knows it must speak. That is why I treat the empty-spreadsheet incident as an event worth writing about, even though on the surface it has nothing to do with football or speed. It exposes a common disease of the analytics age: we have built machines so good at producing form that we forget form is not content. A pretty league table is not a fair season. A smooth chart is not a correct conclusion. A nine-page report is not nine pages of truth. In recent years I have followed many debates about heat maps in football. The heat map has become what I call the "new divination" of the game. People look at glowing red patches and immediately conclude a player's role: he plays left, he drops deep, he covers ground. But a heat map is only an aggregate of touch positions. It does not tell you under what circumstances he touched the ball, under what pressure, with what intent, and most importantly — what task the team's tactical system assigned him. A player may leave a huge heat trace on the left flank not because that is his strength, but because the team was pinned back on that side and he had to retreat to help defend for the entire second half. Pretty heat map, wrong conclusion. Just like my nine-page spreadsheet: perfect form, empty content. I remember analyzing for a small English club. They showed me a heat map of a midfielder they wanted to sign. The color patch showed him covering nearly the entire right channel, from his own box to the opponent's box. The scouting board concluded: an energetic, tireless right-sided midfielder. I asked to see PPDA — the pressing intensity metric. The number showed he pressed very little. A player covering such a wide right channel while pressing so rarely is almost certainly not someone actively occupying space, but someone passively chasing the ball. When I reviewed the footage, that was exactly it: his team defended in a low block, and he was the one running the most in a system nobody wanted to run in. The heat map told one story, PPDA told another, and only side by side did we see the truth. That club nearly bought a player at the price of an attacking star when he was in fact only a makeshift full-back. That is why I built my own framework of 12 metrics, from high pressing to transition capability. Not because I like many numbers. But because I need enough angles that no single metric can fool me. One metric is one testimony. Twelve metrics are a trial. And in that trial, every number must face questioning by the others. Back to the spreadsheet incident. If I applied that mindset, I would ask: which metric signals an empty input? The answer is very simple — the count of information points must be greater than zero. A single check, cheap as nothing, could have stopped the entire downstream error chain. But the system lacked it, because people assumed the input always has content. That is a convenient assumption, and every convenient assumption is a technical debt waiting to mature. In June 2026, when the World Cup in Russia took place, I was 52 and decided not to go to Moscow. I stayed in London, rented a small flat, and set up four screens tracking twenty matches simultaneously via motion data. After the group stage, I published a 4,000-word analysis on my personal blog. In it, I pointed out that Kylian Mbappe reached a top speed of 38 km/h — the highest of the tournament — but the more important point was his acceleration: he went from a standing start to 30 km/h in just 4.5 seconds. That figure created an un-defendable burst, because no defense is organized to react in time to an object reaching near top speed in such a short span. I wrote then: "France will win not through a famous attack, but through the space Mbappe stretches open." When France won, the piece was shared more than 12,000 times. An editor from The Athletic reached out to invite me to contribute. But what I remember most is not that fleeting fame. What I remember most is that I could have been wrong. I had relied on a motion-data sample from the group stage — a small sample, only a few matches, not accounting for stronger opponents in the knockout rounds, not accounting for injuries, not accounting for luck. Had France lost in the semifinal to a controversial penalty, that piece would have been dismissed as a wild prediction. The difference between a prophecy and a joke is sometimes just a moment that lies outside the data. I tell this not to boast. I tell it to point out a trap anyone in the data profession can fall into: after a few correct calls, you start believing the numbers are always right. But a number is only right within the assumptions under which it was created. It is a conditional prophecy, not an unconditional truth. Readers always read with their ears and remember with their emotions, so they turn "38 km/h in group-stage conditions" into "Mbappe, fastest in history." And so a conditional truth becomes an unconditional myth. The empty-spreadsheet incident is the same story in reverse. There, there was no number at all. But had I let it slide, it would have generated fake numbers in the reader's mind: "the system analyzed," "the experts concluded," "the report shows." A blank does not stay still. It always gets filled, because the human brain cannot tolerate emptiness. I spent many years as a transfer market administrator, and I learned that the transfer market is a match in which whoever prices correctly wins. Not whoever spends the most, not whoever is most famous, but whoever prices most correctly. A club paying £80 million for a player worth £40 million is a loser, even if it just signed a big name. A club paying £5 million for a player worth £25 million is a winner, even if nobody knows the player's name. Brentford did exactly that with Watkins: £1.8 million turned into £28 million, a return any investment fund would envy. But behind those figures of £1.8 million and £28 million lies an enormous process of cross-checking data. Brentford does not look at one metric. They do not look at Watkins's goal tally at Exeter — that number, standing alone, only says he scored a lot in a lower league. They look at xG, expected goals, to see what quality of chances those goals came from. They look at PPDA to see how he presses. They look at transition capability — how fast he turns a defensive phase into an attacking one. And they cross-check all of it against their own playing model, to see whether he fits the system. When I analyzed 1,247 players from 15 leagues, I followed exactly that process. I was not looking for the best players. I was looking for players mispriced relative to their true value — players the market had read wrong. That is the essence of my craft: making a living by reading correctly what the crowd reads wrong. And here is what I want to say to those who have been in this profession longer than I have: the crowd does not read wrong only out of emotion. The crowd reads wrong because they are fed pretty, hollow spreadsheets. A nine-page scouting report with full headings is more persuasive than a one-page raw data sheet, even though the raw sheet contains more truth. We taught the public that tidy form signals quality. And then we fooled ourselves with our own lesson. In recent cycles I have seen a repeating pattern at many clubs. They build an analytics department, hire smart young mathematicians, buy expensive data packages, and expect data to deliver an edge automatically. But they forget the hardest part: ensuring that the data entering the system is real. A powerful analytics engine only amplifies the quality of its input. If the input is good, it amplifies truth. If the input is empty, it amplifies emptiness into an illusion of understanding. I once watched another Championship club make a signing decision based on a report that later turned out to be compiled from data of a league that... did not exist. Not a fake league, but a mislabeled data package: third-tier data labeled as second-tier. The whole report was still logical, still had tables, still had conclusions. Only its foundation was wrong from the root. The player arrived, played eighteen months, and was sold at a loss. No one could trace the fault, because every link looked correct. This is what I call "silent error\