The Hollow Template: A Cricket Report With Eight Full Boxes and Not One Score

11:20 pm in Hyderabad. A file sits open on the laptop with eight boxes — format and match analysis, player technique and data, team landscape, league and commercial ecosystem, rules and governance, a risk matrix, public narrative, industry transmission. Every box has a table, every table has columns — average, strike rate, economy, home-away splits, twelve-month trend. Every cell carries the same stamped sentence: insufficient information.

Title: N/A. Source: N/A. Information points: empty list. Players: none. Format: undetermined.

It arrived on my desk looking like a complete report. Not like a scorecard, where the first glance tells you no match was played. This is the other kind of document — the one that looks fully populated and contains nothing. In this tournament cycle it is the most dangerous piece of paper I have handled, and it is not the blank page. A blank page makes a reader cautious. A fully built scaffold with sand in the foundation makes him comfortable.

In 2026 the problem with cricket coverage is not a shortage of information. It is that information and its costume now look identical. Match previews, auction autopsies, player profiles, three-bullet 'deep analysis' threads — all built on one template: a sharp claim, a graphic, and a number that everyone cites and nobody checks. The template was not built by a machine. We built it. The machine only started filling it overnight.

My own ledger runs back to 2026 — filing for Sportsworld in Madras, a Cricinfo byline from 2026. In between came the season I spent around the 2026 match-fixing investigation, where I learned that silence is never a certificate of innocence. No evidence against a man is not the same as a man cleared. The same lesson applies to data today: the absence of support for a claim does not refute the claim, and it does not license publishing it either.

May 21, 2026, Rajiv Gandhi International Stadium. Mumbai Indians made 129/8 and beat Rising Pune Supergiant by one run. Krunal Pandya made 47 off 38, but I froze on Jasprit Bumrah's 2/26. Three clips, seam angle and release height, my kinesiology training doing the talking — 2.1 million impressions. That thread travelled because every clip carried a timestamp and one clean number. Without the denominator, nobody remembers it today.

The following year at the Bengaluru auction I put the same discipline on a spreadsheet. Rajasthan Royals paid Rs 11.5 crore for Jaydev Unadkat after his 24-wicket 2026 season. In IPL 2026 the same bowler finished with 11 wickets in 15 matches at an economy of 9.65. I built a six-slide auction autopsy. It was my most-shared auction post of that season, not because I scolded anyone, but because I wrote down the role the cheque was signed for.

A franchise does not buy a player for Rs 11.5 crore; it buys a death-overs enforcer — and he must be graded against that role, never against the fee.

That single distinction was the missing organ in the empty template.

Bug one: silent failure. The schema came back complete, the substance was zero. Automated validation is worst at catching this, because the format looks correct. The same disease runs through human punditry — columns filled, sourcing blank.

Bug two: no format. 'Cricket Asia' is a geography and competition tag, not a format tag. A Test average and a T20 strike rate are different units; putting them in one column is a metrology error, not a debate. A document that cannot name its format has no business writing a sentence about a bowler's economy.

Bug three: geography read as league. Assuming 'Asia' means the IPL and importing its commercial frame is the easiest and most wrong move available. The Asian cricket economy is not one thing — the Indian market, the growth-stage Pakistan-Bangladesh-Sri Lanka markets, Gulf-hosted franchise properties and associate-member pathways do not share an economics vocabulary.

Slow it down and the story changes. I went looking for the mistake and found the system. The error here belonged to no pundit; it belonged to a pipeline that never required a question to exist before an answer was generated.

And that is where the old trade offered something no software could. A minimum evidence gate: at least one entity, one information point, one confirmed format, one date. Fail any one of the four and the report is not published — the tool is not judged broken, it is judged closed. Cricket has always worked this way. No score without a format. No economy without an overs count. Apply that single rule to the content industry and half the previews disappear.

I could be wrong, and it is worth writing down. Perhaps the empty template is the honest artefact, and the real culprit is the report that has the data and still misleads the reader. Second, my ENTP wiring enjoys the unmasking more than the fixing; the pleasure of demolition occasionally outranks accuracy. Third, this may be a tooling complaint dressed as a systemic critique.

So here is the falsifier. If in the next quarter I find three machine-generated cricket analyses that explicitly carry a format, a date and a sample size, my charge stops being about the system and shrinks to tooling — and I withdraw this column.

Next time a 'deep analysis' lands in your feed, ask one question: what is the denominator here, and which format? Whoever answers, read. Whoever deflects, scroll. The most valuable skill this tournament season is not reading a strike rate. It is telling the hollow from the full.