Last updated: 1 November 2026. This Corrections Policy explains how Sotto Kotha (sottokotha.com) finds, verifies and openly fixes factual errors. When we get something wrong, we do not hide it — we acknowledge and correct.
Read it alongside our Editorial Policy. Contact: [email protected].
1. Why corrections matter
| Reason | Our stance |
|---|---|
| Trust | One bad fact can make the next guide look unreliable |
| Local impact | Wrong result dates, fees or job deadlines can cause real harm |
| Transparency | Update dates and notes show what changed |
| Accountability | Writers/editors do not dodge responsibility |
2. What we correct — and what we do not
| In scope | Usually out of scope |
|---|---|
| Wrong dates, times, fees, roll/registration instructions | Mere disagreement of opinion or tone |
| Wrong statistics, names, titles, organisation names | Requests to add a whole new topic (separate editorial call) |
| Broken or wrong official links | “Make it longer than a competitor” requests |
| Misrepresented sources or cut context | Political preference claims without evidence |
| Misleading headlines that do not match the body | Tiny spelling variants that do not change meaning (unless readability suffers) |
| Wrong image captions / context | Erasing lawful facts just because someone dislikes them |
We focus on provable factual errors. Disagreement is not a correction — but if a fact is wrong, we fix it.
3. Severity levels
| Level | Examples | What readers see |
|---|---|---|
| Minor (micro) | Typos, obvious spelling, formatting | May be fixed quietly; a big note may not appear |
| Medium | Wrong link, small date/fee fix, name spelling | Updated date; short note when useful |
| Serious | Wrong result guidance, deadline that changes decisions, bad quote | Clear correction note + updated date; title/key points fixed if needed |
| Retraction / major warning | Core claim false or dangerously misleading | Warning/retraction note; possible noindex or removal |
4. How to report a mistake
Comments are off at launch. Email is the primary path.
- Email: [email protected]
- Subject line: “Correction” or “সংশোধন” — helps us triage
- Web: guidance on the Contact page
4.1 What to include
| Field | Why |
|---|---|
| Full page URL | So we know which article |
| The wrong sentence/section (copy or screenshot) | So we can find it |
| What you believe is correct | So we know the proposed fix |
| Reliable source link or document | Verification — anonymous forwards are not enough |
| Your name (optional) | For follow-up; we may not publish it |
Do not send unnecessary sensitive data (passport numbers, bank PINs, medical records). See the Privacy Policy.
5. Internal process
| Step | What happens |
|---|---|
| 1. Intake | Email enters the queue; spam/incomplete items filtered |
| 2. Verify | Check primary sources (portals/boards/gazettes/recognised newsrooms) |
| 3. Decide | Correct / partial / decline (with a reason when practical) |
| 4. Edit | Fix Bangla body and English twin (_sk_content_en, etc.) together |
| 5. Note | For medium/serious cases: _sk_updated_note / EN note and updated date |
| 6. Cache | Purge page/topic cache when needed so readers see the new text |
Target response window: usually a few working days. For urgent safety/health situations, use local authorities or hotlines first — we are not an emergency service.
6. How corrections appear on the page
- Updated date in the byline when material changes.
- Correction/update note (
_sk_updated_note) summarising what changed. - Direct fixes to body, key points or title.
- For serious cases, a clear warning sentence near the top.
- English UI meta kept in sync when EN is published.
We generally do not silently erase history when a mistake could have affected decisions — we keep an honest corrected page with a note. Micro-typos do not always need a public note.
7. Who can spot errors
| Source | Examples |
|---|---|
| Readers | Email reports |
| Writers/editors | New sources after publish |
| Source organisations | Board/portal notice updates |
| Rights holders | Copyright or misattribution — Copyright & DMCA |
8. Bilingual consistency
Bangla is primary; English is a full twin. We do not correct one language and leave the other wrong. Numbers, dates and official URLs stay identical across languages.
9. Timely news vs lasting errors
| Situation | What we do |
|---|---|
| Accurate at publish, then official rules changed | Update/note — may not always say “correction”; we clarify context |
| Wrong at publish time | Correction note + fixed text |
| Live events (matches/breaking) | Fast updates; then a stable summary |
10. What we do not promise
- A public reply or name credit on every email.
- Immediate major changes on incomplete or unsourced claims.
- Treating a third-party site’s error as our “correction” by default.
- Legal advice or settling private disputes outside due process.
11. Related policies
- Editorial Policy — how we write and verify
- Terms — limits of informational use
- Privacy Policy — data in your email
- Copyright & DMCA — rights notices
- Contact
12. External references
This page is not legal advice. Comparative reading on accuracy and accountability:
- SPJ Code of Ethics (seek truth / correct mistakes)
- IFJ Global Charter of Ethics for Journalists
- IPSO Editors’ Code of Practice (accuracy & opportunity to reply — comparative)
- RTDNA Code of Ethics
- Poynter EthicNet
- Google — helpful, reliable content (E-E-A-T / trust context)
- W3C — Writing for web accessibility (clear updates help everyone)
13. Changes to this policy
If the process changes, we will update this page and the date. Material changes may get a short site notice.
14. Contact
Email: [email protected]
Subject: Correction / সংশোধন
Web: Contact page
If you catch a mistake, you are helping — thank you for taking the time to check.