Geography Where Format Should Be: Cricket Reporting's Filled-In Template and Empty Evidence

A report landed on my desk last week. Eight sections, forty-one rows, every box filled — format and match analysis, player technique and data, team landscape and ranking, league economics, rules and governance, risk matrix, public narrative, industry transmission. At the bottom, printed plainly: domain label — cricket_asia.

There was not a single score in that report. Not a single player's name. Not a single date. Where the format should have been written — Test, ODI, T20, The Hundred — there was N/A. Where the evidence should have been written, there was 'insufficient information'. And at the very end, without any embarrassment: document status — null return.

The report was not bad. The report was very good. That was the problem.

I spent seventeen years on a print desk among documents like that one. In March 2026, three weeks after the Pune Test and after Steve Smith's press conference, I left the desk and started Chepauk Lab — a whiteboard, one borrowed bowling-angle camera, and very little money. The first series was on Pune, where Steve O'Keefe took 6/35 in both innings and India were bowled out for 105 and 107. Forty-one thousand people watched that three-part series in eight days, nineteen hundred paid subscribers arrived by October, and so did the first bitter email from a former national selector. That was the point at which I stopped writing results-first match reports and started every piece with a question about space — what did the fielding side concede, and why.

Something else surfaced in the same period. Cricket coverage now runs on a two-stage machine. Stage one breaks the match into information points — score, spell, selection news, fees, quotes. Stage two drops a framework on top of those points, an eight-section framework in which every box has a pre-assigned name. The machine works until stage one returns empty. On the day it returns empty, stage two prints a very elegant tombstone — and because it has eight sections and a cold tone, the desk mistakes it for analysis.

This is where a tag like cricket_asia turns dangerous. It tells you the place, not the game. A tag that does not say whether the subject is a Test or a T20 cannot serve as the basis of analysis, because in cricket technique, statistics and benchmarks do not transfer between formats. Yet that is the tag that circulates most, because readers recognise a region instantly and need to watch a match to recognise a format.

Format is not metadata; it is the first precondition of analysis.

Two examples, both from my own notebook. Pune, March 2026: O'Keefe's 6/35, twice. That was a Test, which means the bowling side bought a day of eighty to ninety overs. The wrist turned the same way it turns in an ODI, but the decision it supported was different: the question was whether a batter would survive to lunch, not whether a wicket would fall. Trent Bridge, July 2026: I was close enough to the sightscreen to track Kuldeep Yadav's wrist position on the way to 6/25, and two nights later I watched France beat Croatia in a pub on Maid Marian Way, sketching pressing zones on a beer mat. 'The Ring and the Press' came out of that — Kuldeep's spell and France's counter-press were the same mechanism: collapsing the opponent's decision time.

The same mechanism produces opposite decisions in two formats. In a Test, 6/35 means buying time. In an ODI, 6/25 means shrinking the clock to thirty-five overs. The numbers look alike, the wrist turned the same way, but the selection decision that follows is inverted. Without a format tag you have no right to reach either conclusion. And if you replace the tag with a region, you will inevitably merge the two. The ICC's ranking tables are three separate tables; without a format you cannot even choose which one to read.

The cost to the domestic structure followed from exactly this. Ranji Trophy's real function was as a filter — zonal selectors picked players from four-day second-innings patience, not from fifty-over short cuts. When that filter weakened, franchise scouting took over the job, and franchise scouting watches players in a T20 frame and offers no public accounting. The result is a Test side frequently selected on data produced in another format, and because the media tag is geographic, the substitution is never caught.

N/A does not mean 'clear'.

The risk matrix in that eight-section report was fully populated. But injury, schedule overload, integrity checks and financial stress — all four checks were 'not performed', because the inputs to perform them did not exist. This is the most common language failure on a cricket desk: an unperformed check is read as a clean bill of health. In a team meeting it arrives as: 'There's no injury flag in the report.' There was nothing in the report; the absence of a flag was a consequence of absent data, not a passed test.

I learned that the expensive way in 2026. Nine commentary shifts were cancelled between March and June and the freelance floor vanished. So I did what I do with fear and went to the tape. Sitting in a Mylapore flat, I logged 1,400 balls of India's 36 all out in Adelaide on 19 December 2026, coding every dismissal by seam position and trigger movement. The nine-thousand-word autopsy ran in January. Three weeks later, Rishabh Pant's 89* at the Gabba made the same argument in reverse.

The Adelaide 36 is not a score; it is a pattern. And the pattern took forty-eight hours to appear, because what the entire country was calling 'temperament' was trigger movement and seam position. That is why I no longer publish a crisis piece until every dismissal has been watched twice at quarter speed. My reading arrives forty-eight hours behind the pile-on, and it is the version quoted a year later. I stopped apologising for the delay.

A filled-in template costs more than empty data.

In February 2026 I was in a Bengaluru auction room with a forty-page dossier on 217 players. The room used three pages. Chennai finished ninth, four wins from fourteen. I do not read that as a bad dossier; I read it as proof that the pages used were the ones carrying a clip, a number and a recommendation. The other thirty-seven pages looked authoritative, so nobody called them wrong — nobody opened them either.

That is the real pathology of the eight-section report. Nothing about it looks broken. The tables are full, the tone is cold, every conclusion is stamped 'confidence: high'. The most dangerous document in cricket is the one with a correct skeleton and empty evidence.

The popular read says: add more data and the report will fix itself. Mine runs the other way. In a schema that has no format field, adding rows makes the null return look more trustworthy. When 'economy 7.4' arrives without a format, the desk files it next to a Test spell, nobody asks, and the next day that number becomes the benchmark in a selection argument. The fault lies not with the extractor but with the incentive. Nobody is praised for returning a blank; a filled template gets filed and published. It is the same economics that keeps the commentary box a decade behind the data desk — the system rewards legible consensus, not correction. A model that cannot be said out loud in ten seconds will never survive a broadcast; a template that says nothing at all survives anyway.

One last thing I force into every piece: a named human decision. A captain bringing on spin in the seventh over, a coach refusing a fast bowler a second spell, a batter changing his guard — these calls cannot be held inside a regional tag, and without them analysis becomes a tidy model with the game missing from it. The whiteboard remembers what the crowd forgets.

Before the next selection day, or the next time a chart appears on screen, ask for three things: format, competition, and three to five information points with dates. A fourth: named entities — team, player, board, franchise. If those four are absent, what you are looking at is not analysis but an empty envelope with eight sections printed on it. The tape does not lie; it just waits to be asked. The question is not where the next argument will come from. It is whether, the next time a file says 'confidence: high', you will turn the page and look for the evidence. The next argument will not come from where the data was. It will come from where formatting stood in place of data.