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
Always, ALWAYS budget for more training
Always, ALWAYS budget for more training Always, ALWAYS budget for more training. I don’t know how else […]
We’ve always done it that way
We’ve always done it that way A couple of weeks ago I wrote about approving memberships, […]
Are you sure it doesn’t do that?
Are you sure it doesn’t do that? Even after 20 years of consulting, I’m surprised […]
Be grateful
Be grateful As Thanksgiving approaches here in the US, I’m reminded of two words: Be […]
Do you really need to approve them?
Do you really need to approve them? I often joke that the very best (because […]
Negativity bias is why we need database PR
Negativity bias is why we need database PR I’ve written before how cognitive biases can affect […]
A system change requires a culture change
A system change requires a culture change By its very nature, when you introduce a […]
Where is that data?
Where is that data? This is what data management nirvana looks like: When the question starts with […]
Be deliberate, but act quickly
Be deliberate, but act quickly Be deliberate, but act quickly. These are my words of […]
Why associations don’t like the “S” word
Why associations don’t like the “S” word A couple of weeks ago I asked my […]
