Operations guide
How to resolve data-quality findings
Work from import confidence and provenance into contact, duplicate, linkage, and merge-review findings without destructive automatic cleanup.
- Subject owner
- VehicleDesk Product and Engineering
- Last reviewed
- 2026-07-31
Prioritize by decision impact
A missing vehicle link, malformed contact point, duplicate candidate, or stale source has different consequences. Review starts with the workflows that rely on the affected record.
Trace the provenance
The source, import run, mapping, timestamp, and related records help staff understand whether a finding is local workflow data, imported provider data, or a derived observation.
Preview a possible correction
Duplicate and merge candidates can be inspected before action. The current workflow does not advertise irreversible automatic merging or cleanup.
Verify the result
Record the owner, change, source, date, and validation result, then confirm the downstream customer, vehicle, queue, or report reflects the expected state.
Related product detail