Nine Layers of Analysis Inside F1: Where Data Ends and Speculation Begins

The email arrived at 7:42 a.m. Sydney time. The sender was an editor I had known for years, with a single attached file and a single line of note: “Please dissect this for me, urgently.” I made coffee, opened the file, and found inside only one label: f1. No title. No source. No summary sentence. No list of facts. No team name, no driver name, no race name. A carefully packaged blank space that looked like a document.

Over ten years of observing this industry, I have received such files many times. And I have watched colleagues do the opposite of what I was about to do: they filled the blanks with speculation. They wrote about which upgrade package a team was preparing, about tyre strategy, about whether a driver risked losing his seat — all from a blank sheet. Those pieces read very smoothly. And they were wrong from the first line, because we cannot analyze what does not exist.

I chose not to write. But that very moment taught me something the F1 analysis trade rarely admits: the hardest part is not finding the answer, but knowing when you must not invent the question.

Context: Why most F1 analysis is just an echo

F1 is the most heavily documented sport on the planet. Every car carries hundreds of sensors, every lap generates thousands of data points, every session can be reconstructed to a tenth of a second. Yet most of the content fans read daily is not based on that data. It is based on echo: a quote in a press conference, a photo of a floor in the technical area, a line from an anonymous account, multiplied across hundreds of copies until it becomes “truth” in the public mind.

What bothers me is not the existence of echo. Every sport needs echo to feed emotion. What bothers me is when echo is dressed in the coat of analysis. An article saying “team X is falling behind in the development race” without a single figure on track correlation, long-run pace, or championship position — that is not analysis, it is dressed-up speculation.

My job, for years, has been to try to separate signal from noise. To do it systematically, I had to build a framework of nine analytical layers. Each layer is a different question about the same race, the same team, the same driver. When all nine are answered, the picture is thick enough to call understanding. When one layer is left empty, the whole structure above it wobbles — even when written in the most confident tone.

That empty file was, in a sense, the perfect test of the framework. It forced me to walk through each layer and ask: what evidence do I have here? And in almost every case, the answer was: none. Nine layers, and nine times I wrote down two words: insufficient data. That is the lesson I want to retell here, layer by layer.

Layer One: Technology and the car

At the first layer, the serious analyst asks three questions. First, what has the team brought — a whole-car concept, a single component, or a power unit? Second, has it been validated on track by lap-time data, sector by sector, and by GPS-measured speed? Third, how much room remains for further development — what ATR tier are they in, and where do they sit against the cost cap?

These three questions sound simple, but they eliminate up to ninety percent of what circulates each weekend. A new floor seen in a technical-area photo says nothing unless we know what problem it was designed to solve: porpoising, aerodynamic balance at mid-speed, or rear-tyre temperature over a long run. A new wing is not automatically an upgrade; it may be a step backward brought to the track to close the gap between model and reality.

The test I value most at this layer is the correlation between wind-tunnel data and track data. A team can boast a top-tier wind tunnel, but if what is produced there does not appear on track, its true engineering capability is far lower than its reputation. This is where terms like downwash, zero-sidepod, DRS or ERS deployment become analytical tools, not decorative words. Every word must come with a number. No number, no analysis.

In the empty file, layer one had nothing to analyze. No team name, no component, no quantitative datum. And the only correct thing I could write was: insufficient information.

Layer Two: Race strategy

If layer one asks about the car, layer two asks about decisions. A race is a chain of choices under time pressure: which tyre, which lap to stop, how to react when a safety car appears, whether to gamble on weather. The analyst at this layer does not retell events — they measure the quality of each decision.

The three core tools are undercut, overcut and pit loss. Undercut is stopping early for fresh tyres to jump a rival; overcut is staying out longer to exploit clean air; pit loss is the total time lost on a stop compared with continuing to run. Crucially, pit loss is circuit-specific and cannot be transferred from one race to another. So any strategy analysis only means something when we know exactly which race is being discussed.

At this layer, execution quality separates from the idea. A correct decision can be undone by a two-second slow stop; a wrong decision can be saved by luck when a virtual safety car appears at the right moment. A good analyst must separate three elements: correctness of the decision, quality of execution, and the luck factor. Blending the three is the fastest way to a wrong conclusion.

