The Real Economics of Spreadsheet Management, and How Far It Scales
A shared file for procurement tracking, another for weekly team hours, a third for the consolidated dashboard across subsidiaries. It has worked for five years and the executive team reviews it every Monday. Why change?
It's a fair question, because spreadsheets have real strengths. Everyone knows how to use them, everyone already has Excel, and you can test a new formula in a minute. For a mid-sized company with one or two teams handling simple data, specialized software often isn't worth it.
The breaking point rarely arrives all at once. A controller double-checks everything behind their team, a manager asks "which version is the real one", an audit can't reconstruct who changed what. None of these frictions blocks operations, so none triggers any urgency, yet each one costs time.
Here are the six signals that show a multi-entity organization has reached the limit of shared spreadsheets.
The Six Breaking Signals of a Multi-Entity Organization
Signal 1: Multiple Versions of the Same File Circulate in Parallel
A consolidation manager receives three files by email named Budget_2026_V3.xlsx, Budget_2026_V3_final.xlsx and Budget_2026_FINAL_OK.xlsx. All three carry different dates and contain figures that do not match. Impossible to know which reflects reality. This forces a group email asking who holds the official version, delaying consolidation by two days.
It happens whenever each subsidiary edits its own copy and sends it back to headquarters without coordination. Copies sent by email don't merge on their own, so consolidation turns into manual rework, with the errors that come with it.
Signal 2: The Manager Systematically Redoes Calculations Behind the Team
A finance director opens the file transmitted by their team, randomly selects ten lines, recalculates the totals on a calculator. Two out of ten show discrepancies. They then spend two hours checking the entire file line by line, because a single wrong cell invalidates the whole table.
This second-level control appears on no org chart, yet every month it eats hours of senior managers' time just to compensate for manual entry risk.
Signal 3: Two People Modify the File Simultaneously and One Modification Is Overwritten
Two controllers work on the same day on the workbook stored on the server, one on procurement, the other on human resources. The second one opened it read-only, saved their version under another name, then copied it over the original in the evening. The first controller's work is gone, and they only notice two days later.
Signal 4: Impossible to Trace Who Modified Data and Why
During an internal audit, management requests justification for a budget decision made six months earlier. The file lives on a network server, so its properties show a few author names but say nothing about who changed which cell or when. The team digs through email archives for two days without success, and the audit issues a reservation.
Even in OneDrive or SharePoint, where Excel does keep track of changed cells, the workbook never says why a figure changed (more on this below). For an organization with traceability obligations, that gap becomes a formal documentation risk.
Signal 5: The Person Who Enters the Figures Also Approves Them
A department head types their scope's amounts straight into the consolidated file, then signs off on the final consolidation themselves. Every other month, a wrong figure makes it all the way to the executive committee, because nobody else can approve it without redoing the whole check.
The COSO framework says the person who enters data shouldn't be the one who approves it. A spreadsheet has no way to enforce that, so teams fake it with protected sheets and manual rules that nothing actually makes people follow.
Signal 6: A Copy-Paste Breaks a Formula and Nobody Notices Until Closing
An assistant copies a section of the file to prepare next month's report. The paste breaks a cell reference that pointed to another sheet, and the formula turns into #REF!. A conditional format hides the error, so the file keeps circulating. At month-end close the total is off by 140,000 EUR, and management only finds out by comparing it with the accounting extracts. The whole close has to be redone.
The Hidden Cost of Second-Level Control
The case for spreadsheets rests on not buying extra licenses, but it leaves out the human time spent making up for the lack of automatic checks. Before investing in a business solution, a digital maturity audit helps pinpoint those friction points and measure what they actually cost.
Take a fictional case: a 600-person service group with five subsidiaries that consolidates fifteen shared files every month. The group controller spends 12 hours a month re-checking consolidated data, and their deputy spends 8 more reformatting and cross-checking against accounting exports. At an assumed loaded cost of 75 EUR an hour, that double check comes to (12 + 8) × 12 × 75 = 18,000 EUR a year, before counting the projects the controller never gets to or the errors that slip through anyway.
Add the time operations staff lose waiting for sign-off. What a platform with validation workflow, automatic checks and an audit trail costs depends on scope and support, so the decision is case by case. It tips once manual checking costs more than the software.
Concurrent Access: What Breaks When Multiple Teams Write
The spreadsheet was designed for a single user, and what happens next depends on where the file is stored. On a network folder, the first person to open the workbook locks it and everyone else works read-only. In OneDrive or SharePoint, with Excel for Microsoft 365 or Excel for the web, co-authoring does let several people write at the same time. It still has limits: when two people change the same cell, the last saved change wins, and a single user on Excel 2016, 2019 or 2021 LTSC is enough to lock everyone else out.
So in a group where five subsidiaries fill in their budget section at the same time, organizations work around the problem with rules ("only the consolidation manager edits the master file", "one tab each, in turn"). These rules slow everything down and only hold as long as everyone follows them. The first new hire or the first emergency, and the duplicates are back.
Why Do Rows Disappear When Two People Edit the Same File?
It usually shows up the same way. A subsidiary says it entered its figures on Monday, and the file management opens on Wednesday doesn't have them. Nobody deleted anything on purpose. Lost and overwritten rows are among the most common spreadsheet errors in a multi-entity group, and they come from how the file travels far more than from Excel itself.
The most frequent case is also the most mundane. A spreadsheet sent on WhatsApp or attached to an email isn't really shared with anyone, because each recipient gets their own copy. Whatever they change in that copy never reaches the original, so someone has to retype it by hand later.
A network drive works differently. The first person to open the workbook locks it, and the second can only open it read-only. That is the "locked for editing" message many people mistake for a fault. Microsoft states that server paths don't support co-authoring, and neither do Dropbox, Box or Google Drive. So the second person often saves their version under another name, and now there are two files. If they overwrite the original later, the first person's work is gone.
The old "Shared Workbook" mode has traps of its own. Microsoft now labels it legacy, has removed its buttons from the Review tab and recommends co-authoring instead. It also blocks a long list of actions, including creating tables and merging cells, and Excel for the web can't edit it.
One trap survives even in a co-authored file. When someone sorts or filters a workbook with AutoSave on, the view changes for everyone else. Whoever is typing at that moment sees their rows move, and an amount can land on the wrong line without anyone noticing.
Excel does handle this better than it did ten years ago, provided the file sits in OneDrive or SharePoint and everyone opens it in Excel for Microsoft 365 or Excel for the web. Simultaneous editing then becomes real co-authoring, and each person sees the others' entries almost live. Two limits remain. When two people change the same cell, the last saved change wins, and a single person opening the file in Excel 2016, 2019 or 2021 LTSC is enough to lock everyone else out. Sheet Views fix the sorting problem, since each person filters for themselves only. To see who changed what, the Show Changes command on the Review tab lists who changed which cell, when, and the previous value, going back 365 days. Version history lets you roll back to an earlier state. You can also set a dashboard to Read-Only Recommended so viewers don't save changes by accident, and open only certain ranges for input with Allow Edit Ranges.
These settings limit the damage without changing what the tool is. Show Changes tells you who touched a cell, but never why or who approved the figure, because a spreadsheet has no notion of a reason or an approval step. When five entities fill in the same workbook, with two levels of sign-off and an audit to pass, sharing is no longer the issue; the tool is. Microsoft says as much in its own documentation, where it writes that worksheet protection "isn't intended as a security feature."
Absence of Audit Trail: Reconstructing a Decision Six Months Later
An audit trail is the ability to find who changed which data, when, why and with what approval. Many organizations need one, whether for a financial audit, an ISO certification or a regulated sector.
How much of it Excel keeps depends on where the file lives. On a network server, it keeps only a few author names in the file properties. In OneDrive or SharePoint, Show Changes lists who changed which cell, when, and the previous value, over the past 365 days. Microsoft notes, though, that formatting, PivotTable operations and filtering aren't tracked, and that an edit made in a one-time purchase version of Excel clears the Changes pane, as does replacing the file with a copy.
The old Track Changes (Legacy) feature is no better. It's gone from the ribbon, so you have to add it to the Quick Access Toolbar, and turning it on converts the workbook into a legacy shared workbook, with all its restrictions and a change history kept for 30 days by default. None of these tools records the reason for a change or the approval behind it.
So six months after a contested budget decision, the team digs through emails and questions participants to piece together a rough timeline. Best case, that takes two days. Worst case, the information is gone and the audit concludes that internal control is inadequate.
A business platform, by contrast, records every entry and every approval (who, when, at which step) and lets you attach supporting evidence to each line. That traceability is worthless until the day an external audit or a dispute asks for it, and then it's critical.
Segregation of Duties: What Spreadsheets Cannot Enforce
Segregation of duties means the same person doesn't combine data entry, validation and approval of an operation, which limits both undetected errors and deliberate manipulation.
In business software, the workflow enforces it. A enters, B validates, C approves, and the system can refuse to let the same person enter and then validate.
A spreadsheet has nothing like that. You can password-protect cells or sheets, but anyone who knows the password can do anything, and Microsoft itself says that this protection isn't a security feature. If the file travels by email, every copy also becomes its own independent control point.
For an organization under formal internal control (SOX, statutory audit), auditors often flag this as a weakness, because a critical process run on a shared file can't prove segregation.
Which Files Justify a Platform, Which Do Not
Not every shared file needs replacing. What decides it isn't file size or row count but three things together: criticality, collaboration and traceability.
Files that do not justify a platform:
- An internal contact list kept by one person and read by the team.
- A one-off dashboard built for a single analysis (market study, pricing simulation), with no reuse and no formal approval.
- Exploratory calculations shared by two or three people to test hypotheses. It's a draft, not an official data source.
In these cases, the spreadsheet is still the right tool.
Files that justify a platform:
- Multi-entity budget consolidation: subsidiaries enter forecasts, headquarters consolidates, the finance director validates, the committee approves, and each decision needs an audit trail. An enterprise dashboard solution with built-in workflow is made for this.
- Procurement tracking with purchase order approval: several buyers enter in parallel, department heads validate, management approves above a set amount. It needs segregation of duties and traceability.
- An operations dashboard updated daily by five teams on several sites, which needs simultaneous access without overwrites and a change history.
- Supplier contract management, where legal, procurement and finance all step in and need automatic reminders and an audit trail.
The tipping threshold is generally around these criteria:
- More than three users modifying the file in parallel.
- More than two validation levels (entry, control, approval).
- Traceability obligation regulatory or contractual (audit, certification, compliance).
- Recurring use (at least monthly) over several years.
The Five-Question Decision Test
To see whether a shared file has outgrown the spreadsheet, answer these five questions:
1. How many divergent versions of this file circulate on average each month?
- Zero or one: file is under control.
- Two to three: acceptable friction zone.
- Four or more: significant time loss and high error risk.
2. How many hours per month does a manager spend manually re-verifying data entered by their team?
- Less than 2 hours: normal spot control.
- Between 2 and 8 hours: second-level control starting to weigh.
- More than 8 hours: manual control cost probably exceeds platform cost.
3. Have you ever lost modifications because two people worked in parallel on the file?
- Never: effective coordination mechanism.
- Once or twice: isolated incident.
- Regularly (more than three times in the year): structural concurrent access issue.
4. In case of audit, can you prove who modified which data and why?
- Yes, with certainty: audit trail in place.
- Partially, by searching through emails: fragile informal trail.
- No: documented non-compliance risk.
5. Does the same person enter and validate critical data?
- No, roles separated: segregation of duties respected.
- Sometimes, by exception: acceptable gray zone.
- Yes, systematically: absence of formal internal control.
Interpretation:
- If you answered option 1 to all five questions, the spreadsheet remains suitable.
- Three answers in zone 2, or one in zone 3: you are at the breaking point. The file still works, with growing friction.
- Three answers in zone 3: the spreadsheet has become a documented risk, and moving to a platform is justified.
FAQ
- At what user threshold does a shared file become unmanageable?
There is no single threshold, because it depends on the kind of edits (read-only or simultaneous writing) and on how critical the data is. Tension starts as soon as several people write to a critical file at the same time outside co-authoring, because divergent versions and overwrites then become too likely to manage by hand. If the file needs formal traceability, even two or three users can justify a business platform.
- How do you measure the cost of second-level control?
Find the managers who routinely re-check their team's data, and ask them to log the time they spend on it for one month, leaving out genuine business analysis. Multiply that time by their loaded hourly cost (salary, payroll charges and overhead), then annualize. Finally, compare the result with the cost of an equivalent platform for the same scope; the investment makes sense once manual checking costs more.
- Does cloud Excel (Microsoft 365) solve the concurrent access problem?
Mostly, provided the file is stored in OneDrive or SharePoint and everyone uses Excel for Microsoft 365 or Excel for the web. Co-authoring then removes divergent versions, and Show Changes tells you who changed which cell and when, over 365 days. When two people change the same cell, though, the last saved change still wins, and the tool never says why a figure changed or who approved it. For collaborative work with no formal traceability stakes, that's enough. For a critical multi-entity process that has to pass an audit, the approval workflow is still missing.
- How do you convince executive management to move from a file that has "worked well for years" to a business platform?
Don't start from the idea that change is necessary; start from measurable frictions: time spent re-checking, errors found after the fact, divergent versions, overwritten edits. Put them in hours and euros, then compare with the cost of a platform over three years. If the file runs without significant friction, there's no reason to change, because moving to a platform is justified by reducing a documented risk, not by a technology fad.
- Why does a shared Excel file open as read-only?
Most often because someone else already opened it from a network folder, which doesn't support co-authoring, so the workbook stays locked until they close it. Microsoft also points out that the "other user" can be you, when the file is still open on another device or a previous session didn't close properly. Sometimes the owner has set the workbook to Always Open Read-Only or Read-Only Recommended, and then it's intentional. If the lock comes back every week, the lasting fix is to move the file to OneDrive or SharePoint, as long as everyone opens it in a version of Excel that supports co-authoring.
Sources
- Microsoft, Collaborate on Excel workbooks at the same time with co-authoring
- Microsoft, Excel file is locked for editing
- Microsoft, What happened to shared workbooks in Excel?
- Microsoft, About the shared workbook feature
- Microsoft, What you should know about AutoSave
- Microsoft, Create and manage Sheet Views in Excel
- Microsoft, Show changes made in a workbook
- Microsoft, Get help with Show Changes in Excel
- Microsoft, Excel specifications and limits
- Microsoft, View previous versions of Office files
- Microsoft, Lock or unlock specific areas of a protected worksheet
- Microsoft, Protect a worksheet
Last verified: 4 November 2026.





