Skip to main content

Editorial accountability

Corrections Policy & Practice

Every claim in TECHi reporting is open to scrutiny. If you spot a factual error, a misattribution, a broken link, or anything that's gone stale — tell us. We review every report, publish what we get wrong, and email you the decision.

Response SLA1–3 business days
Public log0 corrections
WorkflowReview · Verify · Publish

What counts

What we'll correct

Factual errors of any kind, misattributed quotes or sources, broken or wrong links, math and calculation slips, and material outdated information — even on older pieces. If a fact in print would be a correction in print, we treat it the same here.

What we don't

What is NOT a correction

Editorial disagreement, opinion-vs-fact framing, or differences in interpretation. We'll happily publish a letter to the editor for those, but we don't retroactively change opinion pieces because a reader disagrees with the take.

How it works

The workflow

Reader submits via the form below. An editor reviews the claim against primary sources within 1–3 business days. If the fix is warranted, we publish a dated correction note on the affected article AND a public entry on this page. Either way, you get an email.

Report a correction

Tell us what we got wrong.

The more specific the better — a linked primary source or an exact quote helps us verify quickly. We'll email you when the review is complete.

What you're reporting

The article

What kind of issue

Type of correction

Tell us what is wrong

The details

Who to thank

Your details

By submitting, you confirm the report is accurate to the best of your knowledge. We'll respond within 1–3 business days.

Public log

Corrections we've published.

Every approved correction, newest first. Each entry links back to the article it corrects.

Showing 0 entries

No corrections have been published yet. When we get something wrong, this is where we publish the fix — every time.

For other editorial concerns, write to editorial@techi.com. For urgent legal or safety issues, see our contact page.