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
Don’t automate for the sake of automation
Don’t automate for the sake of automation I’m the laziest person in the world. I […]
Don’t forget about what got better
Don’t forget about what got better Negativity bias is the tendency to focus on only […]
Give a little at a time rather than taking away
Give a little at a time rather than taking away I’m sure there’s research somewhere […]
First, you gotta have the data
First, you gotta have the data When I work with clients on a new AMS […]
Work on your relationship with your AMS vendor
Work on your relationship with your AMS vendor It is no coincidence that my most […]
Dashboards for Data Integrity
Dashboards for Data Integrity I’ve written a bunch on data integrity reports. (Click here for […]
Next-to-Nothing Goals
Next-to-Nothing Goals I saw a Ted Talk by Christine Carter recently discussing the concept of […]
Just because you can…
Just because you can… In response to a recent Wednesday Wisdom on averages hiding the […]
Always ask “Why?”
Always ask “Why?” Little kids ask “Why?” all the time, because they are sponges for […]
Averages hide the extremes
Averages hide the extremes I can’t remember where I first heard it, but “averages hide […]
