Version Control in Shared Cloud Folder
A team of five editors shares a cloud folder for a quarterly report. The folder contains 12 files, including 'Q3_Report.docx'. Two editors, Alice and Bob, open the file simultaneously. Alice edits for 20 minutes and saves. Bob edits for 30 minutes and saves. The cloud service does not support real-time co-authoring. After both save, the file's modification time shows Bob's save, but Alice's changes are missing. The team uses the service's version history feature, which retains previous versions for 30 days.
1. What likely happened to Alice's changes, and how can the team recover them?
Read the worked answer
Because the cloud service lacks real-time co-authoring, when Bob saved after Alice, his save overwrote Alice's version. The file now reflects only Bob's edits. However, the service keeps version history for 30 days. The team can open the version history for 'Q3_Report.docx', locate the version saved by Alice (timestamped before Bob's save), and restore or download that version. They can then manually merge Alice's changes with Bob's current version. To prevent recurrence, they should adopt a check-out/check-in process or use a service with co-authoring.
2. What collaboration practice could prevent this issue in the future?
Read the worked answer
The team should implement a check-out/check-in system: before editing, a user marks the file as checked out (e.g., by renaming it or using a shared spreadsheet to track). Others see it's in use and avoid editing. Alternatively, they could use a cloud service that supports real-time co-authoring, or assign specific sections to each editor and merge later. Regular communication about who is editing which file is key.