One Spreadsheet, Three Jobs: The Cost of Using Excel as Form, Database and Workflow

The tolerated pain: the spreadsheet that does everything

Most businesses have at least one spreadsheet that is doing three jobs at once. Staff type new requests, orders, leads or incidents straight into it, so it acts as a form. It holds every record the business has on the subject, so it acts as a database. And colour codes, status columns and filters tell people what to do next, so it acts as a workflow system.

It usually started well. Someone capable built a tracker that solved a real problem quickly and cheaply. Over time, columns were added, formulas grew, tabs multiplied and more people were given access. Now the business depends on it, and it depends on the person who understands it.

Mellorca has described how a spreadsheet becomes a business-critical system and why important processes end up running in Excel. This article focuses on the specific cost of asking one file to be the capture screen, the record store and the process engine at the same time, and on separating those jobs.

Why businesses tolerate it

• Everyone already has it. Spreadsheets need no purchase, no project and no training.
• It is flexible. Anyone can add a column or change a rule today, without asking IT or a vendor.
• It mostly works. Errors are found and fixed quietly, so the overall error rate is never measured.
• Replacing it sounds expensive. Owners assume the alternative is a large system implementation.
• The builder is still there. As long as the person who built it is available, problems are manageable.

Operational symptoms

• As a form: people type into whichever row is free, overwrite each other, skip columns, use different spellings and formats for the same thing, and paste values over formulas.
• As a database: the same customer or item appears several times, there is no reliable unique reference, filters hide rows that people forget about, and copies of the file circulate with different contents.
• As a workflow: status is shown by colour or a free-text column, nobody is notified when something changes, and the next person only acts when they happen to open the file.
• Only one or two people dare to change formulas or structure, and they spend part of every week fixing the file.
• Questions such as who changed this, and when, are hard to answer.
• Reports are built by copying data out into yet another spreadsheet.

How the pain becomes money

• Error and rework cost. Overwritten rows, broken formulas and inconsistent entries cause wrong orders, missed follow-ups and incorrect invoices that must be found and corrected.
• Maintenance labour cost. The spreadsheet's owner spends regular hours repairing, cleaning and extending it, often at a senior rate.
• Delay cost. Without notifications, work waits until someone checks the file.
• Key-person risk. If the builder leaves, the business may be unable to change or even trust the file.
• Risk exposure. Personal information in a widely shared file with no item-level permissions or reliable change history is hard to protect and hard to audit.
• Scaling cost. As volume and users grow, the file slows down, conflicts multiply, and the business adds people to manage the spreadsheet rather than the work.

Where spreadsheets reach their limits

Excel is a powerful tool, and its published capacity is large: Microsoft's specification lists 1,048,576 rows by 16,384 columns per worksheet. Size is rarely the first problem. The limits that bite are about shared, structured use. The same Microsoft specification notes that Excel tables cannot be used in workbooks that have the legacy shared workbook setting turned on, that undo is limited to 100 actions, and that the full file path and name cannot exceed 218 characters. None of these is a reason to abandon spreadsheets. They are a reminder that the tool was designed for analysis and modelling, not to be a multi-user system of record with a built-in process.

A transparent cost model

The figures below are illustrative assumptions for a business running its job or order tracking in one shared spreadsheet. Replace them with your own.

Total: about 844 hours a year. At an illustrative blended loaded cost of R280 an hour, that is roughly R236,000 a year, before counting the cost of the errors that reach customers or the disruption if the file is corrupted or its builder leaves.

Illustrative example. An Eastern Cape agricultural supplier tracked customer orders in one workbook. Sales staff typed new orders into it, the warehouse filtered it to see what to pick, and accounts used it to decide what to invoice. A sales representative sorted one column without the rest of the sheet, misaligning customers and quantities for a week of orders before the warehouse noticed. The business moved order capture to a simple form, stored orders in a structured list with fixed columns and change history, and gave the warehouse and accounts filtered views. The spreadsheet remained, but only for analysis.

When it becomes commercially urgent

• an error in the spreadsheet has already reached a customer, a supplier or the bank;
• the person who built it is leaving, or is the only one who can fix it;
• more than a handful of people edit the file every day;
• personal or financial information is held in it and shared widely;
• the business is growing and the file is becoming slow, conflicted or unreliable.

What better looks like

The fix is to give each job its own appropriate tool, while keeping the spreadsheet for what it does best.

A form for capture

Capture new items through a form with required fields, fixed choices and validation, so people cannot overwrite existing records or skip essential information.

A structured list or database for records

Store the records somewhere designed for shared use. Microsoft describes Lists in Microsoft 365 as supporting typed columns such as dates, people, choices and currency, multiple views that sort, filter and group data, version history for each item, permissions down to individual items, and forms for data entry. For many small businesses, a structured list like this is enough. Larger or more complex processes may justify a proper line-of-business system. Mellorca's guide on deciding what should be the system of record helps with that choice.

Automation for the workflow

Let events, not people checking, drive the next step. Microsoft's documentation for the SharePoint connector in Power Automate lists triggers such as When an item is created and When an item is created or modified, which can notify the next person, start an approval or update another system when a record changes.

The spreadsheet for analysis

Keep Excel for analysis, modelling and reporting, connected to the structured data rather than holding it.

Practical steps

1. List the spreadsheets the business depends on and, for each, note whether it is acting as a form, a database, a workflow or all three.
2. Pick the one where errors or dependence on one person are most costly.
3. Agree the fields, unique reference and owner for each record type.
4. Move capture to a form and storage to a structured list or system, keeping a read-only export for reporting.
5. Add notifications for the key status changes.
6. Document the new process so it does not depend on the original builder.

Mellorca's systems implementation and integration service helps businesses move critical spreadsheets into structured, supported tools without disrupting daily work.

Bottom line

A spreadsheet that is simultaneously form, database and workflow is cheap to start and expensive to run. The cost shows up as rework, maintenance hours, waiting and dependence on one person, and the risk grows with every new user. Separating capture, storage and process, and leaving the spreadsheet to do analysis, keeps the flexibility that made it useful while removing most of the fragility.

Sources and further reading

• Excel specifications and limits - Microsoft Support (last verified 10 October 2026)
• What is a list in Microsoft 365? - Microsoft Support (last verified 10 October 2026)
• Microsoft SharePoint Connector for Power Automate (last verified 10 October 2026)

Related Mellorca reading

• The Human Dispatcher: The Cost of Manually Routing Every Incoming Request
• When Every Decision Waits for One Person: The Cost of a Decision Bottleneck
• When Your Experts Become the Help Desk: The Cost of Routine Requests