Choose which system owns each record

Assign ownership by record and decision

Different systems may own different parts of the same business process. One may maintain product information, another may route work and another may hold financial records. A connection needs agreed responsibilities rather than an assumption that every copy is equally authoritative.

1. List the records used by the process.
2. Choose the system responsible for maintaining each record or field.
3. Identify which systems may read or update that information and under what rules.

• A system of record is an agreed responsibility, not a claim that every downstream copy updates instantly.
• Changes to ownership can require migration and reconciliation work.

Work through one example

Follow a redacted record through the systems and identify where its identifier, status and key fields change. Include a failed or corrected case so the team can agree how exceptions are resolved.

• The identifier used to match the record across systems.
• The person responsible for correcting a mismatch.
• The point at which a downstream system should treat an update as accepted.

Document the decision

Keep the ownership decision with the workflow scope and acceptance checks. This gives reporting, integration and support teams the same reference.

• The record or field and its responsible system.
• The permitted direction of updates.
• The owner who approves exceptions or changes to the mapping.