One claim, one source and one publication state
Before editing a report, separate what you know from what needs confirmation. This fictional library ledger links each sentence to its evidence and to the pieces that would need correction; it describes neither an interview nor a real news event.

1. Split the script into checkable claims. “The hours change” and “the change affects every branch” require different evidence.
2. Keep the original notice with its date, issuer and scope. A screenshot without provenance does not confirm who made the decision.
3. Give each sentence a state: confirmed for this scope, pending or excluded. A blank box is not permission to publish.
4. When the source changes, locate narration, on-screen text, captions and description before exporting another version. Retain the correction and the notice that prompted it.

Claim C1: “This library will close at 18:00 from Monday.” Fictional notice N1 dated Friday; scope: one branch. State: publishable only within this example.
Claim C2: “Every library will use these hours.” N1 does not establish this. State: pending; exclude from narration and on-screen text.
Source change N2: The corrected notice says 18:30. Change narration, on-screen text, captions and description; remove the previous file from the delivery route.
Delivery check: C1 links to N2; C2 remains excluded. Check all four appearances of the time and open the exported video, not just the editing project.
Blank ledger: Claim ID __; exact wording __; source/date __; scope __; state __; owner __; dependent pieces __; delivered version __.

Claim C1: ____________________
Claim C2: ____________________
Source change N2: ____________________
Delivery check: ____________________
Blank ledger: ____________________
An accessible source makes a claim checkable; it does not by itself make the entire report accurate. Captions belong in the correction workflow too.

W3C WAI — captions — https://www.w3.org/WAI/media/av/captions/