The practical framework
Design ServiceNow CMDB reconciliation rules around identity, source authority, precedence, exceptions, duplicates, ownership, and review evidence.
The core task is not to make every source equal. It is to define identity, authority, precedence, exception handling, and review evidence in terms that the platform and the operating teams can apply consistently.
Define what makes a configuration item the same item
Start with identity. Decide which attributes, or combination of attributes, distinguish one item from another in each class. The answer may differ between a server, application, business service, or other configuration item type. A value that looks unique in a spreadsheet may not stay unique across environments or sources.
Document the identity rule with examples of valid matches, missing values, changed values, and conflicting values. Include the response when identity cannot be established. Creating a new record by default may be safer than merging two items incorrectly, but it also creates a duplicate-control obligation.
The ServiceNow CMDB data quality route is the relevant internal destination when identity rules need to become repeatable process controls.
Give each source a clear authority boundary
List the sources that contribute data and the attributes each source is expected to own. One source may be authoritative for discovery details while another maintains a business owner or service relationship. Authority should be assigned by field or data domain when a single source cannot maintain the whole record.
A source authority decision needs an owner, a failure path, and a review point. If the source stops updating, the CMDB should not silently present old data as current. If a team changes the source, someone must know which reconciliation assumptions need to be revisited.
Set precedence for conflicting attributes
Conflicts are normal when multiple systems describe the same item. Define which source wins for each attribute, what evidence supports that choice, and whether the update should be accepted automatically or sent for review. Precedence without an exception path can turn a simple rule into a hidden data-loss mechanism.
The ServiceNow integration strategy route provides an internal path when reconciliation depends on source mapping, data movement, or integration boundaries.
Do not use a global “latest update wins” rule as a substitute for authority. The latest value may be a correction, a partial record, or a value from a source that was never intended to own the field.
Handle exceptions instead of hiding them
Create explicit outcomes for missing identity, duplicate suspicion, conflicting ownership, stale source data, unexpected class, and unsupported relationship. Record the reason, owner, next action, and evidence. Exceptions that disappear into a log cannot improve the model.
Use a small set of categories that teams can understand and act on. The purpose is not to create a perfect taxonomy; it is to make the boundary between automatic reconciliation and human review visible.
Review duplicate risk as an operating process
Reconciliation is not finished when the rule is configured. Review duplicate candidates, rejected matches, stale records, and unusual update patterns. Check whether the rules behave differently after a source schema, discovery scope, integration, or class definition changes.
The ServiceNow continuous improvement route is the appropriate internal destination when the rules need recurring review rather than a one-time correction.