The N/A File: The Cricket Ledger Nobody Keeps

The morning of 10 February 2026, Chennai. That week in the middle of a tournament cycle when the calendar carries fewer matches than arguments. A file was open on my laptop — the kind that lands on our desk before every major series: a report that breaks a source text down into information points. The page opened and the first three lines read: Title: N/A. Source: N/A. Type: Unclassified. Information points: none. For twenty-two years I have wrestled with these files. An empty page had never come back. And that emptiness felt oddly familiar, because cricket produces it every day — just without the noise. A Ranji match is played, a scoresheet is filled, four lines appear in a local paper, and then the whole day survives nowhere. What is not recorded is not missed. I did not close the file that morning. I read it as one more ledger — the one that tells us what we have and what we do not. The failure has the same shape in both places: the system runs, the template holds its place, and the answer comes back as N/A. Sitting twelve kilometres from Chepauk, I kept returning to the most honest part of that document: the note underneath declaring that nothing had been filled in by inference. That is the discipline cricket reporting uses least. We learn to fill early and leave blank late. Seventeen years earlier, in 2026, I was on the Chepauk nets with Tamil Nadu's Ranji pre-season camp, fresh off an MS, with no grand method — a notebook and a habit. Every day I wrote down who was bowling at whom, who was taking the first over against which batsman, who was standing outside the net waiting. That year an eighteen-year-old bowled forty overs across three days. Washington Sundar. The height of the release, the patience in flight, and the thing no scorecard carries — his pace was unchanged after the fourth over. The camp closed with a two-day intra-squad match. He took 4/27. That figure sits in my notebook with its 2026 date attached, and if anyone today compares it to a 2026 number, my first question is which format we are talking about. A 2026 figure answers a 2026 question. The day we forget that, the ledger becomes a headline — and a headline is stale by the next morning. The most useful record from that camp was not 4/27. It was that roughly sixty people in the E. Stand asked every day whether that boy would bowl. Sixty people knew an eighteen-year-old before his debut. That information existed in no database. It lived in an informal account kept in a stand, written by nobody, and it disappeared. My method came from there. A hundred and fifty words of net notes before lunch, a long read on Friday. Reader questions within two hours of the first note, and the next day's net focus built on those questions. It worked. It was community-fed reporting, and it carried a weakness I later had to name: I began letting replies determine what mattered. What readers did not ask about quietly dropped out of my notebook. I had to admit that in that stretch I wanted applause as much as accuracy. The wound deepens during a tournament cycle. Everyone counts the score. Nobody has time to count who bowled how many overs in the nets, who repeated the same action on the third day, whose knee has been taped and since when. A four-week tournament compresses emotion and shrinks the record, because the entire machinery of coverage points wherever the camera points. Across the last ten years I have kept three separate ledgers. All three reached the same conclusion. The first is the net ledger. What Chepauk taught me is that India's bench problem is not a talent problem. Of the fast bowlers who take more than sixty domestic wickets in a season, several never reach the national setup's eyeline because their work is recorded somewhere nobody looks. Building a second XI is the hardest job in world sport, and the difficulty is documentation rather than selection. A player with no written record loses, in a selection meeting, to a player whose record a television commentator has repeated. Across my net notes from 2026 to 2026 a pattern is plain. The bowler who could bowl three spells in a day was discussed less; the bowler who sparkled in one spell was discussed more. Forty overs of work is invisible. Four overs of work is visible. That is cricket's aesthetic, and it is also selection's defect. The second ledger belongs to the stands. In 2026, with the Russia World Cup pulling cricket traffic down, my editor sent me to Chennai's football fan zones. I ran a thirty-two-day diary across three supporter clubs. There was a screening at Nehru Stadium where twelve hundred people watched a knockout game, and I collected three hundred voice notes. That diary drew four times our normal cricket page views. What it gave me was the knowledge that a crowd keeps its own ledger, often more precise than ours. Third of July 2026, Nehru Stadium, during the half-time break, a supporter told me the first change should have come in the eightieth minute, because across the middle thirty minutes the opposition had attacked the same channel twice. He had seen it on a clip, repeatedly. The man in the stand counts repetitions. The man in the press box counts moments. When I brought the method back to cricket, every Chennai training report began carrying one reader question and one supporter quote. I started Fan Poll Friday, which shaped the following week's net focus. It worked, and it is also true that it bent me toward the crowd. Becoming a device for measuring applause is dangerous, because the crowd is loudest at exactly the moment clarity matters most. So I made a rule: write the cold chronology first, layer the atmosphere onto it afterwards. Never the sound of the ground in place of the order of events. The third ledger covers the women's game, and I keep it more strictly than the other two because every year of it is public. Twenty-third of July 2026, Lord's, a World Cup final. India lost by nine runs. That match drew more coverage than any women's match before it — and still less than a bilateral tour by the same team drew a year later. Mithali Raj and Jhulan Goswami played that final. One line from my diary entry that day: the question after a final is not who lost; it is who writes for the next six months. Very little was written in those six months. In March 2026 the WPL launched. That was a genuine shift and I do not underrate it — but it was not year zero. Women's cricket was being played and reported before that, thinly, and the dates of that thin layer were never entered in any ledger. Second of November 2026, Navi Mumbai, India won the Women's World Cup. Those calling the win a beginning are forgetting the dates. Those calling it an ending are forgetting the broadcast commitments not yet honoured. For me the most important number from 2026 is not the final's score. It is how many domestic women's matches from that season have a complete scorecard in a public database. I have half an answer. Half an answer is itself the answer. Here is the part that reads backwards from outside. The industry believes more data produces more clarity. Ten years tell me more data only produces more data about whatever was already being measured. What gets scored grows. What does not get scored — the fourth net at a camp, the twelfth-day rewind, the second XI's off-spinner nobody watched — does not grow. And because it does not grow, the selection model will keep undervaluing it. The error is structural, not technical. That is why the empty file of 10 February 2026 did not read to me as a glitch. It read as a mirror. It did exactly what domestic cricket does every season: it stood up the template, left every field blank, and went quiet with N/A as its answer. The system did not fail. The system completed its work and nobody asked why the fields were empty. This is where the outside reader makes the biggest mistake. He assumes an empty report means there was no story. The opposite holds. An empty report means the route to the story was blocked. Those are different situations entirely. In the first you report an absence; in the second you report your own absence. The first is journalism. The second is bookkeeping. My notebook contains both, and I write them separately. One field in that file troubled me more than the rest: author stance, listed as N/A. That is the most dangerous blank of all, because when the file is finally populated, nobody will know whether the original was written to praise a player or to report a fact. A missing stance is not neutrality. A missing stance is unknown, and treating the unknown as neutral is the same error we make in selection when we favour the player whose name we heard first. I have one more admission. The empty file gave me an opportunity I might not otherwise have had — to demonstrate that I do not write without information. In twenty-two years I have filled in blanks that should have stayed blank. A senior player did not appear at the nets and I wrote that his workload was being managed, when all I had was his absence. That is the same disease in a milder form. So I am entering this as a number, not a correction: 10 February 2026, one empty file, and the first full entry in my notebook containing nothing at all. What follows is questions only, and at this point in a tournament cycle questions are the right answer. The next selection round will ask who plays. My question is who keeps the book — the fourth net at Chepauk, the second XI's off-spinner who bowled forty overs last season, the domestic women's match whose scorecard survives in a local edition. Until someone fills those fields, the headline on our cricket reporting will keep carrying the same letters. And I know that the next time a boy bowls forty overs across three days on the Chepauk nets, the highlights will not show him — because highlights do not show repetition. The nets at Chepauk remember what the highlights forgot. All that is needed is the man who sits there and keeps counting.