It’s early June and while some of us might be living in areas of the country where Summer is in full swing, here in New England, we are still in the thick of Spring. And, by thick, all you need to do is look outside at the layers of pollen covering all surfaces to know that it is really still Spring.
So, let’s do some Spring Cleaning in our database!
Clean data is critical for a nonprofit. Sometimes, you’ll hear the practice of keeping “clean data” referred to as “data health” or “data hygiene.” The name doesn’t matter but the practice does.
At its most basic, how can you effectively interact, engage, solicit and steward your constituents if you do not have clean and accurate contact information? This would typically include data points such as name, mailing address, email address and telephone number.
But, clean data goes far beyond communication strategy.
Broadly speaking, the concept of ‘Garbage In/Garbage Out’ means that if you embark on any type of analysis or reporting effort, your results will only be as strong as the data that you have fed into the analysis.
Dirty data leads to bad results. Or, at the very least, results that may be inaccurate or misleading.
It is for this reason that clean data is the most foundational – and most important – element of an analytics project as well.
Where do you start?
The best place to start is to ensure that your organization has clear and consistent data entry policies in place.
It is highly recommended to have a style guide or manual that describes how data should be captured within your database.
Even better if you can use the tools and functionality of your database to “lock down” data fields by requiring standardization in formatting or using dropdowns and picklists.
Let’s look at an example:
Let’s say you are starting an internal prospecting project and you want to run a quick report of all of the people in your database who made a gift last month (May 2024). Seems easy, right? You just navigate over to your query function, select the “most recent gift” field in your database, enter the date range “5/1/24” – “5/31/24” and hit Enter.
Presto, you are done!
But are you?
Your results come back empty, and you know that gifts came in last month.
Going back into your query, you realize that you should have entered “05/01/2024” – “05/31/2024.” You edit your query and run it again. This time you get a few results, but they seem smaller than they should be. Frustration growing, you think: “what now?”
So, you start to do some investigating and realize that your gift processing intern, on a study abroad program from overseas, entered the majority of last month’s gifts using the European date format, meaning that May 1, 2024 is now recorded as “01/05/2024.” What a nightmare!
Now, a date field might seem like a silly example since we know that every quality database on the market will allow an organization to “lock down” dates into a standard format. But it still serves a strong illustrative purpose of how consistent data – or maybe the inconsistency of data – matters.
Since a date field is just one simple example, let’s look at how this could snowball when you consider a more complex project.
What if your requirements were: all donors living in NY, who made a gift last month, and have a major giving capacity of $10K or more.
- Are states entered as: NY, N.Y. or New York?
- Is major giving capacity a free-text field or have you set up pre-defined dropdowns? Does the capacity field include discrete dollar values or ranges?
It’s actually interesting because in many organizations, the function of data entry is relegated to the most junior staff members (or interns!) as it is considered a rote administrative function. However, data entry might be the most important function in your office.
Yes, I said it:
Your data entry person or team is THE MOST IMPORTANT in your office!
So, let’s assume you are thinking: “This is great, but I don’t need to worry about this because I know we have a data entry policy in place, and I know our database is configured optimally.” Even with the best planning, the best intentions, and the most conscientious of people entering data into your database, dirty data still happens.
Here’s a quick list of other considerations:
- Who has access to enter data into your database?
- Have they been trained in both the functionality of your database and the policies that govern data entry?
- Can they enter all datapoints or just specific datapoints?
- Do you have regular data integrity process or run periodic data audit reports that can help identify dirty data?
- Do you have a process in place to address data integrity issues?
- Do you have a cadence in place to update data on a regular basis?
In closing, know that no database will ever be perfect. Data changes rapidly and even with the best intentions, human error happens. Rather than striving for perfection, strive for thoughtfulness, consistency and continued maintenance.
***
For additional reading, guidance and sample policies:
- Check with your CRM vendor. Many companies have policy and procedure manual templates and/or advice that speak directly to the functionality within their products
- The Association of Advancement Services Professionals (aasp) hosts an entire best practice library on record management (membership is required)
- Consult AFP’s Ready Reference Guide: Developing Fundraising Policies and Procedures (membership is required)
- Try an internet search. My quick search turned up quite a number of live policies relevant for our industry from the very targeted Frostburg State University’s Address Entry Guidelines to the much more comprehensive manuals such as those The University of North Carolina at Charlotte’s Data Standards Guide, the University of Maryland, Baltimore’s Data Entry Standards Guide and The Diocese of Jefferson City’s procedures and business rules for data entry. Even if these examples are for a different CRM system than the one you use, or if you are in a different sector, the general flow of the documents and guidance on standardization can be adapted to fit your specific circumstances.