Need help regarding constituent code

@Junita Sutirto
we have 25 chapters (offices location), and that is our constituent code (i.e. New York, Long Island, Ohio, Los Angeles, Miami, etc), which is the primary code. (first line)

we also have other codes (i.e. National Board Member, Local Board, Advisory Board, Staff, Estate, Foundation, etc)

Do not use constituent code for giving related info (i.e. Major donor, monthly donor, etc), here's a good post that talks about this:

@Junita Sutirto Constituent codes should not be anything that relates to money such as monthly donors, major donors, etc. All of that information can be found out through the giviing history. Constituents codes are going to be different from organization to organization but they should be general and how you relate to these people or why they are in the database so such things as Staff, Board Member, Former Board Member, Parent, Alumni, Corporation, Foundation, Non-Profit, Volunteer, Student. Anything pertaining to money like Montly Donor or Major Donor is a really bad idea, because these type of things change all the time and who wants to constantly keep updating these codes, when you can find that information by the giving history. Most organization will also want to report on such thing as Board Giving or Alumni Giving, etc and this info can be pulled easily by the constituent codes of Board or Alumni.

@Junita Sutirto
If you read the post I replied with, you saw the pro and con of tagging vs not tagging based on giving level. So i'm not going to dissaude you if you do decide to do so.

IF you are going to tag, don't use constituent code, use a constituent attribute (custom field in webview terminology).

however, if all you want to do is being able to get a mailing list, email list, etc for “major” donor, then define what that major donor is (i.e. donor who gave $10K and up in any one of the last 10 years) and create a constituent query to target these donors.

@Junita Sutirto you can also create levels under Donor Categories. This is a table and there are multiple options you can set. At the moment, none of this will come out in NXT, but you will be able to run reports to see how many you have in each category. They are put in by the minimum amount they have given and go up to whatever the next category is.

That won't help with the recurring donors, but those can be handled using what @Alex Wong mentioned and Custom Fields/Attributes.

@Junita Sutirto At our organization, we do have some situations where the constituent does not really fall into any of our pre-existing constituent codes. For example, they may be some kind of representative for an organization (a lot of our clients are churches, so we frequently have their pastors, treasurers, etc. as constituents in on database as well). The constituent might also be someone we're pursuing for participation in some type of program, but they are not a participant just yet. For constituents who fall into this gray area, we have a constituent code of “Contact.” This is simply used as a filler for the field since it is required. In the future, that field may get replaced with another code (like Donor, Board Member, etc) if the person takes on some other type of role or relationship with our organization.