A Report of Empty Cells: An Absence Audit from a Rajshahi Editing Room

It is 1:40 in the morning in a Rajshahi editing room, and I am staring at a file that looks like a report, smells like a report, and contains no event at all. Eight chapters, roughly forty cells, and in every single one the same sentence: 'N/A — insufficient information.' I stopped counting at thirty.

Empty cells do not surprise me. I have kept a separate ledger, year after year, of what never arrives from district grounds. What stopped me was the scaffolding. There is a title field, a source field, a list of information points, and even an instruction to identify teams and players. Only the interior is missing. A filled structure, an empty box. That night the file taught me that the most dangerous thing in cricket journalism is not false information. It is a document that looks verified.

In the regular season the real story sits beneath the table: whose pressing has dropped, whose bowler is over-loaded, which umpire's calls keep getting overturned. Those things never become headlines, but they are visible before they do. To write them you need particles from the ground — a name, an over number, a date, a decision.

In Rajshahi those particles arrive through a 340-member WhatsApp group of northern club coaches, groundstaff, bus drivers, two scorers and a physio. Nobody files a match report. Somebody sends one line: 'the pacer is dropping his third spell,' or 'the wicket still has morning damp.' I collect those lines, check them against the scorecard, and only then write.

When I first wrote about Soumya Sarkar in 2026, one rule applied: go to the ground before writing. Building a star from a scorecard is easy, but a scorecard cannot tell you how he releases the ball or how his footwork looks at cover. That rule saved me many errors. That night it returned in institutional form, in harsher language.

In 2026 I watched a tournament from a Rajshahi editing room, one replay behind the world, logging twenty-two overturned decisions into a spreadsheet. Then I carried that spreadsheet to sixty tea stalls and asked which they trusted — the camera's eye or the man's. Most trusted the machine more than the men operating it. Since then every technical decision gets a one-page plain-language sidebar. Readers share those sidebars four times more than the match reports.

The file in front of me was not a match report. It was a report about a report that never reached the desk. The skeleton arrived; the flesh did not. Eight chapters, the same sentence in each, and a verdict underneath: void pending re-run.

What struck me most was the list of what would have made it valid. Title, source, publication date. Format — Test, ODI, T20. At least one named entity. Three to five atomic information points with the source preserved for each. And a core viewpoint, so the argument could be tested rather than summarised.

That list is really a cricket desk's starter checklist under a new name. Without a format flag you cannot read a single number. A strike rate of 145 is elite in T20, above par in ODI, near-meaningless in Test cricket. If someone writes 'strike rate 145' without a format, you cannot tell whether they are praising or warning.

The file's biggest lesson is about process, not play. But the process happens in cricket every day. A district match is played, five hundred people sit on the grass, a spinner takes four for twenty in seven overs. What reaches the desk is a forty-word agency copy: 'District side won by five wickets.' The score is there, the names are not. The cells are full, the event is absent. That is silent failure. The reader believes coverage happened. A template was filled. And because the boy who took four wickets never entered a ledger, he is not on any trial list either.

The second issue is format. Our oldest habit is carrying one format's numbers into another. Three innings and eighty runs off forty balls in a T20 league produce a 'next big name' headline, while nobody has watched his defence once in a Test. The test the file flagged as most valuable was the twelve-month average against the career average. It is simple, and almost nobody runs it, because it takes time and it stops the applause.

Phase splits are another habit we under-use. T20 has powerplay, middle overs and death — three different games. ODI has two new balls and the last ten overs. Test cricket is session-by-session attrition. Without knowing which phase a side loses, the table tells you nothing. A team that leads in the powerplay and loses at the death does not have a batting-order problem; it has a planning problem.

Then venue. Spin dominance at home, collapse against pace abroad — that is cricket's largest structural gap. The file contained no venue at all, so the comparison could not be made. Yet I know what a Rajshahi wicket does; the difference from a Dhaka surface is not written on paper, it lives in the tea stalls.

The third issue is template pressure. Forty empty cells make the hands itch. That is human nature, not software. On a cricket desk the itch produces phrases like 'sources indicate,' where nobody knows the source. To me this is the older brother of the small-sample problem. Manufacturing a star from three innings and manufacturing a fact from three empty cells are the same illness in different clothes.

The fourth issue is the most frightening, because it is not a single event. The file said plainly that one empty record is usually a symptom, not bad luck. If more than five per cent of a batch comes back empty, assume a pipeline defect. In Rajshahi terms: a ground without a camera is never a one-day problem. It means an entire season at that ground went unwritten. One missing match never stays one missing match.

The fifth issue is the file's most beautiful error. In the field meant for teams and players, there was no data — only an instruction: 'identify from the information points above.' A work order sitting in the slot where truth belongs. As a metaphor for cricket journalism it is almost too perfect. The selector's unspoken criteria, the board's 'we are monitoring,' the coach's 'he needs time' — all of these are instructions parked in the fact slot. They look like information. They are blank.

The sixth issue is a warning. The report noted that corruption and spot-fixing risk accumulates where oversight is thinnest — newer or lower-tier leagues with sparse anti-corruption coverage. On paper that is a bullet point. On the ground it is daily reality. A match nobody films, a scorecard nobody prints: errors leave no trace because the instrument for tracing is absent. Absence does not only cost the reader. Sometimes it removes protection.

The reflex now is to assign blame: the machine failed, the pipeline broke. I read it the other way. The most honest document on the desk that night was the empty one. It did not invent. It said: I do not have it. Most of the damage in cricket journalism has been done by confident reports, not by embarrassed silence.

The second reflex is easier still: the Dhaka desk does not see the north. I do not believe it in that shape. Some of the 340 in my group send nothing themselves. The stringer was at the ground and did not file. The desk waited and did not receive. The gap runs both ways. Blaming upward hides the gap below, and in my experience the gap below is the larger one. So I verify both directions — the language of the board release and the language of the tea stall.

The third point I could not have written without this file. An empty cell sometimes carries more information than a full lie. 'N/A' means accepting responsibility. 'Sources indicate' means avoiding it. Of all the files on the desk that night, only one told the truth: I do not know.

So what do I watch now? One simple thing. Whether the re-run returns at least one name and three information points. If it does, the story lives. If it does not, there was no story — only scaffolding. And I will watch the batch. Five more empty files of the same shape would mean this is not misfortune but habit.

Somewhere in Rajshahi right now, people are playing whose names will not be recorded. On their behalf I leave one question with the desk. When the next match is played and nobody files, will the desk hear the silence — or will it print the template?