Corrections log
Last checked: {SITE_LAST_REVIEW}
This site publishes facts about rules that change, drawn from sources that are sometimes wrong and often out of date. We will make mistakes. This page is where they are recorded.
A corrections log that is empty for a long time is not evidence of accuracy. It is evidence that either nobody is checking or nobody is publishing what they found. We would rather this page filled up.
What counts as a correction
| Type | Example | Handled how |
|---|---|---|
| Material factual correction | A fee, threshold, date, eligibility condition, legal citation or jurisdictional statement was wrong | Logged here with full detail, correction block appended to the page, page dateModified and Last checked updated |
| Material change of position | We stated something as confirmed that we should have marked unconfirmed, or resolved a source conflict we should have published as a conflict | Logged here, with the reasoning |
| Superseding update | The rule itself changed; what we published was correct on its date | Not a correction. Updated in place, Last checked bumped, and noted here only if a reader could have relied on the old position to their detriment |
| Typographical or presentational fix | Spelling, a broken anchor, a table that did not stack on mobile | Not logged. Fixed |
| Translation correction | The Chinese said something the English did not | Logged here, in all three locales, because the affected reader reads one of them |
The log
| ID | Date | Page | What was wrong | What it says now | Why | Severity |
|---|---|---|---|---|---|---|
| No corrections have been published yet. This site went live on {LAUNCH_DATE} and the log begins from that date. If you have found an error, tell us at smedigitalhubsg@gmail.com — we would rather correct it than have it stand. | ||||||
The correction workflow
- Receipt. A report arrives by email, through the enquiry form, or from our own quarterly review. Every report is acknowledged within 3 business days, including the ones we end up disagreeing with.
- Triage, within 2 working days. Material, minor, superseding update, or not an error. A material error affecting a fee, a threshold, an eligibility condition or a legal citation is escalated immediately.
- Verify against an official source. The correction has to meet the same standard as the original claim: Tier 1 or Tier 2, with a URL and an access date. A reader’s report is not itself a source, however plausible — it is a prompt to go and check.
- Correct in every affected locale on the same day. English, Simplified and Traditional. A correction applied to one locale and not the others creates a worse problem than the original error.
- Append the correction block to each affected page: what was wrong, what it says now, the date, and the source.
- Log it here, in all three locales.
- Update the Last checked date and dateModified on the affected pages.
- Reply to the reporter, telling them what happened, and offering to name them in the log if they wish. Most people do not, and the offer is what matters.
- If the error was material and someone may have relied on it, consider whether anyone we have corresponded with needs to be told directly. This is a judgement, and the fact that it was considered is recorded against the entry.
- Ask why it happened. A source we misread, a source that changed, a translation drift, a copied block that was edited on one page and not the others. Recurring causes go to the QA checklist.
General information only. Nothing on this page is immigration advice, legal advice, tax advice, financial advice or any other form of regulated professional advice. It does not take account of your personal circumstances. Official requirements change; verify the current position from the source before acting. Living Life Asia is not connected to, endorsed by or affiliated with any government body.