Hello there,

 I didnt mean Donor as Catch all code. Pardon Me if i didnt make myself clear. We use Enquiry as the catch all code. From there they can become any one as member/Patron ans just Donor. In our organisation we often get donations directly from people who we dont know in first place at all. in that case we will create a record and add them as a donor- samethings goes when someone pays fee for our event but they will have an attribute saying Event Participant.

I fully agreee that naming 'Donor' for catch all category will be very misleading. Individual is appropriate but we use Enquiry.

Cheers! Its five 5.30 pm. Home time!

 I am new to my organization and have taken on the task of updating our RE protocols. One area we are working on is constituency codes. As we move forward we will be decreasing our constiuency codes drastically. Our codes are out of control, even for an organization with a complex set of constituencies.

 Our catch-all CC currently is Friend of the Eye - someone who has expressed interest in our mission in some way. We also have a the code Contributor, only to be used for someone who sends a gift with no other connection to our organization. I can see why we need to actully revert those records to Friend of the Eye. ( OK to code those who are contributors and not contributors as Freind of the Eye - what ties them togehter is they have expressed some connection to our mission ( sending a gift, attending an event, asking for a brochure, etc) but do not meet the criteria for any of our other constituencies.

 Melissa, can I hire you? 

LOL - maybe!

I see no need for the contributor code.  To get Friend records who are contributors simply add gift criteria to your query.

You don't need a speical constitutency code for donors.  You can pull them or distinguish them with a gift report or query.  Be careful how you code employees.  You could get yelled at by members of the forum.   

Cindy,

Did you get yelled at?  What for?  Was it me?  I hope not (and if not, I'll beat up whomever yelled at you.  LOL.) 

Missed you at the last few conferences.

Melissa

It wasn't you.  You are always very helpful.  They didn't exactly yell but they made it perfectly clear that we shouldn't have a code for alumns who are also employees.  (I knew that, but I can't change the rules here.)

Why would be be bad to have a CC for an alum who is now an employee?

We employ this system, and often use it to exclude from certain campaigns (hilariously, the staff who were alumni here don't much enjoy supporting the university).

Furthermore, if it's a bad approach, how else can we hold this information?

Cheers,
Pete