Correction Standard
DataSplinter should be corrected when a source-backed error is found. Corrections are reviewed against public records, source documents, and available documentation.
DataSplinter
Corrections
Last updated: October 18, 2026
What Helps
A useful correction identifies the page, the exact statement or figure, the source record, the page or section in that record, and the proposed correction. Screenshots are helpful, but source links and document references matter most.
What May Change
Corrections may update figures, labels, links, plain-English explanations, document references, or date language. A correction may also add a note where records conflict or where the source packet is incomplete.
What This Process Does Not Do
The correction process is not a dispute forum and does not decide legal, political, or personal conclusions. It focuses on whether the public-record summary accurately reflects the cited records.
Source Conflicts
If official sources conflict, the page should say that plainly instead of guessing. The preferred update is a clear note describing the conflict and linking to the relevant records.
Newer Records and Historical Figures
A newer filing is added with its reporting period, source and review date. Earlier figures remain labeled as history unless the original figure was wrong. We do not replace a 2024 amount with a 2025 amount while leaving the old date or source attached. Changed accounting categories, noncash items and transfers are identified before comparing years.
Source comparisons and independent approval are separate. A record-supported figure is not described as independently reviewed until an independent reviewer has signed off. Review packets retain unresolved questions and source conflicts.
Privacy and Names
For project pages that use masked labels, corrections should preserve the page's masking rules. DataSplinter may link to source records that contain public names, but it does not add those names to masked analysis sections or public project data.