Corrections Policy

How to request a correction from the Chesterfield Valley Post, how we handle errors, and our public corrections log.

The Chesterfield Valley Post corrects errors promptly and publicly. This page explains how.

How to request a correction

Email social@surroundsoundnews.com with:

  • The URL of the article
  • The specific sentence or fact you believe is wrong
  • What the correct information is
  • A source we can verify it against (link, document, on-the-record contact)

We aim to respond within two business days. Corrections to factual errors are made as soon as they are verified, regardless of how the error originated (a source gave us wrong information, we misread a document, we made a typo, etc.).

What we correct

We will correct:

  • Factual errors — wrong names, titles, dates, numbers, addresses, quotes, attributions
  • Misleading headlines that don't match the story
  • Broken attributions or missing credits
  • Errors of omission that materially change the meaning of a story

We may clarify but not "correct":

  • Opinions you disagree with (if clearly labeled as opinion or commentary)
  • Facts that are disputed between credible sources — we may note the dispute in the story

How corrections appear

When we make a correction, we:

  1. Fix the error in the body of the story.
  2. Log the correction in our corrections archive (below).

Add a correction note at the top of the story, dated, describing what was changed and why. Example:

Correction, April 23, 2026: An earlier version of this story said the TIF request was for $750,000. The correct amount is $950,000, according to the February 19 committee packet.

We do not silently edit published stories. If a story changes in a way that affects meaning, readers see that change was made.

Minor updates vs. corrections

We distinguish between:

  • Corrections — the story said something factually wrong. Tagged, dated, and listed here.
  • Updates — the story is still accurate, but new information or developments have been added. Noted at the top of the story with a timestamp but not logged as a correction.

Unpublishing

We do not unpublish stories except in rare circumstances involving legal risk, safety, or clear factual failure that cannot be fixed with a correction. If a story is taken down, we explain why at the original URL.

Corrections log

No corrections have been published yet. This section will be updated when corrections are made.


Our approach to corrections is rooted in the belief that accuracy — and being accountable for getting things right — is the foundation of our relationship with readers. Questions about this policy: social@surroundsoundnews.com.