Full Fields, Empty Facts: Who Keeps the Receipts in Cricket's Data Economy

13 March 2026. The scorers' box at Eden Gardens, six rows above the crowd. In front of me was a sheet filled in by hand — 34.1 overs, 120 runs, eight wickets. Sri Lanka had made 251 for 8, and India's chase ended on that over, at least on paper. Down in the stands the scaffolding was burning, and the match referee handed the game to Sri Lanka. I kept the book that night; the crowd kept a different story.

Thirty years later a new edition of that emptiness arrives in my inbox — a report with every field filled in. Title, source, publication date, summary, conclusion. Every fact missing. No match named, no player named, no score, no over count. The frame complete, the content zero. On the old newspaper desks we called it hollow copy — copy a sub-editor could read without ever knowing whether the reporter had been at the ground. The difference is only this: hollow copy is no longer produced by a tired man. It is produced by a system's silence.

This piece is about that silence. Cricket's data problem has long been framed as a shortage. My experience says otherwise. The problem is not the volume of data; it is the missing receipt attached to it — the habit of stating who counted a number, how, and for whom.

Context: the scorecard is a document, not the truth

Cricket's economy now runs entirely on numbers. IPL retention and trade arithmetic, franchise analytics departments, broadcast graphics, ICC rankings, fantasy leagues, and the databases that have grown rapidly over the past few years all run on one raw material: the scorecard.

But the scorecard is not what people think it is. It is not a reflection of the match; it is a summary of it, and a summary always comes from somebody's pen. The host board's official scorer, the broadcaster's statistics unit, the franchise analyst, and now automated scrapers — each records the same event according to its own needs. One counts wides separately; another folds them into extras. One credits the bowler a dot ball on a no-ball; another does not. Over a season, these small habits reshape the raw material on which crores of rupees of auction money rest.

By 2026 I had hand-logged roughly 1,400 one-day internationals and 300 first-class innings on paper grids — first for broadcasters, then on the DDCA payroll. That period left me one lesson that still applies to every report: a number counted by someone cannot be called evidence unless that someone's name travels with it.

Core: four lessons and one design flaw

1. Field geometry before the ledger

Before 2026 I opened my notebook with the score. After that night I opened it with a field map.

At Eden Gardens, 34.1 overs did not mean 120 runs. It meant that across 205 balls there was a specific geometry of nine fielders, a specific angle from the spinner, and a batsman who was or was not in a position to take a second run. Calling pressure 'nerves' is easy. Calling it geometry is useful.

That distinction still holds. Modern broadcast graphics tell you how many balls a batsman left in the powerplay; they do not tell you which way slip was facing. Neither number decides anything alone, yet one gets sold as data and the other discarded as anecdote.

2. Suspicion aimed at your own archive

In April 2026 Hansie Cronje admitted taking money, and that November Mohammad Azharuddin received a life ban. In those months I reopened my own archive hunting for run-rate drift in dead rubbers.

I found clusters. I could not corroborate them, so I did not publish them. What I published was a 2,000-word methods essay whose single argument was that a scorecard is a summary written by people with interests.

The part that still matters is methodological rather than moral. The job of data is not to generate suspicion but to bound it — to say which conclusions the evidence permits and which it does not. An analyst who does not distrust his own numbers will not distrust his own conclusions either, and that is the man who ends up speaking in someone else's name.

3. Kotla's low bounce and the matchup board

In 2026 the DDCA made me Delhi's first full-time video analyst. In 2026-08 Delhi won the Ranji Trophy, beating Uttar Pradesh in the final at the Wankhede. That was my first title as staff. Delhi won the Ranji that year; the paperwork is more interesting than the trophy.

Three months later, in February 2026, I sat in the Delhi Daredevils' auction room building a matchup board keyed to the low bounce at Feroz Shah Kotla — which bowler to which batsman, which over to which field. The side reached the semifinal and lost to eventual champions Rajasthan Royals.

The most useful line on that board was the one I cut first — 'this bowler is good against this batsman' — because it rested on twenty balls. On an auction table, twenty balls is not a trend, it is a coincidence, and betting on a coincidence is gambling, not selection. A number that does not disclose its sample size is not a number, it is advertising.

4. The integrity layer

