PriceCensus

Publication policy

Corrections workflow

PriceCensus treats corrections as first-class publication events. We document what triggers a correction, who approves it, how it is published, and when the launch scope must be reduced.

Trigger

Reader report, reviewer rejection, contradictory snapshot evidence, or a published value that no longer matches the source page.

Approver

Quinn approves standard corrections. Mira approves any correction that changes vendor attribution, correction wording, or launch scope.

Publish SLA

Critical pricing errors are corrected the same day. All other confirmed corrections are published within the next scheduled site build.

When we issue a correction

  • A reviewer rejects an event because the source quote does not support the summary.
  • The before/after values are identical, mislabeled, or tied to the wrong vendor or plan.
  • A published event is materially incomplete, such as missing a quota condition or plan limitation.
  • A vendor updates a pricing page and our published event no longer reflects the canonical source.

Correction steps

  1. Open a correction record. Link the original event, attach the latest source URL, snapshot ID, and a short explanation of what was wrong.
  2. Re-verify the evidence. Compare the stored before/after values against the source quote and page snapshot. If the original event was wrong, mark it as corrected rather than silently deleting it.
  3. Approve the fix. Quinn can approve routine wording and value fixes. Mira reviews anything that affects launch trust, category scope, or vendor reputation.
  4. Publish and annotate. The corrected event is published with a timestamped note, and the original event remains traceable in the audit log.

What readers will see

We do not silently swap out material pricing events. When a correction changes the meaning of a published event, the corrected entry includes a note describing what changed and when the correction was issued.

If corrections exceed 5% of published events in any rolling 7-day window, Quinn flags the trend to Mira and vendor coverage is reduced until the false-positive rate returns to an acceptable level.

How to report an issue

Send the vendor name, affected plan, source URL, and the incorrect value you observed. Reports with a source quote or screenshot move fastest because the review team can match them to the stored snapshot.

View the published changes feed Read the methodology page