The Blank Notebook: How a Cricket Report Gets Written When Stage-1 Comes Back Empty

It is 2:47 in the morning. Not a match night — a file night. There is an eighty-line document open on the screen, and every single field in it repeats the same sentence: 'insufficient information, cannot assess.' Title: N/A. Source: N/A. One-sentence summary: N/A. Format: N/A. Player: N/A. Team: N/A. The thing that was supposed to be analysed is simply not there.

The easiest job in this trade has always been filling the blank. Add two adjectives, one 'source close to the team', one sentence about 'pressure on the bowling attack', and the word count is met. In thirty-seven years I have watched that trick performed many times, and two or three times I have written it myself — an entry that is still outstanding in my notebook.

This time, though, what is on the page is true. A filled-up report does not come out of an empty source; what comes out is a story about the writer's confidence, not about the match. And because a tournament is running, because some desk is asking for copy every single evening, this is no longer a question about one file.

To understand why, you have to see the mould that modern cricket coverage is poured into. A piece passes through three layers. The first is the event — which match, which format, which ground, what happened in which over. The second is the entities — which player, which team, which selection argument. The third is the conclusion, where the first two are joined and something is asserted. In the document in front of me, the first two layers are empty. The third has no ground to stand on.

I learned this method from a notebook in 2026. At Ambedkar Stadium I filled ninety-six pages — grid coordinates, twenty-three throw-in sequences, eleven second-ball recoveries. That notebook was useful because it contained counts. On a day without counts, a notebook is only paper. Two years later, in Doha, I built a fifty-four-page file on Bob Houghton's India: 0-4 to Australia, 2-5 to Bahrain, 0-4 to South Korea — three matches, thirteen goals conceded, two scored, eighteen line-breaking passes allowed per game. That file held because the shape was defined and the actions were counted. First the shape, then the count, then the conclusion. That sequence became my standard.

And that same standard now applies to this empty document — and it is the standard that stops it from being published. A cricket scorecard will tell you a batsman made 61 off 48 balls. It will not tell you where the bowler pitched in the 34th over, when the required rate crossed eight, or which line drew the batsman's front foot forward. The first is a number; the second is the match. When the source is empty, you do not even have the first, and the second is not worth discussing.

There are three established ways of filling the blank, and all three are symptoms of one disease. The first is adjective cricket: 'the bowling has teeth', 'there is depth in the middle order', 'the fielding has energy'. Those sentences can be written about any team, in any weather, in any format — which is precisely why they say nothing about any team. The second is invented attribution: the 'sources close to the team management' sentence that stretches thirty words of substance across three hundred. The third, and the most corrosive, is cross-format contamination: slipping an ODI average into a T20 argument, or imposing Test-match seam presentation on franchise cricket. All three share one property — none of them can be cut open by the replay, because there is no replay.

Here I apply an old habit: the logic of a selection audit, aimed at the pipeline itself. A pipeline is also a squad. Stage-1 is the opener; Stage-2 is the finisher. If the opener is out second ball, the finisher cannot perform a miracle — he does not even know what the target is. An empty Stage-1 is not a small technical glitch; it is the same failure as losing two wickets inside the first three overs — the rest of the batting order is still in the dressing room, but the shape of the innings has already changed. And the easiest mistake at a desk is to blame the finisher when the ball never came off the opener's bat.

There is an older point that recurs every tournament. Role-fit questions do not apply only to players. When an organisation separates the 'extractor' from the 'writer', it must also decide what the writer's job is when the extractor comes back empty. The answer is not 'guess'. The answer is that the writer publishes what he has, and leaves what he does not have visibly open. The null-input gate does the work of a wicketkeeper: nobody notices the competence until a bye is conceded. What shows after a bye is not competence; it is embarrassment.

And this is where the thing I trust least enters the frame. On match day: live feed, live odds, live fantasy points. None of them ever asks whether the information actually exists. A price always displays a number, even if nothing has happened on the ground, even if it is raining, even if the toss has not taken place. On the day the desk's feed is empty and the market's screen is full, the journalist's job becomes perfectly clear: write what is in the replay, not what is glowing on the screen. The darkest edge of data is not that it is wrong; it is that it is never allowed to look empty.

This is exactly where the milestone and the match situation separate. 2 April 2026, Wankhede. The scorecard says: Dhoni 91 not out, India won by six wickets. That is correct and it is insufficient. What made that innings legible was not the score but the sequence — the partnership after the early wickets, the rate managed through the middle overs, the arithmetic of the last ten. Which ball drew the front foot forward in which over is what the replay tells you; the scorecard does not. And with no replay at all, you print 91 as a 91 — as though it were a line from a bank statement.

That is why I trust the archive first and then test it against the touchline. The archive says this team has lost three matches in the last five overs over the past two years. The touchline says all three had the same cause — a set batsman playing an unnecessary shot. Either one alone is incomplete. The notebook says one thing; the replay says another. When they disagree, the story lives in that gap.

In a tournament cycle the pressure triples. Emotion compresses, the reader wants a hero and a villain by eleven o'clock, and at that hour the desk has only a scorecard. The desk that waits until nine the next morning and files with the counts loses that night's clicks and wins next month's record. The desk that prints a guess at eleven wins the night and has soiled its own archive before the semi-final. Every draft leaves a fingerprint on the squad sheet — and a draft built on an empty source leaves the deepest one.

Now the counter-argument. It is easy to say that staying silent on an empty source is integrity. Silence is not integrity; silence is only absence. Integrity is when a desk shows its method — what it checked, where it got stuck, which question is still unanswered, and by when the answer will arrive. The reader has no interest in your pipeline; he is interested in what to watch in the next match. So the correct response to a blank file is not 'we know nothing'. It is: 'this part is settled, this part is open, and this part we will test on the ground on Thursday.'

The real blind spot lies elsewhere. Organisations audit quality at the output — reading the piece, counting the words, watching the traffic. Nobody audits the input. It is the same error as set-piece defending: after the goal, everyone says the marking was loose, but nobody checked whether there was a marking plan at all. A system that is only ever judged by its results will look correct every single time — until the result is bad.

This file will not close. It will only wait. My 2026 Houghton file never closed either; it merely changed formations — first the shape, then the set-pieces, then the line-breaking passes, then the same question that is still open today: how long can an old shape survive faster opposition? When the stadium remembers differently, I open the notebook and start again.

The next time this pipeline runs, do not look first at how the article turned out. Look at whether Stage-1's entity list was populated, whether the information-points field was empty, and whether one human being confirmed, before the writer was given a deadline, that the source article had actually been read. That work is tedious, it earns nobody credit, and it is the only work that will keep you credible on the same story a year from now.

The question is not how an article gets written from a blank file. The question is — if your feed goes dark at seven on a match night, what will your desk print at eleven? Your answer is your editorial policy, whether or not it appears in the style guide.