The Empty File Is an Injury Report
**মূল উত্তর:** একটি ক্রিকেট প্রতিবেদন যখন শিরোনাম, উৎস, প্রকাশতারিখ ও তথ্যবিন্দু ছাড়া নিষ্কাশিত হয়, তখন সেটি বিশ্লেষণযোগ্য নয়। শূন্য তথ্যবিন্দু মানে ঝুঁকি কম নয়, ঝুঁকি অজানা। সঠিক পেশাদার পদক্ষেপ হলো বিশ্লেষণ থামিয়ে উৎস পুনরুদ্ধার করা। **মূল তথ্য:** - আটটি বিশ্লেষণ-ক্ষেত্রের সবকটিই শূন্য ছিল: শিরোনাম, উৎস, ধরন, তথ্যবিন্দু, দৃষ্টিভঙ্গি, সত্তা, সময়-সংবেদনশীলতা, উৎসের মান। - খেলার ধরন অনির্ধারিত থাকলে টেস্ট, ওয়ানডে ও টি-টোয়েন্টির মেট্রিক একে অন্যের সঙ্গে তুলনীয় নয়। - প্রকাশতারিখ অনুপস্থিত থাকলে ম্যাচ-Next লেখাকে 'পূর্বাভাস' হিসেবে প্রকাশের ঝুঁকি থাকে। - উৎসের মান নির্ধারণ করা না গেলে প্রতিবেদনের প্রমাণগত Weight শূন্য ধরা হয়। - 'প্রযোজ্য নয়' ও 'কম ঝুঁকি' এক নয়; প্রথমটি মূল্যায়নের অনুপস্থিতি বোঝায়। **উৎস:** স্টেজ-২ গভীর পেশাদার বিশ্লেষণ নথি; মূল উৎসের শিরোনাম ও প্রকাশতারিখ অনুপলব্ধ, তাই স্বতন্ত্র যাচাই সম্ভব হয়নি। **সম্পর্কিত প্রশ্নোত্তর:** প্রশ্ন: শূন্য তথ্যবিন্দু থাকলে কী করা উচিত? উত্তর: বিশ্লেষণ বন্ধ রেখে শিরোনাম, ইউআরএল ও প্রকাশতারিখ পুনরুদ্ধার করে নিষ্কাশন পুনরায় চালানো উচিত। প্রশ্ন: কেন খেলার ধরন জানা অপরিহার্য? উত্তর: কারণ টেস্ট, ওয়ানডে ও টি-টোয়েন্টির কৌশলগত পর্যায় ও মেট্রিক পরস্পর অপরিবর্তনযোগ্য। প্রশ্ন: 'প্রযোজ্য নয়' আর 'কম ঝুঁকি' কেন আলাদা? উত্তর: 'কম' মানে মূল্যায়ন হয়েছে, 'প্রযোজ্য নয়' মানে মূল্যায়নই হয়নি — ইনজুরি নির্ণয়ে এই পার্থক্য নির্ণায়ক।
Sylhet, April 2026. I was the only woman in the back row of the press box. I had been hired as a radio researcher, not as an analyst. I was told, repeatedly, that women cannot read bowling actions. I stopped arguing and started a paper ledger instead, logging every delivery Mashrafe Mortaza bowled that tournament: which foot took the load, the angle of the knee, where the front foot landed. By his 24th over the ledger showed me a number I had not gone looking for — his front-foot landing angle had shifted by four degrees. Four degrees. Not visible to the naked eye. I showed it to two team physios. Both shrugged. Within months his knee cartilage tore and he was out of the side.

