The Null Innings: When the Data, Not the Scorecard, Comes Back Empty

It was 12:27 in the morning. On the balcony of a Mumbai flat the smell of yesterday’s rain was still hanging. I opened the file — stage1_output.txt. Inside there was no scorecard, no innings breakdown, no pitch report. Only an empty list. Zero information points. No match name, no team names, no format — not Test, not ODI, not T20. Twenty years of watching from the stands has taught me that a scorecard is never fully blank; even a rain-washed match carries a result — “no result.” But when an analysis pipeline comes back empty, that is not the weather’s fault. That is a broken tooth in our own system. The screen flickers, and a boy becomes a sentence in the game — but tonight there is no boy on the screen.

One thing needs to be said plainly. Modern cricket journalism is no longer only a matter of the ground and the microphone; it is a two-tier factory. The first stage breaks an article down — information points, viewpoints, entities, time sensitivity. The second stage builds deep analysis on those fragments: format and match nature, player technique and data, squad balance and rankings, a league’s commercial structure, governance and rules, a risk matrix, and the expectation gap in public opinion. The first condition of discipline is admitting it: where there is no evidence, there can be no verdict.

In twenty years of memory-mapping the game, from the maidans of Dhaka, Narayanganj and Khulna to the academies of Mumbai, the scene is always the same. In the early light a boy puts on his pads and stands there; beside him a scout sits with a tablet. Before the trial is even over, the boy’s name, age, height, delivery speed and bat-swing angle have gone to a server. From there come tags, ranks, “prospect” or “not for selection.” Visas, wages, contracts — all of them run behind that number.

Now imagine that server coming back empty one night. The scout holds no information point, no entity — no boy, no team, no format. The question lands at the centre of cricket journalism: do we work with information, or do we work with the absence of information?

Zero is information. That is the most necessary sentence today. When rain washes out a match we write “no result” — nobody calls that failed journalism. But when an analysis pipeline comes back empty the desk shakes, because our entire working contract is built on wanting a story. The broadcaster wants a prediction, the portal wants a ranking, the fantasy app wants a score. Nobody wants “insufficient information.” It is in that gap between wanting and not wanting that some numbers are born every day, and some numbers are quietly deleted.

1. Sitting near the Feroz Shah Kotla in Delhi, I was watching India play the United States at the Under-17 World Cup. The scoreline was 0-3. The desk kept pushing — “we need a soundbite for the highlights.” I left the scoreline and counted goalkeeper Dheeraj Singh Moirangthem’s seven saves, and wrote the roar of forty-six thousand people. Two weeks earlier I had already watched every India training clip, because I wanted a metaphor that honoured the boys rather than the result. In a ninety-second post-match monologue I said — “a boy stood there guarding a dream.” A broadcast that cannot see seven saves only sees 0-3. Not for lack of data, but for lack of attention.

2026, Kazan. France 4-3 Argentina; nineteen-year-old Kylian Mbappé scored twice and won a penalty. The world wrote “breakout.” I wrote something else — when speed takes the shape of grief, the shadow left behind the defender is the real scoreline. Over eleven days in Mumbai I built a six-thousand-word audio essay — the father’s coaching, the banlieue as a character, the time-compressed career of a teenager. I collect the moments the broadcast forgets to replay.

This is where the ledger opens. Behind every cover drive there is a household budget, a border, the cost of a trial. The federation writes “talent identification”; the family writes “borrowed money”; the agent writes “advance”; and the boy writes “opportunity.” Four different ledgers, one boy. When the analysis machine comes back empty, none of those four ledgers is protected — nobody can prove who gained and who was cheated.

Null handling is not a weakness; it is the discipline of evidence. When there is no team, no format, no innings, no pitch — writing “best four bowlers,” “death-over skill,” “spin-friendly surface” stops being analysis and becomes guesswork. And fabricated cricket writing is more dangerous than wrong information, because it sounds credible.

Here is an uncomfortable point that almost nobody in my profession says out loud. Our collective memory keeps the conclusion and throws away the data. Someone will say “the match was lost in the last over,” and nobody will ask whether the ball-by-ball data from that over was ever stored. Memory builds its own story, and the story always fills an empty room.

But there is an opposite trap. Stopping at “insufficient information” is not journalism either — it is the easy road of avoiding responsibility. Declaring a null and chasing a null are two different jobs. When a pipeline comes back empty you have to ask: did the raw article text actually enter the system? Did the scraper time out? Did empty HTML come back? Whose fault is it — the keyboard, or the conveyor belt? An empty file is often the most honest witness a system has; we simply have to learn to read it.

One more thing. We love to call digital scouting a curse — we imagine the soil of the maidan lost, the neighbourhood coach lost. The truth is messier. The screen is a pitch too, only its grass is invisible. The question should be: whom did this screen let in, and whom did it quietly erase? He who has no video has no trial — that is the cruellest sentence of the day.

Now back to that empty file. The empty Signal Iduna Park did not lack sound; it held its breath. In the same way, the empty payload did not lack information; it blocked our chance to lie. The problem is that the whole business model of the industry rests on certainty, not on accuracy. Readers do not buy accuracy; readers buy “will” or “won’t.”

Before the next batch run, a gate should be installed: an empty information-point list must be rejected, an alert raised, the raw text re-read. But the bigger job is cultural. In our archives we must learn to keep the blank page beside the full ones. Otherwise a generation will grow up not knowing that no answer is also an answer. When the scorecard is blank we write “no result” — data can be blank too; let us learn to write “I don’t know.”