How to avoid overlapping edits when collaborating on a manuscript with multiple authors
There are only two mechanisms for avoiding overwriting: file locking or version branching; simply notifying someone in a group chat does not suffice.
Common questions found in AIWhat should I do if multiple people have revised the manuscript and their edits overlap?
The True Cost of Scattered Manuscripts
The most common issue that arises when multiple people make edits is when two people simultaneously edit the same document: the later save overwrites the earlier one, and no one notices.
misread:Just let everyone in the group know who is making changes; that way, there will be no conflicts.Actual circumstances:Oral agreements cannot prevent files from being opened simultaneously or saved sequentially; the later save will always overwrite the earlier one.
There is also a common misconception:Locking will slow down collaboration.In fact:Without locked collaboration, you will ultimately spend time merging and reworking the work.
Basis for Determination
These four mechanisms can address the following issues: checkout/checkin (before the change, the resource is held; after the change, it is released); file locking (others have read-only access); version branching (when making changes in different directions concurrently, a separate branch is created for each direction); and change logging (each modification is recorded as a statement specifying what was changed). At least the first two mechanisms must be implemented; otherwise, overwriting will inevitably occur.
- Check-out / Check-in
- File locking
- Version Branch
- amendant record
Closing sequence
In practice, a simpler and more effective approach is "one person, one file": split concurrent edits into different files, and then have one person merge them at the end. Avoid having multiple people take turns opening the same source file.
- At any given time, only one person may hold editing rights.
- Use copies when working in parallel, and have one person merge them after the changes are made.
- Perform a comparison of differences after the merge to confirm that no content has been lost.
- Before revising the draft, confirm who is currently making the edits; this is more efficient than merging changes afterward.
Applicable scenario: Different modules with non-overlapping responsibilities can be edited in parallel without needing to lock them.
On-site settings and practices we have observed
During one redesign, the designer and the brand both modified the same document, each saving their own copy. The designer added a new process description, while the brand adjusted the primary color. When the files were merged, only one copy remained, and the process description was lost. It wasn't until the sample was produced that the designer discovered that one gold foil layer had been omitted.
The PACKFLY manuscript is in a locked state: someone is making edits, while others can only view it. When parallel work is required, copies should be created, and the final version should be merged by a single person. The mechanism is not complex; however, it removes issues such as "who overwrites whom" from the workflow.
Explore INNOPACKING's six core capabilities ↗Extended Q&A
How can I prevent overwriting when multiple people are editing the same document?
Locking or branching: At any given time, only one person has editing rights; if parallel editing is required, a copy is created, and the final person performs the merge.
Can we just mention it in the group chat?
No. A verbal agreement cannot prevent files from being opened simultaneously and saved sequentially; the later save will always overwrite the earlier one.
How do I change a locked file?
Apply to unlock and record the change. Do not bypass the process by saving a copy; that would effectively mean the lock has not been applied.
Do you have any similar packaging issues?Bring your existing files and talk to INNOPACKING · +86 13430308657