The Single Source of Truth: Stopping Information Sprawl
Ask three people in a small business for a client's current phone number and you'll often get three answers: one from the CRM, one from an old email signature, one from a phone contact updated last year. None of them is wrong on purpose. The business just never decided where the truth lives.
What a single source of truth actually means
A single source of truth is a rule, not a product: for each type of information, exactly one place is authoritative, and every other copy is a convenience that defers to it. You can hold that rule with a spreadsheet, a CRM, a shared drive, or a whiteboard — the tool matters far less than the agreement.
The failure mode isn't using multiple tools. It's using multiple tools without deciding which one wins when they disagree.
Map the sprawl before you fix it
List your information types down one side of a page and ask, for each: where does this live today, and where should it live?
| Information type | Common sprawl | Pick one home |
|---|---|---|
| Client contact details | CRM, phone contacts, email threads | CRM (or one spreadsheet) |
| Job/project status | Heads, group chat, whiteboard | Project board |
| Prices and quoting rules | The owner's memory | A priced services document |
| Procedures | Nowhere / scattered docs | Your ops manual |
| Files and artwork | Desktops, email attachments, USBs | One structured shared drive |
| Passwords and access | Browsers, notebooks, reused logins | A password manager |
Make the rule stick
- Announce the home for each information type — one line each, written where everyone can see it.
- Route updates to the home first. New client? They go into the CRM before anyone replies to their email. Price change? The document changes before the next quote goes out.
- Let the copies be disposable. Phone contacts, printouts and cheat-sheets are fine — as long as everyone knows they're copies, and nobody updates a copy instead of the source.
- Kill the duplicates you can. Every retired spreadsheet is one less place for truth to fork.
When two tools both feel authoritative
The hard cases are the overlaps. Job details live in the project board, but the client's phone number lives in the CRM — so where does a change of site address go? Decide by information type, not by tool: contact and relationship facts belong to the CRM, work-in-progress facts belong to the board, and each tool links to the other rather than copying from it. Where a tool insists on holding a copy (most do), treat the copy as read-only and let integrations refresh it from the source.
The same logic settles the classic email problem. An email thread is where information arrives; it is never where information lives. The two-minute habit that saves whole afternoons later: when a decision or detail lands in email, move it to its home immediately — the price change into the pricing doc, the new mobile number into the CRM — and then let the thread be archaeology.
The payoff
Businesses that hold this rule get three things almost immediately: new staff stop asking where things are, handovers stop depending on memory, and the answer to "what's happening with this job?" becomes a look-up instead of a meeting. None of that needs new software. It needs a decision, written down, and defended for about six weeks until it becomes culture.