Corrections

How BackflowPath handles errors and stale rules

If a utility page, guide, or provider record no longer matches the source material, the correct response is to review the source, update the record, or suppress the page from indexing until it is supported again. A correction is not just a cosmetic content edit. On this site it is part of the publishing control system.

Good correction reports

What to include

  • The exact BackflowPath URL that appears wrong
  • The utility or authority source URL that conflicts with it
  • A short explanation of what changed
  • The date you saw the change
What happens next

Review and update path

  • Source evidence is checked against the current public page.
  • If the correction is confirmed, the registry record is updated and the page is republished.
  • If the source support is broken or unclear, the page should be downgraded or removed from indexing until it is re-verified.
Commercial boundary

Provider disputes do not override utility rules

Provider feedback can help identify stale links, bad phone numbers, or broken routes, but it does not override the utility's own published workflow or approval status.

Correction triggers

What usually causes a correction review

  • An official source URL changes or breaks.
  • A utility changes a deadline basis, portal, or submission method.
  • A tester route changes from official to non-official or vice versa.
  • A page is still indexed even though it no longer adds enough local value.
Evidence rule

What counts as a strong correction

The best correction requests point to a current authority page, portal, list, or notice. Provider claims can help flag a problem, but the public page should be updated only when the underlying source support is strong enough to defend the change.

Possible outcomes

What a correction review can lead to

  • Direct page update when the source clearly supports the change
  • Route reclassification when an official list is no longer real or a non-official route was mislabeled
  • Temporary suppression from indexing while evidence is rechecked
  • No public change when the submitted evidence is not strong enough
Public expectation

What users should expect from this policy

BackflowPath should prefer being incomplete over being confidently wrong. If a page cannot be supported to a reasonable standard, the right choice is to weaken it, hide it, or remove it from search rather than leave a misleading answer in place.