Nine Dimensions of F1 Analysis and an Empty Report: When the Input Data Does Not Exist

Wednesday evening, on the second monitor in my London flat, a nine-part document opened. Each part had a proper heading: technical and car analysis, race strategy analysis, team and driver analysis, competitive landscape, regulation and governance, driver market, risk profile, public narrative, and industry transmission. Each part had tables, columns, comparison targets and its own conclusions block. But in the first cell of the first table, one line kept repeating: insufficient information to assess. Then the next cell. Then the next. I scrolled to the end, and the only thing not labelled blank was a small line in the corner: domain, F1. Nine dimensions of tactical analysis, and not a single team named. Not a single driver. Not a single race. A Formula 1 analysis containing no Formula 1.

The document closed with a refusal. Its author, and the system that ran it, declared that the correct response to an empty input is to refuse to manufacture signal. I read that line three times. Then I understood it was the most accurate description of my own job I had ever read.

A data pipeline never announces that it has broken

To understand what happened, you have to understand the architecture. A deep analysis like this runs in two stages. The first stage reads a source, an article, a wire report, a press release, and strips out the information points: headline, source, article type, core stance, hard facts, named entities, time sensitivity, source quality. The second stage takes that package and runs it through nine analytical dimensions. In this run, the first stage returned an empty package. No headline. No source. No facts. No entities. The second stage ran anyway, because the framework was intact, and printed nine complete sections with every node marked insufficient information.

The most reasonable hypothesis for the cause sits in the ingestion layer, not the analytical layer. The source may have been behind a paywall. It may have been non-textual, a video, a podcast, a radio clip with no transcript. It may have been geo-blocked. Or the extractor may have hit a JavaScript-rendered page and received an empty body. Based on my experience following race weekends, I have met all four cases, and the symptom is always identical: the skeleton is right, the flesh is missing.

What makes this notable is that Formula 1, as a measurement infrastructure, could hardly be less empty. A modern car carries more than three hundred sensors, logging engine revolutions, brake temperatures, tyre pressures, steering angle, suspension travel, energy recovery current, and hundreds of other quantities no spectator ever sees. A race weekend produces a data volume once measured in gigabytes and now measured in terabytes. Every team has an analysis room, every room has a group of engineers, every group has a model.

And yet that entire volume, when it reaches one reader in London on a Wednesday evening, can reduce to nothing at all. That is the paradox I want to talk about.

The nine-dimension frame, given real data, is a beautiful instrument

I took those nine dimensions and examined each one, assuming the pipeline had worked. Looking at it, you see clearly what a race weekend needs in order to become readable.

The technical dimension puts its central question on the correlation between wind tunnel and track. An upgrade package only has value when wind tunnel data converts into lap time. The 2026 season was the most expensive lesson on this. As teams exploited ground effect, some cars bounced violently on the straights, an effect engineers call porpoising, and no team had wind tunnel data that modelled it properly. The FIA technical department had to issue a mid-season technical directive to measure vertical oscillation amplitude. Technical knowledge, at some level, always arrives later than the car.

Then come resource constraints. The cost cap and the aerodynamic testing restrictions allocate wind tunnel runs in reverse order of the previous year's constructors' standings. The team at the bottom gets the most runs; the champion gets the fewest. It is a deliberate mechanism for compressing the field. And it has teeth. In October 2026, the FIA published an accepted breach agreement with Red Bull over the 2026 cost cap: the team had overspent by roughly 2.2 million dollars, received a 7 million dollar fine and a 10 percent reduction in aerodynamic testing time. That penalty, according to the FIA document, was not about money. It was about development time, which money cannot buy back within the same season.

The race strategy dimension turns on very concrete quantities. How many seconds a pit stop costs, usually somewhere between twenty and twenty-five depending on the circuit and the pit lane speed limit. Whether the undercut works, pitting earlier than your rival to exploit fresh tyres while they run old ones. Whether the overcut works, staying out longer. Whether a virtual safety car opens a free window. And at circuits like Singapore or the Hungaroring, where the gaps between cars compress into a long chain inside the drag reduction zone, strategy becomes a problem of escaping the train, where every car is fast enough to follow and none is fast enough to pass.

The team and driver dimension has very little to compare, so the only trustworthy comparison is the teammate. Same car, same tyre set, same upgrade, same Friday evening. Every cross-team comparison has to be corrected by a model, and every model carries error. That is why I always start with the teammate pairing before saying anything about a driver.

The competitive landscape dimension is now shifting into the 2026 regulation cycle: new power units with an electrical share close to half, active aerodynamics switching between two configurations, lighter and narrower cars, fully sustainable fuel. Any regulation cycle opens a short window in which the old order inverts. That window opens and then closes, and how fast it closes depends on which team reads the rulebook faster.

