# Identifier collision register

> Classify duplicate IDs, compare competing records, and document replacement decisions, owners, and verification in the identifier collision register.

Canonical page: https://datacenterlabeling.com/templates/duplicate-identifiers

Download: https://datacenterlabeling.com/assets/downloads/rackstamp-worksheets.xlsx

Workbook tab: 02 Duplicate IDs. The workbook includes all 30 registers.

Rackstamp provides editorial field guidance. IDs, cases, and worksheet entries are fictional examples unless identified otherwise. Distinguish local conventions from adopted standards. Source notes describe the evidence scope; a linked overview is not the full standard or a project approval.

## Before you start

1. Open a collision reference independent of the disputed records and preserve the exact observed identifier strings before normalizing search copies.
2. Collect permitted physical evidence for every candidate, including complete location context and distinguishing references appropriate to the object class.
3. Identify the allocation owner, record owner, and owners of imports or print sources that may recreate the duplicate.

## Complete the register

1. Enter the complete scope and unchanged disputed value, including significant punctuation, case, and leading zeros.
2. Describe Record A and Record B with their record keys and evidence that distinguishes the represented objects. Do not rely on matching names alone.
3. Classify the case as separate objects sharing a label, duplicate records for one object, an alias issue, a scope/display issue, or unresolved identity.
4. Record the owner's actual decision and retained identity. Keep a proposed replacement separate until the issuer has reserved and released it.
5. Use Evidence to link the physical observations, issuance history, and dependency crosswalk showing the outcome for affected work orders and records.
6. Record verification against the corrected physical objects and current lookup. Leave Status explicit about any pending label replacement, source correction, or external dependency.

## Walk through the example

The original fictional row concerns CAB-0042 in DC01/H1 / cables. REC-A describes endpoints R014 to R021, while REC-B describes a different cable from R018 to R022. Those differing endpoint relationships must be supported by the permitted observations before the row is classified as two cables with one ID. The example decision lets REC-A retain CAB-0042 and records CAB-0098 as a fictional reservation for the other cable. That reservation is not authority to relabel an actual installation. In a real row, link the allocation decision, both endpoint evidence sets, and the dependent records that will change. Record the physical label correction separately from the database correction if they finish at different times. The verifier then checks that each issued scoped ID resolves to the intended cable and that old references remain interpretable. Keep the case open if a stale import can still recreate the disputed value.

## Handle common exceptions

### Two records have the same name but physical identity is unproved.

Keep the classification unresolved and assign the missing observation; do not approve a merge from the name match.

### The collision disappears when the hall field is restored.

Record the scope/display cause and repair the affected report or export instead of issuing unnecessary replacement labels.

### The physical correction is complete but another team's work order still uses the old value.

Record that dependency as pending with its owner and provide the approved crosswalk until the work order is reconciled.

## Review and close

1. Confirm that the classification follows the physical evidence rather than the number of search results.
2. Check replacement allocation and exact label text against the owner's decision.
3. Verify that each affected active reference has a correction or a named unresolved outcome.
4. Repeat current-ID and historical-value lookups, and check the responsible source input when it caused the collision.
5. Have another reviewer resolve an old work-order reference using the preserved crosswalk.

## Fields and fictional filled example

| Field | What to record | Fictional example |
| --- | --- | --- |
| Scope | Site and object class being compared. | DC01/H1 / cables |
| Observed ID | Unchanged disputed label text. | CAB-0042 |
| Record A | First record and distinguishing evidence. | REC-A; R014 to R021 |
| Record B | Second record and distinguishing evidence. | REC-B; R018 to R022 |
| Classification | Physical or record collision finding. | Two cables; one ID |
| Decision | Proposed resolution and retained identity. | REC-A retains existing ID |
| Replacement ID | Reserved identifier for the other object. | CAB-0098; fictional reservation |
| Owner | Role accountable for reconciliation. | Inventory steward |
| Evidence | References supporting the distinction. | DEMO-COLLISION-02 |
| Verifier | Person checking the resolved lookup. | Example reviewer |
| Verification date | Date the resolution was checked. | 2026-09-12 |
| Status | Current review state. | Example only |

## Sources

- [ServiceNow: Identification and reconciliation configuration](https://www.servicenow.com/docs/r/servicenow-platform/configuration-management-database-cmdb/configuring-ire.html?contentId=Qy3dDh~jSw5JICJGU2x7zg): Record identification and update-authority principles; does not prescribe physical relabeling. The expanded triage, decision comparisons, scenarios, and closeout procedures are original editorial guidance.