A great example of a data integrity report!
A couple months back I discussed the importance of data integrity reports. One of my past clients and a longtime reader, David Churchill at Grantmakers in Health, offered up this idea, which I think is fantastic and should be added to any association's list of data integrity reports.
As he explains: "I found that there’s a lot of email address mistakes made during our online registration process. It's not always easy to spot simple typos like .cmo (.com), .ogr (.org) so I created a query that is titled “questionable top level domains” that shows any record with likely typos (or .ru which is largely spam)."
One reason I love this query is that it's designed to capture "common" errors with the knowledge that it won't catch every error. And it has the added bonus of looking at addresses that are likely spam.
But what a great idea! If a customer mistypes their email address, other than checking bounced emails in the future, how will anyone know there is an error? By proactively checking for errors, David is weeding the garden, which is critical to long-term data management success.
![]()
Wes's Wednesday Wisdom Archives
Consider quitting
Consider quitting Patient: “Doctor, it hurts when I do this.” Doctor: “Then stop doing that.” […]
There is nothing so permanent as business rules
There is nothing so permanent as business rules Nobel Prize-winning economist Milton Friedman said, “There’s nothing […]
Budget for feature discovery and adoption
Budget for feature discovery and adoption When developing a budget for implementation of a new […]
Customize staff pages for better user adoption
Customize staff pages for better user adoption The single most important element to data management […]
Don’t ask questions for which you already know the answer
Don’t ask questions for which you already know the answer I was recently completing an […]
All decisions involve risk
All decisions involve risk Whether it’s choosing a new AMS or introducing a new product […]
Try flowcharting your processes
Try flowcharting your processes Working with a client recently on their membership join process reminded me […]
“I just want a system I don’t have to fight with.”
“I just want a system I don’t have to fight with.” I asked my client: […]
Inertia Contributes to Bad Data
Inertia Contributes to Bad Data Without knowing anything about your organization or its data, I’d […]
What are you doing with new contacts?
What Are You Doing with New Contacts/ I was very interested to read in a […]
