creative · local-first tool
Track a Published Correction Through the Version Readers See
A correction request is only useful when the change is reviewed, the published file is updated, and the date is visible.
Log the public asset label, reported issue, source checked, reviewer, accepted/rejected status, revised version location, and republish date.
What changes the result: the asset, source you checked, decision owner, and published location.
Privacy: Calculations run in this browser tab. This tool has no input-upload, account, or AI endpoint. The site may send a page-view signal to Cloudflare; this tool does not add form entries to that signal. A draft is stored only if you choose “Save draft on this device”; that browser storage is not encrypted. Avoid identifiers or sensitive details, and delete saved drafts when finished.
Your entries
The starting rows below are fictional examples. Edit them, replace them with non-sensitive labels and values, or load the sample again. The result is not advice or a source verification.
Amount fields use the same units you enter; the app does not choose a currency. Dates are the ones you provide. Up to 100 rows per run.
Calculated output
What the calculation does
Validate and order user-entered dates; keep the status separate from the event description. An open or waiting entry whose date has passed is highlighted for review, not treated as an official deadline or proof that an event occurred.
Question to keep open: Should a correction be published immediately or held briefly for verification of the underlying source?
Boundary: This is an editorial workflow, not a fact-checking service or legal notice. A reviewer must verify the claim and current version; do not use the log to expose a reporter's private details.
Copy includes the headline, aggregate metrics, and boundary—not the row-by-row input. The CSV contains entries you choose to download. Review it before sharing.