The Empty File, the Unfinished Scorecard: A Cricket Analysis Report With Zero Information Points

At three in the morning, a stadium teaches a different kind of truth. The commentary box has emptied, the dressing-room noise has folded away, the camera outside the boundary is tired too. Only one file stays open — and inside that file, there is you.

Last week one such file landed. Eight analytical dimensions. A risk matrix. A transmission map. Every heading in place, every sub-heading ready, the table columns standing straight — and in every cell where a fact is supposed to sit, two letters: N/A.

Think of a scorecard. The umpires are named. The toss time is recorded. The overs have been counted. There is even a mention of rain. Only nobody has written down the runs. Nobody calls that paper a record. Nobody calls it analysis. It is called an incomplete form, and it is sent back.

But this file refused to go back — and that refusal is the actual story here. Because inside the file was a field called "information points", and the list was entirely empty. A document that saw an empty list and stopped itself is more honest than the thousands of documents that fill the same space with something.

I began on a digital desk in Mumbai writing 250-word agency-fed match reports. I learned the game in 250-word fragments, then listened for the silence between them. For four years on that desk I was told that tactics were "for the boys". The press box was narrow, but the game was not.

Picture the pipeline of that era. A wire feed arrives — result in paragraph one, two quotes in paragraph two, the score in paragraph three. A sub-editor cuts, the desk moulds it into 250 words, and the reader next morning believes they have watched the match. Today the same work happens at scale in two stages. Stage one — break what has been read into facts: what was the headline, who was the source, which entities are involved, which hard information points emerged, what is the time sensitivity. Stage two — build the analysis on those facts: format, player, team, league, governance, risk, narrative, industry transmission.

Between the two stages sits a condition nobody writes down. If stage one comes back empty, stage two cannot build anything. A building's weight is carried by its foundation, not by its blueprint.

One more thing in that document needs reading. The domain label was cricket_asia, while the assigned domain was "Cricket". This is not a small matter. A regional sub-label cannot replace the domain label. The moment it does, the analysis slips out of the format-based branch and into the region-based branch — and then Test, ODI and T20 numbers settle into the same basket without anyone flinching.

This is why the question people usually ask about analysis points the wrong way. They ask whether the analysis is correct. The first question should be whether the fact the analysis stands on actually exists.

An information point is the sentence you can place on someone else's desk tomorrow, in front of someone else, and it will not break. "The batter played a brilliant century" — that is not a fact, it is an opinion. "The bowler conceded seventeen runs in his last three overs" — that is a fact, and nobody can dispute it. When the count of such sentences is zero, one of three things is true: the source text was so thin it contained no hard sentence at all; the extraction was left unfinished; or both. In all three cases the route forward is the same — declare a null result.

Here is a professional truth worth writing down. When an analyst says "I do not have enough facts", he is doing his job. When he fills that empty space instead, he is abandoning the job — even if a byline arrives as the reward.

The format declaration is the first wall. Test, ODI and T20 are not three different games; they are three different economies, and their currencies do not convert. An economy rate of 7.2 is respectable in T20, average in ODI, and close to irrelevant in Test — because a Test bowler's job is not to stop runs but to take twenty wickets. In the same way, the phrase "strike rate" wears two different numbers. For a batter it is runs per hundred balls; for a bowler it is balls per wicket. One name, two entirely different meanings, and merging them in a single sentence is the most common error in cricket analysis. When the format is undeclared, that error becomes compulsory. Without a format, every comparison — of a player, a team, or an ICC ranking — is contaminated. The name for this is cross-format contamination, and it is the first door of analysis that is most easily left open.

The ranking argument hangs off the same wall. The three format tables are built separately and updated separately. Knowing perfectly well that Test points systems keep changing and that ODI and T20 schedules are unequal in length, we still merge all three into one sentence during an argument. And the home-away gap sits on top of that. An average built on subcontinental pitches at home falls to roughly three-quarters on foreign surfaces — this is no secret, it can be read off a pitch report. But when there is no calendar anchor at all, you cannot even establish whether the tour under discussion was home or away.

