Silent Analytical Failure: When an Empty Football Data Sheet Gets Read as 'No Risk'

SILENT ANALYTICAL FAILURE: WHEN AN EMPTY FOOTBALL DATA SHEET GETS READ AS 'NO RISK'

Last season, in a scouting meeting in Jakarta, I watched a scene that seventeen years in this job has taught me to spot instantly. A twenty-four-year-old central midfielder's file appeared on the big screen: the injury-history column blank, tactical-adaptability marked N/A, contract-risk with no figures, and the conclusion line reading "no issues detected." The sporting director nodded: "So he's safe." The room nodded with him. Nobody asked the cheapest and hardest question: are those empty cells the result of checking and finding nothing, or the result of never checking at all?

That is the moment I call silent analytical failure. It makes no noise. It raises no red flag. It simply leaves a cell empty and lets the reader fill that emptiness with the belief that nothing is wrong. Numbers never lie — only the way we listen is wrong. But when there are no numbers at all, the error does not come from the figure. It comes from silence being misread as cleanliness.

Over the past decade, a data department became mandatory at almost every ambitious club in Southeast Asia. Indonesia's Liga 1, Vietnam's V.League 1, the Thai League — all have at least one analyst, one tracking tool, one dashboard refreshed after every matchday. The familiar metrics: xG, PPDA, passes into the final third, off-ball movements, high-intensity distance.

Alongside that came a reporting standard. Every player file must contain strengths, weaknesses, risks, recommendation. Every post-match report must contain game state, data, causes, advice. The template makes information comparable and presentable. It also creates a quiet pressure: every cell must be filled, even when the person filling it has nothing to fill it with.

Yet a deeper paradox sits beneath this: data supply in the region is uneven. Top divisions have international providers, positional cameras, event-coding staff. Lower divisions, youth leagues and regional fixtures are largely undigitized. The further down the pyramid you go, the more players exist in a zone where data about them simply does not exist. And those very players are the cheapest, most attractive scouting pool for mid-sized and small clubs.

I was once inside that machine. In 2026, as an assistant analyst at Persija Jakarta, I presented a forty-page report proposing that Septian David Maulana be moved from the wing into the number ten role. The evidence was a single number: he ran only 8.2 km per match yet delivered eleven passes into the opponent's final third, the highest in the squad. The coaching staff initially dismissed it. After three trial matches, Maulana scored twice and assisted three; Persija won four straight and went on to the 2026 Liga 1 title. The lesson I took then was neat: data does not lie, only the presentation decides persuasion.

The bigger lesson came later, and it was the reverse. The most dangerous thing in a report is not a wrong number. It is an absent number still read as a conclusion.

Three mechanisms turn silent analytical failure into a systemic disease rather than an individual mistake.

The first is template-forced completion. When an evaluation sheet already has a "injury risk" row, that row will be filled. If the database has no information, the analyst faces two choices: write "insufficient data" or write "low." "Insufficient data" sounds like an admission of incompetence. "Low" makes the report look complete and professional. Most choose the second. And so a player who was never fully medically tracked walks into the meeting labelled "low risk" — a label with no basis other than the cell needing to be filled.

The second is source-less data. A twenty-two-year-old from a league with no data provider will appear in the file with a clean injury history, stable output, consistent form — not because he is durable, but because nobody recorded the matches he missed. The emptiness of the database gets misread as the emptiness of risk. Those two things are entirely different.

The third is model extrapolation. An xG metric trained on top European leagues, applied to Liga 1 or the V.League, produces numbers that look precise. Two decimal places. Smooth charts. But if the model was never calibrated to the finishing quality, defensive quality and pitch conditions of the destination league, that precision is purely cosmetic. A wrong model can still print tidy results. And tidy results are the most believable thing in a busy meeting room.

These three mechanisms resonate in a way that is very hard to detect. They do not produce obvious errors. They produce a complete, clean report with no red flags — while in reality not a single check was performed.

This is the point I want to press on anyone building a data process for a club. The absence of warnings does not equal the absence of risk. In medicine, people clearly distinguish "a negative test" from "no test performed." In football, those two states are usually collapsed into one, and the collapse always favours the decision-maker.

I have seen the consequences. A three-year contract signed for a player whose medical file simply did not exist. A transfer assessment based on four matches with data, while the other twenty matches of the season were never recorded. A form-prediction model that produced beautiful output until the club realised the model had never seen a single match in their league.

In 2026 I analysed the World Cup from Jakarta and found that Germany generated a total xG of just 1.2 in their 0-2 defeat to South Korea — the lowest in the national team's history at the tournament. Their pressing index fell 23% from four years earlier. My piece on that collapse was shared fifteen thousand times. But what I carried away from that tournament was not the pleasure of a correct prediction. It was the realisation that the 2026 World Cup did not break my model; it widened my definition of data. Some things I had treated as data were merely assumptions typed carefully.

The counter-intuitive point sits here: the industry's common belief is that more data fields mean better decisions. Reality is usually the opposite. Every new field added to a sheet is a new chance for an empty cell to be misread as a tick. The more "comprehensive" a process looks on paper, the greater the risk of silence in practice.

Football analysis also rewards confidence. An analyst who says "we don't yet have enough data to conclude" is often seen as indecisive and gradually excluded from key meetings. An analyst who says "low risk" gets invited back to the next table. That incentive structure explains why empty cells are rarely left empty. They get coloured in.

My model is only bad when I am too cowardly to ask it the hardest question. The hardest question is always: where did this data come from, and if it does not exist, what am I replacing it with?

In Indonesia, I once sat in a meeting where the entire coaching staff agreed a defender had "good reading of the game" — based on a report containing no metric whatsoever about game reading. The judgement came from the impression of a single match, was typed into the right empty cell, and was then cited as a fact in three subsequent meetings. That is how an assumption becomes internal truth.

At the same time, there is a reverse trap I always remind myself of: correlation is not causation. A team with low PPDA is not necessarily pressing well — they may simply be chasing the ball. A player with many passes into the final third is not necessarily creative — he may simply play for a possession-dominant side. And a player's value is not on the contract; it is in every off-ball movement — something most current data systems still cannot record, and because they cannot record it, it usually becomes one more empty cell in the report.

In football, silence is not exoneration.

What I want to see this season is not more metrics, but a small line appearing on every report: "insufficient data to assess." A line like that does not weaken the report. It makes the report more honest, and honesty is the only thing left standing when every model can be wrong.

A good coach treats a defeat as an update, not a verdict. A good data department should treat every empty cell as an open question, not a completed checkmark. Those who bet on data were once called mad; those who did not are now former coaches. The question for the next matchday is not how many metrics your club has. It is how many empty cells you dare to leave with exactly two words written in them: not known.