What Is a Single Source of Truth in Operations?

What it is not

A single source of truth is smaller than it sounds, and easier to lose than it looks.

The CRM may own deal stage while finance owns invoice status. Define the fact before choosing its authority. Even two correct reports can show different customer totals when they count different populations or reporting dates.

Three misreadings

What it does not mean

It does not mean one system for everything. Assign authority to the specific field or defined measure, not automatically to every value in a tool.

Copies can still exist. A report or cache may show an older value; record its refresh point and reconcile it under the agreed rules.

An edit may originate through another interface. What matters is that it follows the authority and conflict policy rather than silently overruling a competing record.

How teams lose it

A source of truth rarely fails on day one. It erodes in three familiar ways.

The editable export

A copy becomes a second original

Someone exports the CRM to a spreadsheet to work faster, edits it there, and the spreadsheet quietly becomes more current than the system it came from. Now there are two originals, and the more trusted one is the copy nobody can govern.

The two-way sync

Both systems can change the same field

A two-way sync needs a policy for competing edits. Some implementations use last-writer-wins, but that is not inevitable. Others reject stale updates, route conflicts to a reviewer or permit different systems to own different fields.

The failure is an unexplained overwrite: someone changes a value without knowing which authority or version the integration will accept. A later timestamp alone does not establish that the new value is correct.

The trusted side channel

The real number lives in someone's head

The system says one thing, but everyone knows to ask a particular person for the "real" figure. That person is now the source of truth, undocumented, unavailable on holiday, and impossible to audit. The system has been demoted without anyone deciding to demote it.

Fictional customer C-204

Agree authority before the copies disagree.

This example team assigns the fields below explicitly. These choices illustrate an agreement; they are not rules for every CRM or billing system.

Fact	Authority in this example	How another system uses it
Relationship owner	CRM customer record	Billing reads the assigned owner; it does not replace it.
Invoice status	Billing invoice record	CRM displays the billing result and its refresh time.
Billing address	Verified billing customer record	CRM may submit a proposed change for validation; a stale copy does not silently overwrite it.

Two competing address updates

A version check finds a conflict; it does not choose the address.

01
Both tools read the same version
CRM and billing read C-204 at example version 7. Record identifiers establish that the proposed changes concern the same customer.
02
Billing accepts a verified change
Billing records the new address under this team’s authority policy. The earlier version is now stale.
03
The older CRM request arrives
A version-aware implementation can reject the stale write and retain the proposed value for review. Do not assume that every connector has this capability.
04
Resolve and verify the copies
The accountable owner checks the evidence for the proposed address, records the accepted result and confirms that the CRM copy reflects it. Unresolved evidence remains a conflict, not a silent overwrite.

Both tools read the same version
CRM and billing read C-204 at example version 7. Record identifiers establish that the proposed changes concern the same customer.
Billing accepts a verified change
Billing records the new address under this team’s authority policy. The earlier version is now stale.
The older CRM request arrives
A version-aware implementation can reject the stale write and retain the proposed value for review. Do not assume that every connector has this capability.
Resolve and verify the copies
The accountable owner checks the evidence for the proposed address, records the accepted result and confirms that the CRM copy reflects it. Unresolved evidence remains a conflict, not a silent overwrite.

The authority test

When copies differ, can you explain which fact is authoritative and how the difference will be resolved?

A refresh delay, a formatting difference and a genuine competing edit need different responses. Authority is useful when it gives the team a clear rule for that distinction and a named owner for unresolved conflicts.

What is a single source of truth?

A single source of truth is smaller than it sounds, and easier to lose than it looks.

What it does not mean

A source of truth rarely fails on day one. It erodes in three familiar ways.

A copy becomes a second original

Both systems can change the same field

The real number lives in someone's head

Agree authority before the copies disagree.

A version check finds a conflict; it does not choose the address.

Both tools read the same version

Billing accepts a verified change

The older CRM request arrives

Resolve and verify the copies

Both tools read the same version

Billing accepts a verified change

The older CRM request arrives

Resolve and verify the copies

References behind this piece

Jonas Andersson