Raiser's Edge

Ryan Hyde:

Joanne Felci:

lots of ways you can do this - just depends how you want to set up the structure for it


I'd recommend an attribute


but a Con Code would also work


If you are asking about the Prospect Module then I'm not sure as we do have it but don't really use it.

I'd definitely recommend an attribute for this.


For example, let's say you build an attribute called "MG Prospect." You can then use the description to indicate why exactly they are a prospect, so maybe create a table called "MG Prospect Types" and populate it with things like "one time gift of $1k+," "Staff identified," "Identified property value," "Board Member," and anything else you can think of (all of these are examples - you should come up with your own set of definitions that make sense for your org).


You can then add these attributes to records either by manually adding them (in the case of "staff identified") or by doing a query + global change (which you'd do for the case of "one time gift of $1k+"). 


Also, always add a date when adding these kinds of attributes!


Then you just have to decide what you do when someone is in fact an identified MG donor. Do you want to keep the attribute on there or delete it? How do you identify an MG donor? Is that another attribute, or do you have the Prospect module and identify them through there? Or just by adding a MG Solicitor relationship to their record? 


The options are endless. There's lots of ways to do this stuff, so just spend some time figuring out what you'd like to do with your data, and then figure out how to get from where you are to where you need to be to do those things you want to do.