The 3-1 Was Right, the Roster Was Wrong: A Margin-Level Audit of the West Ham–West Brom Report

When I open a match report, I check the goalkeeper's name before I check the scoreline. The score is available on any aggregator; the keeper's name tells you whether the writer held a team sheet or only watched a scoreboard. The file that landed on my desk last week — West Ham losing 3-1 at home to West Brom — had an immaculate goal chain: opener, equaliser, two more, then the lock. Not once in ninety minutes did the clock and the score argue with each other.

And in the same paragraph sat one line — Hermansen had no chance. Mads Hermansen is Leicester City's goalkeeper. The next sentence named Taty Castellanos as a West Ham substitute; Castellanos is a Lazio forward. The story was running fine. The cast had been borrowed from another film's set.

Somewhere behind the north stand, a ladder of 128 names begins — in 2026, at the Delhi under-17 World Cup, I drew that same ladder by hand on chart paper. Two consoles, one marker, very little sleep, and a fixed slot for every name. When names slip out of their slots in a report, the story does not collapse. It just changes its address.

Context: what the report claimed, what the record says

More than twenty of the file's 26 information points trace to a single outlet, and Sky Sports is cited exactly once across the whole piece. No byline, no Opta or official statistics tag, no club statement, no direct voice from the ground. What is being sold as a match report is a rewrite of one source's version of events.

The narrative itself: West Ham are losing at home repeatedly, Nuno Espirito Santo is under pressure, the side sits six points off the pace, Cardiff await on Wednesday, and the report calls West Ham Championship promotion favourites chasing a return to the Premier League. That is where the frame breaks. In 2026-26 West Ham are a Premier League club and West Brom are in the Championship; the two cannot meet in a league fixture. Only a cup tie is possible. No date appears anywhere in the report, which is a signal in itself.

What holds up is precisely the part every reader can verify alone. Nuno replaced Graham Potter at West Ham in September 2026 and spent 2026 to 2026 at Wolves — both true. Jarrod Bowen is captain, Max Kilman is in defence, Kyle Walker-Peters arrived in summer 2026 — correct. Isaac Price, Callum Styles and Jayson Molumby at West Brom — correct.

The core: where the errors sit

The mistakes begin where the camera rarely goes. Max O'Leary is named as West Brom's goalkeeper; he is Bristol City's. Felix Horn Myhre is named as a West Brom scorer; he plays for SK Brann in Norway. The clearest confession is the attack chain the report itself prints: Price to Morgan to Myhre. Three names, and three different clubs — West Brom, the Chelsea system, and Brann. One move was split across three squads and nobody flinched, because the sentence sounded good. Edvin Austbo and Mohammadou Kante are further names whose club verification is still pending.

Narrative coherence is not factual coherence, and that is this file's real camouflage. The goal sequence, the diagnosis of the defeat, the language of pressure, the next fixture — all of it locks together. The internal logic is clean enough that the reader forgets to check outside it. That is the oldest trick in sports journalism and the newest: repair the prose, leave the names.

The accounting is broken too. One information point is tagged simultaneously as fact and data — double counting. The first two points cite the headline as their source, which is self-reference, not independent evidence. And phrases like feels the heat, few saving graces, patience wearing ominously thin are opinion, filed in the fact column.

Read it backwards: the easy culprit is not AI slop

The convenient explanation is that a machine wrote it. Convenient, and half true. The real fault is single-source dependency: twenty-plus of 26 points from one place, zero direct quotes, zero signatures. Any desk — human or machine — repeats that error under the same conditions. The report labels itself neutral while its language is a coaching-sack story from first line to last. That is not neutrality. That is a position.

The second correction applies to my own trade: treating the file as pure fabrication is also lazy. A cup meeting between these two clubs in 2026-26 is entirely possible. Writing the match never happened without opening the FA Cup or EFL Cup draw is the same carelessness pointed the other way. The right posture is to treat the fixture as plausible and confirm the XI against club lineups.

This is where an old habit earns its keep. Forty-one nights, most at 2:30 AM, on a Hauz Khas rooftop, and the city kept showing up. One thing those nights taught: European football always had the better production — graphics, lineup cards, half-time data — and that production trains a viewer to check who is actually on the pitch. Domestic coverage never built that habit. Every error in this file is a symptom of the gap. We learned to read scores. We never learned to read names.

Forward

The verification ladder has five rungs, and order matters. First, the official squad lists of both clubs — Hermansen, Castellanos, O'Leary and Myhre all get settled there. Second, Transfermarkt for 2026-26 club affiliation. Third, the Premier League and EFL tables to prove that six points off the pace cannot apply to this pairing at all. Fourth, the BBC or Sky archive for Nuno's exact appointment date. Fifth, the cup draw.

If the first three rungs confirm the errors, the file should be dropped as a factual source, not as a narrative template. Tournament cycles let speed beat verification every time, and this time the losing question was not what happened in the match. It was who was standing on the pitch. The audience is no longer asking for the score. It is asking for the team sheet. Every host is a bard with a clipboard and a ruined sleep schedule, and a bard's job is to remember that the name left out of the count is the one that comes back loudest.