Without a named entity, no metric can be selected. No player name, so no role; no role, so no metric set. This sounds like theory. It is daily practice. An opener's numbers and a finisher's numbers are printed in the same column and do different jobs. One line keeps returning to my pitch notebook: twenty-five off twelve balls at the death reads as less on a scorecard than fifty off forty-five from an opener — while the first wins the innings and the second slows it down. A finisher's measure of failure is different. His job is to advance the team even if it costs his wicket; average punishes him because average counts how often he was not out. The same average rewards an opener, whose real task in the first ten overs is not to protect the ball but to take the risk of scoring. In this country we have learned to weigh both on the same scale, and that scale does not lie — it simply weighs half the mass.

The team landscape is shut behind the same door. Without a team's name, no tier can be assigned — elite power, middle tier, emerging force, or associate. Without an opponent, no style collision can be constructed. Pace against a short-ball weakness, spin against visiting batters — all of it rests on names. For me this is the emptiest cell of all, because Indian cricket's oldest mistake sits right here.

I hold that India's bench strength is a selection failure, not a talent shortage. Every domestic season throws up at least ten names whose first-class record is good enough to travel. The difficulty lies elsewhere. Zonal selectors have quietly been replaced by franchise scouting, and a franchise asks a different question — "what will this player do for me", not "what can this player do for the country". Both questions are legitimate; they do not produce the same answer. The Ranji Trophy no longer commands the media footprint it once did, and that absence makes the selection process opaque. Even knowing that not every Indian domestic match will be broadcast, someone somewhere has to know, week by week, who did what in which Ranji match. When that information is empty, the bench-strength debate runs on hope rather than fact.

The evidence of sound has been left out of this file too. There is no stadium in the document. No Eden Gardens, no Chepauk, no pitch report, no dew, no rain. In my trade that is not a small gap. Crowd noise is a character whose dimensions can be measured — which over the volume rose, which ball produced silence, which review made an entire stadium hold its breath together. That is data, and it never reaches the microphone because the table has no column for it.

One more thing belongs here. The democratisation of Indian cricket is happening in Tamil, Hindi and Bengali microphones long before it shows up in a board press release. A match that exhausts the English commentary box in five minutes becomes legible in a regional language, because there you do not get "the ball was dangerous" — you get the dew making it impossible for the bowler to release the ball at all. That is the difference. One person is explaining technique; the other is explaining the temperature of the ground.

Price and sporting value are two different documents. An auction price is a statement by the market; it is not a statement by cricket. One question goes missing most often in the business section — was that price paid for the player's cricket, or for his scarcity? Every auction produces three kinds of premium: the local young star, the rare all-rounder, and the one bought in a panic. The third is the most expensive and the least discussed.

The way I test this I borrowed from football. At the 2026 World Cup I followed three brothers from Casablanca who had saved four thousand two hundred euros over eighteen months and travelled six thousand kilometres; their tournament ended after one result. That same week Neymar's transfer fee of 222 million euros dominated the headlines. I put the pilgrimage first and the tag afterwards. A price tag is a story the market tells; a pilgrimage is the answer. The cricket translation is direct: a player's price is not proof that he will win you a match; it is proof only that his services were considered scarce at that moment. Scarcity and utility are different things. The concrete test is this — watch what that player does in the phase where his team actually loses. If the answer is that he is not on the field in that phase, the price was paid for something else.

Source grading is the discount applied to every claim. A board release, an established cricket outlet, general media, self-media — each carries a different discount, and printing all four with the same confidence is the error that has cost me most. In that document the source field read N/A. This does not mean there was no source; it means the discount could not be set, and therefore no claim could be made. The media problem of Indian cricket sits exactly here. The most-shared content is often the least-graded content, and the least-graded content is often written with the greatest confidence.

Governance stories hide in quotes, not in the lede. Regulatory stories — NOC disputes, central contracts, revenue-share arguments, disciplinary action — rarely arrive in paragraph one. They arrive inside a quote, after a "when asked about this". If extraction only reads the lede, it will miss them entirely, and the governance dimension will look empty in the analysis when the biggest fact in the story was sitting right there. A caution attaches to this. If an extraction finds no integrity signal, do not conclude there was no integrity risk. Not finding and not existing are different things, and merging them is this profession's oldest sin.

