Trace where spreadsheet copies split, preserve competing edits, and restore one authoritative workbook with a supported editing route and clear ownership.
Direct answer: Conflicting versions usually mean people are editing different copies, using an unsupported collaboration route or working without a clear rule for returning offline edits. Preserve every relevant copy, identify where they split, and reconcile disputed values against source evidence before naming an authoritative workbook. Then test a supported shared-editing process with harmless rows; do not simply keep the file with the newest modification time.
“Shared” can mean an email attachment, a network folder or a cloud workbook opened by several people. Those arrangements do not have identical behaviour. A familiar filename does not establish that everyone is looking at the same underlying file.
The problem is therefore partly technical and partly ownership. A working co-authoring feature cannot decide which of two contradictory customer addresses is correct. That requires evidence and a person accountable for the decision.
Applies to: shared spreadsheets, with documentation-based examples for Excel and Microsoft 365. Check the exact application, account and storage service before adopting a collaboration method.
Make the file-copy lineage trace
The file-copy lineage trace is an editorial diagnostic method. You reconstruct which copy came from which source, identify edits made after each split and resolve the meaningful differences. It applies the parent guide's workflow-based assessment of software to one source of repeated rework.
Agree a short pause in editing before reconciliation. Save protected copies of the candidate workbooks and ask each contributor which one they used and when. Do not delete a file because its name includes “old”; it may contain the only surviving correction.
Choose an authorised location for the comparison. Customer or staff data should not be uploaded to an unknown online spreadsheet-merging service. If multiple people need access, give only the permissions required for the review.
Find the first split
List each file's location, owner, received time and known origin. An emailed attachment that began as the cloud workbook becomes a separate branch when someone edits it independently. A downloaded copy can similarly diverge even if its filename is unchanged.
Ask concrete questions: who downloaded the attachment, who used a desktop shortcut, and who made changes without a connection? This is evidence gathering, not blame. People often create copies because the official editing route is slow, locked or unavailable to them.
Look for a shared identifier or original version, but do not trust modification time as a measure of correctness. Opening, copying or saving can make a file look newer without incorporating someone else's work. Record which source event supports each disputed change.
If the workbook contains formulas, named ranges or linked sources, include them in the comparison. Looking only at displayed cell values can miss changes that affect the next calculation.
Verify the collaboration route
Microsoft's Excel co-authoring guidance specifies supported Excel versions, account requirements, file formats and storage in OneDrive or SharePoint Online. Its desktop Microsoft 365 instructions are not a guarantee that every Excel installation or shared server provides the same function.
Confirm the actual file location and application used by every editor. Microsoft also documents that an unsupported Excel version can cause a locking problem for others. If a colleague cannot use the agreed route, solve that access or compatibility issue rather than telling them to download another untracked copy.
Before changing a live workbook's format or storage, preserve the original and check features that must survive. A conversion or upload can create another version and may change permissions. Get the owner's approval and verify the resulting file with a synthetic example.
Do not repeatedly restore historical versions while people are still editing. First pause the workflow and decide which information the restoration would replace.
Reconcile edits by meaning
Use a stable record identifier to align rows, not their position on the screen. Sorting can move a row without changing its identity. If no stable identifier exists, agree a careful matching method and flag uncertain matches instead of treating them as exact.
Classify changes into additions, independent edits and genuine conflicts. Two people adding different records may be straightforward to combine. Two people changing the same amount or status require a decision about which source is authoritative.
For each conflict, record the field, competing values, supporting evidence and resolution owner. A customer confirmation can outweigh an earlier internal note; a formula change needs calculation checks rather than a popularity vote. Keep unresolved values visible until someone can establish the answer.
My recommendation is to preserve and reconcile before consolidating. Automatically choosing the newest cell or workbook is defensible only when the workflow explicitly makes recency authoritative and you have verified that timestamps reliably represent the relevant event. Most messy attachment chains do not meet that condition.
Work through six illustrative copies
Imagine a small training team finds six workbook copies. After aligning record identifiers, it finds 38 distinct changed rows compared with the agreed starting version. These are invented counts, not a measured incident.
Of those rows, 26 contain independent additions or corrections supported by evidence. The remaining 12 have competing values. The reconciliation covers 26 + 12 = 38 rows; it does not mean every copy contributes 38 unique changes.
Assume the independent rows take one minute each to inspect and the disputed rows take four minutes each to resolve. Review time is 26 × 1 + 12 × 4 = 74 minutes. Locating copies takes 15 minutes, agreeing the final file takes ten and testing the new route takes 15. Total effort is 74 + 15 + 10 + 15 = 114 minutes, or 1 hour 54 minutes.
If six contributors all attend the 74-minute detailed review unnecessarily, that uses 6 × 74 = 444 person-minutes. Instead, involve the relevant source owner for each conflict and keep others informed through the record. That is an editorial allocation choice, not a claim that every review can be completed by one person.
Time recovered is not automatically cash saved. More importantly, excluding a disputed row to finish faster can create a wrong operational decision later. The review must resolve meaning, not merely reduce the file count.
Re-establish one working route
Name the authoritative workbook by its actual location and owner. Share a link through the approved system, explain which copies are reference-only and tell contributors how to submit any late-discovered edits. Do not delete preserved candidates until the owner approves retention and the reconciled version has been checked.
Use a harmless test row to confirm that each required editor can see and modify the intended file through the supported application. Check what happens after closing and reopening, and explain the permitted offline process if one is necessary.
If simultaneous editing is not supported for an essential workbook, a controlled single-editor handover may be preferable to pretending collaboration is live. A more elaborate system is justified when the task needs access controls or change management the spreadsheet cannot provide.
Resolve one branch today
- Spend fifteen minutes pausing edits and preserving the candidate copies in an authorised location.
- Trace their origins and reconcile one consequential section first, allowing longer for disputed records.
- Assign the authoritative file, owner and supported editing route, then test it with harmless data.
- Review for new forks after the next working cycle. Stop automated merging when row identity or source truth is uncertain; ask the responsible person to resolve it before operational use.
Related guides
Frequently asked questions
Should I keep whichever workbook was modified most recently?
Not without knowing what the timestamp represents. A later save can contain fewer correct edits than an earlier copy, particularly after attachments or downloads have split the work. Compare the changed records against the agreed starting point and source evidence. If your workflow explicitly defines a later authorised event as replacing an earlier one, apply that rule to the relevant field, not blindly to the whole file. Preserve competing copies until the reconciliation is accepted. A convenient timestamp is a clue about chronology, not a general certificate that the workbook contains everyone's correct work.
Can a shared folder still contain separate versions?
Yes. People can save copies inside it, open local downloads or work through applications that do not support the intended collaboration. Check the actual path and file identity each person uses rather than assuming the folder name proves they share one workbook. Ask how they open it on an ordinary day, including shortcuts and attachments. Then test the agreed route with harmless rows. If the storage or application cannot support simultaneous editing, use a controlled handover or another approved arrangement rather than relying on a shared folder label to provide behaviour it has not demonstrated.
Is it safe to merge matching rows by their row number?
Usually not when sorting, inserting or deleting rows has occurred. Row position is not the same as record identity. Use a stable identifier where available and inspect uncertain matches before copying values. If the sheet lacks identifiers, agree a combination of fields that can distinguish records and flag cases where it cannot. Do not hide ambiguity with an automated merge that silently treats similar names as the same person. Preserve the originals and record disputed matches. A slower explicit decision is preferable to combining two different customers' information in a way that looks tidy but is wrong.
What if someone needs to work offline?
Define the offline handover before they make changes. Identify the version they start from, the records they may edit and how those edits return to the authoritative file. Avoid simultaneous changes to the same records where the tool cannot reconcile them appropriately. On return, inspect the differences rather than replacing the shared workbook wholesale. If offline work is routine, test the actual supported behaviour of the chosen application and storage service. Do not assume an icon saying the file is available locally establishes a safe process for combining everyone's later edits after the connection returns.
Should I restore an old version to fix the conflict?
Only after identifying what the restoration would remove and pausing current edits. An old version can be a useful reference or recovery source, but replacing the current workbook may discard legitimate later work. Preserve both states and reconcile the important differences first. Follow the storage service's documented version-history process, checking whether you are opening a copy or restoring over the live file. If you cannot explain which edits will be lost, stop and obtain help. Restoration is a consequential change, not a substitute for deciding which data should be authoritative after conflicting work.
When is the spreadsheet itself the wrong tool?
Consider another system when the task repeatedly needs controlled ownership, fine-grained access, linked records or auditable changes that the actual spreadsheet workflow cannot deliver. Repeated copies alone do not prove migration is necessary; an agreed location and supported editing route may solve the problem. Test that simpler correction first. If failures continue because the requirements exceed the arrangement's capabilities, document those requirements and compare alternatives on migration, maintenance and permissions. Do not buy a database merely to avoid clarifying who owns a record, because that unresolved decision will follow the data into the new system.
Sources and verification
- Microsoft: Excel co-authoring, checked 11 September 2026 for supported storage, versions and locking conditions. No live workbook was tested.
- The parent was read from the supplied site source; its public route could not be retrieved. The copy counts and timings are illustrative.
This article is practical guidance. Apply it in proportion to your tools, evidence, risks, and responsibilities.