Today a different sheet of paper has landed on my desk, and it is also blank. A cricket dispatch has arrived with no title, no source, no byline, no publication date, the format unclassified, and the list of information points entirely empty. Eight fields, eight of them blank. No team, no player, no score, no venue.
I am not writing this to complain about an empty space. I am writing because the most useful lesson of a life in cricket journalism is this: an empty file is itself an injury report. Only the patient here is not a cricketer. The patient is the story.
Cricket has two economies. One speaks loudly; the other is nearly silent. Transfer fees, auction prices, broadcast rights, sponsorships — those shout. The medical file stays quiet. How many millimetres of cartilage remain in a man's knee, how many overs he has bowled in the last six weeks, how many hours he has spent in airports, how much he has slept — none of that reaches a headline. I have written it many times: the transfer fee is loud; the medical file is quiet. And the media's worst failure comes when it stands beside the noise and forgets to read the quiet file.
But the silence in front of me today is a different kind. It is not the silence of a tired physio. It is the silence of a file that was never found.
Let me explain, because this is exactly where I like to over-explain. A cricket report reaches a reader in four stages. First the source — a player, a coach, a board, a journalist, or the commentary box. Then extraction — pulling the facts, numbers, dates and names out of that source. Then analysis. Then publication. The document in front of me collapsed at the second stage. But the manner of the collapse matters: it did not fail loudly. It failed quietly. The extraction tool found nothing, so it did the only thing left to it — it emitted the template's own instructions as though they were answers. The blank field reads 'identify from the information points above', and there are no information points above. It reads 'judge from the source fields', and the source field is itself missing.

That is a tactical signal, and tactical signals are my working language. A report that errs loudly can be repaired; a report that fails silently is dangerous. Because the reader cannot tell 'no findings' from 'no input'. If a physio writes 'no issue' without ever examining the player, that is the cardinal sin of medicine. The same sin has been committed here.
Now look at exactly which doors an empty file closes.
With the format undetermined, no tactical reading holds. Test, ODI and T20 use metrics that cannot be transplanted into one another. In T20 there is the powerplay from overs 1 to 6, the middle overs from 7 to 15, the death overs from 16 to 20; in ODIs, two new balls and the acceleration of the final ten; in Tests, session-by-session attrition and the 80-over new ball. Each runs on different logic. A T20 strike rate says nothing about Test batting capability. So whether the headline says 'first Test' or 'third ODI' — that single word rewrites the entire architecture of the analysis.
Without venue and innings state, two more things are lost. First, home-ground bias: in cricket, home advantage is structurally the largest single differential, and unless it is stripped out, a single-match report often tells the wrong story. Second, the state of the innings — wickets down, runs required, follow-on or not. Without it, nobody can tell whether the piece is a preview, an in-play report or a post-match analysis.
Lose the player's name and you lose the most damaging thing of all. When there is not a single number — average, strike rate, economy, wickets — comparison is impossible. And here an old rule of my trade applies: data that cannot be verified cannot be cited. In cricket, the player narrative is the most hype-contaminated layer of the sport. When a young star's one-season flash is written up as the next great thing, the multi-year, multi-condition record behind it is usually absent. I remind myself at this point: a player is not a spreadsheet, but a spreadsheet can miss a player.
The team and ranking field is empty too. ICC rankings are format-specific — separate tables for Test, ODI and T20. With no team named, even the classification of 'elite side' versus 'emerging force' cannot be made. Nor is there any World Test Championship points table or tournament stage, so no qualification picture can be inferred.
The commercial field is quieter still. No league, no franchise, no auction, no broadcast deal. I hold a standing position here, and I show it through case selection rather than declaration. An auction price is commercial value; it is not evidence of international capability. The bidding wars between elite clubs are largely brand arms races; the genuinely valuable signings happen at smaller clubs. A small-league prodigy becomes a satellite asset in a bigger system, and that transfer is never visible in the price. No-objection certificates, central contracts, league windows — how those three levers spend both a player's body and his calendar is entirely absent from this blank field.

