Zero Information Points: The Asian Cricket File That Kept Only Its Label

Six-forty in the morning, Chepauk. The gate was still locked, two men sat silently at the tea stall outside, and the first net session was a good ninety minutes away. I opened the laptop and pulled up the file three days of work had gone into. On the screen was a table — twelve rows, an N/A against every one, and in the last cell a single word: cricket_asia. Where the headline should be, N/A. Where the source should be, N/A. The article type — "unclassified." And the list of information points — empty. Absolutely empty. That morning I had eighteen years of Ranji scorecards, eight years of net diaries and more than three hundred voice notes behind me, and what came back was one geographic label. Twenty years ago, on my first day at the Times of India sports desk, I was taught exactly one rule — news is not what you heard, it is what you have written down. That rule has saved me many times. That morning it saved me from one thing: filing a lie. Go to any cricket desk and say you have a packet with zero information points. The first reflex will be: "then there's nothing to print." My experience says the opposite. A document in which nothing is recorded is itself a document. And the oldest illness of Asian cricket is precisely this — we have recorded the game less than we have labelled it. First, what an information point is. It is a fact pulled out of a piece that can carry the next conversation: who, when, where, how much, under what conditions. It is something you could tell another reporter on the phone and he could run with, unverified, without falling over. That morning there was not one such point. Which means every conclusion that followed — format, player, team, league, governance — would have stood on air. And there is the first lesson. cricket_asia is a geography label, not a format label. Asian cricket contains the five-day Test and the hundred-ball franchise game. Their tactical logic is as different as a Test's third innings is from the last four overs of a T20. So the label cannot tell you whether the story was a Test or an IPL match — and if you assume one, the rest of the analysis rests on that one bad guess. Look at the asymmetry: the label survived, the body died. That pattern is not a coincidence. When a pipeline's classification runs off source metadata — the URL, the section, the feed category — and the article's body text never extracts, this is exactly the shape you get. One cell filled, everything else blank. Which means cricket_asia must be read as an estimate, not a fact. The label at least tells us the matter touches the Board of Control for Cricket in India, the Pakistan Cricket Board, Sri Lanka Cricket, the Bangladesh Cricket Board or the Afghanistan Cricket Board, or an Asian Cricket Council event. Nothing more. Whether it was a bilateral India-Pakistan series, an Asia Cup, a franchise transaction or a rule dispute cannot even be guessed at. It is worth saying here that Asian cricket's record-keeping over ninety years has improved and stayed incomplete in the same breath. The scorecard we have. The first Ranji Trophy season was played in 2026-35 and that number is still in the board's tournament record. The first Asia Cup was played in Sharjah in 2026, and that final is recorded too. Every ball that landed on the pitch, every run scored, every wicket lost — all of that is safe. What is not safe is the world outside the scorecard. Who was bowling to whom at the nets, who got no batting time in the practice match, which batsman did not bowl a single extra over of spin in three days, how many players were called to a state camp and how many turned up. None of it makes a newspaper, none of it enters a database, and next year when the selection committee sits, that missing record is the one that matters most. In 2026 I was at the Tamil Nadu Ranji pre-season camp at Chepauk. There was an eighteen-year-old off-spinner, Washington Sundar. Over three days I counted forty overs from him. The release point, the wrist angle, that small pause that makes the ball arrive later than the batsman expects — all of it is in my notebook. The E. Stand had a group of about sixty people who asked about him daily. I filed 150-word net notes on WhatsApp before lunch and a long read on Friday. He took 4/27 in the two-day intra-squad match that closed the camp. Those forty overs and that 4/27 exist in my diary. Not in any official record. If I had not been standing there, those forty overs would have had no existence, and that would not mean they were never bowled. I kept the count when nobody else was counting, and that one habit fixed the architecture of everything I write — ball, over, date, name. The quote comes later. From that habit came the net-to-news method. The rule is simple: publish a tactical observation within two hours, then ask the reader to rate it and hand you the next question. It is community-fed, and that is also its danger — when the room goes cold, the writer reads it as a signal that what he is filing is wrong. I have fallen into that. During the 2026 World Cup in Russia I ran a thirty-two-day diary out of Chennai's fan zones: three supporter clubs, twelve hundred people watching a knockout game at Nehru Stadium, three hundred voice notes. The diary drew four times our normal cricket page views. It was not decoration for me, it was a route — walking in from the stands. I brought that route back to cricket: one reader question and one supporter quote in every training report. Fan Poll Friday began deciding the next week's net-session focus. And there I had to admit my own weakness — often I was chasing applause, not information. So I set three tiers and began naming them in the copy. Seen — it happened in front of me, I was there. Told — someone phoned it in, and I have a name and a date. Documented — it sits in a paper, a scorecard, a board release, a published record. There is no fourth door. That morning all three were empty. Not seen, not told, not documented. One more rule, and it has been the hardest for me. Two independent confirmations before anything enters the ledger. Independent means two sources not agreeing because they heard each other. In a decade of WhatsApp groups and district correspondents the line blurs. A well-wisher's claim starts feeling like a source. It is not a source, it is a hypothesis still waiting to be checked. Now the objection that will land first: if there's no information, what's there to write? It is a fair objection and I take it seriously, because there is a real anxiety behind it — the reader's time. He picked up his cup of tea and asked you for news. You told him you don't have any. In his ledger, that is a loss. My answer is that when a file has zero information points and one filled label, the file is reporting on how our record system fails. That is not a weather report, it is a radar report. A radar report has value, provided you do not claim the radar saw a storm. That is the whole difference. I did not write that a storm arrived. I wrote that one line of the radar survived and the rest died. The second objection is cleverer, and it is my own disease. When a writer has a record, he turns it into an argument-stopper. "The ledger says" — and the debate ends. That is wrong. A 2026-35 scorecard does not answer a 2026 selection dispute, because the format changed, the rules changed, the over limits changed, and an over then is not an over now. Without a date, a record is just noise. Stamp every comparison, or it is not a comparison, it is an old photograph you are passing off as today's evidence. The one thing genuinely present in this empty packet, and the most reliable fact in the whole affair, is the asymmetry. The label survived, the text vanished. If the article had truly been empty, the label would not have survived either. The label survived because it came from outside the article — the site section, the feed category, the URL path. Which means the failure is mechanical, not editorial. That is unpublished information, and it was the most useful thing I found that morning. There was another trap in the packet, and I want to name it in plain words because I came close to it. If I had filled in two or three players from memory, the paper would have looked complete. A senior batsman whose form is sliding, a young star whose auction price outruns his output, a fast bowler with a long injury history — those three templates turn up in Asian cricket coverage every week. Writing them was the easiest thing available. And the most expensive. Why expensive? Because what you write about a cricketer lands somewhere in a reader's life. A fantasy team, a betting market, a selection argument, a child deciding whose bowling he wants to watch. If I filled in an age curve or an injury history from memory and got it wrong, I did not break the record — I forged it. A forged record is more dangerous than a real one, because you can check a date on a real record and not on a forged one. Time has its own arithmetic too. Auction news is counted in hours, a match report in days, governance analysis in weeks. When a packet comes back in this condition, the first task is to establish how old the material is. Analysis written without a publication date becomes commentary on a match that finished two series ago. I have the evidence — I once treated a stale packet as live, filed, and learned the next morning that the series under discussion had already ended. Re-extraction needs four things: the article title and its source, a populated information-point list, the entity list, and the publication date. With those four, all eight dimensions open at full depth; without them, the report that now exists is the correct and final output. I know that is not a satisfying answer. Much of good journalism isn't. Which brings us forward. When I next sit down to write, the first question is not what the article said. It is how many other Asian cricket stories are sitting in exactly this condition — one label alive, body lost, nobody counting. How many domestic scorecards exist only in a district edition that ran once and never reached a database. How many camps are accounted for only in a clerk's register. How many women's series have coverage so thin before 2026 that calling it a record is generous. I will not write that the 2026 World Cup invented women's cricket. That final at Lord's was played on 23 July 2026; England made 228/7 and India were bowled out for 219 in 48.4 overs — a nine-run defeat. That is a date, not a birth. Women's cricket was played, written about, and very sparsely printed long before it. What changed is that after that date, the absence of coverage stopped working as an excuse. The Women's Premier League arrived in 2026. Its media rights for the 2026-2027 cycle sold for ₹951 crore, and at the first auction Smriti Mandhana went to Royal Challengers Bengaluru for ₹3.4 crore. Those numbers are documented, in board announcements and public auction results. And they raise the harder question, because a sport that raised that much money still does not hold a complete record of its own early coverage. The 2026 Women's World Cup staged in India was the biggest event the game has had in this country. Its real account now sits inside broadcast commitments shaped by the league market, and the question is how many domestic minutes survive inside them. This is why every report I file carries one thing from the nets that no scorecard holds. Last time at Chepauk, an extra spinner in the morning session bowled roughly seventeen overs straight and did not bat afterwards. It appeared nowhere. But next month, when the domestic side's bowling depth is debated, those seventeen overs will be the only solid ground under the argument. India's second-innings problem is selection, not talent — and the selection problem only looks like a mystery because we stopped logging everything except the first innings. One admission, because the piece is incomplete without it. I do not feel good writing this. A reader asks for something and I tell him there is nothing. My wiring reads the room first, and this room is saying: give us something. I won't. When the correction comes, I will publish it beside the empty cell, not over it. A correction that hides the count is not a correction, it is a quietly altered record — and I have no interest in building those again.