The risk matrix is a scalpel for celebratory stories. A large share of cricket coverage is festival journalism — centuries, comebacks, records, farewells. Three things are almost never present in such pieces: injury, workload, and overhype. From my own years of watching matches, whenever I have audited a glowing tour, the first questions have been how many balls those runs cost, how many flights were taken, and how much cricket is scheduled in the next two months. That question does not spoil the celebration; it makes the celebration last.

The calendar anchor is the real address of form. No date, so no time sensitivity; no time sensitivity, so no narrative phase — no germination, no acceleration, no climax, no backlash. The meaning we use for "form" in cricket is half the game and half the calendar. A player's slump is often not a story about technique; it is a story about the fixture list. The Future Tours Programme is no administrative artefact. It is the paper that decides which player jumps from which format to another in which month, how many hours he spends in an airport, and which week he can play for his Ranji team and which week he cannot. For me this is the moral calendar question. A fixture list is not a logistics detail; it is a statement of institutional priorities. The domestic window from December to February — when the Ranji Trophy is played and when its coverage is thinnest — is not a coincidence. It is a choice. And when there is no calendar anchor at all, you cannot even say whether the slump under discussion is the product of three format switches in five weeks or a genuine technical failing. Without a date, every form argument is guesswork.

The transmission chain has no input at all. When there is no story, nothing enters the chain — no broadcast, no South Asian market, no talent supply, no capital network. Yet one thing in that document was not zero: the label cricket_asia. That label is not a fact, and it is worth remembering. Still, it is a pointer, and it points toward the richest cricket market on earth. This is the real danger. In the market with the most money, mistaking a label for content is easiest. When a regional label replaces the domain, analysis moves into a branch where it cannot be audited. And analysis that cannot be audited should be called advertising, even when it has dressed itself as analysis.

Now the part least written about.

We audit the output. Not the input. The entire cricket argument rests on this — who bats at three, yorker or slower ball, who should be rested and who should not. Beneath every argument sits an information point nobody verified. We are arguing on the seventh floor of a building whose foundation nobody has inspected.

A direct incentive sits behind this. Confidence gets published. Doubt gets spiked. "Sources say" is the shortcut that outsells "I did not have enough facts" — and that gap belongs to the desk, not to the reader.

The second point is the one that troubles me most. An analytical framework can itself become a costume. Eight dimensions, a risk matrix, a transmission map — all of it looks like rigour, and looking rigorous is easier than being rigorous. What this document did is rare precisely for that reason. It built the scaffolding and left the cells empty. Most published analysis does the reverse — thin scaffolding, filled cells, and data extracted from somewhere underneath.

The third point is the most uncomfortable. The board-adjacent register — press-conference paraphrase, "sources say" with no named document behind it — is often the final product of an empty pipeline. When extraction yields nothing, the writer reaches for the language of the press conference, because that language feels pre-approved. Then that same language goes to print as analysis.

The one risk this document flagged with complete confidence is not about cricket but about systems — silent pipeline failure. A system that returns "success" with an empty information list, a blank summary and an unevaluated time-sensitivity field. That is the risk nobody sees, because nobody inspects a thing that looks successful.

So what is the fix. A simple door with four panels. Before any cricket analysis is published, it passes four questions. Is the information-point list non-empty. Has the format been declared. Is there at least one named entity. Is there a calendar anchor. If even one answer is no, what has been written is not what happened. It is what the writer believed must have happened.

This document built that door for itself, which is why it came back empty. One question remains, and it is not a question about cricket. If that door were installed on every cricket desk, how many published analyses would pass through it? And who would inspect the list — the editor, the board, the broadcaster, or the one paying the price?

I will wait. At three in the morning the stadium will teach its truth again. Only this time I would like the file to hold at least one fact — one ball, one over, one name. I will write the rest of the story myself.