A great example of a data integrity report!

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

Perfection is expensive (in fact, it’s not possible!)

April 22, 2026

Perfection is expensive (in fact, it’s not possible!) “Perfection is expensive. The last 5 percent […]

AI is a journey, not a destination

April 15, 2026

AI is a journey, not a destination Lately I’ve noticed a lot of associations talking […]

Action produces information

April 8, 2026

Action produces information “Action produces information. If you’re unsure of what to do, just do […]

Why a single source of truth is so beneficial…

March 25, 2026

Why a single source of truth is so beneficial… The holy grail of data management is […]

Just because you can, doesn’t mean you should

March 18, 2026

Just because you can, doesn’t mean you should I’ve worked in and with associations for well […]

Data doesn’t need to be perfect to be useful

March 4, 2026

Data doesn’t need to be perfect to be useful “Your data doesn’t have to be […]

Don’t just clean data, clean reports and queries

February 25, 2026

Don’t just clean data, clean reports and queries One of the reasons I exhort my […]

Don’t forget, your staff have day jobs…

February 18, 2026

Don’t forget, your staff have day jobs… The vast majority of my work is finite […]

Beware the automated “How did we do?” trap!

February 11, 2026

Beware the automated “How did we do?” trap! One of the downsides of technology is […]

Hindsight is 20/20

February 4, 2026

Hindsight is 20/20 I’m currently working with a client that is moving from their legacy […]

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top