The weekly spreadsheet email often looks harmless: “Please add your figures and send this back by Friday.” The trouble appears on Friday afternoon, when somebody has to combine six returns, resolve two contradictory changes and work out whether an earlier attachment was sent to a customer.
The aim is not to ban email or Excel. It is to give the process one reliable home, so email carries a link, a notification or a finished report rather than another editable version.
First find out why people send the file
An instruction to stop attaching spreadsheets will fail if attachments are solving a genuine access problem. Speak to the people who send and receive them. They may be unable to reach the shared drive, find the live workbook awkward on a phone, need a fixed record for approval or simply be unsure whether co-authoring is safe.
These needs require different answers. A PDF sent after approval is a useful point-in-time record. An editable workbook returned by six branches is six competing versions of the truth.
For one reporting cycle, note who sends each copy, why they send it and what happens when it comes back. Also record the time spent merging changes or checking which values are current. This gives you a baseline and prevents the solution being based on guesswork.
Start with one clearly owned workbook
For a straightforward process, the answer may already be available in Microsoft 365. Put the workbook in one agreed SharePoint or OneDrive location, nominate a business owner and make the link easy to find. The owner is responsible for access, structure and deciding when a change is safe, rather than becoming the only person allowed to enter data.
Set a simple working rule: colleagues edit the shared workbook; email may contain a link or a non-editable report. People who only need the result should have view access, not a copy of the working file.
Modern Excel co-authoring is well suited to stable workbooks with a manageable number of editors. Comments can stay with the relevant cells, and version history offers a route back after an accidental edit. If the workbook contains complex macros, changes shape frequently or is used through a mixture of unsupported desktop versions, test it with a small group before relying on co-authoring.
This is an important point in Excel's favour. If a better sharing routine removes the problem, replacing the workbook would add cost without a corresponding business benefit.
Keep approval evidence without keeping another master
Approvals are a common reason for creating copies. A manager wants to know exactly what was agreed, so a dated workbook is attached to an email. Later, somebody updates that attachment and it quietly becomes a second working version.
Separate the evidence from the live data. Keep the approval decision and status in the agreed working location, then generate a dated PDF or protected export if a fixed record is needed. If an approved figure must change, record that as a new change rather than editing the approval copy.
Consider a hypothetical stock-ordering process. Each depot updates expected demand in the shared workbook, and a purchasing manager approves the total on Wednesday. The Wednesday PDF can be retained with the purchase order, while Thursday's amendments go into the live workbook for the next order. Nobody needs to guess whether the PDF is still open for editing.
Recognise when file sharing is no longer enough
Sometimes emailed copies keep returning because the work has become more demanding than a shared document can comfortably handle.
A web app becomes worth considering when outside partners or field staff need simple remote access; users should see different information according to their role; several people update related records throughout the day; or work passes through formal review and approval stages. Repeated version errors after a fair attempt at co-authoring are also useful evidence.
Instead of opening a whole workbook, each person signs in and works with the information they are allowed to use. A supplier might update delivery dates without seeing margins. A regional manager might approve unusual cases for their own area. Office staff can see those changes immediately, while the app records who changed what.
The app can also make the next step explicit. New submissions can appear in a review queue, missing information can be flagged before submission and an approved record can be locked or changed through an agreed route. This turns an informal chain of attachments into a visible workflow.
Excel need not disappear. Users can still export current data for analysis, while the app remains the place where records are updated. Excel and hosted web apps each have distinct strengths, and a mixed approach is often the most practical.
Change the habit without disrupting the work
Whether you choose co-authoring or an app, introduce the new routine around a named process, not the whole company. Pick a cut-off date, move new work to the agreed location and keep the last master as a read-only archive. Give users a short guide based on their actual tasks, including how to sign in remotely and where to get support.
During the first few weeks, count editable spreadsheet attachments for that process. Do not treat every one as disobedience. Ask what the sender was trying to achieve. If a field worker could not use the new screen on a phone, or a supplier had no suitable account, the old email has exposed a gap that needs fixing.
Useful measures include:
- editable copies sent each week
- time spent combining returns
- corrections caused by an old version
- time from submission to approval
The figures need not be perfect. A consistent before-and-after count is enough to show whether the change has reduced work or merely moved it.
Avoid moving the same problem elsewhere
Uploading copies to a chat channel creates the same version problem with a different delivery method. Locking a complicated workbook in a shared folder may also force one person to become a permanent gatekeeper. Neither provides the flexible multi-user access the team was missing.
It is equally unhelpful to declare that all spreadsheets must go. Personal analysis, forecasts and one-off calculations may have nothing to do with the troubled process. Keep the scope around the editable copies that currently require reconciliation.
If the evidence points beyond file sharing, the guide to what a spreadsheet-to-web-app project includes will help set realistic expectations. For a review of the actual workbook, users and handovers, you can then request an assessment before deciding whether a web app is justified.