The Empty Spreadsheet Never Blinks: Cricket's Data Provenance, the Blockchain Ledger, and One Missing Row

Second shelf of my fireproof cabinet, in a Mumbai flat. Last night I opened a folder. Inside, row after row, a single word — N/A. No title, no source, no information point, no player or team named. The analyst's own hand: "Insufficient information, cannot assess." Eight chapters, and every cell in every one of them carried the same inert answer.

I have been reading cricket's ledgers for thirty-three years. Blank pages are not new. But a page that stays blank this honestly is rare. Most people, seeing empty space, fill it with imagination; they put a score on a match that was never played, an amount on a contract they have never seen, a rehab date on an injury they have never examined. My job is the exact opposite. When the input is zero, every conclusion is fabricated. That one line has been the most expensive lesson of my trade in the last decade, and today's article is the proof of it.

My cabinet now holds thirty-four folders, each stamped with a date. In 2026, covering the Wills Cup in Dhaka, I never imagined that one day I would log every contract, every audit report, every ledger into one spreadsheet — one row per clause. That sheet has now passed fifteen thousand rows. What arrived last night had zero. That is today's story, and the story is not about cricket; it is about the data chain built around it.

We are in a transfer window now. Every morning my inbox fills with claims — this bowler to that side, this batter sold for six crore, this coach gone on a night flight. Ninety-two per cent of those claims have no document behind them; there is only a source whose own source is "a person close to the matter." The structure of the release clause and the size of the wage bill are the real story, and nobody reads them. I do not chase rumours; I chase receipts.

Those inbox claims and the analytical pipeline are two faces of one disease. One turns imagination into fact; the other turns an empty input into a conclusion. Today's file is the second kind. Some cricket article entered a pipeline, and what came out was an analysis in which every cell of eight chapters was blank. No title, no source, no date.

The natural reaction would be: "Then the analysis is rubbish, throw it away." I will not say that. A file that comes back empty is sometimes the most necessary document of all. It proves the pipeline was at least honest — it did not invent. The danger lies elsewhere, where another pipeline does invent, and nobody notices.

Today's file is really a ready framework — eight chapters, every cell arranged, the machine prepared. Only the raw material is missing. It proves the problem is not in the machine but in the input. And if the input is blank, even the most modern framework can only arrange the blank cells more beautifully.

The reader is drowning in a sea of rumour now. What the reader needs is a reliability filter — which claim has a document behind it and which does not, where an injury update came from, where a club's structure is heading. The real job of an analytical pipeline is to give that filter, not to add new rumours.

To think about the data chain, I have to go back to a contract. In 2026, I spent eleven weeks reading Star India's Rs 16,347.5 crore award for the IPL's global media rights. I matched the bid's deferred-payment schedule against the BCCI's 2026-17 audited accounts. Everyone printed the number; nobody printed the condition. Of the headline figure, Rs 1,240 crore depended on a floor — a minimum of sixty live matches per season. The award was worth sixteen thousand crore; the questions were worth more. I followed the money; it led me to an empty stadium.

From then on a rule took shape: before any number is printed, its condition, its date and its source must all sit in my ledger.

Now the cricket world is looking to the blockchain. The idea is simple and seductive: contracts, tickets, payments, player transfers — all written to an immutable ledger, and no one can reach back and erase them. For provenance there is no better instrument today — who wrote what, when; whose hands it passed through; who altered it — all of it stamped and fixed. Smart contracts for wages, tokenised tickets, verified transfer registries; the theory is beautiful.

But when I look at my cabinet, I see a cold truth. The blockchain makes information immutable, not true. If a blank row goes onto the ledger, it stays a blank row forever — no one can erase it, and no one can fill it either. Immutability makes an error permanent; it does not correct it. A system that does not verify its inputs will preserve those inputs, yes, but it will not make them true.

In 2026 I took a flat in Moscow's Khamovniki district. The World Cup was on; sixty-four matches, nearly three thousand journalists, and I never entered a stadium. I was working the doping file. In September WADA reinstated the Russian agency; I obtained the Compliance Review Committee annex and counted the 2,262 sample records its forensic team had flagged. Then I mapped them against the twenty-four reinstatement conditions. Twenty-one were unverified. There were 2,262 rows, and one of them was lying. Khamovniki was not on the fixture list, but it was in the file.

In 2026 the stadiums were empty. I stopped writing match reports and started reading balance sheets. The 2026-20 accounts of six ISL clubs arrived: five showed negative net worth, aggregate losses of Rs 402 crore, and under the central contract's force majeure clause the broadcaster could withhold the final Rs 86 crore instalment. The contract said force majeure; the turnstiles said nobody came.

That was when I finally wrote down the rule — the three-document rule: accounts, contract, correspondence. Without those three, I do not file a financial story. And another rule: no document runs on a single source, and no anonymous claim runs at all unless two independent methods confirm the paper existed. Last night's empty file is the mirror of that rule.

I have an old habit around ledger-writing that borders on a bad habit. In tidying fifteen thousand clean rows, I have nearly buried the actual truth more than once. So the rule now is: start with the lying row; move the other 2,261 clean rows to a footnote. If the reader wants the rest, the reader gets it; but first, in front of them, must sit the one row that was lying.

Here is what my colleagues miss. They say the blockchain is a silver bullet for catching corruption in cricket. I say the gun is pointing the wrong way. The blockchain does not verify inputs; it only stores them. If you insert a false date of birth into the system, the ledger will preserve it flawlessly — for centuries. The machine does not ask questions; people have to. That is why investigative journalism in the blockchain era demands more clause-level verification, not less. Technology cannot be an excuse for dodging responsibility; technology increases it.

And there is another trap I could have fallen into myself: crying fraud the moment an anomaly appears. An empty input, a strange row, a date that does not match — these must be separated into error, incompetence and intent. Collapse the three without evidence and the journalist himself becomes the fake. In my ledger, error and conspiracy sit in separate columns.

One more thing I have examined in myself. I was born in Australia and live in India. That distance can tempt me to make the Indian cricket system look exotic through foreign eyes. I do not do it. I run the same clause-level audit on Cricket Australia's revenue model, on the ICC's auction rules, on franchise systems. The ledger has no colour and no country.

The last trap is the cruellest, because it comes from my own nature. When verification is incomplete I stay silent, and that silence sometimes loses the whole story. So the rule has changed: publish what is verified; state the gaps explicitly; give the accused the right of reply. An incomplete truth beats a beautiful lie.

The "prove yourself" narrative around a returning player belongs in this same ledger-view. Nobody measures a capacity from three or four deliveries in a comeback match; the disease of drawing a large conclusion from a small sample is just another form of the analytical pipeline's error. The analyst who writes a verdict off four overs and the analyst who writes a conclusion off a blank file are two children of the same mistake.

Today's file will stay in my cabinet. Zero rows, and still a document. Because it proves that, asked properly, a system can at least return blank. My fear lies elsewhere — where a pipeline does not return blank but invents, and the reader believes it as truth.

The spreadsheet does not blink, even when the stadium does. If cricket truly wants to put its data chain onto an immutable ledger, the first task is to learn to stay honestly blank — who knew what, on what date, from what source, and what remains unknown. The ledger becomes trustworthy only when it stops hiding its own empty cells.