14 min read
Excel is not the problem.
In many complex asset organizations, spreadsheets exist because they solve real problems quickly. They are easy to create, easy to share, and easy to adapt when the official system does not quite match the way work actually happens.
That is why Excel still runs so many critical operations. But the risk begins when spreadsheets stop being supporting tools and become the place where operational work is controlled.
When maintenance tasks, asset deployment status, quality checks, evidence, approvals, handovers, and responsibilities are managed through spreadsheets, the organization is no longer just using Excel. It is depending on Excel as an execution system.
And Excel was never designed for that. A spreadsheet can track work, but it cannot reliably govern work.
When spreadsheets become workflows
A spreadsheet-based workflow is an operational process where tasks, updates, asset records, approvals, or handovers are managed through spreadsheets instead of a structured workflow system.
In practice, this can look like a shared Excel file tracking maintenance tasks, a deployment plan updated by several departments, spare parts or support equipment tracked in separate worksheets, or quality checks recorded manually and linked to evidence stored somewhere else.
It can also be more informal than that. A name in a column becomes task ownership. A color code becomes priority. A comment becomes an approval note. A SharePoint link becomes evidence. An email thread becomes context.
At first, this setup can feel efficient. Everyone knows how to open the file. Changes can be made quickly. No one has to wait for IT, procurement, or a long system implementation. But as the workflow becomes more critical, the same flexibility that made Excel useful starts to create risk.
The problem is scale, not the spreadsheet itself
A small team using a spreadsheet to organize simple work is usually not the issue.
The problem appears when the spreadsheet becomes part of a larger operational process involving several teams, assets, sites, approvals, data dependencies, and compliance requirements.
The more people and dependencies involved, the more dangerous it becomes to rely on a file as the operational backbone.
Why spreadsheet risk is easy to underestimate
Spreadsheet risk rarely appears all at once. It builds slowly.
A team starts with one file because it needs a fast way to track work. Then another department adds a column. Someone adds a tab for open actions. Someone else adds color coding, formulas, comments, or links to evidence. A manager asks for a weekly report, so the file becomes the source for status updates.
Over time, the spreadsheet becomes part of the workflow itself.
By then, removing it feels difficult. It may not be officially recognized as a system, but everyone depends on it. It contains current tasks, old decisions, workarounds, assumptions, and informal knowledge. It becomes the place people go to understand what is happening.
This is why spreadsheets often create a false sense of control.
Raluca, a Delivery Lead at Empact who works on projects helping some of the world’s largest defense OEMs (Original Equipment Manufacturer) replace spreadsheet-driven workflows, sees this challenge regularly in operational environments where critical work still depends on Excel files.
As she explains:
“Excel feels safe because people know it and feel in control. But in reality, it can be very easy to share the wrong file, enter the wrong data, break the structure, or lose accountability when too many people depend on the same sheet.”
That is the hidden risk. The organization sees the spreadsheet, but not always the fragile manual process behind it.
The hidden risks of spreadsheet-based workflows
Spreadsheet dependency creates many small weaknesses that can become serious operational risks over time. The most important risks are not only about errors in cells. They are about traceability, accountability, visibility, security, and the organization’s ability to trust its own data.
1. Weak traceability
Traceability is not just about knowing that something happened. It is about knowing who did it, when it happened, why it happened, what data it was based on, what asset it affected, and whether the correct process was followed. Spreadsheets struggle with this because they are built for editing, not controlled execution.
A cell can be changed. A row can be deleted. A formula can be overwritten. Evidence can be stored somewhere else. A comment can be removed. A status can be updated without the full context of what changed. Even when version history exists, it is not the same as operational traceability.
Version history is not an audit trail
Version history may show that a file changed. It does not automatically create a reliable audit trail across tasks, assets, roles, validations, approvals, and evidence.
For maintenance, assembly, and sustainment workflows, this matters. A missing trace can create uncertainty around whether an action was completed correctly, whether a part was inspected, whether an asset was configured as expected, or whether a decision was based on the right data.
Traceability should not depend on whether someone remembered to update the right cell.
2. Human error and fragile data integrity
Every manual workflow depends on people doing the right thing, in the right place, in the right format, every time. That is a fragile foundation for critical operations.
In spreadsheet-based workflows, small errors can have large consequences. A part number is mistyped. A date is entered in the wrong format. A row is sorted incorrectly. A formula stops working. A filter hides the relevant task. A status is updated in one version of the file but not another.
None of these mistakes are unusual. They are normal human errors. The problem is that spreadsheet workflows often make those errors hard to detect.
In a structured workflow, the system can guide the user, enforce required fields, validate inputs, restrict certain actions, and connect the update to a specific task or asset. In a spreadsheet, the structure is easier to bypass.
3. Workflows become dependent on a few experienced people
Spreadsheet-based workflows often look more documented than they really are.
The file may contain the data, but the real knowledge sits with the people who know how to interpret it. They know which columns matter, which old tabs can be ignored, which formula should not be touched, which SharePoint folder contains the real evidence, and which status labels are actually used by the team.
That works until those people are unavailable. They may leave the organization, retire, change role, go on holiday, or simply become too busy to support everyone else. When that happens, the workflow becomes harder to understand, harder to trust, and harder to improve.
The file may remain, but the context disappears
This is especially risky in long-lifecycle asset environments. Complex assets can remain in operation for years or decades. The people who created the original spreadsheet may not be the same people maintaining the asset later.
If lifecycle knowledge only lives in a file structure that a few experienced people understand, it is not really organizational knowledge. It is local knowledge with a spreadsheet attached.
4. Version control issues
In a low-risk context, version confusion is annoying, but in critical operations it is dangerous.
If several teams are using different versions of the same spreadsheet, they may also be working from different versions of reality. One file says a task is complete. Another says it is pending. One version includes a risk update. Another does not. One person has the latest asset status, while someone else is working from an exported copy.
This is especially common when spreadsheets move through email, shared drives, SharePoint folders, downloads, and offline edits.
The familiar naming pattern says it all:
Final.xlsx
Final_updated.xlsx
Final_updated_v3.xlsx
Final_REAL.xlsx
In operational workflows, the issue is not the file name. It is the absence of a controlled process.
Which version is true?
The key questions are simple:
Which version is authoritative?
Who can change it?
Who approved the update?
Who was notified?
Which downstream process depends on it?
If those questions cannot be answered quickly, version control has become an operational risk. Spreadsheets often create multiple versions of the truth, maintained through manual effort.
5. Poor accountability
A name in a spreadsheet is not the same as ownership.
This is one of the most common weaknesses in spreadsheet-based workflows. A person may be listed next to a task, but that does not mean the task has been assigned, accepted, tracked, reminded, escalated, or handed over properly.
In practice, accountability becomes informal. Someone has to check the file. Someone has to remember the deadline. Someone has to notice that a task is overdue. Someone has to chase the responsible person. Someone has to know what happens next.
If that person is absent, busy, retiring, or transferred to another project, the workflow weakens.
As Raluca explains:
“When the workflow lives in one massive spreadsheet, people often struggle to see what is actually assigned to them and when they need to act. There are no real reminders, and even filtering by name can create problems for someone else using the same file.”
This is where spreadsheet dependency becomes more than an efficiency issue. It becomes a governance issue.
Accountability should not depend on manual follow-up
A controlled workflow should make ownership visible. It should show what is assigned, what is overdue, what depends on what, and what has changed. It should not require someone to manually filter a spreadsheet and hope the result is still accurate.
6. Security and access control gaps
Spreadsheets often feel safe because they are familiar, but familiarity is not the same as security. When sensitive operational data is stored in files, access control is often managed at the folder, email, or document level. That may be enough for simple collaboration, but it is rarely enough for complex workflows involving different roles, classifications, suppliers, operators, OEMs, and internal teams.
The risk goes in two directions. First, data may be shared too broadly. A file can be forwarded, downloaded, copied, or stored locally. People may have access to more information than they need because the workflow is not structured around roles.
Second, data may not be collected at all. In defense environments, security concerns can lead teams to avoid recording operational data because they are worried about where it might go or who might access it.
Both outcomes are damaging. If data is overshared, the organization loses control. If data is not captured, the organization loses insight.
Secure workflows need more than secure folders
Security is not only about where a file is stored. It is also about what each user can see, change, approve, export, and share. A spreadsheet does not naturally enforce that level of operational control.
For complex asset organizations, especially in defense and regulated environments, this creates a difficult tradeoff: teams either restrict access so much that collaboration becomes slow, or they open access so broadly that control becomes weak. Neither is ideal.
7. Operational visibility breaks down
Operational visibility cannot be created after the fact from scattered updates. Yet this is often what spreadsheet-based workflows require. Teams do the work in one place, update a file somewhere else, send context through email, store evidence in folders, and then manually consolidate the status into reports.
By the time leadership sees the overview, the real situation may have already changed. This creates a gap between operational reality and management visibility.
A maintenance planner may not know which asset is blocked by a missing part. A sustainment team may not know which tasks are overdue. A program manager may not see that the same bottleneck appears across multiple projects. A customer support team may not have reliable status on what has been done, what is waiting, and who owns the next step.
More data does not automatically create better insight. For complex asset organizations, this matters because readiness, maintenance, assembly, and sustainment depend on timing. A delayed update is not just an information issue. It can become a planning issue, a customer issue, a compliance issue, or an availability issue. Read more about this topic in our article about operational visibility.
8. Advanced maintenance becomes impossible to scale
Many organizations want to move toward predictive maintenance, digital twins, automated reporting, and better lifecycle analytics. But those ambitions depend on the quality of the underlying data. You cannot build predictive maintenance on inconsistent manual records.
To predict failures, optimize spare parts, or understand how asset usage affects maintenance, organizations need structured, trusted, time-relevant data. They need to connect asset configuration, usage history, maintenance actions, parts, inspections, failures, and operating conditions.
Spreadsheet-based workflows rarely provide this foundation. They may contain useful information, but it is often incomplete, inconsistent, difficult to validate, and disconnected from the systems where it could create value.
Jacob, one of Empact’s founders, connects this directly to the larger digital maturity challenge in complex asset organizations:
“When workflows are built around paper, spreadsheets, and disconnected systems, you lose the digital trail. And without a digital trail, you cannot build the foundation for digital twins, smart maintenance, or lifecycle visibility.”
This is where the spreadsheet problem becomes a lifecycle problem. Poor data capture today limits the decisions that can be made tomorrow.
The operational consequences are bigger than administration
It is tempting to think of spreadsheet risk as an administrative problem, it is not.
In complex asset environments, workflow quality affects operational quality. If tasks are missed, evidence is incomplete, ownership is unclear, or maintenance history cannot be trusted, the consequences can move far beyond office efficiency.
Maintenance risk becomes readiness risk
When maintenance workflows are fragmented, organizations may struggle to understand what has been done, what still needs attention, which assets are available, and which problems are likely to repeat. That can affect readiness, delivery performance, customer confidence, and long-term lifecycle value.
Spreadsheet-based workflows are not the sole cause of those problems. But they can contribute to the conditions that make them harder to see and harder to solve. If an organization cannot trust its maintenance data, it cannot confidently prioritize work.
If it cannot see overdue actions, it cannot manage risk early.
If it cannot trace decisions and evidence, it cannot learn reliably.
If it cannot connect operational data across teams, it cannot improve the workflow at scale.
The hidden risk is not that a spreadsheet might contain an error. The deeper risk is that the organization may not know which work is controlled, which data can be trusted, and which decisions are being made from incomplete operational reality.
What good looks like instead
The answer is not to ban spreadsheets. Excel still has a place in analysis, planning, calculations, and local problem-solving. The goal is not to remove every spreadsheet from the organization. The goal is to stop using spreadsheets as the control layer for critical execution.
From tracking work to governing work
A safer operational workflow should provide clear task ownership, role-based access, automatic traceability, standardized data capture, controlled approvals, audit-ready histories, reminders, escalation, and reliable status visibility.
It should also connect to existing ERP, PLM, MES, CMMS, logistics, or asset management systems where relevant.
Existing enterprise systems still have an important role. ERP, PLM, MES, and CMMS systems are often essential systems of record. But the real operational workflow often happens between those systems, across teams, assets, sites, suppliers, and frontline users. That is where fragmentation appears.
The goal is structured execution
The strongest organizations do not simply digitize the spreadsheet. They redesign the workflow so that execution, data capture, accountability, and traceability happen together.
This does not mean making the process heavier. In many cases, it means making it easier for frontline teams to do the right thing without relying on manual follow-up, copied data, or local file logic. If you want to move away from fragmented systems, read this article on the subject.
Spreadsheet dependency is the real risk
Spreadsheets are useful, but dependency on them is dangerous.
There is a difference between using Excel to support work and relying on Excel to govern work. The first can be practical. The second creates hidden operational risk.
For complex asset organizations, the question is not whether Excel should exist. It is whether the organization can still answer the questions that matter when work becomes critical:
Who owns this task?
Which asset does it affect?
What changed?
Who approved it?
Where is the evidence?
Which version is correct?
Can we trust the data?
Can we use it again?
Can we learn from it?
If the answer depends on finding the right file, asking the right person, or manually reconstructing the workflow, the organization does not have control. It has a spreadsheet.
And that is not enough for critical operations.
FAQ
The main risks are weak traceability, human error, version confusion, poor accountability, limited access control, fragmented data, and unreliable operational visibility.
Maintenance workflows depend on accurate asset history, task ownership, parts data, approvals, and evidence. When this information is managed manually in spreadsheets, it becomes harder to trust, audit, and use for future planning or predictive maintenance.
No. Excel is useful for analysis and local calculations. The risk appears when Excel becomes the primary system for assigning work, controlling execution, storing evidence, and maintaining operational records.
They make traceability dependent on manual updates and user discipline. A controlled workflow should automatically capture who performed an action, when it happened, what changed, and which asset, part, or task it relates to.