Zero Information Points: Asian Cricket's Coverage Crisis Isn't the Stars, It's the Source

It was nearly one in the morning in Chennai. On my desk there was nothing but the blue of a screen and a file whose every header read N/A. Title: N/A. Source: N/A. Type: unclassified. One-line summary: empty. Author stance: N/A. Purpose: N/A. At the bottom, filled in with what looked like genuine effort, sat one box: cricket_asia. Directly above it, one line that set the tone for the whole document — information points: zero.

I have done this job for twenty-four years and I carry one habit: in any collapsing story, I go looking for the date first. There was no date here. No name, no number, no day. The only exhibit was a taxonomy tag, telling me that somebody, somewhere, had seen the words "Asia" and "cricket" in the same vicinity.

For years my complaint has been that the scorecard lies and the tape tells the truth. Tonight the scorecard told a story of collapse, but the tape kept whispering a slower, stranger story — that the tape itself was empty. And an empty tape is the most useful fact in this whole piece.

The settled view of Asian cricket coverage is that the problem is volume. Too much cricket, too many television panels, too many tweets, too little patience. You open your eyes in the morning and a hundred verdicts on a selection call are already written, and not one of them travels with a source attached. The industry complains that attention spans are shrinking; the audience complains that the same four faces occupy every panel. Both are right, and both are missing the same thing.

We have defined the word coverage by counting outputs — how many stories ran, how many videos went out, how many clips travelled. The number nobody counted is the number of verified inputs. In the trade these are called information points: who, when, how much, who said it, and what backs it up. Give me three to five of them and analysis can stand. Give me zero and whatever stands is not analysis. It is a hunch wearing a jacket.

My own education happened in that gap. Twenty years on the franchise and auction beat taught me that most "character failures" in Indian cricket — a slow strike rate, a strange selection, a rested fast bowler — are outputs of scheduling, purse arithmetic, retention rules and net run rate. I go looking for the villain and I find a system with better PR than any individual could manage.

The night that empty file landed in front of me, I assumed I had found the same system again. This time nobody was in the villain's chair. The source's chair was vacant and the door was open.

Start with the thing that matters most: a tag is a taxonomy, not an argument. Inside the phrase cricket_asia sit three formats, six boards, at least four languages and two time zones, compressed into one string. Whatever unit you build your analysis on, the conclusion will arrive at the same thickness. Take the Asia Cup. When the Asian Cricket Council announced the hybrid model in June 2026, it converted a tournament into an administrative arrangement — hosting split, most matches moved to Sri Lanka, and the decision off the field drawing more attention than anything on it. Something whose logistics are that tangled cannot be described by one English tag.

Second: a null result is still a result, and it tells you where the pipeline chokes. The four standard causes of a blank extraction are JavaScript-rendered pages, paywalls, non-Latin scripts, and PDF or image-based documents. All four map precisely onto the part of Asian cricket that is least machine-readable. Bangladesh's domestic circuit, Nepal's franchise league, Sri Lanka's provincial tournaments, Afghanistan's domestic competition — their records live mostly in PDFs, often in local languages, sometimes on websites no crawler reads properly.

Which produces the claim I hold to be the sharpest in this argument: the cricket whose record is least machine-readable is the cricket that gets covered least — and we explain that outcome as audience demand. The coverage map does not show where cricket is happening. It shows what can be parsed. Nepal qualified for the 2026 T20 World Cup; how many Indian desks ran a single monthly report on that campaign? The question is unanswerable, which is exactly the point.

Third, the detail that stung. Two notes inside the file refuted each other. The first read: "Entities Involved: identify from the information points above." The second: "Source Quality: judge from the source fields of the information points." There were no points above. It reads like comedy, and it is — but it is the same architecture that carries our daily cricket reporting. The lede completes the claim; the body leaves the evidence chair empty. "According to board sources" is the profession's most comfortable alibi because nobody can test it; neither side of the argument has a route to verification. Sources and dates are where a story shows its unpaid debts.

Fourth: whether a take survives has nothing to do with the argument and everything to do with the name. My habit is to swap the name in my own draft. Take Virat Kohli, Rohit Sharma, Babar Azam or Rashid Khan out and put a fringe player in that sentence, keeping the claim identical. If the take dies, it was never an argument. It was a name. Asian cricket suffers this acutely because the reader's eye is trained on three names, and the stories of the other five teams resemble that empty file — no headline, no source, no date.

One more layer belongs here, because money runs through it. Since live data began flowing straight into betting companies, the darkest corner of the data chain stopped being the numbers and became the verification. Where money sits on every single ball, the question "who supplied this and how was it checked" is the first thing to fall. Feed speed rises, source-checking trails behind, and an empty file is a photograph of that decline. We dislike the photograph because there is no score in it.

Injury coverage is the cleanest specimen of the disease. "The player returning from an ACL looks sharp in the nets" — off how many balls? Against what quality of bowler? Across how many consecutive days? For twelve years I read items where the sample was three deliveries and the verdict was full fitness. A body's repair can be measured against a timeline. The mental block cannot, and the mental block is what breaks the second act. That information point never appears in any PDF, which is why it is the least written truth in the sport. The error looks sudden, but the pattern had been warming up for weeks.

Now the section a man in my position owes his readers and which his readers least want to hear.

The dullest explanation is that a scraper broke. Somebody changed a flag, the pipeline jammed, and the output came back empty. That is all. That explanation is strong precisely because it refuses to build a thesis out of one failure event. I should have written it first, and I concede it.

Which forces honesty about my own footing: this entire argument rests on a null result. Sample size, one. One file, one night, one pipeline. If that pipeline returns three clean reports tomorrow, my claim that the coverage map is merely a parse map weakens badly, and I will have to write that I mistook a technical fault for a cultural crisis. I have made that error before. I keep a list of takes I got wrong and reread it quarterly so it can remind me how reliable I actually am.

The second temptation I want to refuse is going quiet behind "it's the system." That is the safe, unfalsifiable, sophisticated-looking exit, and it launders somebody's real responsibility. So plainly: the decision belonged to the extraction system, the date is today, and I cannot attach a name to the decision-maker. That does not mean accountability is absent. It means accountability is diffuse, which is true of every such system and is the least reported fact about them.

Here is the forward call, written as a claim you can check. If within the next three months the pipeline starts reading non-Latin scripts and PDF sources, coverage of domestic cricket in Nepal, Bangladesh and Sri Lanka will surface on English desks — at minimum the space an IPL trade rumour gets. If it does not surface, the problem was never technical. It was priority. And then the question stops being what the next big Asian cricket story will be. It becomes which language it gets printed in first, and how long before we learn its name.