The Report With No Player In It

Last week I opened a file at my desk in Kolkata. Forty-eight pages. Eight chapters. Every chapter had its heading set, a table under each heading, every cell in every table filled, every cell typeset cleanly. The work was professional. I turned the first page. The second. The tenth. The fifteenth. Not a single cricketer's name on any page. Not one date. Not one score. Not one ground. And the most startling absence of all — no format. Not Test, not ODI, not T20, not The Hundred.

One sentence repeated across every chapter, eight times, in slightly different words: "Insufficient information, cannot assess."

The file was titled "Cricket Domain: Deep Professional Analysis." And it was, in fact, complete. All eight dimensions were present. The risk matrix was present. The industry transmission map was present. The signal-tracking table was present. What was missing was cricket.

This article is about that file. And about the machinery that made it possible for anyone to call it complete.

Context: the fastest-growing part of cricket coverage is not the match report

The fastest-growing segment of cricket media, and the least policed, is not the match report. It is "analysis" — previews, stat interpretation, and the interpretation of the interpretation. Squad reports for every franchise three weeks before an auction. Predicted elevens before every series. Tactical breakdowns before every tour. "Power rankings" squeezed into the middle of every tournament.

Proving any one of these false is nearly impossible, because none of them makes a claim that can be tested. They are documents that speak about the future, and the future never shows up in court.

I have watched this trade for seventeen years, and in those seventeen years the demand for cricket content has never climbed this fast. The IPL stretched from two months to nearly three. The WPL arrived. Bilateral series were jammed into the calendar. Every domestic match now streams. Every match needs a preview, a mid-match report, a post-mortem, five clips, ten thumbnails. The faster the number of slots grew, the harder the pressure to fill them.

In a slot-filling economy, the document is worthless. The empty space is everything.

That is where my file was born. When a system is required to produce something every morning, it gradually learns that very few people can tell the difference between "something" and "the right something." The visible structure arrives first. The content arrives later — and often never. My forty-eight pages were the last stop on that lesson: a document whose scaffolding was so complete that the absence of content was never noticed.

This is not a new disease. It is the same disease I have been writing about in cricket administration for years, and it has now turned around and entered the newsroom. The affidavit was signed. The courthouse never saw it. I first wrote that line about sports governance. Today it applies to the analysis sitting on my desk.

Core: when the record itself is blank, where do the conclusions come from

I read the file the way you read a certificate — starting with the part that is easiest to forge, finishing with the part that is hardest.

The hardest part was the names.

There was a chapter on format analysis. Five hundred words. It explained that every cricket conclusion is format-specific, and that Test, ODI and T20 data must never be pooled. Entirely correct. I agree with every word. I liked that it stated plainly that if the format is undetermined, analysis cannot begin.

Then I noticed that the same document never once stated what the format was.

That was the moment I understood I was not reading an analysis. I was reading the shell of an analysis. The document was breaking its own rule — on the very page where the rule was written down.

The player-data chapter spoke even more clearly. It had a cell for average, a cell for strike rate, a cell for situational splits, a cell for recent trend. All four empty. Beside each cell sat a "benchmark" column — the standard against which the comparison was to be made. Also empty. The player's name was empty. The role was empty.

Notice what that chapter was actually saying. It was not saying the data could not be found. It was saying the data was never there — and simultaneously that drawing any conclusion from it was forbidden.

That is honesty. Without that honesty, the matter would have ended there. The real danger lay in the next step.

The real danger: a blank chapter that survives

Two things were true of my file at the same time. One, every chapter stated plainly that assessment was impossible. Two, the file still reached me carrying the status of "complete."

Between those two facts sat a gate that should have closed and stayed open instead.

Consider the machinery. Stage one breaks an article down and extracts facts from it — dates, scores, names, conditions. Stage two lays an eight-dimension framework on top of those facts. When stage one returns empty, stage two has two options: stop, or lay the framework down anyway. My file tells you which road was taken.

Converting an empty input into an empty output is also a decision — and it is the most damaging decision of all, because it does not look like a decision.

It looks like process. And nobody files a complaint against process. The reason is obvious: the domain label was populated. The file said "cricket" on it. That alone was enough for any reader to assume the file contained cricket.

I have seen this trick before. In governance reporting we call it the shine of the title — when a filing is submitted under the name of something it does not contain. An amendment filed in the name of amendment that amends nothing. A compliance report with no mention of compliance.

Now I come to the part of the file that stopped me longest.

A risk matrix that could not measure risk

There was a risk matrix. Six categories — sporting, personnel, commercial, rules and integrity, public opinion, systemic. Each category had a level, a likelihood, an impact, a mitigation. Every cell held the same sentence.

