The Scorecard With Every Box Blank: Cricket's Memory, Silence and Twenty-One Years of Notebooks

On Tuesday morning I opened a file on my desk. Inside was a match report: a slot for the headline, a slot for the date, a slot for the format, a slot for the toss, for the batting average, the bowling economy, the venue, the result. Every box had been built. Beside every box sat a single word: not applicable. Nobody answered what format it was, who batted, who won, which ball turned the game. My first thought was that the match had not happened. Then the opposite thought arrived. It had happened. Nobody wrote it down.

I have been keeping cricket notebooks for twenty-one years. I have counted deliveries from behind a camera, waited outside dressing-room doors, held a player's unfinished sentence on tape and written it out later. In that time I have learned that cricket's biggest events sometimes do not occur — they were supposed to occur, but nobody recorded them. In an old notebook of mine there is one such page. The result is written there. The sound is not. 8 July 2026, the Ageas Bowl, Southampton. The first international cricket match after the shutdown, England against West Indies, an empty ground. West Indies won by four wickets. In the margin I wrote: "The loudest thing today was not a sound."

Cricket's data vault is bigger than it has ever been, and that same vault is the thing doing the most forgetting.

The ESPNcricinfo ball-by-ball archive now holds every delivery — the over, the line, the field, the batsman's footwork. Tracking systems tell us how fast the ball travelled, how many degrees it spun, what percentage of the time a catch should have been taken. The upside is obvious. We know that on 14 July 2026 at Lord's, England and New Zealand finished level, the Super Over finished level, and the match was settled on boundary count, 26 to 17. Kane Williamson was at the crease, Ben Stokes dragged his side back with boundaries off the off side, and England won their first World Cup. All of it is filed.

But the question that came with the empty file is this: what exactly are we filing? A boundary count is a rule, a number, a decision. It decided a World Cup. Yet no archive records why a man of forty-nine in the Lord's stands was crying that evening, or how long the New Zealand dressing room stayed silent. We have learned to measure the thing. We have forgotten to write down what the thing was.

Based on my years of watching matches, this error happens most often with young players. 18 June 2026, The Oval, the Champions Trophy final. Pakistan made 338 for 4, India were bowled out for 158, a margin of 180 runs. That night everyone wrote the story of Pakistan's return. The sentence that stayed with me belonged to Fakhar Zaman. Nobody had spoken his name before the tournament; in the final he made 114. His name survived for one reason only — a reporter sat in a corner of the dressing room, asked him a question, and wrote the answer down. A scorecard reading 114 would never have told you that his first shot was a gamble against every piece of logic on the field.

This is where it gets complicated. In the 2026 newsletter, a nineteen-year-old paragraph learned how to run. I was in Manchester then, a mid-level writer tired of maintenance work. On 9 September 2026 Liverpool lost 5-0 to Manchester City, and Sadio Mané's 37th-minute red card changed the air in the stadium. That evening I wrote 1,200 words about the empty space where a winger was supposed to run. A red card, an absence, and a team that suddenly became its own shadow. That piece started my weekly letter.

That teenage sentence is still sprinting through my old newsletter. Because that was the first time I understood that leading with the scoreline makes the story disappear. What did the red card actually do? It put twenty-one players on a pitch meant for twenty-two, and it turned down the volume of fifty thousand people. That was the event. The rest was arithmetic.

What worries me now is worse. We are not trying to understand players' lives; we are inflating their numbers. We turn a nineteen-year-old's first first-class hundred into a banner while the bones in his shoulder have not finished knitting together — and that fact never reaches an archive, because it is not a number.

An old habit of mine kicks in here. Every column I write carries a small box called "Sound of the Match", three sounds unrelated to the score. On 8 July 2026 the box read: the metallic ring of the bell, the flat knock of ball on stump, and a fielder applauding himself. Fourteen times that day a player looked towards a crowd that was not there. That number fourteen exists in no database. It also became my most-cited piece, because readers wanted feeling, not figures.

So what do we do with the empty file? First, an empty box can never be read as "nothing happened". A blank column means missing information; missing information is never evidence of safety. That distinction is the most neglected one in cricket writing. If we say a match produced no controversy while holding no record of that match at all, we are lying — we are passing ignorance off as a finding.

Second, and harder: the easy route out of a blank box is a guess. Guess the format, guess the result, guess the name. Cricket journalism has large precedents for this, where a reporter who could not get into the dressing room built an entire match from one sentence on a manager's face. Readers believed it. Later it became history.

Silence does not always mean refusal; often it means nobody asked the question.

That is why the blank match report reads to me as a moral document. It says: we do not know. The hardest work in cricket journalism is not writing. It is saying, out loud, that I cannot fill this box.

And still a problem remains. Readers do not want blank boxes. They want story, names, causes. That demand is splitting cricket's information world in two: verified numbers on one side, unverified feeling on the other, and in between the young player whose name makes our headlines while his body, his fear and his unfinished sentences are stored nowhere.

I hold a firm position here, though I rarely state it plainly in a column. The greatest risk to a teenager pushed into senior rhythms is not the opposing bowler. It is the archive that never records the gap between his body's age and his numbers' age. Years later, someone reads the numbers and makes a decision, and the player never gets a second act.

I have not thrown away that page in my notebook. Now and then I open it. Those boxes marked not applicable are really charges filed against me. Across twenty-one years, how many of the matches I watched were never written down, only remembered? And how long does memory last?

Had nobody recorded that empty evening in 2026, we might still know that West Indies won by four wickets. We would not know why Jason Holder's side was so calm, or why a fielder forgot to celebrate a catch in an empty ground.

Over the next decade, cricket's biggest journalistic fight will not be at the ground. It will be in the archive. The question is this: when someone goes looking for today's matches in 2030, will they find a heap of numbers, or the sounds nobody remembered to write down?