Accurate information is the foundation of Resultpedia. When we get something wrong, we correct it openly.
How we handle errors
| Error type | Action |
|---|---|
| Typo, broken link, formatting | Fixed silently; dateModified updated |
| Date / number error | Page updated; "Correction" notice added at top with summary and date |
| Substantive error (eligibility, exam pattern, vacancy count) | Page updated; "Correction" notice; Telegram + push alert if the error reached subscribers |
| Defamatory or legally problematic content | Removed pending review; reach our editorial team via Contact |
How to report an error
- Email editorial@resultpedia.com with the page URL and the error.
- Use the "Report an error" button on any article (when launched).
- We respond within 2 working days and act within 5 working days for non-urgent corrections, and within 24 hours for urgent corrections affecting subscribers.
What a correction notice looks like
A substantive correction adds a labelled Correction block to the top of the affected page. The block names what was wrong, what the corrected figure or date is, when the correction was made, and — where the change was non-trivial — the source that triggered the correction (for example, an SSC corrigendum PDF or a UPSC press note). The page's dateModified is bumped in the same edit, so the byline and JSON-LD reflect the fresh timestamp. We do not silently rewrite numbers and pretend the original number was never there — opacity defeats the trust signal a correction is supposed to send.
What we do not correct
We do not retro-edit factual analysis or commentary that turned out to be a reasonable forecast at the time but proved wrong in hindsight (for example, a Tier-2 cut-off estimate that ended up higher than the official cut-off). Where opinion or forecast content needs an update, we publish a follow-up note rather than overwriting the original. We also do not delete a page just because a reader disagrees with the conclusion — we will, however, take down any factual claim we cannot verify against a primary source.
Transparency
A running list of corrections is maintained at /corrections-log/ for the current calendar year (page launching with first published correction). Each entry carries the page URL, a one-line summary of the error, the corrected figure or text, and the date the correction was published. The log is also available to anyone who emails the editorial address — we send it as a plain CSV on request, no questions asked.