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
Discipline is required
Discipline is required Last week I discussed the importance of taking action. To manage data […]
Action is required
Action is required Over my many years of consulting, one thing I’ve noticed about many associations […]
Some data analytics tips from the DAN “Science Fair”
Some data analytics tips from the DAN “Science Fair” Last week I had the opportunity […]
Are all your processes frictionless?
Are all your processes frictionless? I’m not a huge fan of buzzwords, but I love […]
Trends don’t need perfect data
Trends don’t need perfect data When it comes to analyzing data trends (changes in data […]
Start with “Why” before you move to “How”
Start with “Why” before you move to “How” Something I’ve noticed over my years in […]
The power of users groups!
The power of users groups! Last week I had the honor and pleasure of speaking […]
Associations are complex businesses!
Associations are complex businesses! One of the reasons managing data at an association can be so […]
Snapshots are required
Snapshots are required Recently a couple of different clients have asked me why it’s necessary […]
“It’s in the database…”
“It’s in the database…” I often joke with my clients that AMS nirvana looks like […]