The regulation and governance dimension is the driest and also the one that decides the most championships. Post-race scrutineering, floor plank wear, rear wing deflection, power unit allocation limits, and penalty points on the super licence, where twelve points mean a one-race ban. The 2026 United States Grand Prix at Austin offers a clean example: after the race, two cars belonging to Lewis Hamilton and Charles Leclerc were disqualified because their floor plank wear exceeded the permitted limit. No argument about skill, no emotion. Just a measurement and a rule.

The driver market dimension has two kinds of money: money paid to a driver and money a driver brings. Plus a variable the media usually ignores, the contractual wait time of technical staff. When a senior chief engineer moves teams, they often have to sit out a period, and their technical knowledge cools month by month. Adrian Newey announced his move to Aston Martin in September 2026, a deal whose value sits not in the signing date but in the date he is allowed to start work.

The remaining three dimensions, risk profile, public narrative and industry transmission, are where everything above gets churned into emotion. Injury risk, reliability risk, grid penalty risk, the risk of one driver carrying an entire points haul. Media turns those risks into characters. Industry transmission flows from power unit manufacturers, through teams and the commercial rights holder, down to broadcast rights, sponsorship and derivative markets.

Nine dimensions. And in this run, all nine needed something they did not have: a name.

The blind spot is not in the document, it is in the next step

This is the part that worries me most.

An empty data package, if it flows downstream without a circuit breaker, will produce commentary. Nobody reads a table that says insufficient information and then writes three thousand words about it. But if people ignore that line, or if a system automatically fills the blanks with a plausible-sounding template sentence, then within three shares an empty document becomes a story: this team is in crisis, that driver has lost form, that upgrade has failed.

I have seen that happen. Not with a machine, but with people.

A data void is not the absence of information. It is information about the pipeline itself. When a source fails to load, what we learn is not about any team, but about the break between the car and the page.

And there is a deeper paradox. This sport prides itself on being the most measured on the planet. But most of what fans read about it does not come from sensor data. It comes from a line of text, written by a person, based on a source that sometimes nobody re-checks. An enormous analytical building stands on a very thin foundation: whether an article loads or not.

The shaky line and the summer without football

Every tactical diagram starts with a shaky hand-drawn line in PowerPoint.

I say that often enough for it to be reflex, and I still have to remind myself to hear it again. That sentence is not about humility. It is about the order of work. You draw first, you verify second. You sketch a hypothesis in rough strokes, then go looking for data to break it. If the data is not there, you still have the sketch and a question. If you start with data, and the data never arrives, you have nothing.

The summer of 2026 taught me that a gap is never empty, it is only waiting for the right reader.

For six months without crowds in the stands, I sat rewatching dozens of old football matches and redrawing them, because football was what I had at hand and the race track was not. When there is no football, I draw football. And it turned out that drawing is also a way of understanding. I called that work the geometry of space.

Those skills carried over to the track almost intact. I measured corner radii, found braking points, marked exit angles, and built my own spreadsheets to log every transition phase, because I could not find a ready-made source. Transition is not a stretch of running. It is the silence between two intentions that few people know how to read. And self-built data has one fatal weakness: it depends entirely on whether I can load the source at all.

Which is why, that Wednesday evening, I did not delete the empty document.

Emptiness does not need filling

The natural reflex of anyone in this trade is to fill the gap. There is a hot story, there is no data, so you write on instinct. Readers are waiting, editors are waiting, the algorithm is waiting. An empty article is a failure; a speculative article is a product.

I think the opposite. The greatest value of an analytical system lies in knowing when to stop. A nine-dimension frame that prints nine empty sections is a frame working correctly. A frame that prints nine full sections from an empty input is a frame that has broken, and broken in the most dangerous way: it still looks credible.

There is a difference between refusing and giving up, and readers are entitled to tell the two apart.

There is one more point, and it belongs to the audience. We are used to reports with names, with figures, with polished graphics. We rarely ask where the data inside them came from. Who loaded it. Was it taken from a press release, a press conference, another article, or from the car itself. The first three can all be wrong, and the third rarely reaches the writer in raw form.

In a major tournament season, that pressure is heavier. Everyone wants an answer before the race starts, and certainty sells better than caution. But a conclusion that is right on Thursday and wrong on Friday is not a conclusion.

What to watch this weekend

This weekend, when another race begins and the screens fill again with quantities, I will be watching something else. I will watch what someone says during the time when there is nothing to measure. After the car has pitted, after the tyres have changed, after every model has run and returned a tidy answer. The moment before the data has fully formed, that is where I want to stand. And if the next time you read an analysis that does not contain a single name, perhaps the right question sits elsewhere: who just dropped the data pipeline.