Governance is blank as well. Revenue-distribution disputes, arguments over Duckworth-Lewis-Stern, dissatisfaction with the DRS umpire's call, anti-corruption monitoring — none of it is mentioned. One caution is essential here: silence is not proof of safety, and it is not proof of suspicion either. The status is unknown, pending recovery of the source.
If source quality cannot be graded, the evidentiary weight of the report is zero. And the rumour ladder — official announcement, authoritative journalist, general media, traffic-driven account — is my profession's main self-defence. Without that ladder, auction season and the transfer window swallow us whole.
The time-sensitivity field is the most neglected of all. Cricket information ages within hours — the toss, team news, weather, a revised target after rain. Without a publication date there is no way to know whether a report was written before the match or after it ended. A 'prediction' published after the result is the most common and most damaging deception in cricket content.
Now to the central point, the one I consider most urgent after reading this file.
Null is not low, and confusing the two is the biggest trap in cricket analysis. A risk field marked 'low' means an assessment happened and came back low. A field marked 'not applicable' means no assessment happened at all. In injury diagnosis that distinction is life and death. A scan that was never taken is not a clean scan. Declaring a knee normal when no MRI was done is the most dangerous sentence in medicine. The same holds for information: eight empty fields do not mean eight low risks. They mean eight unknown ones.
The second point I make repeatedly, and which this document proves. The body keeps a load ledger, and the load ledger does not lie. A career is spent in small debits — one extra over, one short night's sleep, one back-to-back match, one flight. Then comes a single ball, a single landing, a single scream, and everyone says it happened suddenly. Information keeps a ledger too, and that ledger is credibility. Every unverified number, every speculative headline, every 'sources say' is a small debit. They accumulate until one day there is a default, and the reader stops believing anything.
Now the other side. The industry rewards precisely the opposite of this column. The confident voice is rewarded; hesitation is punished. When an empty file lands on the desk, the easiest thing in the world is to fill it — drop in a team, a name, a number, so the story stands up. That is the temptation of the trade, and it is exactly the temptation that sits in front of a physio when the coach walks in and says, 'we need him for tomorrow.'
Publishing on the strength of an empty file is, in editorial terms, clearing a bowler to bowl a full spell eleven days after a grade-two tear was found in his knee. Someone has written 'no issue' on paper, because nobody ever looked at the paper.
I did not want this column to be right. I wanted the file to be full. But it arrived empty, and staying silent about an empty file would be the greater injustice to this trade.
One caution, aimed at myself. I write from Bangladesh but I was born in the UK. An outsider reads the data too closely and the local context too loosely — that risk applies to me as much as to anyone. So I make no claim without speaking to local physios, coaches and players, and I state my confidence level. On this document: I am highly confident that building substantive cricket claims from an empty payload would be fabrication. I am moderately confident that the failure is an extraction or paywall problem rather than an article that genuinely contained no facts. Keeping those two levels separate matters.
The route to prevention is cheap and simple. Recover the title, the URL and the publication date, and for most cricket articles the format, match identity, team and narrative phase come back with them. Then require at least three information points, each carrying a number, a name or a dated event; at least one team and one player named; the identity of the source; and a comparison of publication date against event date. With those six things in hand, analysis can proceed. Without them, it should stop.
The signals I am watching now are clear. A re-fetched source document: recover the title and three information points and the whole analysis becomes executable. A format token in the title — 'Test', 'ODI', 'T20', 'Qualifier', 'Final' — any one of them opens the door to three separate metric systems. Entity extraction: one team and one player make player analysis and narrative grading possible. The publication timestamp: if it post-dates the match, the piece is stale and must not be dressed up as a preview. The identity of the outlet: board or ICC versus self-media; if self-media, downgrade every claim to rumour tier. And the ratio of commercial to sporting language: if price and contract dominate, the piece is commercial, and the error of treating price as capability must be avoided.
One last thing. The oldest data set in cricket is the body. And the body has a property no feed possesses — it never leaves a field blank. It writes something down every day, even when nobody is reading. Our problem is that we read it only after the player has left the field.
So the question today is not about this report. The question is this: when the file you sent comes back empty, will you fill it in — or will you send it back?
