The Blank Page in the Record: The Cricket That No Database Writes Down

The file had nine fields and every one of them was filled — with N/A. Title: N/A. Source: N/A. Article type: unclassified. One-sentence summary: empty. Information points: none. Entities extracted: none. Time sensitivity: not assessed. Source quality: not assessed. Exactly one field carried a value: 'Domain: cricket.'

I was asked to write a report on it. Three thousand words. I sat in front of that screen for a long time, thinking that in forty-one years I have held this file before. The difference is that it used to be a ground, not a document. The empty fields were not a format. They were a day.

27 November 2026. Eden Gardens, full house. I was a twenty-five-year-old economics graduate filing on a freelance pass from a Delhi sports desk, with four hundred words prepared on the batting. I filed nine hundred on the pause before each delivery — the way ninety thousand people can draw breath together and go quiet enough for you to hear a stud on turf. Anil Kumble took 6 for 12 in ten overs that afternoon. West Indies were bowled out for 123. India, having made 225 for 7, won by 102 runs. The cleanest evidence of that match in my possession is not the scorecard that ran the next morning. It is the second that never fits a column.

Nineteen years later, 2 April 2026, Wankhede. I was forty-three, a magazine senior writer, and I argued my way out of the press box into a seat behind the sightscreen. India chased 275; Mahendra Singh Dhoni made 91 not out off 79 balls and finished it with a six off Kulasekara. The number that came home with me was not 275 and not 91. It was 28 — the count from 2026 — and forty thousand people crying in the same second. I wrote that night about my father's radio instead of the cover drive.

That piece set my method permanently: never the result first, always the inherited emotion. My editor has run a 'what this match means' sidebar alongside every tournament piece I have filed since. But the file in front of me today is not even eligible for that sidebar. There is no match in it. Which is precisely what makes it interesting.

I went looking for the scorecard and found a silence instead. This time the silence was on a server, not on a ground.

The scorecard is a suspect document

My entire working method rests on one premise: the printed scorecard is not a verdict, it is testimony — and testimony always carries room for argument. What the scorecard shows is the accounting of a match. What actually happened usually sits beside it, unwritten.

Ball-by-ball record-keeping in Indian cricket is not a natural phenomenon. It is a cost line. A broadcast match carries behind it a commentator, a scorer, a data operator, a stats feed and a server. A non-broadcast match carries a scorer and, on a lucky day, a handwritten sheet. Both matches are played to the same laws and exist at completely different densities.

That density is set by money, and the money is public. In June 2026 the BCCI sold the IPL's 2026-27 media rights for ₹48,390 crore. The Women's Premier League's 2026-27 rights went for ₹951 crore. Both figures have a direct consequence: where the camera is, the data is; where the data is, comparison becomes possible. Where the camera is not — a December morning, a small-town ground, sixty spectators, one scorer, a scoreboard propped behind a tea stall — a single line survives: 'Match drawn.'

This is why the Ranji Trophy's long decline was never a natural death. It was a scheduling decision. Push the domestic season into the cold window where the morning air helps the seamers, split the fixtures into two phases, move it out of the month when spectators could have come, and you have not killed the tournament — you have thinned its record. And whatever has a thin record becomes light in a selection argument without anyone having to argue.

I have a cheap proof of this. Every time I have wanted to praise a domestic batter in the last few years, I have had to compare his fourth-innings knock to something, and all I had was runs and balls. What was the pitch doing? How old was the bowler? Where was the field? Those three questions decline to answer, because nobody asked them at the time. The ignorance is not accidental. It is budgetary.

Three silences, three different causes

The gaps in the record are not all the same, and lumping them together is the commonest mistake in the trade. The first gap is technological. 18 June 2026, Tunbridge Wells. India were 17 for 5; Kapil Dev made 175 not out; India reached 266 for 8; Zimbabwe were bowled out for 235 and India won by 31 runs. There is no television footage of the greatest innings in Indian one-day history. The BBC had no camera there.

Here is my first stubborn point, and it is visible from a distance: the biggest hole in the record sits at the very top, not at the bottom. The innings that opened a door for a generation is not present in a single frame. Forty-plus years later we know it by arithmetic, not by witness.

The second gap is economic, and far more common. A December morning on a ground whose name you have heard and forgotten. Day four. The home side needs 140 and the pitch is behaving like day five. A twenty-four-year-old at number six, never looked at by a franchise, bats through the last session for 96 not out to force the draw. Two lines in the next morning's paper. One scorecard in the database. Not one ball of that innings was logged, so it has no context, so it has no comparison, so it loses to someone else's 96 in a selection meeting — the 96 that happened under lights with a camera behind the arm. Both knocks are worth exactly the same number of runs. They are worth completely different amounts of evidence.

