Nine Layers of F1 Analysis: When the Data Is Empty, the Conclusion Is Empty

There is an F1 analysis running thousands of words, fully stocked with terminology, naming the right teams, the right drivers, the right circuits — and it is worthless. Not because it is wrong. Because not a single line in it can be traced back to a source data point: no lap time, no cost cap figure, no tyre degradation number, no technical document named. That is the condition I call the empty analysis — a framework built out to every cell, with every cell blank. In F1, people are used to everything being measurable. A lap is measured in thousandths of a second. A pit stop in tenths. A team's budget in millions of dollars. Aerodynamic development in wind-tunnel runs. Yet most of the content audiences consume each weekend runs on what cannot be measured: transfer rumours, strategic guesswork, and a feeling about a driver. That mismatch is the subject of this piece. Not which team is faster. But when a conclusion about F1 is allowed to stand — and what it must pay for that privilege. Modern F1 is a closed data system operating under three layers of constraint at once. The first layer is the cost cap: the ceiling on total annual spending per team, currently in the range of one hundred and thirty-five to one hundred and forty million dollars, depending on the year and the number of rounds. Breach it and a team can be fined, restricted in development, or, more seriously, docked points. The second layer is the aerodynamic testing restriction. Wind-tunnel runs and CFD hours are allocated in reverse order of the previous season's standings: the weaker the team, the more testing it gets. This is the balancing mechanism the sport uses to stop advantage from compounding. The third layer is the technical directives issued mid-season to close grey areas in the interpretation of the rules. A single directive can neutralise a high-performing design in a few pages of text. Together these three layers create what I call F1's hidden structure of power. A backmarker does not only benefit from draw order — it gets more wind-tunnel time than the champion. A team that spends wisely can beat a team that spends more, provided it allocates well. And a team that understands the rules better can win before a wheel turns. For the audience, a weekend is one race. For the practitioner, a weekend is the end point of a chain of decisions that began months earlier. Every decision leaves a numeric trace, and that trace is the only thing separating an analysis from a commentary piece. I divide an F1 race weekend into nine layers of analysis. Not to complicate matters, but to know which layer is short on evidence. Layer one, engineering and the car. To discuss an upgrade, the first task is to check whether the track has confirmed it. A new floor is only worth something when lap time proves it. If wind-tunnel data does not correlate with track data, any claim about it is guesswork with decoration. Layer two, strategy. How long a pit stop takes, when the pit window opens, whether there is a safety car, how many laps a tyre has left, how the weather shifts. This is the most quantifiable layer, and the one most often skipped when people talk about form. Layer three, team and driver. Comparing two teammates is the cleanest comparison this sport allows, because they run the same car. Every other comparison is contaminated by equipment. Layer four, the competitive landscape. Who is in the title fight, who is fading, who is preparing for the next rule cycle, and who is betting on the future instead of the present. Layer five, regulation and governance. Scrutineering, the cost cap, sporting penalties and points. This is the layer that can reverse an entire season without a single lap being run. Layer six, the driver market. Contracts, empty seats, the movement of technical staff as well, and the mandatory break before an engineer can join a rival. Layer seven, the risk profile. Technical, personnel, financial, public opinion, and systemic risk. Layer eight, the public narrative. Whether audience expectation runs ahead of or behind what happens on track. Layer nine, industry transmission. From engine manufacturers, through teams and the championship promoter, down to broadcast rights, sponsorship and capital markets. These nine layers do not all need to appear in one article. But an article is only worth reading when it stands on at least one layer with real data. This deserves a longer pause, because it is the line between craft and entertainment. Newcomers to F1 tend to think they are watching speed. Veterans know they are watching an equation. The cost cap forces teams to choose between developing this year's car and preparing for next season. The aerodynamic testing restriction turns wind-tunnel running into a currency of its own: spend it and it is gone. A technical directive can topple a design with a single notice. None of those equations appears on a television screen, yet they decide the entire finishing order. Which is why a conclusion not anchored to a number is merely a beautiful conclusion. Beautiful, and useless. I once wrote a two-thousand-word piece about a young talent after a major tournament, and it drew three hundred reads. But it was still correct, because every claim came with a number: goals, assists, top speed, a date, and a specific predicted valuation. Years later, I still use that exact method for F1. Before saying a driver is better than his teammate, I need qualifying data and average race pace. Before saying a team is improving, I need to know which upgrade arrived at which round and how lap time shifted between circuits. Based on my experience following every Grand Prix since 2026, I have noticed a fairly consistent rule: verdicts issued within hours of a race ending are almost always wrong about cause, even when right about emotion. People see a driver dropping back and immediately attribute it to decline. The real reason is usually a mistimed pit strategy, tyres degrading earlier than predicted, or a technical directive that just stripped part of the team's design advantage. Those three causes sit in three different layers, and none of them appears in a hot take. This is where I want to argue back against the audience's own reading habits. In F1 there are two kinds of value. Short-term value is attention: a fine overtake, a controversial remark, a mid-season transfer rumour. Long-term value is position: a team with a healthy cost structure, a driver the market re-prices correctly after each season, an engineering system that understands the rules and prepares ahead for the next cycle. These two kinds of value usually pull in opposite directions. What generates the most attention this week is often what matters least to the final standings. Conversely, what decides the final standings is often what nobody mentions: a small shift in budget allocation, an engineering hire, a few-page interpretation letter. Fans have every right to enjoy the short term. But practitioners must know how to separate the two. I was once persuaded into error in exactly that way. When my hometown club overspent on wages, I produced the figure: the wage bill was sixty-eight per cent of revenue, far beyond the fifty per cent safety threshold. I recommended cutting twenty per cent immediately to preserve five billion dong in liquidity. The board delayed, afraid of upsetting the players. The club was relegated and then dissolved. The lesson was not in the number, because the number was right. The lesson was that data only has force when it compels a decision within a defined timeframe. I carry that principle into F1. A team that breaches the cost cap does not collapse immediately. A driver who loses form does not lose his seat immediately. But both are racing against a deadline, and that deadline always sits in the spreadsheet, not on the track. A record on the track is only a delayed sum of the numbers in the spreadsheet. And a driver's value lies not in his current contract, but in how the market re-prices him after each season. If he finishes in the leading group in a car nobody rates, his price moves before anyone finishes writing a tribute. In the other direction, a dissolved team is not a full stop. It is the most honest financial statement the team ever published — because when there is nothing left to protect, people are forced to show where the money went. So when you read any F1 analysis, do one simple thing: count the traceable data points. If that number is zero, you are reading prose, not analysis. This sport will keep generating more data, not less. The cost cap will keep shaping how teams choose projects. The aerodynamic testing restriction will keep rewarding diligence in the teams that lag. And the driver market will keep running its own way: no summer holiday, only a summer of arithmetic. The question worth asking is not who wins the next round. It is: which data layer is being left empty this season, and who fills it before the results on track are forced to fill it for them?