The Empty Map in Liverpool: The Discipline of Saying 'Not Enough Data' as a Tactical Analyst

At 2:40 a.m. on December 15, 2026, in a small apartment in south Liverpool, I opened the data file I had been waiting four hours for. It had 41 rows. The left column listed the metrics I use every week: passes into the final third, ball recoveries within five seconds of losing possession, high-speed running distance split by unit. The right column, all 41 cells, was empty, repeating the same note: not enough information. Six hours earlier I had watched the Morocco–France semi-final, pen in hand, following every phase, my eyes fixed on how Morocco's midfield compressed into a dense block each time France switched the point of attack. I believed I had seen something real. But when the file came back empty, I had nothing to prove it with. The report to my editors was still filed on time. It was missing one thing: a conclusion. In this profession, a report without a conclusion is usually read as weakness. I read it differently — as a reminder that the hardest part of analysis is not finding the answer, but knowing precisely what you are missing. Professional football analysis today runs as a three-layer pipeline. The raw layer holds millions of data points: player positions, touch events, timestamps, movement vectors. The extraction layer turns raw data into readable metric tables. The interpretation layer — where I work — turns metric tables into a story with causes and consequences. The public only ever sees the third layer. When the two below it break, almost nobody knows. Event-detection systems miss off-ball actions, especially when a team drops deep and leaves large gaps behind. Wide camera angles lose tracking when a defensive block compresses nine players inside twenty-five metres. A data provider can change the definition of a progressive pass mid-season without informing its clients on the third layer. I learned to audit the bottom layer before reading the top. That is why I built my own notation system at eighteen: recording player coordinates every five minutes, by hand, across a full match. It is slow and clumsy, and colleagues have teased me that it belongs to a previous decade. It is also the only way I can tell whether a beautiful metric table is lying. I do not trust randomness. I trust passes that repeat. Football has its own version of a broken pipeline, and it does not live inside machines. An eight-second clip is cut from its context and spreads across social media. A transfer story originating from an agent is republished as if it came from the coaching staff. A single VAR frame at fifty frames per second is used to draw a conclusion about a stride, in a sport never designed to be measured at that resolution. In 2026, while covering the summer transfer window, I was the first to report Emile Smith Rowe's loan move from Arsenal to a mid-table club. The source was a scout I had verified across four previous deals. Before publishing, however, I spent two days answering a different question: did Smith Rowe fit the double-pivot system that club was building. The data showed he received 8.7 passes per ninety minutes in the left half-space — exactly the zone the new structure needed to exploit. An inside source can answer whether something is true. Nobody else can answer whether it makes sense. That part is mine. That 41-row file was a case of extraction failure, and it forced me to rebuild the entire frame of my report from scratch. In my own records, though, the most dangerous reports have never been the empty ones. They are the full ones. The first type is the cherry-picked report. The writer selects only the metrics that support a conclusion already formed, discarding the rest of the table. I once saw a report conclude that a defensive midfielder had been outstanding, citing an 88 percent tackle success rate. The figure was real. What went unmentioned was that he attempted only eight tackles all match, and four came after his side led by three goals. The second type is the incompatible-proxy report. A metric designed for one context is applied to another. Passes per match measure involvement in ball circulation, not chance creation. A midfielder who plays two hundred sideways passes posts a prettier number than one who plays sixty but delivers twelve balls into the box. Read without the positional map, those two figures are placed side by side meaninglessly. The third type is the narrative-captured report. In England I call it the front-page effect. When a young player scores a late winner, the match report rebuilds itself around that shot, and every other data point is rearranged to serve it. Before you praise the star, measure the space he leaves behind. A striker with twenty goals who plays no part in the pressing phase poses a different problem from one with fifteen goals who holds the team's pressing structure together. The fourth type is the time-window report. Take a team's last ten matches and the conclusion differs sharply from the last twenty. The same data, two opposite verdicts, both presentable as fact. This is where the profession most needs to defend itself, because the eye cannot detect the manipulation. Only by reading the time-window definition in the footnote do you learn you have been steered. When I began my Croatia series at the 2026 World Cup, my goal was not to celebrate a run. I wanted to prove it could be measured. I logged 24 receptions by Luka Modrić in the space between the lines and tracked his total distance in the semi-final against England: 11.2 kilometres, of which only about 3 kilometres were forward movement. Most of the captain's energy went into dropping, turning and restarting the rhythm. From those figures I predicted Croatia's midfield would collapse in extra time under accumulated load. It did. Croatia did not produce a miracle; they drew a map. Miracle is simply the name spectators give to a process they have no instrument to see. Four years later, at the 2026 World Cup, I was contracted as a remote analyst for a Vietnamese sports channel and tracked all six of Morocco's matches. I charted how their deep 4-3-3 allowed Spain 1,020 passes while generating only 12 dangerous entries into the central channel. Morocco's defensive-midfield zone occupied 71 percent of their active time, against Spain's 38 percent. Morocco did not defend in numbers; they turned space into a maze. Before the semi-final against France, I predicted Morocco would lose. The basis was not squad quality but the cost of running: their high-speed running totalled 8.4 kilometres per match, the highest at the tournament. I built a metric I called defensive endurance, combining high-speed distance with tackle success in the final thirty minutes. It fell sharply round by round. They lost 0-2, exactly to script. Every formation is a hypothesis; the match is the experiment. An experiment only counts if you record it before you know the result. The rule I set for myself afterwards is simple: every conclusion must carry at least one counter-indicator. When I write that Morocco's back line is well organised, I must note that their tackle success rate drops markedly after the seventieth minute. When I write that Croatia controls midfield, I must note that their turnovers in the final third rise with each half. If I cannot find a counter-indicator, my conclusion has not been tested — only decorated. There is a boundary my model cannot cross. In 2026, when stadiums stood empty for 112 days, I analysed fourteen Liverpool home matches played without crowds at the end of 2026/20. Their high defensive line committed 38 percent more positional errors than with crowds. The cause was in no tactical metric. Midfielders lost the auditory signal from the stands that told them when to cover — something no camera records. Across the same period, I logged that high-pressing teams conceded an average of 0.7 goals per match once opponents were allowed five substitutions. 112 days without football, and the substitution rule was the lifeline. Since then my pre-match checklist carries a separate section for off-pitch factors: crowd density, substitution regime, flight schedules, actual rest days. Metrics answer what is happening. They do not answer why. The why usually lives in injuries, in the fear of re-injury, in a player taking the field for the fourth time in ten days. This is where the industry goes wrong, and I will say it plainly. We are building an economy of manufactured certainty. Analysts are paid to deliver conclusions, not to say the data is insufficient. Editors need a declarative headline. Fans need a story to believe. When every link in the chain demands certainty, the market manufactures certainty regardless of whether it exists. The transfer market exposes the mechanism most clearly. A player with fewer than fifty top-flight appearances can be valued at one hundred million euros, and nobody in the room asks how large the sample behind that valuation really is. Meanwhile the cost of failure is pushed onto the player. The transfer market does not buy footballers; it buys problems. The trouble is that most buyers never read the brief properly. On the pitch, VAR is the perfect expression of the same error. A millimetre offside line turns a counter-attack built in two seconds into an administrative dispute. Referees are becoming the editors of the match, empowered to cut a goal not because it was wrong but because it was hard to read. Attackers adjust their instinct out of fear that a line will appear. Nobody can measure that loss, because it produces no metric. In the medical room the mechanism turns cruel. Demanding that a player prove himself in his first match back is not a sporting demand. It comes from a public that wants an immediate answer, not from physiology. That pressure raises the risk of re-injury, and when re-injury comes, the story is told as a personal tragedy rather than a system failure. There is one consolation. Tactics are the only thing on a football pitch that cannot be faked. A club can buy players, buy media, buy narrative. But the gap between two lines cannot be bought. It has to be filled by hundreds of training sessions, by passes repeated until they are boring, by a structure nobody can decorate in a press conference. After that night in Liverpool, I printed the 41-row file and pinned it to the wall. It is still there. I keep it not as a memory but because of a question I have not answered: when a report comes back empty, what broke — the data system, or the writer's process? I have not solved it. But I know how I will test it next match. Before every fixture I will ask myself: if today's data were wiped clean, how much of my conclusion would I still believe. That percentage will move. It will also tell me whether I am an analyst, or just a storyteller with a spreadsheet attached. And if the answer is not enough data, that is exactly what I will write.