The CRM, project board and finance system show different client details. A source-of-truth register identifies which record controls each important field, who maintains it and how changes reach other places. One system does not have to control every kind of information.
Photo by Richard Heinen on Unsplash.
Start with fields that create real confusion
Choose a small set, such as client contact, approved scope, delivery date and billing reference. Trace where each value starts, where it is copied and who relies on it. Record actual practice before prescribing a new system architecture.
Use this field-level register
Information or field and agreed meaning.
Authoritative record and owner.
People permitted to update it.
Other systems displaying or using it.
Update route and conflict resolution.
Check or reconciliation needed.
State what happens when a downstream user finds an error. They need a correction route, not permission to create another private master copy.
An illustrative allocation
A service business uses its signed scope record for agreed deliverables, its delivery plan for the current working forecast and its finance system for billing details. The register explains these distinctions so a forecast update is not mistaken for an approved contractual change.
Trial the update route
Add an effective date where a value changes over time. An approved scope, a working forecast and a historic delivery commitment may all be legitimate records with different purposes. Do not force them into a single field merely to claim one source of truth. Define their meanings and the relationship between them so downstream users do not mistake one for another.
Related guidance: practical process-mapping guide.
Follow a normal change, a correction and a conflicting update across the relevant systems. Check whether the receiving users know which value to trust. Resolve ownership before expanding integrations; a faster connection can distribute conflicting information more quickly. Hili Consulting can help clarify the records your workflows depend on.
