The Hollow Report in Cricket's Information Chain: Why 'Not Assessed' Is Not 'No Risk'

A document landed on my desk last week. Eight sections, four tables, a risk matrix, a five-star rating scale. No title. No source. No player, no match, no venue. Every single cell carried the same sentence: "Insufficient information, cannot assess." The most confident line in the entire file was the one admitting it knew nothing at all.

I stopped before filing it away, because the structure of the document was the actual story. A system that can produce eight sections from an empty input will never shout "I failed." It will hand over a beautifully formatted grid of nothing, and somewhere downstream somebody will read that grid as "no risks identified."

That is the widest gap in cricket's information flow right now. There is no shortage of rumour, no shortage of documents, no shortage of tables. The shortage is of files that know what they do not know — and say so loudly.

Cricket is now a year-round market. The IPL auction barely closes before the PSL retention list lands, then SA20, ILT20, The Hundred, the CPL, MLC. Each list drags its own paper universe behind it: no-objection certificates, central contracts, salary caps, right-to-match cards. A reader who wakes up to four different "exclusives" from four different leagues is not short of information. He is short of a filter.

That has been my job for a long time: sorting rumour into evidence tiers. Who is saying it, how much paper can they produce, whose interest does it serve. In 2026 in Barcelona I followed the €222m clause until it turned into a paper trail — others were writing "interest," I was writing who would deposit the clause and when, and how the amortisation would land in the accounts. When the game stopped in 2026 I built the Covid Contract Index, because wage deferrals and balance-sheet amortisation show a club's real face.

Those two experiences gave me a habit: treat every claim as a first draft. That habit is exactly what stopped me on last week's file.

Because the document had precisely one non-null field — the domain label. It did not say which format. It said: "cricket_world." Test, ODI, T20, The Hundred, all in one bag. In cricket, that single word hides the largest analytical hazard there is.

This is where the real work begins. A cricket document that cannot identify a format cannot make any comparative claim at all, because the formats are separate currencies and the exchange rate between them is not fixed.

A strike rate of 150 in a T20 league and an average of 45 in Test cricket are not numbers from the same market. One is manufactured on a league flat deck, inside short boundaries, across two-over spells; the other comes out of five days of fatigue, reverse swing and the mental erosion of the third session. Put them in one table and the numbers stay accurate while the conclusion goes wrong. The Hundred's 100-ball arithmetic is a third universe — over-based economy benchmarks simply do not function there. The ICC rankings are also three separate tables, and without a format anchor you cannot even decide which one to open.

From years of watching matches from the stands, one thing I know: the evening dew at Old Trafford is not in the pitch report. It is in the outfield at eight o'clock, when the spinner's ball leaves the hand and goes straight on. The data sheet does not capture that. The camera does, and so does the person sitting in the ground. Analysis without a format anchor loses exactly that dew.

The document was honest about its own blindness. It stated that the information-points array was empty, that title, source and type were all null, and that even the instruction to identify entities was circular — "identify from the information points above," when there were no points above.

That circular instruction is the most political confession in the file. A system that grounds its own decision in evidence that was never produced is not a novelty in cricket administration. A board cites a "review" that was never published; a selection panel cites "workload management" while nobody has seen the workload dataset; a franchise cites "the project" while the salary-cap sheet stays closed. Plenty of paper. Very little number inside the paper.

And this is exactly where the commercial layer enters. Auction price and international strength are two different things — a division I keep returning to. Right-to-match cards, NOCs, retentions, forfeited central contracts: at every one of those points, money and cricket pull in different directions. A document that cannot name a single league or quote a single fee has no way of catching that division.

The market speaks in fees, but it confesses in clauses and add-ons. This file had no fee layer at all, so there was nothing to confess with. Its risk matrix was empty by construction, not because the underlying reality was safe. Writing "Low" in that column would have been a straightforward misstatement — missing information and missing risk are different animals.

Still, the file had value in one place. In its own rating grid it gave itself one star — "reference value" — on the grounds that the null pattern itself was a usable signal that the pipeline had failed. Everything else was zero. The system graded its own failure, then shipped the file as a deliverable anyway. That is the real event. A wrong number gets caught. A beautifully formatted zero does not.

The instinctive reaction is to blame the machine. The machine is innocent here; it followed its template. The blame sits in the template.

A template with a box for every question and no box marked "stop" is more than a technical bug — it is an administrative design. The structural resemblance to cricket's own information system is uncomfortable. Over the past decade we have received unprecedented volumes of data from boards, leagues and broadcasters: economy rates, tracking, workload, injury logs. Every release has a format, a box, a star rating. Ask who verified the boxes before they were filled, and the answer is usually silence.

And here the reversal arrives. Of all the documents cricket produced last week, this empty one may have been the most honest — because everything else was presenting confident numbers with no paper trail behind them. The empty file at least declared its ignorance in a structured way. But honesty that does not lead to correction stops being honesty; it becomes a shrug in a nice format.

"Not assessed" and "assessed as safe" are two different sentences, and the distance between them is the most dangerous gap in cricket journalism today. The first is a statement about missing data. The second is a claim about reality. Read one as the other and a wrong decision becomes inevitable.

The next domino is administrative, not sporting. When the next central-contract review, the next NOC dispute, the next retention list is published — will anyone ask whether the information-points array was actually filled? Or will we keep admiring the tables and mistaking formatting for fact?

I do not chase rumours. I chase the invoices that make rumours nervous. This file's invoice said one thing only: nobody paid, nobody played, nobody knows. The question is who catches the hollow invoice next time.