Duplicate records can split a learner’s attendance, payments and learning history. Review suspected duplicates carefully rather than merging records on a name match alone.
A practical starting point
Two learners share a similar name, while one learner has been entered twice using different spellings. A simple name-based merge would create a new problem.
Turn the idea into a working routine
- Flag potential duplicates using several relevant identifiers available through approved records.
- Ask an authorised reviewer to verify whether the entries concern the same person before changing anything.
- Document how linked records will be handled and retain the correction history according to institutional procedures.
Measure what matters
Track new duplicate entries and the workflow that produced them. Prevention is easier than repeated clean-up.
A matching name or phone number does not establish identical learner identity.
What should the team agree before putting this into practice?
Agree who can approve a merge and how the institution will validate the resulting history.
MAKE IT PRACTICAL
Your planning checklist
Use this checklist during a team discussion. It tracks your planning progress, not a score of your institution’s quality. Selections stay in this page and are not submitted.
Treat identity corrections as a careful review, not a bulk shortcut.
About this archive: 6 January 2025 is the collection’s reference date. This article was prepared and published on 7 November 2026. It is AI-assisted editorial content; examples are illustrative and do not describe a specific customer deployment.
