How does version control support transcript drafting?

• A. Eliminates need for editors.
• B. Only keeps the latest version.
• C. Tracks revisions, allows comparison between versions, and prevents data loss across edits.
• D. Automatically finalizes the record without human review.

Answer: (C)

Version control in transcript drafting is about keeping a complete history of edits and managing changes over time. It records each revision, who made it, and when, so you can view exact differences between versions, compare drafts side by side, and revert to a prior version if needed. This protects work from being lost during edits and supports safe collaboration, since multiple people can contribute, branches can be created for different lines of the transcript, and changes can be merged with an audit trail. In practice, you get tracked revisions, clear change comparisons, and robust safeguards against data loss across edits, which is why this option best describes how version control supports drafting. The other ideas miss important points: editing isn’t eliminated by version control, only the latest version isn’t preserved without history, and records aren’t automatically finalized without human review.