The 7 Signs Your Spreadsheet Has Become a Database (And Is Failing at It)

Somewhere on your shared drive there is a file called Client_Tracker_FINAL_v7_USE_THIS_ONE. Next to it sits Client_Tracker_FINAL_v7_USE_THIS_ONE (2), and nobody is sure which one the finance team is reading from. You open it, scroll right past column BZ, and find a tab called “OLD - DO NOT DELETE” that three formulas still depend on.

Congratulations. You are running a database. It just happens to be a very bad one.

That isn’t an insult to spreadsheets. They are brilliant at what they were built for: calculating, modelling and exploring numbers. The trouble starts when a sheet stops being a calculation and becomes the system of record for a business process. Here are seven signs that has already happened to you.

1. Your filenames carry version history

If the only way to know which copy is current is to read the filename, your file is doing a job a proper system does automatically. Real tools keep one live record and a history of changes behind it. You see who changed what, and when, without anyone emailing round “v8 attached, ignore v7”.

The test: could a new hire find the current version in under a minute without asking someone? If not, tick this box.

2. Colour is carrying meaning

Green rows are “done”. Yellow means “waiting on client”. Orange means “waiting on us”, unless it is a lighter orange, which means Priya is looking at it. Red is either “urgent” or “lost”, depending on who formatted it.

Colour coding is a sign that you need a status field with defined values and the sheet can’t give you one that sticks. Colours can’t be filtered reliably, don’t survive copy-paste between files, and mean nothing to anyone colour-blind or reading the data in a report. For more on fixing this properly, see Replacing the “Status” Column: Designing Real Workflows with States and Transitions.

3. There’s a tab nobody dares delete

Every long-lived workbook grows one. It might be called “Lookup”, “Backend” or simply “Sheet3”. Nobody remembers who built it. Several columns elsewhere reference it, so deleting it would break something, but nobody knows what.

This is what engineers call a hidden dependency: a piece of the system that other pieces rely on without anyone being able to see the connection. In a real application those connections are explicit. In a sheet, they’re buried inside cell formulas and discovered only when something breaks.

4. The same customer appears four different ways

“Acme Ltd”, “ACME Limited”, “Acme” and “acme ltd " (with a trailing space) are, to your sheet, four different customers. So when you total revenue by client, Acme looks smaller than it is and your top-ten list is wrong.

A database solves this with something called a unique identifier: every customer is a single record with its own ID, and everything else points to that record rather than retyping the name. If your team spends time “cleaning up names” before every monthly report, your sheet is failing at one of a database’s most basic jobs.

5. Two people can’t safely edit at once

Maybe you’ve moved to a cloud spreadsheet tool so simultaneous editing technically works. But in practice, someone sorts column C while someone else is typing in row 140, and a phone number lands next to the wrong company. Or someone filters the view, forgets, and the next person thinks half the records have vanished.

Databases handle concurrent edits record by record, so your change to one client can’t scramble someone else’s. If your team has informal rules like “don’t sort the main tab” or “only Marcus edits on Fridays”, you’re managing a technical limitation with social workarounds.

6. One person is the only one who understands it

Every team has a sheet whisperer. They built the macros, they know why column AF is hidden, and they’re the only one who can fix it when the totals go strange. When they’re on holiday, the process slows down. When they leave, it may stop entirely.

This is the riskiest sign on the list, because it’s invisible until the day it isn’t. We cover the cost of this in more detail in The Hidden Cost of “It’s Just a Spreadsheet”.

7. You’ve started building forms, rules and reminders around it

People submit requests through a form that dumps rows into the sheet. Someone has written a script that emails the team when a cell changes. There’s a validation dropdown on column D that half the rows predate. There’s a weekly calendar reminder to “check the tracker for overdue items”.

At this point you’ve assembled an application out of spare parts. Forms, business rules, notifications and scheduled checks are exactly what internal tools provide natively. Bolting them onto a spreadsheet works for a while, then becomes the thing you spend your Tuesdays maintaining.

Score yourself

Count how many of the seven apply to your most important sheet.

A high score doesn’t mean you did anything wrong. Most of these sheets started as a sensible quick fix that grew because it worked. That’s a success story with a maintenance problem.

It also doesn’t mean every spreadsheet must go. Some genuinely belong where they are, and When a Spreadsheet Is Actually the Right Tool draws that line clearly. The question is whether the sheet is holding analysis or running a process.

Where to start this week

1. Pick one sheet and score it. Choose the one that would hurt most if it disappeared tomorrow. Be honest about the “nobody dares delete” tab.
2. Ask who else depends on it. Send a two-line message to the teams you suspect read from it. You’ll usually find at least one consumer you didn’t know about. Who Owns This Sheet? Mapping the Shadow Processes in Your Company walks through doing this across the whole business.
3. Write down what the colours mean. Even if you change nothing else, a one-paragraph legend turns tribal knowledge into something a new hire can use, and it’s the first draft of a real status field.
4. Book 30 minutes with your sheet whisperer. Ask them to explain the hidden tabs and formulas while you take notes. If they’re the only one who knows, that knowledge should not be living in a single head.