Cicketreader fact-check team takes all efforts to ensure that any of the information that goes live is verified. We endeavor to be promptly responsive in correcting errors in the material published on our platform. When we run a correction, or clarification on our social media handles or share an editor’s note, our goal is to tell readers, as clearly and quickly as possible, what was wrong and what is correct. Anyone should be able to understand how and why a mistake has been corrected.
Updating a Report
We make it a practice to put notes on stories if a story has been updated. It is important for us to use a correction or clarification to inform readers whenever we correct a significant mistake or edit a story to include comments and updates from a stakeholder.
If we are substantively correcting an article, photo caption, headline, graphic, video or other material, we promptly publish a correction explaining the need for the said change. For any factual error in our fact-check article, as it comes to our notice, we do a revised article with a new conclusion and explain the correction at the top of the article and distribute it on all the social media platforms where our presence is.
When our journalism is factually correct but the language, we used to explain those facts is not as clear or detailed as it should be, the language is rewritten and a clarification added to the story. A clarification is also used to note if we initially failed to seek a comment or response that has since been added to the story.
Other Corrections Policies
When an error is found by a reader and posted to the comment stream, our community engagement team can indicate in comments that it has been corrected. When we publish erroneous information on social networks, we correct it on that platform. We retract the incorrect information if we cannot alter it.
If you believe a story, we have published is inaccurate, please suggest corrections via ‘Suggest A Correction’ section that appears at the end of every web story that is published. We also request our community members to send the correction at [email protected]