Corrections

• Build pipeline errors. A Census value misrouted, miscomputed, or attached to the wrong city. A growth field calculated against the wrong base year. A rank that doesn’t match the underlying sort.
• Missing or misidentified communities. Report a missing town, a wrong geography type, or a population attached to a different boundary. Check the community directory, including "Other local governments" and the "Include other Census areas and historical records" search option. We will check whether the cause is a source omission, an inclusion rule or a search error, and correct errors on our side.
• Broken provenance. A published number whose source file can’t be re-derived from the build manifest, or whose source_* columns point to the wrong file.
• Typos and content errors. Misspellings, broken internal links, mislabeled axes on charts, wrong vintage year on a page, incorrect last-built date.
• Methodology accuracy. A claim on the methodology page that doesn’t match what the build script actually does. The methodology and the build script must agree.

• Census Bureau numbers themselves. If you believe a Census estimate for a specific city is wrong, that’s a dispute with Census. For PEP estimates, Census provides the Population Estimates Challenge Program. We publish what Census publishes; we don’t reissue or override official figures.
• Census methodology disputes. Differential privacy, the cohort-component method, the blended base, raking to county totals — methodology disputes belong upstream with the Bureau’s Population Division, not in our editorial.
• Unsupported measurements. We do not invent annual PEP estimates for a Census-designated place or substitute a nearby city's population. ACS publishes separate survey-period estimates. Census publishes annual estimates for eligible minor-civil-division towns and townships, even though the legacy city CSV excludes those records. See the community coverage rules and legacy dataset limits.

A paid release is never silently overwritten. A confirmed package defect creates a new immutable revision with new checksums, a description of the affected fields and geographies, and a link to the replacement. Customers who acquired the affected release receive its correction even after ordinary update eligibility ends.

A warning notice keeps the historical file available for reproducibility and points to the corrected revision. A blocking recall stops future downloads only when a serious data-integrity, safety, or source-rights problem requires it. The account notice then explains the replacement or refund path. Files already downloaded cannot be remotely retrieved.

This page has no published correction entries yet. Confirmed changes will identify the affected dataset or page and the release that applied the correction. A coverage change is not complete until its published result has been verified.

Each entry will record what was wrong, when it was reported, when it was fixed, and which build manifest applied the fix. The log is the receipt — what was found, what changed, when.