"Customer Database Principles" was the very first tip sheet I ever posted to the Internet, back in 1994 (to a USENET newsgroup), and it's still as popular now as it ever was (yes, I've revised it more than a few times).
Just as for-profit businesses gather data about customers and potential customers, to build a population of buyers for their products, mission-based organizations (nonprofits, non-governmental organizations or NGOs, civil society organizations, public sector agencies, schools, etc.) must track information about people too -- current donors, volunteers, clients, potential donors and volunteers, ticket-buyers, event attendees, students, etc. -- to build ongoing support their programs and services. Capturing this information is crucial for an organization to show the impact its programs, to measure how people are perceiving the organization, and to show the gaps regarding where and how the organization's messages are being communicated. Every department of your organization relies on databases to fulfill their goals as well.
The following basic database advice is designed especially for the unique needs of small mission-based organizations with very limited staffing and funds. Employees and volunteers of these organizations have to stretch existing resources a long way, and may not have the resources to hire a full-time database manager or even a short-term consultant, let alone purchase specialized database software or send employees to computer training.
This advice also comes from the author's point of view that the best designers of these databases are the users -- the people who input and manipulate the data as part of their jobs. That means volunteer coordinators and development directors and office assistants should direct the design, rather than senior managers and IT professionals.
Not everything in the following suggestions will be appropriate for your database; field names vary, as does the information you want to track about customers and clients.
This advice comes from the many years the owner of Coyote Communications has spent creating and/or managing databases that track people and their activities, be it what tickets they buy, how much they've contributed to an organization in time or money, ways they have volunteered, or if they've received the latest brochure. This advice is further enhanced by continued suggestions posted to various online discussion groups.
If you are new to database management, review the Basics of People Databases, which includes
Please note that regular data entry and maintenance may significantly change your present organizational procedures, depending on who enters the data, what the scale of operation is, and training requirements. It is of the utmost importance to support the person(s) who maintain the database (i.e. the people who input the data). This should be a priority job, not an after thought or a "when-you-have-time" task, and not something to think about late in a database adoption process. Without full and initial support of this person or persons who will primarily input and manage the data, your database, no matter how well designed or how highly thought of it is by IT experts, will fail to meet your organization's needs.
In addition, you should be tracking in what projects/programs people are interested, how they are hearing about your organization, how many hours they volunteer each month, if they received your latest newsletter, etc. This doesn't take an elaborate system -- it takes staff members who understand when and how to capture information on the phone, via a sign-in sheet, etc.
Develop systems that everyone can and will use to capture this information, and make sure this information is inputted in a timely manner -- a good rule is that new information is inputted into your database no more than 48 hours after it was received by the organization.
(also see Keeping Volunteer Information Up-to-Date for specific tips on how to ensure volunteer information is inputted regularly and kept up-to-date)
Develop your systems of tracking "people" information based on how your staff wants to use information about clients, volunteers, donors and potential audiences. The first step in deciding WHAT information you need to track is to find out what each staff member wants to be able to do with the database. Fund-raising staff may want a list of volunteers each quarter who have also made financial contributions; the executive director may want to occasionally see what city and county officials have attended your organization's events; the marketing staff may want to know to know weekly who or what referred people who call your organization. If you don't know what staff members need out of your information-tracking systems, ASK.
Deciding what information needs to be tracked will help you decide what fields to create to track information about people in your database(s).
You should either have only ONE central database system for tracking all people and organizations involved with your organization (or that could potentially be involved), OR, all of your databases need to be able to "talk" to each other.
Your accounting staff may need their own for vendors, bills and payroll; your program manager may need one to track projects and their progress; your marketing staff may have a press-tracking system they want all to themselves; and various staff will have their own personal databases (electronic address books) to track certain contacts. But anything that relates to your membership, customers, volunteers, donors, potential supporters (including city & county officials), event attendees, etc. should be kept in one, centralized database system (you can have different databases for each of these, but the information should be joined; read more about what this means in The Basics of People Databases.
Here are some basic, general suggestions for information categories for a people database:
(this should be an automated field)
Also, other information will need to be tracked about volunteers and clients as well, and this may not be in the "records" database. For instance, you will want data that shows volunteer impact beyond just number of hours contributed; number of hours does NOT show program impact! You need feedback from surveys of volunteers, staff and clients, testimonials from all three of these groups, and other qualitative data!
If you must use an outside consultant, make sure that person builds the database on a simple software package and trains at least two staff members in how to alter the database design and structure as needed, so that you are not completely reliant on the consultant; or, again, make sure the staff person(s) who will use the database are directly involved in the purchase of a specialized package.
There are many simple computer database programs that don't require you to upgrade your computer to install, and that can be easily designed to track donors, volunteers, ticket-buyers, clients, staff, projects, etc. Designing a database in-house can be as simple as taking a couple of classes or looking at other organizations' information tracking systems. And there are LOTS of online discussion groups and free information sites for users of the most popular database programs, customer relationship management (CRM), content management systems (CMS) out there.
Even if you decide to use an outside consultant, it is a good idea to look for yourself at other organizations' information tracking systems, to get an idea of what qualities you do or don't want. The same is true if you do have to go with a specialized software package. Coyote Communications has a tip sheet on what to look for when shopping for software that can help you make the right purchase.
Also, you need a written policy regarding privacy for those who are in your database. How confidential is this information? Will any of it be shared with other organizations, or published in your annual report? This written policy needs to be communicated to ALL staff at your organization, and communicated to those who provide you their information.
Another example -- a key supporter leaves the company where you were sending his or her information, and the company won't give you forwarding information. You remove the person from the database, instead of flagging them not to receive mail until the correct address is found. A board member then could ask if that person is on the database, and you would say no, and the board member would wonder what kind of database manager you are anyway, not having such an important person on the database. If you flag the person instead, your answer would be "Yes, but that person recently left Acme Systems and hasn't received information from us since last month. I don't have a forwarding address. Do you have information?"
However, you should regularly remove duplicate records from your database, as well as people who have moved outside of your targeted area, are deceased, or have had a bad address in your system for a year or more.
These tip sheets may also help you:
This comprehensive web site provides detailed information about a variety of technology-related issues specifically for mission-based organizations. This includes resources and advice regarding databases. It provides some of the best information you can find regarding technology resources for mission-based organizations. TechSoup is a non-profit organization based in San Francisco, California.
Base and Back Again
This is a series of tutorial articles that follow the creation of a database designed to serve as a birder's log, tracking birding field trips, bird sightings, etc. It's a great tutorial for anyone creating a database (not just regarding birds) using a database program from NeoOffice, OpenOffice, Microsoft Office, or other similar programs.
Return to Index of Coyote Communications' Technology Tip Sheets
Disclaimer: No guarantee of accuracy or suitability is made by the poster/distributor. This material is provided as is, with no expressed or implied warranty.
Permission is granted to copy, present and/or distribute a limited amount of material from my web site without charge if the information is kept intact and without alteration, and is credited to:
Otherwise, please contact me for permission to reprint, present or distribute these materials (for instance, in a class or book or online event for which you intend to charge).