Corrections log — every fix the desk has issued
A running record of factual errors that have appeared in our pieces, with the date, the reporter who caught the mistake, and a link back to the corrected article. We publish this list publicly so that the next reader can see what we got wrong, when, and how it was fixed.
Our corrections policy
When a piece contains a factual error, we follow three rules. First, we add a corrections section at the top of the article, dated and named. Second, we update the text in place where the correction does not change the meaning of the piece. Third, we never quietly rewrite an article so that the original error vanishes from the public record. The next reader can see the error, the correction, and the date the correction was issued.
The list below is the running public log. Each entry links back to the original piece and to the diff that was applied. Older entries from the 2016–2024 archive are summarised inline; the full diffs are available on request.
How a correction gets logged
Five steps, in order:
- A reader or reporter flags a possible factual error via the contact form, with the article URL and the paragraph concerned.
- The features desk investigates — checks the underlying source, talks to the original reporter, and decides whether the claim is wrong, out of date, or a matter of interpretation.
- If the claim is factually wrong, a correction is drafted, signed off by the desk editor, and dated.
- The article is updated: a corrections block is added at the top, and the body text is amended in place where the meaning is unchanged.
- The correction is added to this public log, with the article URL, the date, and the name of the person who caught it.
We do not delete old articles. A piece that was wrong in 2021 is still wrong in 2026 — the correction is layered on top, not used to rewrite history.
The log
2026
2026-04-12 — IPL 2026 final venues article. An earlier version of the piece listed the qualifier 1 venue as the Wankhede Stadium in Mumbai. The BCCI confirmed on 2026-04-11 that qualifier 1 will be held at Eden Gardens, Kolkata. The article has been corrected and a note added at the top. Flagged by reader R. Menon (Mumbai); corrected by the features desk.
2026-03-29 — Most sixes in IPL 2026 article. The opening paragraph originally credited Nicholas Pooran with 18 sixes after 12 matches. The figure was the count at the end of match 9, not match 12; the correct count at match 12 was 21. Body text and the leaderboard table have been corrected. Flagged by reader V. Iyer (Bengaluru); corrected by the stats desk.
2026-03-18 — Rohit Sharma retirement rumour piece. The article initially stated that the BCCI had issued an official clarification on the retirement rumour. The BCCI had not; the clarification was issued by the Mumbai Indians media team. The article now attributes the statement correctly. Flagged by reader S. Kulkarni (Pune); corrected by the Mumbai desk.
2025
2025-10-04 — IPL 2025 final match report. The original report credited the winning runs to the number 5 batter; the correct number was 6. The body text has been amended and a note added at the top. Flagged by a reader email; corrected by the match desk.
2025-08-21 — Captain picks archive. The archive page listed a captain pick as “unverified” for a match that had completed; the result was a 31-point haul, and the entry should have read “verified — 31 pts.” The archive entry has been corrected. Flagged by reader A. Banerjee (Kolkata); corrected by the fantasy desk.
2025-05-30 — Points table mid-season. A rounding error in the NRR column for the seventh-placed team understated their NRR by 0.04. The figure has been corrected in the table and a note added. Flagged by reader M. Pillai (Chennai); corrected by the stats desk.
2024
2024-04-17 — IPL 2024 opening match preview. The preview listed the visiting team’s captain as the player who had stood in as captain for one match in 2023; the official captain for the 2024 season was a different player. The article has been corrected. Flagged by the visiting team’s media manager; corrected by the features desk.
2024-09-12 — Playoff qualification scenarios. The scenarios table mis-stated the qualification rule for teams level on points — the tie-breaker is NRR, then head-to-head, then most wins, in that order. The table has been corrected and a clarifying paragraph added. Flagged by reader D. Rao (Hyderabad); corrected by the stats desk.
2023 and earlier
Between 2016 and the end of 2023, the desk issued 38 corrections in total. The full archive — every entry with date, article URL and the original phrasing — is available on request via the contact form. Summarised here by year:
- 2023: 6 corrections (4 player-stat errors, 2 venue errors)
- 2022: 5 corrections (3 result errors, 2 stat errors)
- 2021: 4 corrections (2 player-name errors, 2 fixture-date errors)
- 2020: 3 corrections (all fixture-related; the 2020 season was played in the UAE)
- 2019 and earlier: 20 corrections across the 2016–2019 archive
None of the corrections issued in the 2016–2023 archive changed the core argument of the piece in which they appeared. Most were stat or name errors caught within 48 hours of publication.
How to flag a possible error
Use the contact form. Include the article URL, the paragraph or table cell in question, and the source you are cross-checking against. If the source is a printed newspaper, scan and attach the page. The features desk replies within three working days.
If we agree the piece was wrong, we issue a correction following the policy above. If we disagree, we reply with the desk’s reasoning and the underlying source — so the conversation is on the record either way.
FAQs
Do you ever delete corrected articles?
No. A piece that was wrong stays wrong in the public record; the correction is layered on top of the original, dated and named.
How long does a correction take to appear?
Once a factual error is confirmed, the corrections block is added within 24 hours and the public log is updated within the same window.
Do you correct opinion pieces?
No. We correct factual errors. We do not correct the desk’s opinions, predictions, or analytical judgements — those are bylined and dated, so readers can disagree on the record.
What happens if I flag something that turns out to be right?
We reply with the source we relied on, so you can see how the desk reached the original conclusion. The original article is not changed.
Where can I read the full archive of 2016–2023 corrections?
Email the contact form with “archive request” in the subject line; the features desk sends back a CSV with every entry.
