Where Fact Ends and Commentary Begins: A Practical Verification Framework for Cricket Reporting

This is the English companion version of the Bengali article above; it is an editorial-method piece, not a match report. This article is not about a particular match result, a particular player's performance, or a particular series. It is about editorial method. Its single purpose is to make explicit where the line falls between fact, interpretation and speculation in cricket journalism. Reporting written without evidence damages reader trust, and broken trust is hard to rebuild. Cricket reporting is often assumed to be simple: one match, one score, a few quotes, done. In practice it is the reverse. Cricket is a game where many interpretations of the same event are possible, where statistics are abundant but their meaning is contested, and where team sources, governing boards, selection committees and fan expectations all pull at once. In that multi-centred reality the reporter's job is not only to say what happened but to keep apart what happened from what is said to have happened. The first step is recognising the tiers of information. Tier one: primary, verifiable material—official scorecards, match referee reports, formal board statements, published broadcaster statistics. Tier two: eyewitness accounts and statements made at press conferences; these are information, but they arrive with a perspective attached. Tier three: analysis, opinion and prediction, which may be valuable but must never be presented as fact. The commonest failure is writing tier two and tier three as if they were tier one. For any match-related claim, the scorecard is the final authority. Runs, wickets, which over something happened in—none of this should rest on memory or oral account. When a report claims a record, a milestone or a first, cross-checking a database is mandatory. Likewise claims about player-of-the-match awards or league standings are time-bound; if the writing does not state the date on which the claim holds, readers are misled. Quotation demands the most care. A sentence spoken at a press conference and the same sentence cut from an interview are not equivalent; removing context changes meaning. The rule should be: keep enough surrounding context that the speaker's position is legible; when quoting partially, make clear what has been left out; when translating, label it a translation rather than the original wording. In cricket, translation errors routinely create unnecessary controversy. The second major trap is chronology. Where several versions of an event exist, they should be arranged in sequence. Who said what, and which statement preceded which event, determines whether the analysis points the right way. Old comments are repeatedly presented as reactions to new developments. Such errors are not hard to expose, provided each claim carries a date and a source. Numbers need their own caution. Averages, strike rates and economy rates each carry limitations. Averages built on small samples cannot support large conclusions. Comparisons that omit period, competition type and conditions mislead. The best order for readers is: the number, then its limitation, then the interpretation. Reversed, the number is arranged rather than explained. Social media is now a major source of cricket news, but it is a lead, not a source. A viral post, a clipped video or an anonymous account's claim cannot be published unverified. Minimum verification: find the original post, check when it first appeared, understand the poster's identity and context, and where possible obtain independent confirmation of the event. If unverified, label it a claim circulating on social media, not an event. Writing about players' private lives, family details, physical condition or mental health carries a different ethical standard. Absent a public-interest justification, publication is questionable. If a team does not state the nature of an injury, guessing is wrong; write instead that the team has not confirmed the nature of the injury. One such sentence prevents many inferences. With team and internal sources, the question of who is speaking matters. Vague attributions such as 'team sources say' are unverifiable by the reader. Protecting a source's identity can be legitimate, but the reader deserves a sense of the source's position and the type of information—first-hand or second-hand. Where possible, confirm across two independent sources. Without limits on language, analysis slides into assertion. 'He is in poor form' is opinion; 'he has not scored significantly in his last five innings' is a checkable description. Write the second and the first becomes unnecessary. Words such as certainly, obviously and proves should be weighed against the evidence actually available. For prediction, the best policy is explicit conditions. Rather than 'this team will win the series', write 'if the leading bowlers stay fit and the side starts well in the first two matches, its chances rise substantially'. Conditional predictions can later be tested; unconditional ones are only a display of guesswork. Headlines deserve separate treatment because that is where information is most often distorted. A headline must not claim more than the body supports. Metaphor and colourful wording are permitted, but they must not occupy the place of fact. Photographs and captions are part of the information. Using an old image with a new event requires a caption stating that the image is from the archive. Captions should answer who, where and when; they are not the place for allegation or interpretation. A corrections policy is the foundation of credibility. When wrong, say so, say where the error occurred, and publish the corrected information clearly. Cricket results change quickly, so reports should carry explicit time references, allowing later readers to know which information belongs to which moment. Transparency with readers means making them part of the verification process. Marking which information comes from official sources, which from eyewitnesses and which from analysts lets readers weigh the claims themselves. The press supplies information; it should also supply the tools to think about it. Cricket has its own vocabulary, some of it not literal. Swing, spin, death overs and powerplay carry technical meanings; explaining them once is good practice. When writing about team strategy, keep inference apart from actual strategy: decisions not visible from outside should be described as possible reasons, not as reasons. Verification without contextual knowledge remains incomplete. How important a competition is, what conditions a side is playing in, the local weather and pitch type—without these, facts can be accurate while the analysis is wrong. This is the local reporter's advantage: knowing which question to ask, and which answer sounds abnormal. Editorial and commercial pressure cannot be ignored. Big events, big names and controversy attract readers. But skipping verification for reach costs more in the long run. The durable approach balances speed with accuracy: publish what is confirmed quickly, wait on what is not, and tell readers why you are waiting. A working checklist applies to any cricket report. One: does every claim carry a source? Two: are date and time explicit? Three: do the numbers come from primary sources? Four: are quotes in context? Five: does the headline claim more than the text? Six: is personal information necessary in the public interest? Seven: is there an open route to correction? If any answer is no, look again before publication. Finally, the principle. Cricket reporting is not merely delivering news about a game; it involves players' careers, teams' reputations and readers' leisure. Accountability to all three naturally builds a culture of verification—and with it, readers who do not merely know, but can trust. This framework concerns no specific match or series; it is a procedure. Producing an actual report requires first collecting its sources, dates and claims, then applying the framework step by step. Without sources a framework stays on paper; with sources, the framework shows how to use them.