The 6/10 Ratings and Bournemouth vs Liverpool: When Data Testifies Against Itself

1:47 AM. I opened the data pack for Bournemouth vs Liverpool that an editor had sent me. The first index appeared on screen: nine Bournemouth players rated 6. Truffert and Adams rated 5. Not a single xG figure. No PPDA. No pass numbers, no heat maps, no count of ball recoveries within five seconds of losing possession. I scrolled up to the headline: “Jacquet and Alisson impress.” I went back to the body and read it line by line. Jacquet does not appear. Not once. Alisson is mentioned exactly once, in the save from Evanilson’s shot. By the fourth paragraph, Bradley Barcola — a Paris Saint-Germain player — shows up in a passage involving Petrovic. I closed the tab. This ratings sheet is unusable for analysis. But it teaches something else: a broken data product always exposes itself, if the reader is patient enough.

Context: a source broken just enough to fool the skimmer

Bournemouth host Liverpool in the Premier League. That is all I can confirm from this source. No final score. No league table. No information on the matchweek, recent form, or league position. A player-ratings piece usually appears after the match, once the result is settled. Here, the writer left the result blank. The only sign the match is over is the line that Isak broke the deadlock, and that Alisson denied Evanilson’s shot.

A few human signals are more trustworthy. Adam Smith, the right-back, made his 431st appearance for Bournemouth. That is the milestone of a man who has tied his whole career to one club. James Hill made his 50th Premier League appearance. Alex Scott was called up to England. Ryan Christie started in the absence of Justin Kluivert. These four lines stand firmer than the ratings, because they are facts that can be independently verified.

The rest is empty. No line-ups, no formation, no substitution minutes. For an analyst, that is the worst case: the source is not entirely broken. It is broken just enough that a skimmer still believes it.

Reading a ratings sheet like reading traces

I start with what can be verified. Nine players rated 6. That number says something concrete: the writer places Bournemouth at a safe average. No one too bad. No one too good. A 6 is the safe shelter of a rater who does not want to be contradicted.

Truffert and Adams get 5. These are two positions that can be isolated and probed. Truffert is matched against Cody Gakpo. Adams is pulled into the midfield vortex. If we keep the reading “the lowest rating usually sits where the opponent attacks most,” then Liverpool attacked Bournemouth’s left flank and the centre of midfield. But that is inference. Not data.

The more striking thing lies in three micro-matchups. Adam Smith against Barcola. Truffert against Gakpo. Antonio Silva and James Hill tracking Isak. These three pairs sketch a defensive plan with a shape: Bournemouth chose to isolate the flanks and assign a centre-back pairing to shadow the opposing striker. That is the trace of a deep defensive block that demands disciplined distances.

But I have to be clear: that is inference, not numbers. An analyst reading this would need PPDA to determine whether Bournemouth pressed high or low. They would need ball recoveries in the opponent’s final third. They would need shot counts and xG. I have none of it. I have only traces.

Three questions, three gaps

I cross-check myself by asking three questions. Did Bournemouth control the game? Without possession data, unanswerable. Did the defence hold its distances? There are traces, but without Liverpool’s shot count, inconclusive. Did the game shift after the goal? Without substitution information, unanswerable.

Three questions, three gaps. That is the definition of a source that cannot support high-level analysis. And an analyst’s value lies in daring to say “I don’t know” rather than filling the gap with guesswork.

The factual error and its consequences

Barcola’s presence in a Bournemouth vs Liverpool match is a serious error. He belongs to Paris Saint-Germain. Unless there was an unreported transfer, this is a factual error. That error opens two possibilities. First, the article was aggregated from several sources and mixed up matches. Second, the article was generated automatically and never passed review. Both possibilities lower the value of the entire source to near zero.

There is one more detail worth noting. Alex Scott was called up to England. If true, this is a positive signal about a young player’s development curve. But in a source with a factual error, even a good signal needs re-verification. That is the price of reading a broken product: even the true parts fall under suspicion.

Execution blind spot: how a 6 feeds a false story

A ratings sheet is not really data. It is a story-telling method that has been digitised. And this is its blind spot.

A match where nine players average a 6 usually evokes a serene game. But if Bournemouth lost to Isak’s goal, and if they squandered chances through Christie and Evanilson, then that 6 creates a false impression: this team played well but lacked luck. The league table teaches the opposite: football is counted in points, not in feelings. A team that loses with nine 6s is still a team that lost.

People tend to assume numbers make an article objective. But player ratings are among the most subjective forms of data in football. They do not measure. They judge. Every 6 is a comment hidden under a coat of arithmetic.

By contrast, the lines that seem small are the most trustworthy. Adam Smith made his 431st appearance. James Hill his 50th. Alex Scott to England. Three facts. They need no interpretation, no xG, no context. They stand on their own. In a broken source, self-standing facts are gold.

I draw one rule for myself: when reading a source, separate the verifiable from the trust-based. Use the verifiable. Discard the trust-based. With this source, I keep four lines and throw away the other forty.

The silence of the pitch and a data type with no name

There is a deeper layer this ratings sheet touches. What is not recorded is also data. Justin Kluivert’s absence is a signal, even though no one states the reason. It could be injury, suspension, or personal reasons. Each possibility leads to a different conclusion about Bournemouth’s squad depth.

Likewise, Ryan Christie starting is a signal. If Kluivert were fit, Christie would sit on the bench. If Christie starts, then either Kluivert is out, or the coach has changed his tactical intent. Without information, no conclusion. But at least I know what to watch.

That is the true value of an analysis: not delivering a certain conclusion, but pointing precisely to where the question must be placed. An empty stadium lets me hear every misplaced footstep — and a broken source does the same, exposing every gap if the reader stays awake.

What to track

Three signals will determine whether this broken source accidentally got something right. First, the official line-ups and final score will resolve the factual contradictions. Second, Alex Scott’s minutes for England will show where he stands on his development curve. Third, Justin Kluivert’s return will reveal Bournemouth’s true squad depth.

Pressing is not about running faster than the opponent, but about running at the moment they stop thinking. Reading data is the same. It is not about reading more, but about knowing when a number stops being trustworthy.

Numbers do not lie, but they do keep secrets. And sometimes the secret they keep is this: they have nothing to say at all. This Bournemouth vs Liverpool match, for me, ends exactly where it began — an empty ratings sheet, and one belief re-verified.