In the empty file, no race was named, no lap, no tyre compound, no pit window. The whole of layer two was a silence.

Layer Three: Team and driver

This is the layer where fan emotion most easily floods in, and where data discipline must be strongest. For a team, the analyst looks at constructors' standings position, two-car balance, and the rate at which upgrades convert into results. For a driver, the analyst looks at qualifying comparison, race pace, and consistency — but all must be anchored to a single control frame: the driver's own teammate.

The teammate is the best control frame we have in the paddock, because they drive the same car. When we strip the equipment factor from the human factor through this comparison — what I call “equipment-filter stripping” — we finally see a driver's true quality. A driver who regularly outqualifies a teammate but trails him in long runs tells a very different story from one who occasionally flashes brilliance.

At this layer, too, the risk of team orders appears. When a team is fighting for a title, collective interest may be placed above individual interest, and that must be read through contract structure, not only through one on-track situation.

No team name, no driver, no standings in the empty file. Layer three, once again, could not be built.

Layer Four: The competitive landscape

Once we understand each team and driver, the next question is the whole picture. Who is fighting for the title, who for podiums, who is in the midfield, who is at the back? This tier diagram sounds obvious, but it only has value when based on data rather than the feel of a few recent races.

Three variables shape the landscape: cost-cap constraints, an upcoming regulation change, and the arrival of new entrants. The cost cap has changed how teams allocate resources — it turns every dollar spent on development into a trade-off, and makes the gap between teams persistent in a different way than before. A new regulation cycle opens opportunity for teams stuck in the middle. And the flow of talent — engineers poached by rivals — is the earliest signal of an approaching reshuffle.

Position in the regulation cycle is the single most important context variable for interpreting any competitiveness claim. Early in a cycle, gaps can be reversed quickly. Late in a cycle, the order is largely set. Without knowing the season, we cannot know where we are in that cycle — and so we cannot read anything correctly.

The empty file has no season, no round, no standings. Layer four is empty.

Layer Five: Regulation and governance

F1 runs on four regulatory layers: sporting, technical, financial, and the international sporting code. Each has its own oversight mechanism. Technical has scrutineering. Financial has the cost cap and independent audits. Sporting has a penalty system. And above all sit the Technical Directives — documents tightening rule interpretation, typically used to close grey-area designs.

The analyst at this layer tracks four signals: scrutineering results, protests, sporting penalties, and waves of regulation change. For each signal, the question is: which clause is being touched, and what precedent was set in the past. Building penalty scenarios — worst case, middle case, optimistic case — is a way to prepare rather than wait.

What I learned over the years: never default to assuming a design is legal just because no one has objected. Silence is not evidence of compliance; it is only silence. As the line I always repeat goes: numbers never lie, but the people reading the reports do.

The empty file has no regulatory text, no directive, no protest. Layer five is left blank.

Layer Six: The driver market and talent ecosystem

The transfer market has its own rhythm: a quiet phase, an undercurrent phase, and a peak phase — usually called silly season. Misreading this rhythm is misreading every rumour. A story appearing in the quiet phase carries different weight from one appearing just as a seat is vacant.

At this layer, the analyst builds a seat matrix: which team has an opening, the probability of change, potential candidates. But a seat is inherently a time-stamped object. A contract seen as “locked” one season becomes “expiring” twelve months later. Without knowing the date, we cannot build the matrix.

Alongside this is the flow of technical talent. When a top engineer moves teams, they usually must pass through a mandatory interval — called gardening leave — the period the old team uses to reduce the value of the technical knowledge they hold. That is a strong signal, but it only means something when we know the effective date.

And above all is grading rumour credibility. Three tiers of question: which source, which motive, which interest. A rumour can be seeded to pressure a contract negotiation — a tactic I call “leak and inflate.” No source, no grading; no date, no placement in the phase.

The empty file has no driver name, no contract, no date. Layer six is empty.

Layer Seven: Risk profile

Risk in F1 comes from six directions. Sporting risk: collisions, DNFs, power-unit quota, points concentrated in one driver, weakness at a specific circuit type. Technical risk: wrong development direction, wind-tunnel/track correlation failure, supplier dependence. Personnel risk: losing people, internal conflict. Regulatory and financial risk. Reputational risk. And systemic risk — events beyond anyone's control.

