Track decisions rather than every mouse movement
A useful ledger is small: source timestamp, proposed cut, reason, meaning risk and reviewer. It does not need a transcript of every editing action. Focus on deletions that remove a question, exception, speaker correction or pause with a purpose. Ordinary dead space can be noted briefly; a changed claim deserves a specific explanation.
Separate correction from reinterpretation
Removing a repeated word can improve flow. Removing “in this example” can broaden a claim beyond what the speaker said. Write the before-and-after meaning in plain language when uncertain. If the editor cannot explain why the shorter version is still faithful, return to the original or ask the responsible reviewer rather than guessing.
A fictional entry shows the difference
Source: “For this test, we used a clean sample; other surfaces may behave differently.” Unsafe cut: “Other surfaces” and everything after it disappear. Safer decision: retain the qualification or choose a different demonstration point. This example is our own editing exercise, not a product result or customer story. The ledger makes the otherwise invisible tradeoff reviewable.
Carry the ledger into handoff
Attach the final filename and version to the reviewed decisions. If a later revision restores or removes material, update that one entry. Avoid a second untracked export becoming the delivered master. The record can remain a simple local document; no additional SaaS or client-access system is required to keep an edit understandable.
Use a restoration note
When a reviewer asks to restore a removed condition, record the original timestamp and the version in which it returned. Check the adjacent captions and framing again. A restoration is not merely a text change when the timeline becomes longer. This small note helps a second editor avoid reapplying the earlier cut from an outdated draft, especially when several versions share a similar filename.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- Submagic documented editing workflow — Merchant documentation · care.submagic.co · Merchant-controlled · checked 2026-09-25