You need a PLAN to deal with duplicates
Here's the thing about duplicate records: No matter what you do, you'll never get rid of them completely, because humans are human. Whether it's a staff member creating a duplicate record because they forgot to check if the record exists, or it's a customer who doesn't want to take the time to reset his password and just creates another record with a different email address, duplicates are going to happen.
And because duplicates are inevitable, you have to have a plan for dealing with them. Here are some suggestions:
- Create data integrity reports that will help you identify potential duplicate records, and run those reports consistently. ("Consistently" means at least once a month, if not more often.) And make sure someone (or several someones) on staff has responsibility for cleaning up this data.
- Make it everyone's job on staff to identify potential duplicates whenever they are using the database and make sure you have a clear process for how those duplicate records are reported. And make sure someone (or several someones) on staff has responsibility for cleaning up this data.
- And did I mention to make sure someone (or several someones) on staff has responsibility for cleaning up this data?
Managing duplicate records is a journey, not a destination. No matter how good your technology is, like weeds in a garden, duplicate records are going to appear. So you have to have a plan for dealing with them, not just now, but always.
![]()
Wes's Wednesday Wisdom Archives
How you respond matters
How you respond matters Very recently I wrote that I measure customer service by how […]
Your one non-renewable resource
Your one non-renewable resource For any project, the three primary resources are time, money, and […]
No system is perfect
No system is perfect When working with my clients on the selection of a new […]
Ask your members to update their info
Ask your members to update their info One of the greatest data management challenges any association […]
Customer vs. staff
Customer vs. staff In a properly designed AMS, when the customer goes online to your […]
Measuring customer service
Measuring customer service When I work with clients on AMS selection, one question that often […]
Iterate or innovate?
Iterate or innovate? When moving to a new association management system, there is often an implicit […]
Who is in control?
Who is in control? Speaking with a client once about their database project, the client […]
Sometimes Staff Has to do the Work
Sometimes staff has to do the work… As a child, I was attracted to computers […]
Documentation and the Great Resignation
Documentation and the Great Resignation Unless you’ve been living under the proverbial rock, you’ve heard […]
