Auditing a Match Report: Lessons from Volgograd and the Data Standard of the Season

On June 18, 2026, in Volgograd, the afternoon temperature reached 34°C. In my hands was a four-page analysis that opened by predicting England would press high and that Tunisia's midfield would collapse inside twenty minutes. England won 2-1, the deciding goal arriving in the 91st minute. Tunisia's midfield stood firm for almost the entire match. England's players covered an average of 9.2 km, 1.8 km less than in their previous game, and Tunisia produced five notable shots. Gareth Southgate told reporters that the heat forced him to deliberately lower the intensity. I read the formation diagram very carefully. I simply did not read the temperature.

Eight years later, that sheet of paper still sits in my desk drawer in Valencia. I keep it as a record of my own professional error. Since that day, every report I write carries an extra section that colleagues in analytics departments rarely fill in: non-tactical factors — temperature, humidity, pitch surface, flight hours, the gap between matches, even the tendencies of the assigned referee.

Football analysis has changed enormously since then. Every match in the top leagues now generates thousands of data points: passes by zone, PPDA, xG, heat maps for each player. But every information chain has a weak link, and that link is always at the input. When the input is empty — no title, no source, no information points, no identified entities — every conclusion downstream turns into literature. In the trade, I call that an empty file.

An empty file has four characteristic gaps. Without source and timestamp, the analyst loses the ability to rank credibility. Without a list of information points, there is nothing left to cross-check. Without a core viewpoint, the piece has no object to challenge. Without entities — teams, players, coaches, competitions — every risk model, every resource comparison and every matchday forecast loses its anchor. Such a report is correct in its wording yet empty in its facts.

The most correct conclusion in that situation is "insufficient data to assess", and the writer must have the nerve to put that sentence on the page.

I learned this by a different route, earlier than Volgograd. In 2026, at 24, I joined Valencia's coaching staff as an assistant analyst. At my first press conference, a senior male reporter asked whether I truly understood Marcelino's pressing block or had simply come to fill a seat. I did not answer. That weekend I sent the staff a fourteen-page analysis showing that the team surrendered 62% of ball control along the left flank after every transition. Marcelino adjusted his line-up for three consecutive matches. The press room is not for the timid; it is for those with numbers.

Yet that same experience taught me the limits of numbers. The 2026-20 season stopped for three months because of the pandemic. Valencia slid into financial crisis, and sale rumours surfaced weekly. As the only staff member still in contact with the players by video, I had no training sessions, no friendlies, and fitness data that had all gone stale. I built a notebook inventorying the final nine matches based on pre-pandemic data, then compared it with the physical state of the squad when the league resumed. When 2026-21 kicked off, the conclusion — Valencia had to shift from a 4-4-2 to a 3-5-2 because they lacked a centre-forward — was republished in full by a major football outlet.

The method there was simple and repeatable: inventory first, commentary second. List all available data, mark which points remain valid and which have expired, and only then issue a judgement. A decent match report answers four foundational questions: where the information came from and when, which data points have been verified, who the subject of analysis is, and which conclusions could be overturned if new facts emerge. Those four questions are not glamorous, but they mark the boundary between analysis and storytelling.

What is worth noting is that this approach runs against the rhythm of the media industry. A post-match piece is usually due within hours, and what gets rewarded is decisiveness. Audiences want to know who was wrong, who is good, who will win the title. A report that says "insufficient data to conclude" is treated as evasive, even as a lack of expertise. This is the biggest blind spot in sports writing: we mistake confidence for competence, and length of copy for depth of thought. In a regular season, where each round is only one beat in a long current, early certainty is usually what gets paid for later.

In the other direction, I have to warn myself about a different kind of evasion. Silence because the input is insufficient is professional discipline. Silence because you fear responsibility for a judgement is cowardice. The two are entirely different, and readers are entitled to tell them apart. Data does not lie, but the people who read data do — and so do the people who write it. A beautiful statistical table can conceal a team that is falling apart; an ugly one can conceal a structure that is being built correctly. The analyst's job is to say which table is hiding what.

So every report I write this season opens with three fixed questions. Before asking why we lost, ask which scenario we prepared for. Have we accounted for temperature, flight schedule, pitch surface and the assigned referee. And which of the data in hand is actually usable for the next match, rather than merely enough to retell the last one.

Based on my experience watching matches across La Liga and multiple World Cups, most analytical errors do not live in the conclusion — they live in the preparation. A rule is written in blood, not in ink. The Volgograd analysis is one such drop of blood, and it still sits in my drawer.

What time slot is your team's next match in, at what latitude, after how many days of rest — and if the file in your hands is genuinely empty, are you willing to write two words, "not enough", instead of building a story that merely sounds plausible?