Why a Spreadsheet Can Never Be Your Single Source of Truth
Right now, somewhere on your team, someone is making a confident decision from the wrong version of your spreadsheet. They don’t know it. You don’t know it. They’re reading numbers they completely trust, in a file that looks exactly like the real one and you’ll both find out it was wrong in about three weeks, when a deadline slips or a figure refuses to reconcile, long after the copy that caused it has been overwritten and the trail has gone cold. If that sounds familiar, the instinct is to blame people: someone was careless, someone used the old file. But this isn’t a discipline problem. It’s a property of the tool, and once you understand why a spreadsheet behaves this way, you stop trying to fix it with rules and start fixing it properly. This article explains what a “single source of truth” actually is, why a spreadsheet is structurally incapable of being one, and what to do about it even if you love your spreadsheets and plan to keep them.
First, what “single source of truth” actually means
The phrase comes from how software and data systems are designed, and it means something precise: for any given fact, there is exactly one authoritative place it lives, and everything else reads from that place rather than keeping its own copy. Change the fact once, and every person and every view that depends on it sees the change immediately, because they were never looking at a copy, they were looking at the source. The opposite, the state most teams are actually in is what you might call multiple sources of truth: the same fact stored in several places that drift apart over time. The deadline lives in the tracker, in an email, in someone’s calendar, and in the deck from last month, and nobody can say with certainty which one is right. A single source of truth isn’t about tidiness. It’s about trust: it’s the quiet foundation that lets a team move fast, because no one has to stop and work out which version of reality they’re operating in before they act.
Why a spreadsheet is a “copy-first” tool by design
Here is the root of the whole problem, and it is worth understanding clearly: a spreadsheet is a file, and files are built to be copied. Portability is the entire point of a file, you can email it, download it, drop it in a folder, duplicate it, rename it, carry it on a USB stick. That portability is genuinely useful, and it is exactly what makes a file the wrong container for a single source of truth. The moment a fact lives in a file, it can exist in a hundred places at once, and the file format has no way to know which of those hundred is the real one. There is no “master” flag baked into a spreadsheet; “the real one” is just a social agreement among people, and social agreements decay. Contrast that with how a database or a modern work system stores a fact. There, the fact lives in one record, in one place, and when you look at it you are looking at the source itself, not a copy you downloaded. You can’t accidentally email the record; you can only share a link back to the one place it lives. That single architectural difference record you point to, versus file you copy, is the entire gap between a tool that can be a single source of truth and a tool that structurally cannot. A spreadsheet is the second kind, no matter how disciplined your team is.
The four ways a spreadsheet’s truth quietly fractures
Because a spreadsheet is copy-first, it forks through ordinary, reasonable actions not through carelessness. Watch how it happens:
● The emailed copy. Someone sends the file so a colleague can “take a look.” The instant Send is pressed, there are two files, and they begin diverging immediately, with no link between them and no way for either to know the other exists.
● The offline download. Someone saves a copy to work on during a flight, makes real progress, and the edits either never merge back or silently overwrite what three other people changed in the meantime.
● The divergent fix. Two people spot the same error and correct it differently. Both are certain they fixed it. The file keeps one version and discards the other without telling anyone.
● The rename ghost. A file named “Tracker_final_v3_USE-THIS” is not a label; it is a confession. The existence of “v3_USE-THIS” all but guarantees a v4 somewhere, and now “which is current?” is a genuine, unanswerable question.
Last-write-wins: the silent data-integrity trap
When two people edit the same spreadsheet cell, there is no negotiation and no conflict warning, the tool simply keeps whoever saved last and erases the other change without a trace. Engineers call this “last-write-wins,” and it is the opposite of data integrity. A real source of truth either merges changes safely or flags the conflict for a human to resolve. A spreadsheet just picks one and moves on, which means data can vanish while everyone involved believes their edit stuck.
“But we use Google Sheets, isn’t it live?”
This is the fair objection, and it deserves an honest answer. Cloud spreadsheets like Google Sheets and Excel on the web genuinely solve part of the problem: real-time co-editing means one shared file can stay in sync, and there is some version history. If your only issue were “people emailing copies around,” a cloud sheet would help a lot. But live co-editing fixes the sync problem, not the source-of-truth problem and the two are not the same.
Three things still break. First, people keep making copies anyway: they “File → Make a copy” for a client version, export to a deck, or download a snapshot for analysis and every one of those is a new fork the moment it’s created. Second, a cloud sheet still has no concept of a record you own, no structured status, no clear owner per item, no validated fields, so the “truth” is still just whatever someone typed into a cell, unverified. Third, link sprawl replaces file sprawl: now there are fifteen shared sheets and the question quietly becomes “which tab in which sheet is the current one?” A live file is a better file. It is still a file and a single source of truth is not a file at all.
Why this problem costs more than the others
Most spreadsheet problems cost you time, and time is recoverable. This one costs you trust in your own data, which is far harder to earn back. The first time someone acts on a stale copy and gets burned, they learn a quiet, corrosive lesson: don’t trust the file. So they begin double-checking every number before they use it re-deriving totals, re-confirming dates, cross-referencing against a second copy “just in case.” That is the cruel irony: the lack of a single source of truth drags back every bit of the manual overhead a shared tracker was supposed to remove, and adds a layer of anxiety on top.
It’s also invisible until the damage is done, which is what makes it so expensive. A forked file throws no error. You discover it downstream, the wrong figure in the board deck, the resource double-booked, the campaign built on last week’s budget and by then you’re fixing the symptom while the mechanism that produced it, the quiet forking of your data, keeps running, ready to produce the next one. Multiplied across a year, that is not a nuisance; it is a steady leak of decisions made on numbers that were wrong before anyone read them.
What a real single source of truth looks like
A work system built around records, Asana is one example, holds one live version of each item, and the difference from a spreadsheet is structural, not cosmetic. There is nothing to copy, download or email, because everyone works in the same place; you share a link to the record, not a duplicate of it. A change made once is instantly the truth for everyone. Ownership, status, due date and full history live on the item itself, so you can always see who last touched it, when, and what it said before the audit trail a spreadsheet never had. And when two people act on the same item, the system tracks both rather than silently keeping one. “Which version is current?” stops being a question, because there is only one, and it’s the one in front of you.
You don’t have to abandon spreadsheets to get this. The practical move is to separate your coordination data from your calculation data. Tasks, owners, deadlines, status and handoffs the facts many people need to agree on belong in one shared record system, your single source of truth. Budgets, models and analysis where a spreadsheet genuinely shines stay in the spreadsheet, ideally pulling from that source rather than keeping their own private copy of it. The goal is simple to state and powerful in practice: reduce the number of places any given fact can live to exactly one.
For a fuller view of where each tool wins, see Asana vs Excel: where each one actually wins; and if you’re planning a move, Moving from Excel to Asana: don’t migrate everything covers the mistake to avoid.
The one test to run this week
Pick a single important fact, a key deadline, a budget number, a project’s status and count how many places it currently lives. The tracker, the email, the calendar, the deck, someone’s private copy. If the answer is more than one, you don’t have a single source of truth for the fact that matters most, and the only reliable fix is to make one of those places authoritative and have every other read from it.
How many “true” versions of your tracker are out there right now?
Take our Spreadsheet Scorecard, in a few minutes it shows you where your setup leaks time, where it puts work at risk, and what to fix first. As a certified Asana Solutions Partner, we turn fragile trackers into systems that run themselves.
Comments