The Return-to-Play Ledger: Who Writes Bangladesh Cricket's Injury Timelines, and Who Erases Them

Seven in the evening. The floodlights at Mirpur's Sher-e-Bangla National Cricket Stadium are on, but play has stopped. A fast bowler pulls up mid-run-up, hand pressed to his left side. The physio sprints out, the team doctor behind him. Four minutes later he is walked to the dugout — smiling, ice pack at his waist. The post-match bulletin arrives: "Slight strain, ten days' rest."

Ten days.

I was not on the field. I was in the tunnel corridor, where the physio pauses for two seconds before setting down his bag. In those two seconds I watch three things — how much weight the left leg takes, how far the hip rotates when he walks, how often the ice is changed. Those three data points do not add up to ten days.

Every injury has a story. My job is to find the page someone tore out.

Context: a calendar that has never measured a body

Bangladesh's cricket calendar is an odd machine. December to February — the BPL. Between it, national series, sometimes an Asia Cup, sometimes World Cup preparation. March to April — the Dhaka Premier League, the first-class National Cricket League, domestic T20s. June to July — tours of England, the West Indies, Zimbabwe. September to October — the Asia Cup window. November to December — new contracts, new auctions, new preparation.

Track one right-arm seamer through that year and a strange coincidence appears. In the BPL he belongs to a franchise, and the franchise's support staff count his overs. In the NCL he belongs to a division, where the support staff is often one physio shuttling between two venues on the same day. With the national team he is a BCB central-contract player, and his workload is monitored by the board's medical panel. Three institutions, three databases, one body.

The most uncomfortable question sits right there: who owns that body's medical file? Whose property is the scan report — the board's, the franchise's, or the player's own? If the answer is unclear, there is no independent route to check whether the timeline was ever told honestly. Where a file belongs to no one, a ten-day announcement answers to no one either.

I have watched this gap for years. In 2026, during the 1-1 draw between Sheikh Russel KC and Abahani Limited Dhaka, defender Sohel Rana collapsed with a knee injury in front of me. The team doctor called it a fourteen-day sprain. I spoke to a physio, looked at where the swelling sat, listened to the stability test. At Sheikh Russel, fourteen days was not a timeline. It was a test of who would lie. That piece passed fifty thousand reads, but its real result for me was different: injury news and injury information are not the same thing.

Core: a ledger with three columns

I read injuries like a ledger. Three columns. The first holds the scan date. The second holds the date of the statement. The third holds the return date. The gaps between those dates are the actual information — not the injury itself.

On February 25, 2026, Neymar fractured the fifth metatarsal against Marseille. Brazil's medical staff gave a three-month window. In June he played at the World Cup in Russia. Read the three columns together and the story is not about swelling and return; it is about the type of surgery and the rehab protocol. That year I settled on something: in medical language the unit of time is not the day, it is load.

On November 8, 2026, Sadio Mané injured his fibula against Werder Bremen. Qatar's World Cup began without him. In the same tournament N'Golo Kanté stayed home with a hamstring. I was building an Injury Impact Index for an outlet then; the forecast of Senegal's group-stage exit landed, because the index did not count goals, it counted absences. The World Cup clock does not care about your hamstring, your contract, or your country.

Now the Bangladesh pages of that ledger. Mustafizur Rahman's shoulder surgery in Australia in 2026 is public record. The workload management that followed is a textbook. But who wrote the textbook — the national support staff, the franchise support staff, or the player himself? Usually all three, and that is the problem. In mid-2026, Ebadot Hossain's knee ligament injury kept him out of both the Asia Cup and the World Cup. Nobody shortened that timeline; if anything it was lengthened. But the real question was never the return date. It was how many competitive overs he bowled before returning, and who approved them.

One confusion needs clearing here. Fit and available are not the same thing. Fit means the tissue-healing phase is complete. Available means the body can absorb two matches in four days, a flight, a training session. The first is measured by a scan; the second is measured in a ledger that, in Bangladesh's domestic structure, is the emptiest page of all.

Do the workload arithmetic once. A seamer's BPL overs, plus 30 to 35 overs across a four-day NCL match, plus the T20 and ODI load of a national series — the sum is a rising line that regularly crosses safe limits. Nobody writes that sum in one place, because writing it requires three institutions' data on one table. Where that does not happen, injury is not an accident. Injury is a decision — taken consciously by some, absorbed silently by others.

The cleanest model I have seen came in 2026. During the COVID hiatus, five of Bashundhara Kings' 32-player squad tested positive. I quietly organised isolation, shielded their identities from the media, and wrote an internal return-to-play protocol. When the stadiums emptied in 2026, the responsibility stayed in the room. That protocol had three steps: clinical clearance, load graduation, re-entry review. Nobody played until all three were signed. The problem is that the ledger lived inside one franchise's file, not a league-wide standard. A protocol that works in only one place is not a protocol; it is luck.

I translate between the scalpel and the scoreboard. Every injury statement gets three questions from me. First: how many days until the swelling dropped, and who measured it? Second: how many balls at maximum intensity before return, and who approved that number? Third: did the player consent to the return decision, or was he merely informed? In Bangladesh, written answers to those three questions are almost never available. And I am not the voice in the room. I am the checklist in the hallway. An unticked box is an unticked box, however elegant the announcement.

Contrarian: sometimes the rush comes from the other side

The easy reading of this piece is that boards and franchises push players. That reading is simple and incomplete.

I have seen players push themselves, many times. The reason is human and economic. A central contract means match fees, match fees mean a household, and an injury means a quiet question mark in your file at the next evaluation. In a system where performance is counted before contracts are renewed, returning fast looks like a rational choice from inside the dressing room. There is no single villain. The villain is a calendar, a contract clause, and a silent medical file.

The second inversion is discussed even less. Sometimes the longer timeline is the wrong decision. Extended rest means deconditioning. For a fast bowler it is crueller, because throwing mechanics must be rebuilt; healing the tissue is not enough. I write the rule this way: without a minimum of match simulation before return, risk does not fall, it relocates. Repairing one area and breaking another is not rare in Bangladesh's domestic game — especially where nobody sits down with the strength and conditioning coach while writing the rehab protocol.

So the arithmetic has to be in exposure, not days. How many overs, how many spells, across how many days, on what surface, in which format. Those five produce a load curve, and the slope of that curve tells you who is at risk. In Bangladesh we still do not draw the curve; we count numbers after the injury. The audience has a part here too. We celebrate the comeback, but we rarely audit the rush that caused the injury. Nobody does, because the comeback is a beautiful story and the timeline audit is boring.

Takeaway: three documents for next season

Blaming the system and stopping there is not my job. Mapping the system, then locating the specific dates and the specific signatures, is. So my proposal is plain, and it is only three documents.

First: at the start of every season, a written load budget for each fast bowler — BPL, NCL, and national duty combined. Second: injury statements that carry the swelling-reduction milestones and the maximum-intensity ball count alongside the dates. Third: written player consent on every return decision, archived with the player himself.

With those three, nobody can lie without lying under their own name. I am not a scan machine. I do not want to catch anyone. I want the page torn out of every injury story to be readable. If the first bulletin of next season adds a single date — either the scan date or the return date — that will count as progress.