Version control: stop emailing drafts

Version control means tracking changes so you can revert or merge edits without losing work. The core contrast is between a shared system—like Google Docs' version history or a formal check-in/check-out workflow—and emailing attachments. When two colleagues edit a policy draft in parallel, emailing creates separate copies that quickly diverge; merging them later is error-prone and time-consuming. A shared document keeps a single source of truth, and version history lets you see who changed what and when.

To spot the right answer in a scenario, look for clues about parallel editing. If the question mentions 'two people edit at the same time', the solution must involve a tool that handles concurrency—either real-time collaboration with an audit trail or a locked check-out system. Eliminate any option that says 'email the latest version' or 'save multiple copies with different filenames', because those cause duplication. Also watch for 'track changes' in a non-shared document: it helps but still requires manual merging if edits are simultaneous.

A quick way to test your understanding: imagine you and a colleague both need to edit a document. If you email it back and forth, you risk overwriting each other's work. The fix is to use a platform that records every change and lets you see the full history. Remember: version control is about preventing chaos, not just tracking edits—so shared access with history beats any manual method.