The Load Ledger Does Not Lie, but Cricket's Injury File Is Often Blank

A scorecard tells you plenty — runs, wickets, run rate. But the paper ledger in my hand told a different story. At the 2026 World Cup, sitting in the Sylhet press box, I was the only woman present, and my designation was radio researcher, not analyst. People liked to say women cannot read bowling actions. I stopped arguing. I simply began keeping count — every delivery Mashrafe Mortaza bowled, the angle of his front-foot landing, over after over. By his 24th over the ledger showed the landing angle had shifted four degrees. I showed it to two physios. Both shrugged. Within months his knee cartilage tore. That day I understood the most uncomfortable truth in cricket analysis: the body keeps a load ledger, and the load ledger does not lie — but the injury file we hold is often blank. And in a blank file, the biggest story hides. Cricket's data revolution gets plenty of airtime — Hawk-Eye, smart balls, heat maps, ball tracking. All fine. But outside that sits a layer no camera captures: workload, recovery windows, travel, heat, sleep, injury history. This layer tells you how much of a career has already been spent — long before the injury appears. The transfer fee is loud; the medical file is quiet, and that quiet space matters most. The problem is that this layer is the least documented. The 2026 ICC Cricket World Cup ran in Bangladesh, India and Sri Lanka from 19 February to 2 April — even at that scale, accurate spell counts for domestic quicks did not exist. Franchise leagues and national schedules send players from one country to the next, and nobody logs the travel load or the change in conditions. The ICC itself has issued workload-management guidelines with rest periods and spell caps. But a gap always opens between guideline and practice, especially when two tournament calendars collide. Across 44 years of watching, this is the largest gap I have seen. And here sits the story of missing data that no analyst wants to admit. A blank file does not mean no risk. A blank file means we are blind. And analysis written blind does not prevent injury — it makes injury more certain. All my career I have kept one habit — what I call three frames, four tenths of a second. Run-up, delivery stride, landing: within the four tenths of a second those three frames capture, fatigue, technique and risk converge. Three frames can carry a career, and four tenths can break it. In April 2026, at Old Trafford, I pulled three broadcast frames of a knee hyperextension in a Europa League quarterfinal and annotated the collapse frame by frame. 2.1 million views in 72 hours. Editors who had never given me a byline suddenly wanted my face in the studio. I said yes to the graphics and no to the camera. That habit taught me the honest move with missing information: do not guess. Consider this — how many overs a young quick bowls across a domestic season, a national series and a franchise tournament, no single record holds. Each tournament keeps its own books; nobody reads the whole ledger together. The body does the opposite: it deposits every delivery in one account. Cricket analysis tends to do the reverse of honesty. A quick returns from injury, performs in his first match, and we write a superb comeback. Nobody asks: what was his workload before returning? Which rehab stage was he at? How many overs in the nets? How much tape, how much painkiller? A return from injury is never a match story; it is a timeline — pain control, range, strength, then bowling. Skip a stage and you pay later. The trouble is that teams often do not publish that timeline. The analyst is left with a single date — he returned. That date is one line of the load ledger, not the whole book. And here lies the biggest confusion: we assume a return means fit. In the body's accounting, returning and being match-fit are not the same. Whether a quick's shoulder or knee is ready for match load is not something a scorecard reports — it reports recent spells, pitch hardness, heat, and the hours of travel behind him. The oldest data set is the body, and it does not lie. Now the most uncomfortable part. Cricket culture loves one sentence — he bowled through the pain for the team. It is a story of patriotism, of heroism. My ledger calls it something else: a duty-of-care gap. When a fast bowler sends down a long spell in a series decider and breaks down months later, everyone forgets one question — how many alternatives did he have that day? Would resting him have lost the series, or could a fresh quick have been given the ball? Almost always the answer was: the option existed. I am not claiming every injury was avoidable. I am claiming that an injury which looks sudden is often the sum of months of small debits — and nobody keeps that account, because we never built the culture of keeping it. Workload management is not calling a player weak; it is protecting his greatest asset, the body. One more thing. I was born in the UK, but my work is in South Asian cricket. So my greatest risk is arriving from outside and reaching conclusions from numbers alone. Explaining injury with data while ignoring local physios, coaches and players is a mistake. Data can show how much load fell; it cannot show where a player stands mentally. Without both, the analysis stays incomplete. Filling a blank file is not the analyst's job — it is the game's job. Logging workload, publishing rehab timelines, recording travel and conditions — these are not luxuries; they are the cheapest investment in future injury prevention. That 2026 ledger is still with me. I did not want this column to be right. If in 2030 a 20-year-old quick breaks down after ten straight matches and someone asks why it happened suddenly, let there at least be a ledger that says: it was not sudden, it was written in the book long ago. The question is not mine but cricket's: will you keep the ledger, or stay content with a blank file?