The Verifiable Injury Ledger: The Discipline of Writing 'Insufficient Information' in Cricket's Injury Reporting

I began the Zlatan Ibrahimović ACL audit where the highlight reel ended: at the first twitch. On an evening in 2026 I was in the Old Trafford press box, a 45-year-old woman, one of only a handful of women journalists in that old ground. In the Europa League, against Anderlecht, Zlatan's right knee gave way at the very moment of landing; his anterior cruciate ligament (ACL) tore. He wore No. 9 and had scored 28 goals in 46 games that season. I asked about his landing mechanics — which foot he loaded on. A male colleague brushed the question aside with a light laugh.

Back in Barishal I watched all 46 of his matches again, logged 312 aerial duels in a table, and set a timestamp beside each one. The finding: he landed on his right leg 73 percent of the time. That 4,000-word injury timeline was published by a new sports website. From that day one rule stood: I will never print a player's return date without three independent medical sources.

Cricket's injury reporting is caught in a strange contradiction. On one side, formats change every week — Test to ODI, ODI to T20, plus franchise leagues, travel, bubbles, board pressure. On the other, a news culture that wants a number attached to every injury immediately: how many days, how many matches, how many weeks. Whether it is a Bangladesh Cricket Board medical bulletin or a franchise press release, we usually get a one-line announcement: "hamstring injury, rested." No scan grade, no load data, no rehabilitation timetable.

For seventeen years I have run an "Injury Ledger" logging fifty players' injuries, return times, and reinjury patterns. It has been syndicated in three countries and taught me an uncomfortable truth: where information is missing, all of us rush to fill an empty cell — and we usually fill it with guesswork.

My journalism began in 2026, covering the Wills Cup in Dhaka for Prothom Alo. Since then I have watched cricket media treat the phrase "insufficient information" as a weakness, as if admitting it were defeat. In data engineering the opposite holds: an empty payload is itself a result. When a pipeline leaves a field blank, that alone tells you the source could not be found, could not be parsed, or someone deliberately withheld something. An empty cell is never truly empty — it is itself a signal.

In the age of social media the pressure is even sharper. One tweet, one clip, one blurry photo — and immediately a thousand "confirmed" return dates. But the faster these claims arrive, the faster they are forgotten. A verifiable ledger walks the exact opposite road: slow, but it endures.

This is where my three-source rule operates. I do not write whether a player returns until I have verified it from three independent sources: a club or board statement, an independent medical opinion, and my own archival pattern. Only when all three converge do I pick up the pen. It is slow, but it keeps me free of the hot-take cycle.

1. In the 30th minute of the Champions League final, Mohamed Salah took a shoulder injury after Sergio Ramos's tackle. Salah wore No. 10 for Egypt and had scored 44 goals in 52 games for Liverpool. I cross-checked Liverpool, Egypt and UEFA reports — three sources — and wrote that he would not start Egypt's first World Cup match against Uruguay. He did not. My editor wanted a quick hot take; I refused to write without the data.

Before the tackle became a talking point, it was a joint, a load, and a millisecond. Long before a tackle becomes a talking point, it was a joint, a load, and a millisecond of arithmetic. The broadcast replay stops; my audit begins exactly there.

1. Under lockdown, in Barishal, I was reviewing 120 Premier League matches after the restart. In the Merseyside derby Virgil van Dijk tore his ACL; he wore No. 4 and had played only five league games. My count showed ACL injuries rose 40 percent in empty stadiums after the restart. The empty stadium did not touch Van Dijk; rather it was the silence of the stadium that disturbed his proprioception. A TV producer called the piece "too academic." I then moved from match reports to building a longitudinal database of 300 ACL cases, and began every article with a methodology note.

Now to the ledger question. Blockchain's core idea — an immutable, timestamped, publicly verifiable record — applies exactly to cricket's injury information. When a board says "he is rested" while nobody knows under whose supervision, on which scan, on what date, that information is not fit for an immutable ledger; it is an oral rumour. Information that cannot be verified is not information — it is an expectation. I want a ledger where every injury entry carries a date, a time, who reported it, which scan, whose signature. Only then will it surface why the same pacer bowls more than four overs in four straight matches, or why the same board fields him again after an injury.

Every one of my articles opens with a methodology note: how many cases were reviewed, over what period, which sources were used, and what remains unknown. That short paragraph tells the reader where the writer stands. Transparency is no weakness — it is the only basis on which a reader can check my conclusions.

My second archival rule: conventional "effort metrics" — distance covered, high-intensity sprints — cannot mislead me, because pointless running also produces pretty numbers. For a bowler the real question is not distance covered but the rotational force on shoulder, elbow and lower back in every delivery. In cricket we still borrow football's shadow to measure bowling load, when the core units should be — how many deliveries, how many spells, how much rest per week.

In the Bangladesh context this discussion is even more urgent. Our domestic and international calendars frequently overlap — Dhaka Premier League, BPL, national-team series, with the same few pacers at the centre of it all. With a verifiable ledger we could see which bowler is carrying what load and why he suddenly breaks down. Here the absence of information is not merely a journalist's problem; it is a direct question about a player's health.

But mechanism alone is not my job. Behind every ACL case is a person who, standing before a mirror, first fears he may never run the way he once did. Zlatan came back; Salah came back — but their road back held doubt, sleepless nights, the fear of reinjury. Numbers give only the frame of the story; the player writes the rest.

Now the uncomfortable part no one wants to write. Cricket has two main languages for injury — "bring him back fast" and "scientific rehabilitation." The media usually favours the first, because a fast return means a fast story. My ledger says most reinjuries happen exactly at the moment a player is declared "ready" while the load data says otherwise.

Still, I stay careful — not every delay is negligence. Three distinct things get mixed together: negligence, communication failure, and structural incentive. Negligence is when someone knowingly takes a risk. Communication failure is when scan information never travels from doctor to coach, coach to selector. Structural incentive is the system in which board revenue depends on a star player's presence, so the word "rest" instantly becomes a financial decision. Collapsing these three into one is the greatest journalistic crime, because then we make a physio the villain while the real pressure comes from far above.

I write slowly, I write late, and I don't hide it. My contemporaries print a return date the night of a day's match; I wait for three sources. That wait is my only defence. So the question is no longer "who returns when" — the question is, who owns injury information? The player, the board, or that ledger no one can erase?