When multiple users edit the same Excel workbook at the same time, the problem is not simply whether the file opens for everyone. The real issue is whether the team can rely on one current value when that value drives an operational decision.
For an operations manager, this often appears in a live job tracker, production plan, order list, stock sheet or project register. Two people update the same row. A third person checks the workbook and needs to act. The question becomes simple but important: which update should be trusted right now?
Modern Excel co-authoring can make shared editing practical. But co-authoring does not decide who should change an operational value, resolve conflicting business decisions or establish who owns the final update.
What happens when two people edit the same operational workbook
Consider a shared order-management workbook.
- One person changes an order status after speaking to a customer.
- Another changes the expected dispatch date after speaking to the warehouse.
- A colleague uses the row to plan the next action.
Each update may be reasonable. The risk comes when people are changing related information at nearly the same time without a clear owner for the record or a shared rule for how changes are handled.
The result is not necessarily a technical failure. It is often a process failure: people can see a live workbook but still disagree about what the current operational position is.
This becomes more serious when the workbook is used to control work rather than analyse it. A changed date, quantity, job status or production priority can affect what someone does next.
Shared access is not the same as shared certainty.
Excel co-authoring can help, within its role
Excel supports co-authoring for compatible workbooks stored in supported cloud locations such as OneDrive or SharePoint. Microsoft explains that co-authors can work in a workbook together and see one another's changes while collaborating. Read Microsoft's guidance on co-authoring Excel workbooks.
That is useful for collaborative analysis, planning sessions and temporary shared work. For example, a team may use Excel successfully to:
- build a forecast together
- review assumptions in a model
- carry out ad-hoc analysis
- explore options before agreeing a plan
- work through flexible calculations
Those are valuable uses of Excel, including when more than one person contributes.
The limitation appears when a workbook becomes the live place where people repeatedly update operational facts and other people act on those facts immediately.
The simultaneous-editing risks that matter in operations
Conflicting changes to the same record
Two people may update the same cell, row or related fields for different reasons. Even where collaboration features are available, the team still needs a business rule for whose update represents the current position.
For instance, if a planner changes a delivery date while a customer-service colleague changes the order status, the workbook itself may not explain which change should determine the next action.
Delayed awareness of a relevant update
Co-authoring is intended to share changes, but what each user sees can depend on their connection, application, workbook and the timing of edits. A user may begin an action based on the value they saw before they notice another person's update.
For a low-stakes planning sheet, that may be manageable. For a live operational tracker, it can create avoidable calls, rework or incorrect instructions.
Unclear ownership of updates
A shared workbook can make it easy for several people to change a value. It does not, by itself, answer questions such as:
- Who owns the status of this job?
- Who is allowed to change the planned date?
- When should an update be treated as final?
- Who resolves two valid but competing updates?
When these answers live only in informal habits, people have to stop and check with one another before they can trust the workbook.
Uncertainty about the value that should drive action
Operational work needs a trusted current state. If staff routinely ask, “Is this the latest number?” or “Has anyone changed this since I looked?”, the workbook may be creating friction at exactly the point where the team needs clarity.
This is not an argument that every shared spreadsheet should be replaced. It is a sign to look closely at the workflow the workbook is supporting.
A practical test for a shared operational workbook
Ask these questions about the workbook in use today:
- Do two or more people regularly update the same jobs, orders, plans or records?
- Can one update change what another person needs to do next?
- Does the team need to pause, message or verbally confirm which value is current?
- Are updates owned by individuals, or does everyone edit the same fields as needed?
- Would a conflicting update create a customer, production, delivery or commercial problem?
If the answer is yes to several of these questions, the concern is not the number of Excel users. The concern is that the workbook is being asked to coordinate live work between people.
What to do if Excel must remain the shared tool
Excel can remain appropriate where the work is primarily analytical, exploratory or temporary. If the workbook is still the right tool, reduce ambiguity around simultaneous updates.
Give each live record an owner
Make it clear who is responsible for the current state of a job, order, plan or item. This is more useful than a general instruction to “avoid overwriting each other”.
Agree which fields can change together
Identify the fields where changes can affect one another, such as status and scheduled date, quantity and availability, or production priority and target completion. Agree how the team should coordinate those changes.
Separate live updates from analysis where possible
A workbook can be excellent for forecasting and modelling without also being the place where staff make every live operational update. Keeping these purposes distinct can reduce contested changes.
Treat repeated uncertainty as a process signal
If staff often need to ask which figure is current, that is useful evidence. It shows the process needs a clearer way to manage concurrent operational updates.
When a managed custom web application is a better fit
A managed custom web application becomes worth considering when the business needs a dependable current state for work that several people update during the day.
The key requirement is not simply more users. It is a workflow where people need to update live records without repeatedly second-guessing the latest position or negotiating ownership outside the system.
A purpose-built application can be designed around the actual operational process, such as:
- a job moving through defined stages
- an order being updated by office and warehouse teams
- a production plan being changed by several operational roles
- a project record requiring one current status for the next decision
Instead of asking a shared grid to represent every possible situation, the application can provide a clearer route for the updates the team actually needs to make. The aim is a trusted current operational state, not a more complicated version of Excel.
For a broader view of that decision, see when to replace Excel with a web app.
The decision is about live operational control
Do not replace Excel just because more than one person uses it. Excel remains a strong tool for modelling, forecasting, ad-hoc analysis, flexible calculations and exploratory work.
Consider a managed custom application when simultaneous updates to one live operational workbook are creating conflicting changes, unclear ownership or uncertainty about which value should drive action.
Spreadsheet Upgrade builds fully managed custom web applications for UK businesses whose operational Excel workflows have outgrown a shared workbook. If your team needs a clearer way to manage concurrent live updates, start with a Free Fit Check.