Check whether people edit the same source.
Separate emailed copies, local copies and a shared online workbook. A later import from an old file can overwrite new work even when staff never edit at the same moment.
Diagnostic guide
Find which save replaces someone else's work.
Use a safe copy and fictional records to reproduce the conflict. Preserve the working file and its available history first.
Reviewed October 16, 2026 ยท Faith Forge Labs
Use a two-person example.
In a fictional test, two users open record A at version 3. One changes its status; the other later saves an older copy with a new note. Decide whether the second save should warn, merge independent fields or require a fresh review.
Define the application rule.
A database alone does not settle competing edits. The app needs an agreed response to stale values, repeated requests and failed saves. Show the user whether their change was stored.
Record a useful incident.
Note the source file or record, relevant times, each action and the expected result. Keep private values out of the initial inquiry. Do not repeatedly reproduce the problem on live records.
Discuss conflicting edits or compare repair and app options.