Corrections Policy
Law Leaderboard is intended to be auditable. If a factual error appears on the site, it should be corrected clearly and without rewriting history in a way that hides what changed.
What Qualifies For Correction
- Wrong office identity, merged offices, or duplicate-entity errors.
- Wrong public business information such as address, phone, website, or category.
- Incorrect tracked, retrieved, or analyzed counts.
- Incorrect review-theme labels, aggregate theme counts, percentiles, or brand-consistency metrics.
- Incorrect legal citations or materially inaccurate legal summaries.
- Broken links, stale timestamps, or missing provenance blocks on pages that require them.
Entity Graph Corrections And Quarantine
Law Leaderboard separates a brand from each physical office. An office can be linked automatically only when its raw Google Place ID or CID exactly matches an existing office. A shared domain, similar name, address, phone number, brand relationship, or nearby location can support investigation but cannot silently merge records. If those signals conflict, the candidate remains quarantined and is excluded from automatic office-level linkage until the identity is resolved.
A confirmed identity correction is made in structured data, not only in page copy. The correction produces a new versioned release and updates downstream pages; the prior release, manifest, and checksums remain available so the change can be traced.
Review Theme And Metric Corrections
A review-theme label describes explicit language in a captured public review; it does not verify that the reviewer’s allegation, result, settlement, recovery, or other claim occurred. If a rule is confirmed to be wrong, the classifier receives a new version and affected aggregates are rebuilt through the release pipeline. We do not hand-edit a public percentage while leaving its underlying labels unchanged. Themes that fail publication gates remain suppressed until a later validated release.
How Corrections Are Handled
Corrections should be reviewed against source documents and the underlying dataset. If the issue is confirmed, the page should be updated in the next publish cycle and the corrected data should flow through the export pipeline rather than being patched only in the rendered page.
Entity-resolution issues should be fixed at the structured-data layer first. Legal-source issues should be fixed at the citation layer first. Classifier issues should be fixed in the versioned rule and QA layer first. Surface copy should be updated only after the underlying fact pattern is corrected and downstream checks pass.
Historical Snapshots
Because the site is based on recurring snapshots, a page can become outdated without being wrong at the time of publication. The preferred fix is to refresh the underlying data and update the visible freshness markers rather than silently rewriting old claims without acknowledging the page’s timing context.
Submit a Correction Request
Include the exact Law Leaderboard URL, the detail you believe is wrong, and a public source that supports the change. Submitting this form opens a structured email in your mail application; the site does not collect the form data itself.