In May 2026 Delhi Police arrested Sreesanth, Ankeet Chavan and Ajit Chandila; two years later, in July 2026, the Lodha Committee suspended Chennai Super Kings and Rajasthan Royals for two seasons each.

I was working as an opposition analyst, and those arrests changed my job description. I added a layer to my logs — no-ball frequency by over, dot-ball clustering, unexplained slowdowns immediately after a strategic timeout. I handed the method to the coaching staff, not to a reporter.

I also dropped a habit: trusting any single source, including myself. A number that does not say who counted it, and for whom, is somebody's claim, not somebody's evidence.

5. The design flaw: the derived field

Now back to the hollow report.

The problem was not that the facts were wrong. The problem was that the facts field did not exist, and every field after it was built out of that empty field. The template said: identify the entities involved from the information points above. The entity list was therefore not an independent finding but a derivative of the previous field. When the information points were empty, the entities silently emptied too, without an error message.

Cricket has a name for this disease: extras. Open any scorecard. The extras line is derived from wides, no-balls, byes and leg-byes. If the scorer never filled the wides column, the extras figure still prints, because it is derived. The reader sees a filled box and assumes a count was taken. He never learns that the source column was blank.

And a hollow payload is more dangerous than a blank page, because a blank page invites questions while a filled, hollow payload invites trust. When a report preserves its own shape while writing source: N/A, status: N/A, conclusion: N/A, the reader downstream cannot distinguish 'the article mentioned no player' from 'player extraction failed.' The two outcomes look identical and mean the opposite.

6. Memory versus record

This is not a software problem. It is cricket's problem of remembering, and it is old.

25 June 2026, Lord's. India bowled out for 183; West Indies all out for 140. Public memory holds Kapil Dev's catch to dismiss Viv Richards. The catch is real, but the match was decided by duller things: bowling rhythms in a 60-over game, and a batting plan that pushed Richards into the shot. The catch was the ending, not the cause.

2 April 2026, Wankhede. The crowd remembers the six. The record remembers the decision that made it possible — Mahendra Singh Dhoni promoting himself above Yuvraj Singh. That single call changed the left-right balance through the middle overs and neutralised the spinners' angles. Memory kept the six; the file kept the decision.

19 November 2026, Ahmedabad. India were bowled out for 240; Australia made 241 for 4 and won by six wickets. The story became the slow pitch. The pitch was slow; that is not a lie. But the real question that evening was who chose 240 and why — which batsman went in at which stage against which bowler, and why runs did not come in the first ten overs when wickets were not falling either. The pitch did not lose the match; the pitch supplied the alibi.

29 June 2026, Barbados. India 176 for 7, South Africa 169 for 8, a seven-run win. What changed in the last five overs was a bowling map — which bowler for which over, and where the deep fielders stood. None of it prints on a scorecard. That is why the scorecard is incomplete evidence, and treating it as complete is the actual error.

The archive only confesses when you read it out of order. Put two log sheets of the same over side by side and the gap will tell you what was removed. What we missed is not always drama; often it is a field nobody filled.

Contrarian: the failure is in the measurement design, not the data

The industry's first reflex is that the data was bad. That is a convenient excuse, because it makes nobody accountable.

My reading is different. The failure was not in the data but in the definition of the field. The moment you define the entity list as a by-product of the previous field rather than an independent finding, you have built a frame that will look successful even when it fails. Add an explicit status flag that says extraction failed. Without it, the analyst downstream can never tell whether he holds an empty truth or a broken pipeline.

Cricket carries the same disease everywhere. We ask how much, never who counted. A bowler's economy is displayed without disclosing whether it includes the overs he bowled after injury. A batsman's strike rate is printed without noting that half of it was made on a ground with a short boundary.

The second inversion matters more. An analyst's most honest report is the one with some fields left empty and the reason for the emptiness written down. I withheld clusters in 2026, and it remains the correct call of my career. In a profession that treats silence as weakness, silence with a stated reason is the actual skill.

What to watch next

Over the coming months, as retention and trade stories arrive, I will count something that is not money. I will count how many reports state whose register the number came from — the franchise's, the board's, the agent's, or a scraper's. The day a franchise press release carries a single line marked source, cricket's data will have moved one step from an economy toward knowledge.

Until then, keep one question beside every scorecard you read: who did this counting, and who is keeping the receipt?