We are in the process of trying to clean up our records, including attributes and constituencies. In doing this, we've realized our constituencies tend to be repetitive with information found in other places in a Tess record. Out of curiosity --
What do you have constituencies for and why?
Does it seem like better practice to track your prospects for foundation, gov, individual, etc. in a solicitation rather than a constituency?
Thanks!
Hi Sara -
We tend to think of our constituencies as quick labels that are, for the most part, generated off other information in Tessitura. Most of our constituencies are all based on things stored elsewhere - ticket/donations, relationships, CSIs, attributes, solicitations, etc. We nightly wipe and reform most constituencies to make sure that the information is current. Our staff are trained (mostly) to view constituencies as a quick label, but not something that should be edited by them. We use it mostly as identifiers on the customer header and in reporting.
We've definitely gone the way of a solicitation for tracking prospects, and then my nightly script goes out, looks for an active solicitation and creates a constituency of the correct type.
HTH,
Heather