Testimony of an Empty Column: The Cost of Writing 'Insufficient Information' in Cricket Analysis

At 1:47 in the morning in Delhi, there is a sheet on the desk — twelve columns, and against every one of them the same line: "Insufficient information — assessment not possible." The format box is empty. The venue box is empty. The player's role and recent numbers are empty. Broadcast values, selection rules and auction valuation are empty. What should have become a one-page file inside fifteen minutes has stayed an empty ledger. Only one thing is full: my notebook, thirty years old, carrying dates, team bus bills and the names of men who shared rooms.

The real danger of a blank sheet is not its blankness. The danger is that filling it is the easiest job in this trade. Any report with the word cricket in it keeps a guessing hand permanently ready — "his form has dropped", "there is a weakness against swing", "the franchise has opened the purse". Not one of those sentences comes from a fact. They come from the weather.

The first-stage extraction returned zero. That means the article from which facts were to be drawn never reached the process at all — no body text, no publication date, no source, no author's stance. In that situation the most honest report is the one that writes: insufficient information, assessment not possible. That line takes ten seconds to type. Failing to type it costs years.

In cricket, every number needs a tag before it means anything, and that tag is the format. A Test average, an ODI strike rate and a T20 economy rate are three languages, and seating all three at one table is not comparison but a typing error. An economy of 8.5 is a bad day in a Test; in a T20 it is ordinary. A strike rate of 45 can be a brisk innings in a Test; in a T20 the same figure is a stall. On a sheet where the format box is blank, every average, percentage and spike that gets filled in will not be false — it will merely be incomparable. And the market sells incomparable figures as comparisons.

This is why for thirty years I have opened the ledger before writing the commentary. The habit began in 2026, as a trainee at a Madras daily — the expense sheet first, the story after — and it has not left me. My first Ranji assignment was the rain-ruined December draw between Delhi and Railways at Feroz Shah Kotla in 2026. The press box held four men and a scorer, and two of them asked whether I was there to interview the players' wives. I filed 600 words that night, the paper ran 140, and I returned the next morning with a notebook listing every player's hometown, club, diet and family phone number. Numbers come later. First you learn who paid for the team bus and who shared a room with whom.

I have proof of the format tag from the 2026 WTC final as well. That afternoon in Southampton was one Test, one season, one condition of ball — and selling that single result as a team's true strength has always been convenient. A dew-soaked night ODI runs on different metrics; a day-night Test on others again. The history of the laws says the same thing: Duckworth-Lewis-Stern was first applied on the big stage at the 2026 World Cup, and the old "result on run rate" has carried no meaning since. At the 2026 World Cup final the Super Over was tied and the trophy was settled on boundary count. An analyst whose sheet carries no date for the laws is hunting a new road with an old map.

I also keep a reference library, and honestly, the temptation to apply it is constant — the 2026 match-fixing scandal, the Lord's spot-fixing case of August 2026, the 2026 IPL spot-fixing affair, the India-Pakistan bilateral freeze since 2026, the NOC system that releases players to overseas leagues, the red line on government interference. These are permanent texts of cricket governance. But repeating a text and pasting it onto a live case are two different acts. On a sheet carrying not one fact, adding any of those names would be filler, not reporting.

Sitting through twenty Kotla winters taught me one thing: the Kotla taught me that noise and truth keep different clocks. A crowd's roar rises fast and sits down fast; a recorded fact arrives late and stays late. The same happened with this report — a technical fault was logged in the pipeline, and the data label itself came back as a broad, loose tag instead of the expected name. That is not news about cricket. It is news about cricket coverage, and it deserves to be filed too.

How filler happens I learned across 44 days in 2026. My pitch for the IPL's first full-season travel diary was approved on one condition: file every day. Fourteen league matches, seven cities, moving with Delhi Daredevils. The franchise denied me the dressing room all season — "not a place for a lady", the media manager said — so the diary was built from bus seats, breakfast tables and the twenty-minute mixed zone. On 30 May at the Wankhede the side were bowled out for 87 and lost to Rajasthan Royals by 105 runs; my 1,100-word piece that night did not reach that score until the ninth paragraph. A score is a data point inside a match situation, never the story. The day you let it become the story is the day you start swapping it for an estimate.

Four traps of exactly that kind sit on today's sheet. The format is unavailable, yet the urge to describe someone's "form" is strong. No league or board event has been identified, yet two lines about auction premiums and broadcast rights could be written with confidence. No person, team or date has been fixed, yet "retirement cliff", "injury load" and "cross-format form transfer" can be enumerated as risks. That is the filler — an article that reads as finished and audits as hollow.

The second half of the problem happens quietly. When a template is blank in every cell, it is sometimes read downstream as "no risks found" rather than "no risks assessable". The gap between those two sentences is the credibility of the entire trade. So one more tag must travel with such a sheet: analysis blocked. Without it, a blank sheet arrives on the next desk as a trustworthy report.

Here is the counter-intuitive part. This report, which contains not a single cricket conclusion, is the strongest report in the chain. Cricket coverage's real shortage is not data but verification — and the number shouted loudest is often the one least checked. Some of that is structural: big matches, big names and big noise invite more scrutiny, yet the ledger's pages fill fastest in cases where nobody wants answers. Some of it is my own habit. Protecting sources can curdle into managing access, and a silence traded for convenience never becomes part of the ledger again. The fix is plain: write the record first, then make the withheld lines part of the record as well.

In this instance, the withheld lines are also clear. Three things are needed to run the process again: the article's title, source and publication date; at least three information points, each tagged with format (Test, ODI or T20) and competition type; and the author's stance plus the article's purpose. After those come entity resolution for players and teams, a time-sensitivity grade, and numbers recorded with their units. The day that sheet is complete, the analysis moves from blocked to running. The ledger never lied; it just waited for the night shift. The question is whether, when the sheet lands on the desk next morning, we can resist the urge to fill the empty cells — or whether we print the weather as fact one more time.