But here is the thing. The document had identified one risk, and it was not a sporting risk. It was analytical-process risk. It said plainly that if this blank record were passed downstream, whatever "analysis" was built on it would be fabricated.

That is extraordinary candour. And it is exactly what points to my real complaint. A document that knows it is at risk of being fabricated — why did it arrive at the place where fabrication happens?

Because stage one returning empty was never declared an error. It was accepted as a valid result and passed forward. Nobody asked whether a publishable cricket article should yield at minimum one player, one board, or one league. If none surfaced, where was the fault — in the article, or in the machine reading it?

The answer is usually the second. And that is where my old trade comes in.

From men who spent thirty-five years in journalism I learned one thing: write without fear, without favour — but before you write, make certain the paper is in your hand. If the paper is not in your hand, do not write. That file's machine did the reverse. It wrote, and deferred the search for paper.

System risk: the five per cent rule

On this story I trusted an old reflex — the RTI log reflex. Count every request, record every count, turn every recorded number into a basis for comparison.

The same method applies here, only the currency changes. In governance we watch how many associations filed the affidavits they swore and how many did not. In a content pipeline we should be watching how many records return empty and how many return names.

If more than five per cent of a batch returns with empty information points, that is not bad luck. That is a machine defect — and five per cent is a very generous line.

The second line: every record should carry at least two named players or teams. If the median falls below two, the eight-dimension analysis has lost its footing. It is floating, the way my forty-eight pages were floating.

The third line, the most overlooked: preserve the raw input. My file had no title, no source, no publication date. That means the original article can never be retrieved. How can a document that cannot prove itself be permitted to prove anything else?

You may think this is technical hygiene, not my subject. I have written from the opposite direction for sixteen years, and I will tell you it is exactly my subject.

Today's name for tomorrow's cause

In June 2026 I was in Nizhny Novgorod, in a football fan zone, learning Russian chants. Most of those nights I was working the Cape Town file — Cameron Bancroft's nine-month ban, Steve Smith's and David Warner's twelve. What stung most was not the sandpaper. It was that a board had written its verdict before the ICC code was even opened, and then presented that verdict as process.

Sandpaper leaves a grain. Small print leaves a trail. That file left a trail, and the trail is now leading me somewhere else.

In February 2026 the Cricket Association of Bengal sent me a two-line refusal. I kept it. Institutions that do not answer have also produced a document. A page with nothing on it is still evidence — you simply have to know what should have been written there.

My forty-eight pages are that page. Every empty cell is a claim: that something belonged here and is not here. And if cricket journalism learns one thing this year, let it be that collecting empty cells is also reporting.

Contrarian: the fault is not in the analysis, it is in the machine

Now the part where I usually lose the room.

Whenever a blank report like this surfaces, the accusation lands first on whatever is newest. Machines are writing, people will say, and so the substance has run out. That accusation is convenient, and dishonest.

The custom of the empty shell in cricket predates the machines by a long way.

I remember the winter the domestic tournament was scrapped, the IPL finished in empty stands, and the match fees of more than seven hundred domestic cricketers sat in my spreadsheet. That work led me to sixty-one men across three states, unpaid for a season they had already played. Behind those sixty-one names were sixty-one shells — every shell complete, every pay grade recorded, every grade facing an amount, and every amount unpaid.

No machine built that shell.

So when a blank cricket analysis arrives, my first question is never who wrote it. My first question is: which gate in the pipeline stayed open?

And my second: when stage one returned empty, why did nobody call it empty?

This is where the critics miss it. They blame the technology and pardon the supervision. The machine did exactly what it was told — it laid down the framework. Nobody told it to stop when it came back empty-handed. That instruction was ours to write.

The old failure was this: every fact fell out of an article, the fact was mentioned in a closed room, and the door was shut. The new failure is this: the same article now returns printed across forty-eight pages and walks out of the room. The difference is not one of error. It is one of speed.

Where this goes

I did not move the file off my desk. It is still there.

The next time an analysis reaches you — an auction preview, a series forecast, a squad review — count one thing. Where the first name appears. If the opening page carries not one player, not one date, not one format, the remaining forty-seven pages need not be read.

This is not a harsh standard. It is a minimum standard. And the fastest-growing part of Indian cricket coverage is not clearing it today.

One sentence in that file will stay with me. I do not know whether a script wrote it or a person did, and that is precisely the point — because it made no difference to whoever typed it. The line was: "Preserve the raw input before passing this analysis forward."

I asked the office clerk who had sent the file. He shrugged. There were six people in the room at the time, and all six shrugged the same way.