Don't forget about periodic maintenance
Just as most automobiles need periodic maintenance, keeping your data as up to date as possible requires maintenance, as well. And while most cars have a "typical" maintenance schedule, they are not all exactly the same (all-electric cars, for example, don't need oil changes!).
The same is true for the data in your AMS; not every organization is the same and so the maintenance won't be identical for all groups. But here are four suggested periodic maintenance activities that would apply to most associations:
- Review all demographic fields being captured against individuals and organizations, and determine if any need to be updated or eliminated. For example, if you collect experience level for individuals (e.g., "new," "mid career," "experienced"), as time passes, that data becomes incorrect. The same is true for "areas of interest" and even "markets served" (for organizations). I recommend doing this annually.
- Send a periodic reminder to your members to review and update their basic contact information (e.g., address and email, title). This should be done at least annually, but for some organizations, even more frequent check-ins may be necessary.
- For trade associations, check to make sure you have correct contact information for primary and other key contacts (e.g., billing, secondary/alternate, etc.). Depending on your dues cycle, this should be done at least annually if not more frequently.
- If you have a student membership, send a periodic reminder to students to confirm their expected date of graduation or other key data that you collect from them (e.g., area of study). Given the high rate of changes, especially among undergraduates, this should be done twice per year.
These are just four examples of the kind of maintenance all associations should be executing on a regular basis. Your organization probably has many more that should be done. So make sure you develop this "maintenance checklist" and that it is assigned to the appropriate staff to execute when necessary, to keep your database running like...a well-maintained automobile.
![]()
Wes's Wednesday Wisdom Archives
The “S” stands for “Standard”
The “S” stands for “Standard” In a conversation with a past client, we were discussing […]
Is that meaningless data?
Is that meaningless data? I’m not a big quotes guy, but one of the few […]
Be aware of unintended consequences
Be aware of unintended consequences I’ve written before that every decision involves a trade-off. When […]
Positive change is harder to see
Positive change is harder to see Humans are wired to see negative change because we […]
MVP: Minimum Viable Product
MVP: Minimum Viable Product In product development there is a concept known as MVP, or […]
You always need a reason for collecting data
You always need a reason for collecting data When you ask for data from someone […]
If you’re unhappy, speak up!
If you’re unhappy, speak up! My clients will often ask me something along the lines […]
Does it advance the mission?
Does it advance the mission? Because associations are mission-driven, everything you do should be seen […]
How should you start a new data project?
How should you start a new data project? When you’ve got a new data project […]
A Data Integrity Report…for Reports!
I’ve written elsewhere about the value of data integrity reports. But one of the most […]