Which produces the sentence my profession writes least often: selection arguments are rarely arguments about quality; they are arguments about available evidence. A player without data is not a bad player. He is an absent one, and absence is punished more heavily than weakness.

The third gap is the most embarrassing, because it was fillable and the decision to fill it came late. Women's cricket's systematic ball-by-ball record thickened rapidly once broadcast money arrived — that is, after the WPL. Before that, in the domestic seasons, we had a score, an order and very little else. An international career average rested on matches with no durable, searchable detail. Nobody conspired to produce that. It was simply the shape of the investment nobody made. But the effect on the record is identical to the effect of a conspiracy: history looks shorter than it was.

The metric that hides the role

Now the part where sports journalism repeats its oldest error.

Football has spent a decade pricing goalkeepers on distribution — the length of the kick, the accuracy of the throw, the contribution to build-up. I have watched, repeatedly, as a keeper whose basic shot-stopping is declining gets a premium because he can hit a long ball. That is not a football disease. It is a measurement-convenience disease. Whatever is easy to count is quickly declared important, and whatever is hard to count — reading the situation, closing the angle, staying balanced while the ground shifts — falls out of the language entirely.

Cricket has handed that job to the heatmap. Anyone can look at a shot map and say a batter is 'strong through long-on.' The harder question is why the map does not contain the moment he knew the slower ball was coming and played the shot anyway. A heatmap tells you where the ball went. It cannot tell you what role he was playing inside the team — whether he was 70 not out protecting the other end, or 45 and out having cost his side twenty runs. I trust the role more than the scorecard, and the role is never printed.

Which is why the empty file did not first make me angry. It triggered an old reflex. I read the blank fields the way I read a two-line note about a match: what is missing is the largest clue in the document.

The case for looking in the other direction

The fashionable claim of this decade is that cricket has, for the first time, entered an age of complete data. Ball-tracking, DRS, expected runs, role maps, field-placement charts. I think that claim is looking in the wrong direction. The data has grown deeper, not wider. The gap is in altitude, not in depth.

A broadcast match now has so many layers that we can argue about a fielder's foot direction on the third ball of the fifth over. A non-broadcast slice of the domestic season remains exactly as empty as it was twenty years ago. Total knowledge has risen; its distribution has become more unequal. When distribution is unequal, a rising average means nothing, because comparison itself has broken.

Second, and this is the point I would defend in any press box: an empty record is not neutral. Where no figure is found, a quiet conclusion installs itself — that nothing happened here. In cricket that conclusion is expensive, because it gets applied to a player's ability, a team's depth, a series result. A report in which every risk reads 'N/A' must never be read as low risk. It must be read as nothing was examined. That is a one-word difference and a career-long consequence.

Third, the guard against my own favourite ground. 9 March 2026, Dubai. The Champions Trophy final, India against New Zealand, and I had a seat in the stands. That night's record was complete — every ball, every angle, every audio clip. The reason was simple: the camera was there because the richest board's team was there and the ticket market was whole. I was born in the Gulf and I write from India, and that vantage genuinely lets me see some things from outside in. But I have to draw a line for myself. Using Dubai as evidence that capital decides where the camera goes is legitimate, because the attendance, the broadcast revenue and the fixture list all support it. Turning the Gulf into the market thesis of this argument would be inflation. It is a lens, not a market.

Fourth, about the file that started this. A null record inside any large organisation is never only a malfunction. It is also a decision about what was considered worth capturing. A report with no title, no source and no facts has to be flagged as a null input rather than filed as a finding. My trade has a dangerous luxury: we can turn an absence into a story. The price of that luxury is that one day we will mistake the absence for the fact.

What gets logged next

In 2028 cricket will be part of the Los Angeles Olympics — six teams per gender, T20 format. I already know what that tournament's record will look like: dense, glossy, three cameras on every ball, a graphic on every shot, an interface that produces any batter's 'impact' in three clicks. I also know that in February of the same year, when a Ranji match is decided in the last hour of the fifth day, its record will look exactly as it did in 2026 — one line, one date, and a name followed by '96 not out.'

The question is not whether we will have more data or less. The question is what the next big archive project will be built for: to add another layer at the top, or to fill the part at the bottom where the camera never went.

I did not get an answer out of that file. I got its question, and the question belongs to cricket, not to a server: when a match's entire record is empty — title to fact — do we say nothing happened there, or do we ask who it was that stopped writing?