Somewhere in your company there is a spreadsheet doing a job your real software was supposed to do. It might calculate commissions. It might track which jobs are ready to invoice. It might be the actual source of truth for pricing, quietly overriding the catalog. One person built it, one person maintains it, and half your management team does not know it exists.
We call these shadow spreadsheets. They are close cousins of shadow IT, the unapproved apps and services that show up inside businesses, but sneakier, because a spreadsheet does not look like a system. It looks like a file. Nobody thinks to inventory it, back it up separately, or ask what happens if it breaks. Meanwhile it runs a process the business depends on.
Why They Appear
Here is the part most articles get wrong. Shadow spreadsheets are not a sign of a sloppy team. They are a sign of a gap between what your software does and what your business needs, and of an employee who cared enough to close it themselves.
The sequence is always the same. Someone needs a report the system does not produce. The vendor quotes a five-figure customization or a six-month roadmap. So on a Thursday afternoon, a competent person exports the data, builds the thing in an hour, and solves the problem. Nobody asked permission because nobody broke a rule. That file then becomes load-bearing one dependency at a time, until three years later the whole department opens it every morning.
That is a rational response to a real constraint. It also creates a system nobody manages, which is the same underlying dynamic we described in our post on shadow IT and the risk hiding inside your own organization.
The Risk Profile of a Spreadsheet That Runs a Process
A file used for analysis is fine. A file a process depends on is something else. Here is what changes.
- One author, no reviewer. Nobody checked the formulas. Nobody checked them last year either. Mistakes here are quiet, because a wrong number looks exactly like a right number.
- No validation. Real software refuses to accept a date in a price field. A spreadsheet accepts anything you type and calculates confidently around it.
- Formulas nobody understands. Especially after the author has revised them for six years. The knowledge lives in one head, which is a problem in its own right.
- Living on a desktop. If the file sits on one machine rather than in company storage, it is outside whatever backup you pay for, and it disappears with the laptop.
- Version sprawl. Emailed copies mean three people work from three versions and nobody knows which is current.
- Sensitive data with no access control. Shadow spreadsheets frequently hold customer records, payroll figures, or account numbers, shared with far more people than need them.
That last one has a compliance dimension. The Federal Trade Commission’s guide to protecting personal information tells businesses to “scale down access to data” and follow the principle of least privilege, meaning “each employee should have access only to those resources needed to do their particular job.” A file on an open share that everyone can read does not meet that standard, however useful it is.
How to Find Them
You will not find shadow spreadsheets by scanning file servers. You will get ten thousand results and no idea which ones matter. Ask people instead, and ask a better question than “what spreadsheets do you use.”
- “What do you open first thing every morning?” Habitual daily use is the strongest signal that a file is part of a process rather than a one-off analysis.
- “What would you have to do by hand if this file were gone tomorrow?” The answer tells you both the dependency and the fallback, if there is one.
- “Who else knows how this works?” If the answer is nobody, you have found a single point of knowledge alongside a single point of data.
- “Where does the data come from and where does it go?” Files fed by a manual export and feeding a customer invoice sit directly in your revenue path.
- “Does it have customer or employee information in it?” This determines how urgently the access question needs answering.
This is an inventory exercise, and inventory is the foundation of every security framework for a reason. CISA’s cross-sector cybersecurity performance goals begin with asset inventory and include an approval process that “requires approval before new hardware, firmware, or software/software version is installed.” Most businesses apply that thinking to applications and never to the files quietly acting like applications.
Decide: Formalize, Support, or Retire
Once you have the list, sort it. Not everything needs to become software, and the instinct to replace every spreadsheet with a proper system is how you spend a lot of money slowly.
- Formalize the few that run the business. If it touches revenue, payroll, or customer data, it deserves a real home. Sometimes that means configuring the feature you already own but never turned on. Sometimes it means a modest custom tool. Rarely does it require replacing the whole platform.
- Support the ones that work fine as spreadsheets. Move the file into managed company storage so it is backed up and versioned, set permissions so only the right people can edit it, protect the formula cells, and write half a page on how it works. A two-hour fix removes most of the risk.
- Retire what nobody needs. Many were built for a situation that ended two years ago and are still updated out of habit. Ask who reads the output. Sometimes nobody does.
- Give every survivor a second trained person. Whatever you keep, somebody besides the author should know how to run it.
Ready.gov’s business continuity plan template makes a related point for any process you rely on, instructing organizations to “document all forms and resource requirements for all manual workarounds.” A shadow spreadsheet is a manual workaround that got a promotion. It deserves the same documentation as anything else you cannot operate without.
Thank the Person Who Built It
This matters more than the technical part, and it is where most cleanups go wrong. If the conversation feels like an audit, people hide their files, and you end up with the same risk and less visibility.
The framing that works is straightforward and true. This person found a gap and solved it without being asked, using tools they already had. That is initiative. We are looking at it now not because they did something wrong, but because the business came to depend on their solution, and anything the business depends on deserves backup, documentation, and a second person who can run it. Say that out loud. Then fix the file with them, not around them.
There is a practical payoff too. The person who built it knows exactly what the official system fails to do, which makes them your best source for what to buy or configure next. That connects to the argument we made about valuing recovered time over the cheapest line item.
The Bottom Line
Shadow spreadsheets are not a discipline failure. They are a map of where your software falls short, drawn by the people closest to the work. Find them by asking what people open every morning. Sort them into formalize, support, and retire. Move the survivors into managed storage with real permissions, write down how they work, and make sure two people can run each one. Then thank whoever built them.
If you would like help finding the spreadsheets quietly running your operation, deciding which deserve to become real systems, and getting the rest into backed-up storage with sensible access, that is the kind of project we take on. We work with small and mid-sized businesses throughout Denton County. Contact us today.
Sources:
Comments are closed