When Excel is no longer enough: how to tell that a process needs an application

A spreadsheet is a sensible tool, and many business processes rightly start in one. It is quick to set up, everyone understands it and it can be changed without outside help. Order records, stock levels or a list of requests can work in it for a long time.

The difficulties do not usually lie in Excel itself. They arrive when the work of several people starts to depend on one spreadsheet and a web of e-mails, phone calls and copies grows around it. So the question is not whether a spreadsheet is good or bad, but when it starts to cost you more time than it saves.

Eight signals that a process has outgrown the spreadsheet

One signal on its own does not mean much. If you recognise several of them in the same process, it is worth stopping to take a closer look.

1. Nobody is sure which version is current

The file circulates in e-mail attachments, or everyone has their own copy on their drive. Before every decision you have to check that you are working with current data, and someone merges the changes from two copies by hand.

2. You have to ask about the order status

The salesperson phones production, the customer writes to the salesperson, and the answer depends on who happens to be at their computer. The information exists, just not where people look for it. Both the question and the answer cost time.

3. Approvals happen by e-mail

A purchase or leave request is sent by e-mail and the approval stays in someone’s inbox. A month later it is hard to find out who approved what, and when. If the approver is away from work, the request stalls and nobody knows about it.

4. The same data is retyped several times

An order from an e-mail is retyped into the spreadsheet, from the spreadsheet into the stock or accounting system, and then once more into a report for management. Each retyping takes time and is a chance for a typing error that only shows up on the invoice or when the goods are issued from stock.

5. Everyone sees everything, or everyone has their own copy

A spreadsheet is usually shared as a whole, so people also see data they do not need for their work, such as purchasing terms or personal data. Companies often deal with this by keeping separate files for individual departments. That takes them back to the first signal.

6. You cannot tell who changed a value, or when

The delivery date is suddenly different, the quantity in stock does not add up, and nobody knows whether it is a correction or a mistake. When the file circulates in copies, a change is hard to trace afterwards and responsibility for the data becomes blurred.

7. A broken formula is found late

Someone inserts a row, overwrites a cell containing a formula or sorts only some of the columns. The spreadsheet looks fine, but the total no longer includes everything. The error only comes to light when someone orders material or sends a quote based on the wrong figure.

8. Reports are put together by hand

At the end of the week or month, someone opens several files, copies the data and arranges it into a report for management. The report is already out of date the moment it is sent, and the person preparing it is not doing their own work during that time.

When a spreadsheet is still the right choice

Not every process needs an application. A spreadsheet remains a suitable tool if:

• one person works with the data, or a small team that can easily agree among themselves;
• there are few records and new ones are added slowly;
• it is a one-off analysis, a calculation or the basis for a decision;
• the process still changes from week to week and you are still working out what it should look like.

The last point deserves attention. An application built on a procedure that has not yet settled will be reworked repeatedly. In that case it makes more sense to let the process mature in a spreadsheet and to note down, as you go, what gets in the way when you work with it.

What the next step can look like

Moving away from a spreadsheet does not have to mean a large project. The options can be ordered from a small change to a more extensive one.

Tidy data in one place. Often it already helps when the file stops circulating in attachments. A workbook stored in SharePoint or OneDrive can be edited by several people at the same time in Excel for Microsoft 365 and Excel for the web. Version history there shows when the file was changed and who changed it, and lets you return to an earlier version. This goes together with an agreement on what each column means and who is responsible for it. This step helps with the first signal and partly with the sixth; the others remain.

A simple application on top of the same data. People no longer overwrite rows in a spreadsheet. They fill in a form that asks only for what is needed. Every record has a status and a responsible person, approval has a fixed procedure and a history, and everyone sees only what they are meant to see. Power Apps and Power Automate, for example, are suited to records and approval workflows of this kind.

A custom application connected to other systems. It makes sense where the process spans several departments and data is to be exchanged with ERP, accounting or a production system without manual retyping. It can be built in Power Platform or as a standalone web application. We describe how these two routes differ on the page about app development.

A bigger step is not automatically better. The right one is the step that removes the signals that really trouble you, and that you are able to introduce and to run. Comparing the options for a specific process is also one of the topics of a consultation.

How to start

Do not start by choosing a technology. Start with one process.

1. Choose the process in which you recognised more signals than in the others. It is usually the one people complain about and where the customer sees the errors too.
2. Describe how it runs today. Who starts it, what data is recorded and where, who decides, where things wait and where data is retyped. One page of text or a simple diagram is enough. Write down how the process really runs, not how it should run.
3. Name what should be different after the change. For example: the order status is visible without a phone call, an approval can be traced, data is entered once.
4. Only then decide on the solution. The description usually makes it clear whether tidying up the data is enough or whether the process needs an application.

A description like this will be useful either way, whether you adjust the process yourself or brief a supplier. And if it shows that a spreadsheet is enough for now, that is a good result too.