Multi-System HRIS Record Deduplication Matrix
Design a master reconciliation matrix to deduplicate and standardize employee operational data.
Use this template during HR system migrations or enterprise mergers to clean conflicting personnel files. It establishes deterministic match rules and conflict resolution priorities.
Role: Principal People Analytics Operations Specialist and Enterprise Data Steward.
Context
- Primary HRIS platform: {{primary_hris_system}}
- Merging sources: {{legacy_data_sources}}
- Attribute fields: {{employee_record_fields}}
- Match threshold: {{match_confidence_threshold}}
- Security level: {{privacy_classification}}
- Retention window: {{retention_policy_window}}
Task
Produce an HR Master Record Resolution and Deduplication Matrix that maps conflicting personnel attributes across disparate source systems and outlines precise deterministic merge criteria.
Method
- Analyze {{employee_record_fields}} across {{legacy_data_sources}} and {{primary_hris_system}} to identify semantic discrepancies.
- Establish hierarchy of truth rules giving priority based on system of origin and update recency.
- Define deterministic matching criteria (e.g., composite keys) and probabilistic criteria governed by {{match_confidence_threshold}}.
- Formulate normalization logic for legacy job codes, department tags, and location strings.
- Address handling of inactive, terminated, or historical profiles within {{retention_policy_window}}.
- Incorporate data masking and access protections matching {{privacy_classification}} standards.
- Construct the multi-attribute resolution matrix detailing transformation and survivor logic for every field.
Constraints
- MUST preserve historical tenure and compensation continuity across all merged profiles.
- MUST NOT drop active employee records when collision occurs without generating a manual audit flag.
- Ambiguous identity matches below {{match_confidence_threshold}} must be routed to quarantined review.
- All data transformations must comply with the specified {{privacy_classification}}.
Output format
- Master Field Mapping Summary (bulleted list)
- Record Reconciliation Matrix (Markdown table with columns: Field Name, Primary Source, Secondary Source, Match Rule, Conflict Resolution Rule, Survivor Logic)
- Edge-Case Triage Protocols (numbered list of 3-4 handling workflows)
Self-review
- Does the matrix cover all fields listed in {{employee_record_fields}}?
- Are fallback rules specified when records fall below {{match_confidence_threshold}}?
- Does the retention approach respect {{retention_policy_window}}?
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.