Worker identity across systems, not just one
Worker identity breaks when a person moves between contract types, legal entities or systems and picks up a new ID each time. This fragments their history and makes tenure, mobility and attrition analysis unreliable. A durable identifier that follows the person, not the record, is what keeps their history intact across every transition.
A person can pass through three IDs in one career: a contractor number, a permanent employee number, and a new one again after an internal transfer between legal entities.
Where identity breaks
- Contractor-to-employee conversions issued a fresh ID by payroll
- Cross-entity transfers in multinational structures
- Mergers where two HRIS instances are never reconciled
The cost of fragmentation
When identity breaks, tenure resets to zero, internal mobility looks like external hiring, and attrition figures overstate turnover because a transfer is counted as a leaver and a new joiner.
- 2-3
- IDs a mobile employee can accumulate across systems
- 1
- durable identifier needed to keep history intact
Building a durable identifier
- 01Choose an anchorUse a government ID hash or a dedicated master data key, not a system-issued number.
- 02Map legacy IDsBuild a crosswalk table linking every historical ID to the anchor.
- 03Enforce at entryRequire the anchor ID whenever a new system record is created.
Once identity is durable, tenure, mobility and attrition analysis stop needing manual reconciliation before every report.
Underlag
- Our assessment
Contract-to-permanent transitions are a frequent trigger for duplicate worker records in HR systems.
Common questions
- What should the anchor identifier be?
- A hashed national ID or a dedicated master data key that never changes across systems or contract types.
- Can this be retrofitted?
- Yes, through a crosswalk table, though it requires a one-off historical reconciliation project.