← Front Page Corrections

Local Record

Corrections Policy · Public trust

Corrections log and policy

Local Record is derived from public records. When the site gets something wrong, the correction should be visible, specific, and traceable to the source.

Meeting summaries on this site are AI-assisted and can contain errors, especially in proper nouns, vote tallies, dollar figures, addresses, and transcript-derived wording. Every meeting page links to its primary source. The official document, recording, agenda packet, or transcript remains the authoritative record.

How to report a correction

Send correction requests to corrections@localrecord.org or use the feedback form and choose Correction. If the issue appears on a meeting page, include the meeting URL and the exact sentence, phrase, number, name, or link that appears wrong.

What to include

  • Page
    The Local Record URL where the issue appears.
  • Specific claim
    The exact text, vote tally, date, dollar figure, name, address, source link, or summary point that should be reviewed.
  • Source support
    A link, page number, agenda item, timestamp, transcript interval, or public-record citation that supports the correction.
  • Contact
    An email address if you want a reply. Anonymous reports are reviewed, but follow-up may not be possible.

How corrections are reviewed

Correction requests are checked against the linked official source first. If the linked source is incomplete or ambiguous, Local Record may check another public record from the same public body, such as a later approved-minutes packet, meeting recording, agenda attachment, or public portal entry. Unsupported assertions are not substituted for source-backed facts.

When a correction is confirmed, the affected page is updated and the change is logged below. If the issue is material, the page should include a visible correction note near the corrected passage or source-verification area. Minor typographical fixes may be made without a separate log entry when they do not change meaning.

What gets corrected

  • Factual errors
    Wrong names, dates, vote tallies, dollar figures, addresses, ordinance numbers, parcel references, motion outcomes, source links, or meeting metadata.
  • Unsupported summary language
    A statement that overstates, understates, or adds meaning not supported by the cited source.
  • Missing uncertainty
    Cases where the source is unclear and the page should say so instead of presenting the claim as settled.
  • Broken trust metadata
    Broken source links, missing source labels, incorrect source-status language, or incorrect AI disclosure.

What does not count as a correction

  • Disagreement
    A policy disagreement, objection to a public body's decision, or preferred interpretation that is not a factual error in the summary.
  • Omission
    A request to add context that is not necessary to correct an inaccurate or misleading published claim.
  • Private information
    Non-public material, private correspondence, or background claims that cannot be checked against public source material.
  • Official source changes
    If a public body later changes, replaces, or corrects its own record, Local Record may update the derived summary, but the issuing body remains responsible for the official record.

Visible updates

Confirmed material corrections should identify what changed, when it changed, and which source supports the change. The goal is not to erase errors silently; it is to make the corrected version useful while preserving a public trail for meaningful corrections.

Published corrections log