N/A — Insufficient Information: The Professional Courage of Saying 'I Don't Know' in Cricket Injury Analysis

It was 2:40 in the morning. On my laptop screen sat a table with columns labelled Article Title, Source, Information Points, Entities Involved. Every cell was empty. One line kept returning: N/A — insufficient information. I have forty-six matches of workload sheets, sixty-three overs of frame-by-frame notes, twelve-angle camera maps sitting in my own files. But the document that reached me contained no name, no date, no delivery count.

In my profession, an empty cell is not a failure. It is a decision — to write down the truth instead of inventing one. When I launched a cricket page called BDCricTeam in 2026, I did not know that one day my hardest piece would be the one where almost nothing can be written. That is what I am writing today.

Context: more demand for story, less supply of data

One thing the document did carry was a domain label: cricket_asia. Everything else was blank. It concerned Asian cricket, but no team, format, player or match was specified. As a sports-medicine journalist, that is exactly where my work begins. I cover the BPL from Sylhet, build workload tables, count frames of bowling actions. To me an injury is not an event; it is a process.

In a tournament cycle, readers float on flags and stories. Before a quarter-final comes the sudden bulletin — 'star pacer a doubt'. It becomes a headline, not data. A large share of Asian cricket injury coverage still leans on press releases and coach quotes. Nobody records how many overs a bowler sent down, how many rest days he had, how often he dived in the field, how heavy the dew was.

Trying to fill that vacuum changed my habits. I stopped waiting for press releases. That 2026 table was my first solo data experiment — built at night, alone, from game film.

Core: reading the body as a machine

2026, Sylhet. Covering the BPL T20 for a new sports site, I tracked fourteen pace-bowling injuries across forty-six matches. When Khulna Titans' Abu Jayed suffered a side strain, I stopped and re-watched sixty-three overs — delivery counts, rest days, dew. The result was blunt: bowlers exceeding 120 deliveries in ten days carried 3.2 times the soft-tissue risk. I published an interactive injury-risk table. Since then I write injury-risk previews with workload thresholds and minute markers, not just match reports.

1. Following that thread, I worked on Mohamed Salah's shoulder at the Russia World Cup. After Sergio Ramos's 26th-minute challenge in the Champions League final, Salah arrived injured. I watched Egypt's three group matches — zero points, two goals. Across twelve camera angles I mapped it: thirty-one sprints per ninety in qualifying, eighteen against Russia. Left-side dribbles dropped; the protective body language around the shoulder was plain. I wrote a mechanism-first breakdown tying the injury to Egypt's attacking collapse. That is where my injury impact matrix was born — sprint counts, dribble direction and xG placed side by side before and after injury. It replaced the vague 'race to be fit' story as my tournament standard.

1. A pandemic-hit season. On 17 October, an empty Goodison Park, Everton 2-2 Liverpool. In the sixth minute Jordan Pickford's challenge drove Virgil van Dijk's knee into valgus; the ACL ruptured. I studied twelve angles. I also tracked twelve ACL injuries across Europe's top five leagues in the first three matches after restart — five of them inside the first 180 minutes. I published a 'ramp-up deficit' theory: empty stadiums and compressed schedules change injury mechanisms. I explained why the injury happened with video frames and load data, not coach quotes.

What links these three pieces is primary data. Frames, scans, delivery counts, sprint logs. None could have been written without it. And that is today's core point: when primary data is absent, the only honest output is N/A — insufficient information.

The document I received signals a pipeline failure. No match, no player, no format, no venue. Writing 'analysis' from here would produce my imagination, not reality. In injury journalism that trap is dangerous, because an invented workload number can later become someone's training plan.

The second condition is harder still. Even with data, it is not prophecy. 3.2 times is a ratio from a 46-match sample, not a law of nature. Dew, humidity, action, sleep, travel — all missing variables. So I write in the language of probability and name the missing variables each time.

Contrarian: the punishment for saying 'I don't know'

This industry does not forgive 'I don't know'. It wants a verdict instantly. Contact-blame is easy, fast, clickable — 'Pickford's tackle took Van Dijk out' — but the truth is more complicated. Career-ending speculation is even easier, and far more damaging.

Here lies a structural weakness. News publishes in the moment; injury data arrives over days. The two never align. So the audience receives not the mechanism but a shadow of it. In Asian cricket the gap is widest, because several boards still do not publish injury data.

A line can be drawn here. The same logic that has led digital systems to keep records tamper-evident and verifiable — so no one can quietly alter them later — applies to cricket's injury records. But let me be clear: the technology is not the point. The point is the integrity of the data — who said it, when, from what count, and whether it can be checked. Without a tamper-proof record, blockchain or notebook, it is worthless.

Takeaway: next headline, ask for the sheet

Next time you see 'star bowler an injury doubt', ask one question — where is the sheet? How many deliveries, how many rest days, what action, what dew. If there is no answer, know that the piece is not journalism but guesswork. And one honest empty cell is worth more than a thousand invented analyses. A wrong number does not just ruin a story — it can ruin a career.