The Empty Spreadsheet and One Word: When Only 'Football' Survives at the Transfer Desk

At sixty, I have one habit locked in: before opening any file, I read its first column. Last week the file on my desk had an empty first column. No headline, no source, no date. It was a twenty-row extraction sheet with 'N/A' beside every line. Only one field contained anything — the domain label: football. That was it. Like that night in Kochi in 2026, when the third tab of Berbatov's deal file sat open on my laptop with an image-rights stream left unfinished, I did what I did then: closed the file and began writing about what it does not contain.

There is a hard rule in transfer journalism that I have repeated for thirty years and that no spreadsheet designer obeys. The rule is that the biggest event in reporting is often not what got recorded, but what disappeared in the attempt to record it. Over the past decade I have built clause ledgers — fifteen columns, nineteen, once twenty-two. Every ledger has one row that will not reconcile. Remove that row and what survives is a clean, handsome, entirely false document. Automated extraction pipelines do exactly this. The fault is not that the machine dropped something; the fault is that it filled the gap with zero and told us the file was complete.

I keep a sheet logging 214 automated transfer-related reports from the past eight years, collected on trains between London and Manchester. Forty-eight of them carried the same defect as this empty file: one domain label survived, everything else was gone. In 2026 I found four different versions of a Premier League club's loan-out story — one had the player's name but no club, one had the club but no date, one had the date but no fee, and one said only 'football.' The fourth was the least useful and the most shared. That is not coincidence. The emptier the information, the faster it travels, because empty space lets every reader fill in their own story.

Cataloguing what is missing from this file is the actual report. Missing: a date, meaning I do not know which part of the transfer window this belongs to. Missing: a publisher, meaning I do not know whether this is an official club statement or an agent's WhatsApp message that became news after five hands. Missing: a single quote, meaning I do not know who said what and in what context. Missing: any number — no fee, no wage, no buy-out clause, no sell-on percentage. And the largest absence: no player, no club, no person. A transfer story with no transfer in it.

Now pause and consider how common this condition is. Of the hundreds of 'updates' we read in the final twenty-four hours of every window, a large share look exactly like this — nothing actually happened, there was only a deadline-day atmosphere, and words were poured in to fill it. In that Goa bubble I counted sixty-one contracts, and the lesson was this: count exits, not entrances. What leaves tells you what was inside. This file does not even record an exit — not of a player, not of money, not of trust.

When an extraction pipeline returns empty, there are three causes, and I have seen all three. First, the page was never read — dynamic rendering, paywall, encoding. That is technical death, and the cure is simple: send me the source code and I will tell you where the text is hiding. Second, it was read but the filters cut everything — threshold too high, rules too strict. That is the tool's fault, not the writer's. Third, and most interesting, the article was so short there was nothing to extract — a one-line tweet, a score, a 'deal close.' In the third case the error is not that the system found nothing; the error is that we treated that emptiness as insufficiency and hid it rather than treating it as a finding and printing it.

This is where I fight a habit of my own profession. We journalists fear empty space. We believe that saying 'I don't know' costs us credibility. The opposite is true. I still have the 2026 Kochi sheet, and the column for Berbatov's wage is plainly blank, because that number appeared in no document I could find. That blank column saved me in hundreds of later deals, because when someone hands me a round figure, I remind them of the blank column. A file that will not reconcile is the most honest file there is — at least it tells you where the lie can be told.

There is a second side to this, equally important. When an automated pipeline returns 'unclassified,' it is often telling a truth we do not wish to hear: the text does not fit the definition of football. I have watched Indian football's registration windows for twenty years, opening late and closing unrecorded. When a story does not sit inside that window, it is not football, it is administration. When a story is only a score, it is not a report, it is a result. The machine's 'unclassified' says what my editors said for thirty years: 'this is not a story.' We are not in the habit of hearing it, because we have columns to fill and the machine has only the truth.

Now to the error fewest people see — and the real conclusion of this file. The moment an extraction returns empty, our instinct is to call it a failure and rerun it, or call it a tool problem and have someone else fill it. In both cases we do what everyone does on deadline day: we fill empty space with speed. This is the oldest rule of the transfer market — where there is no information, rumour does not stop, it accelerates. A player whose name appears in no document trends fastest. A club that has said nothing attracts the firmest claims. The empty file is not an exception; it is the rule.

Thirty years ago in Kolkata a senior editor taught me that the story is not what you were handed, it is what you verified. We had no extraction pipeline then; we had a telephone and a man on it saying 'according to sources.' Today that man has become a machine, but his sentence is unchanged. The only difference is that the machine is faster and looks far cleaner. An Excel sheet with empty columns was not sent by a human, so we do not suspect it. That is our largest mistake.

So what will I do with this file. First: ask for the source — the original text, or the URL, or the complete extraction output including the information-point array. Second: separate the facts in that text — match, score, transfer, injury, contract, number. Third: list the entities and their relationships, and separate every source by layer — official statement, club insider, reporter, aggregator, and the final link that merely repeats others. Fourth: fix the time sensitivity — window dates, contract expiries, return from injury; which conclusion goes stale tomorrow. Fifth: flag the round claims — 'official soon,' 'close,' 'huge deal' — and check whether a number sits behind them or only enthusiasm. Sixth: sort into three baskets — credible, pending confirmation, rejected. And seventh, most important: if nothing emerges from all of it, I will print exactly that — that nothing emerged.

I have a document from 2026, the Bhutia deal at Bury. It is perhaps the only file in this country's transfer history with a real fee architecture, real clauses, real registration. Everything after it — including the ninety-five goals — generated no sell-on value, no successor, no resale market. A stock depreciating to zero in public. When I look at an empty extraction sheet today, the feeling is the same: much noise, much speed, and zero at the end. The difference is that the zero belonged not to a player but to our reporting.

Tomorrow morning the next file will arrive — it always does, because the window never stops — and I will look first at what I have always looked at: the first column. If it is empty, I will not try to fill it. I will print it empty and tell the reader that where there is no document, you may write whatever you like — but I will not. The question is not why the machine found nothing. The question is how many words we spent hiding that emptiness, and how many of them were true.