For each risk, the analyst assigns a level, probability, impact, and mitigation. But there is a deadly temptation: defaulting to the assumption that when no risk is found, everything is safe. Wrong. Failing to find risk because data is missing is a completely different conclusion from there being no risk. The difference is small in appearance but separates the real analyst from the one reassuring himself.

The empty file has no concrete claim about performance, reliability, personnel, finance or calendar. Layer seven is a blank table, and I deliberately left it blank rather than writing the word “low.”

Layer Eight: Public narrative and expectation

Every F1 season has its own stories: the GOAT debate, the succession of a dynasty, a generational talent, a veteran's redemption, a team's revival, or an internal power struggle. Layer eight asks: which story is being inflated, which has a basis, and how far does market expectation deviate from reality?

Three tests help separate. The first is the degree of fundamental support: is the story confirmed by numbers stable across many races, or by one anomalous race? The second is sample size: a result after two races is entirely different from a result after ten. The third is the equipment-fraud test: after stripping the car factor through teammate comparison, does the story still stand or collapse?

A classic trap at this layer is the winter-testing trap. Lap times in testing do not reflect the true order, because each team runs a different fuel load and programme. Yet every year, stories of “team X rising” are built from numbers that mean nothing.

The most important test at this layer is the ratio between social buzz and underlying fundamentals. When that ratio crosses a threshold, we are at the peak of a fever, and every fever fades.

The empty file has no author stance, no article purpose, no source. That means the very pillar for detecting PR-driven framing has vanished.

Layer Nine: The transmission of the F1 industry

The final layer asks about the flow of money and power. An upstream signal — a manufacturer deciding to enter or exit, a change in power-unit supply, a batch of young drivers from an academy — transmits down to the midstream of teams, events, and the commercial rights holder. From there it flows downstream: broadcast, sponsorship, and derivative products.

For each layer, the analyst estimates direction, magnitude and time horizon. A manufacturer commitment does not only affect one team; it shapes the entire next regulation cycle. A title sponsorship is not only money; it is a vote on where the sport will be seen. A calendar change is not only a location; it is a decision about which market is prioritised.

I always remind myself that value is not the number on the balance sheet, but how that number is valued. A driver's value is not in his fastest lap, but in how he is valued in the market. The same lap, two valuations, two fates.

The empty file has no manufacturer, no team, no event, no sponsor, no commercial counterparty. Layer nine is empty.

The counter-intuitive angle: The discipline of zero

This is the part I am most grateful for in the whole story. On a platform that rewards confidence, writing “I don't know” is an act of resistance. And I believe it is precisely that act that defines an analyst.

When handed an empty file, the reflex of most is to fill it. The human brain hates blanks; it automatically knits scattered facts into a story, even when those facts are only labels rather than content. A single “f1” tag is enough to trigger imagination. And so an analysis is born — no team, no driver, no race, but full of names, predictions, and a tone of certainty.

Such pieces share one trait: they cannot be wrong, because they say nothing specific. But precisely for that reason, they cannot be right either. They are the echo of an echo.

I don't believe in luck. I believe in numbers verified three times. But I also believe that honesty with data demands a different kind of courage: the courage to say data is missing, and to refuse to build a story out of nothing. In this industry, the biggest temptation is not distorting figures — it is inventing figures just to make the piece look complete.

After all, when the stadium is empty, money flow is the only player left on the pitch. But when the data is empty too, even money flow has nothing to analyze. That is the boundary between a craft and a game.

Takeaway: What fans should demand

Those nine layers are not an academic ritual. They are a filter between what is credible and what merely sounds good. Fans do not need to know how ATR is calculated, but they have the right to demand that a technical analysis name the team, the component, and the on-track evidence. They have the right to demand that a strategy piece name the race, the lap, and the pit loss. And they have the right to demand that when there is no data, the writer says so plainly, instead of dressing speculation in the coat of analysis.

I return to that 7:42 a.m. email. I replied to the editor with one short line: the source is empty, resend the original, I will analyze as soon as there is data. He laughed and said I was difficult. Perhaps. But if I had filled that file with what I wanted to see, I would have lost the very thing that makes people come to me: honesty with the truth, without compromise. And in a sport where every tenth of a second can be measured, that honesty is the only thing that cannot be faked by any tool.