Platform standard

Corrections and update policy

How to report an inaccuracy so it can be investigated, traced and propagated to every page it affects.

A report naming the exact page, quoting the exact statement in dispute and explaining what is wrong with it can be acted on immediately; general disagreement with nothing specific to check usually cannot. Reports are triaged by consequence instead of order of arrival, and a fix is not closed until it has been propagated to every page that depends on the same fact. Four things follow below, each stated once: exactly what to send in a report, why health and identifying details never belong in one, how a report is triaged once received, and how a change is logged so a reader who acted on an earlier version can trace what it said and when it changed. None of it requires legal language or a formal complaint: an email naming the page and the sentence is enough to start.

01

Corrections and updates: what to send

Email corrections@dentalcarecosts.com. A report that can be acted on immediately identifies the exact page, quotes the specific statement in dispute, explains what is wrong with it, and where possible points to a primary or professional source. Reports that describe a general disagreement without attaching it to a sentence usually cannot be investigated, not because they are unwelcome but because there is nothing specific to check.

  • The full URL of the page
  • The exact sentence or claim in dispute, quoted
  • What is inaccurate, misleading or out of date about it
  • A primary or professional source, if you have one
  • Whether you believe the error could affect someone's health decision
02

Please do not send health information

Do not include symptoms, diagnoses, medications, images of your mouth, insurance identifiers or other personal health details in a correction report. We cannot give individual advice in response. Holding that information serves no purpose that would justify the risk of holding it. A correction is about the page, not about your case.

03

How a report is triaged

Reports are prioritized by consequence instead of by order of arrival. Anything that could lead a reader to delay urgent care, miss a warning sign, or act on a materially wrong statement about safety is treated as the highest priority and may result in the page being unpublished immediately while it is investigated. Removing an unsafe page first and resolving the question afterwards is the correct order.

  • Potential safety error, page may be unpublished immediately pending investigation
  • Material factual error, corrected, logged, and propagated to dependent records
  • Scope or clarity problem, the claim is narrowed or the limitation is made explicit
  • Stale content, returned to the review queue instead of patched in place
  • No error found, the reasoning is recorded so the same report is not re-litigated from scratch
04

Propagation is part of the fix

A correction that is applied only where it was reported leaves the site contradicting itself, which is how a single error becomes several. When a fact changes, every record that depends on it is identified and updated in the same cycle: the glossary definition, the treatment page that links to it, the comparison that relies on it and the cost page that assumes it. A correction is not closed until the dependent pages agree.

05

What is not an editorial correction

A commercial request to remove accurate information, to soften a documented limitation, to change where an option appears in a comparison, or to add or promote a provider is not a correction and is not handled through this route. Such requests are declined. The distinction is whether the request is that the page is wrong, or that the page is inconvenient.

06

Change records

Material corrections are logged with what changed and why, not being silently edited into place. The purpose is auditability: a reader who acted on an earlier version should be able to establish what it said and when it changed. Routine copy edits that do not alter meaning are not individually logged.