A departmental Excel workbook can gradually become the place people rely on to know what is true right now.
It may begin as an order tracker, production plan, quotation log, approval list or project register. Over time, staff update it every day, managers use it to make decisions, and other systems or reports depend on its contents. No one may have formally appointed it as the authoritative record, but in practice the department treats it that way.
That is when Excel has become an unofficial system of record.
Excel remains valuable for modelling, forecasting, ad-hoc analysis and flexible calculations. The governance issue begins when a workbook is no longer just analysing information. It is being used to create, change, approve and communicate the operational record.
What is an unofficial system of record?
A system of record is the place the business treats as authoritative for a particular process or set of data.
An unofficial system of record develops when a workbook fills that role without clear organisational ownership or controls around how the record is maintained. The spreadsheet may be familiar and useful, but key questions remain unanswered:
- Who is accountable for the accuracy of the record?
- Which version is authoritative?
- Who can change operational data, and under what circumstances?
- How are approval decisions recorded?
- What happens when two people need to update the same item?
- How does a new employee know the correct process?
- When should the workbook stop being the live record?
The problem is not that the workbook exists. The problem is that the department depends on it as a business system while managing it as a document.
How a departmental spreadsheet becomes authoritative
The transition is usually gradual.
Consider an operations workbook that starts with an export of customer orders. A coordinator adds delivery dates and notes. Sales staff send amendments by email. A manager updates priorities. Finance checks selected rows before invoicing. During meetings, everyone refers to the workbook to understand the current position.
The workbook has become more than a report. It now holds the department's working truth about orders, priorities and decisions.
This pattern can appear in many operational workflows:
- Job and project trackers
- Production planning sheets
- Stock and purchasing registers
- Quotation and revision logs
- Maintenance schedules
- Inspection and compliance records
- Approval lists
- Recurring operational reports
A workbook can be useful in each of these settings. The governance concern arises when staff must consult or update it to move work forward.
A practical test: if people need a particular workbook to know what is approved, what is current, who is responsible or what should happen next, it is functioning as an operational system.
The difference between a spreadsheet and an operational record
The file format is not the deciding factor. The role the workbook plays is what matters.
| Use of Excel | Typical purpose | Governance need |
|---|---|---|
| Analytical model | Exploring scenarios, forecasts or assumptions | Clear inputs, ownership and review of important calculations |
| Team tracker | Recording routine work and current status | Defined ownership, consistent updates and an agreed authoritative version |
| Operational workflow | Managing hand-offs, approvals, actions and outputs | Controlled access, visible responsibilities, structured workflow and clear record authority |
A forecasting model can remain in Excel because its value comes from flexibility and analysis. A workflow that determines whether an order can proceed, a quote is approved or an inspection is complete needs a clearer operational boundary.
For a broader explanation of when a workbook supports a business-critical process, see What Is a Business-Critical Operational Spreadsheet?.
Signs that Excel has become an unofficial system of record
Look at how the workbook is used, rather than how many formulas or tabs it contains.
Several of these signs together usually indicate that the spreadsheet has moved beyond personal or exploratory use:
- Staff enter new operational information into it as part of their normal work.
- Managers rely on its latest state to make allocation, scheduling, delivery, approval or invoicing decisions.
- A status column, colour, comment or email reply determines whether work can continue.
- Different people update separate parts of the same process.
- The workbook is passed between departments as the current record.
- A department relies on one person to explain the rules, exceptions or correct sequence of updates.
- Users create copies because they are unsure which version is live.
- A macro, button or hidden tab performs an important operational step.
- People discuss changes to the workbook as though they are changes to the process itself.
These are primarily ownership and authority signals. They show that the workbook is carrying process responsibility, whether or not it was designed to do so.
The governance questions to resolve first
Before deciding whether to keep Excel, strengthen controls or replace the workflow, establish what the department needs from its authoritative record.
1. Who owns the process?
A named business owner should be accountable for how the process works, what the record means and which changes are permitted. This is different from identifying the person who built the workbook or the person who happens to update it most often.
The owner should be able to answer:
- What business activity does this record support?
- Which information is authoritative here?
- Which teams rely on it?
- Who can approve changes to the process?
- What should happen if the workbook is unavailable or unclear?
2. Who can change authoritative data?
File access alone is not the same as operational authority.
For example, a coordinator may need to update a delivery date, while only a manager should approve an exception. A finance user may need to view a status but should not be able to alter the operational details behind it.
When these distinctions exist, they should be reflected in the process itself. If every user can edit any relevant cell, the workbook may not match the authority structure the business expects.
3. How are decisions evidenced?
Approval often develops informally around a spreadsheet. It may be represented by initials in a column, a colour change, an email response or a comment added after a meeting.
That can be workable for a simple, low-consequence process. It becomes harder to govern when people need to understand:
- What was approved
- Who approved it
- What information they reviewed
- Whether the decision was later changed
- What action followed
The goal is not to create bureaucracy for its own sake. It is to ensure that a business decision is visible in the record that drives the work.
4. Where is the authoritative boundary?
Departments often have more than one version of the same information: an export from another system, a live workbook, emailed copies and reports prepared for meetings.
A controlled process needs a clear answer to a simple question: where should someone look for the current record?
Without that boundary, users can make legitimate updates in different places and still create conflicting versions of the truth.
When stronger Excel governance may be enough
Not every operational spreadsheet needs immediate replacement.
Excel controls may be a reasonable interim or longer-term option where the workbook supports a stable process, the users are limited, the business can define a single live location and the required authority is straightforward.
A sensible governance baseline includes:
- A named business owner
- A documented purpose and scope
- An agreed authoritative file location
- Defined user responsibilities
- Clear rules for changing formulas, structure and process logic
- A review routine for access and process changes
- Documented cover arrangements for routine operation
- A decision about when the workbook should be reviewed again
This approach can reduce ambiguity. It does not automatically make a workbook the best place to run a workflow with multiple roles, approvals, exceptions and recurring operational actions.
When a controlled application becomes the better fit
A managed custom web application may be a better fit when the department needs the process itself, not merely the file, to be controlled.
For example, an application can be designed around the workflow so that users see the tasks, fields and actions relevant to their role. It can provide a central record with defined states, guided data entry and approval steps appropriate to the process.
This is particularly relevant where the workbook contains distinctive business rules, calculations, terminology or exceptions that are important to the way the company operates.
The important distinction is not “Excel versus software”. It is whether the current process needs a controlled operational record with clearer ownership and authority.
A managed application can help establish that boundary by moving the live workflow out of a departmental file and into a shared operational process. Excel can still remain useful for analysis, exports and exploratory work where its flexibility adds value.
Explore managed options for replacing an operational Excel workflow.
Moving from an unofficial to a controlled record
Avoid treating replacement as a worksheet conversion exercise. The priority is to make the process rules explicit before recreating them elsewhere.
Keep the transition focused on the governance questions that matter:
- Define the live record. Decide which system will become authoritative for the workflow.
- Identify roles and authority. Specify who creates, updates, reviews and approves each type of record.
- Make workflow states explicit. Replace informal indicators with clear statuses and next actions.
- Separate operational records from analysis. Retain Excel where it is useful for modelling, while preventing it from becoming a competing live record.
- Retire ambiguity. Once a controlled record is in use, make clear when the previous workbook is reference-only rather than operationally live.
The detailed work of scope, data preparation, testing and launch depends on the workflow. For a step-by-step replacement guide, read From Excel to Web App: 7 Steps for Replacing a Business Spreadsheet.
A useful next step for departmental leaders
If a departmental workbook has become the place where the business decides what is current, approved or actionable, start by clarifying its ownership and authority.
You do not need to treat every spreadsheet as a replacement project. The aim is to distinguish between a flexible analytical tool and an operational record that needs more deliberate control.
Spreadsheet Upgrade helps UK SMEs assess whether a business-critical Excel workflow is suitable for a managed custom web application.
Start a Free Fit Check
Discuss the workbook, the people who rely on it and the operational decisions it supports.