Gift Recognition proceedures - best practice?
Hi,
I wanted to check in to see if anyone has any suggestions or ideas on my method of gift recognition data entry.
When I came in to this org, they used an Addressee/Salutation field for Recogniton Name. This works, except for those cases when the recognition varies by gift (say, a donor makes a gift but wants this one gift anonymous, but her other gifts named a certain way.)
In my past org., what we did was use a "Recognition Name" as a gift attribute, that way we could track it gift by gift. The advantage to that for me was that if they gave two gifts in a year, each with a different recognition, both would then get picked up for our Annual Report listings. Ideally, I would like to do this again, and also keep the Addressee/Salutation field for their "most commonly used" recognition name so I have something to default to.
The nice thing about starting new jobs is the chance to clean up your own personal habits, so my question is... does anyone have any suggestions on why this is or isn't a good idea?
Thanks!
Ali
Comments
-
Aldera Chisholm:
Hi,
I wanted to check in to see if anyone has any suggestions or ideas on my method of gift recognition data entry.
When I came in to this org, they used an Addressee/Salutation field for Recogniton Name. This works, except for those cases when the recognition varies by gift (say, a donor makes a gift but wants this one gift anonymous, but her other gifts named a certain way.)
In my past org., what we did was use a "Recognition Name" as a gift attribute, that way we could track it gift by gift. The advantage to that for me was that if they gave two gifts in a year, each with a different recognition, both would then get picked up for our Annual Report listings. Ideally, I would like to do this again, and also keep the Addressee/Salutation field for their "most commonly used" recognition name so I have something to default to.
The nice thing about starting new jobs is the chance to clean up your own personal habits, so my question is... does anyone have any suggestions on why this is or isn't a good idea?
Thanks!
Ali
Mmmmm. Other than memorials/honorariums, our donors have one listing. Interesting that a donor would want different listings. How's the public going to know anyway, espeically if they opt for anonymous? But that's heading a different direction.
I can see where gift attribute would provide a better way to track this for you. However, I still really like Addressee/Salutation option as it auto populates and so much less chance of typos. We do a different recognition listing using add/sal for each fund. Maybe you could have multiple add/sal listings for "gift 1"/"gift 2"/"gift..."? Just use when needed and pull all for your listing.
I think trying to track their "most commonly used" recogition would be extra work especially if you're not pulling it for reports. Why bother?
My 2 cents...
0 -
JoAnn Strommen:
Mmmmm. Other than memorials/honorariums, our donors have one listing. Interesting that a donor would want different listings. How's the public going to know anyway, espeically if they opt for anonymous? But that's heading a different direction.
I can see where gift attribute would provide a better way to track this for you. However, I still really like Addressee/Salutation option as it auto populates and so much less chance of typos. We do a different recognition listing using add/sal for each fund. Maybe you could have multiple add/sal listings for "gift 1"/"gift 2"/"gift..."? Just use when needed and pull all for your listing.
I think trying to track their "most commonly used" recogition would be extra work especially if you're not pulling it for reports. Why bother?
My 2 cents...
I am also surprised by how often I come across this. Sometimes it's a family thing - they will do their "annual gift" as John and Mary Doe, but then will do a mid year gift and want it to be from "The Doe Family" as their kids were involved.
My biggest thing is wanting to ease running reports at the end of the year, to keep the queries as clean and simple as possible.
0 -
Aldera Chisholm:
I'd like to see some client docs on this. We recently had this conversation at my org. We're moving away from add/sal to gift attributes as well, but I worry that this is going to complicate reporting. For example, today I ran a quick constituent query of all in-kind donors and realized, I woudn't be able to get the publication listing from that query... I'd have to drill down into gift criteria to get the publication listing out!Hi,
I wanted to check in to see if anyone has any suggestions or ideas on my method of gift recognition data entry.
When I came in to this org, they used an Addressee/Salutation field for Recogniton Name. This works, except for those cases when the recognition varies by gift (say, a donor makes a gift but wants this one gift anonymous, but her other gifts named a certain way.)
In my past org., what we did was use a "Recognition Name" as a gift attribute, that way we could track it gift by gift. The advantage to that for me was that if they gave two gifts in a year, each with a different recognition, both would then get picked up for our Annual Report listings. Ideally, I would like to do this again, and also keep the Addressee/Salutation field for their "most commonly used" recognition name so I have something to default to.
The nice thing about starting new jobs is the chance to clean up your own personal habits, so my question is... does anyone have any suggestions on why this is or isn't a good idea?
Thanks!
Ali
0 -
Aldera Chisholm:
Hi,
I wanted to check in to see if anyone has any suggestions or ideas on my method of gift recognition data entry.
When I came in to this org, they used an Addressee/Salutation field for Recogniton Name. This works, except for those cases when the recognition varies by gift (say, a donor makes a gift but wants this one gift anonymous, but her other gifts named a certain way.)
In my past org., what we did was use a "Recognition Name" as a gift attribute, that way we could track it gift by gift. The advantage to that for me was that if they gave two gifts in a year, each with a different recognition, both would then get picked up for our Annual Report listings. Ideally, I would like to do this again, and also keep the Addressee/Salutation field for their "most commonly used" recognition name so I have something to default to.
The nice thing about starting new jobs is the chance to clean up your own personal habits, so my question is... does anyone have any suggestions on why this is or isn't a good idea?
Thanks!
Ali
I saw a post recently where someone said they had a Addressee/Salutation that said "see notes" and the alternate/irregular Recognition Name(s) was noted there. So that they could be caught every time.
I see a couple things I agree with from others that have posted to you.
1. Drilling down too many layers for something that should be easy to pull.
2. The Gift Attribute is not a field that is easily populated in any reports and I have found that I use the Recognition Name in reports, even internally so that department peeps know who the couple or family is that gave the gift, as opposed to just the individual person/HoH that the gift is recorded on.
3. Addressee/Salutation Configs are pre-populated and therefore less chance of typos and misspellings. You cannot do that if you drill down into another obscure area like Attributes.
Multiple Recognition Names listed on the Addr/Sal tab as someone suggested or the "see notes" Rec Name seem the safest. If you are not the only one adding this info, controlling the input/output could get sticky with what you are suggesting -- that there be a different name on every gift entry. As it is, you must clearly document and educate those that do data entry in order to keep your Addr/Sals and Rec Names clean and consistent.
0 -
Christine Cooke:
Christine - Not sure if it was my post you saw previously (it was in a different thread). We use a notepad called Recognition Name but ONLY for organization records, because org records don't have an addressee/salutation tab. It would be much better if there was an addressee/salutation tab for org records, so we could enter the recognition name as an addressee/salutation for BOTH individual and organization records. So the notepad is second choice....I saw a post recently where someone said they had a Addressee/Salutation that said "see notes" and the alternate/irregular Recognition Name(s) was noted there. So that they could be caught every time.
I see a couple things I agree with from others that have posted to you.
1. Drilling down too many layers for something that should be easy to pull.
2. The Gift Attribute is not a field that is easily populated in any reports and I have found that I use the Recognition Name in reports, even internally so that department peeps know who the couple or family is that gave the gift, as opposed to just the individual person/HoH that the gift is recorded on.
3. Addressee/Salutation Configs are pre-populated and therefore less chance of typos and misspellings. You cannot do that if you drill down into another obscure area like Attributes.
Multiple Recognition Names listed on the Addr/Sal tab as someone suggested or the "see notes" Rec Name seem the safest. If you are not the only one adding this info, controlling the input/output could get sticky with what you are suggesting -- that there be a different name on every gift entry. As it is, you must clearly document and educate those that do data entry in order to keep your Addr/Sals and Rec Names clean and consistent.
0 -
Aldera Chisholm:
We use Alias next to the name in Bio 1 - I like this better because you can use it for Orgs too.Hi,
I wanted to check in to see if anyone has any suggestions or ideas on my method of gift recognition data entry.
When I came in to this org, they used an Addressee/Salutation field for Recogniton Name. This works, except for those cases when the recognition varies by gift (say, a donor makes a gift but wants this one gift anonymous, but her other gifts named a certain way.)
In my past org., what we did was use a "Recognition Name" as a gift attribute, that way we could track it gift by gift. The advantage to that for me was that if they gave two gifts in a year, each with a different recognition, both would then get picked up for our Annual Report listings. Ideally, I would like to do this again, and also keep the Addressee/Salutation field for their "most commonly used" recognition name so I have something to default to.
The nice thing about starting new jobs is the chance to clean up your own personal habits, so my question is... does anyone have any suggestions on why this is or isn't a good idea?
Thanks!
Ali
1 -
Gina Gerhard:
Christine - Not sure if it was my post you saw previously (it was in a different thread). We use a notepad called Recognition Name but ONLY for organization records, because org records don't have an addressee/salutation tab. It would be much better if there was an addressee/salutation tab for org records, so we could enter the recognition name as an addressee/salutation for BOTH individual and organization records. So the notepad is second choice....yes! Gina, it was a different thread. I think I missed the detail that you were only doing that with Org records. Maybe someone else was also doing it with individuals? <shrug> I agree -- there should be the option of Addressee/Salutation for Org records and the Rec Name can be different from the Org Name.
0 -
Best if RE had a recognition module that helped us track all of these.
1 -
I have used an Additional Addr/Sal, but now use a Constituent Attribute of "Donor Listing" and like it much better.
Our default is the same as Home Addressee (i.e. Dr. & Mrs. Robert C. Hernandez), so I use a Default Set to load the Addr/Sal format that fits the Record (i.e. is the husband or wife the HOH, do they have the same last name, are there nicknames, etc.) then check the [Editable] box next to the Home Addressee, copy the text, uncheck the box (doesn't take nearly as long as it seems) and paste it into the Donor Listing Attribute (which is also added to the Record by the Default Set).
This means that Ind & Org Records have the donor listing/recognition name in the same place. The Attribute Date indicates when that text was last edited, and the Attribute Comments provide other information. So when a donor makes a specific request, we can note that in the Comment, or put "see ConstNote" and add a longer explanation or cut-and-paste of an email thread in a Note for future reference. In your case (we don't have any of these, thank goodness!), you could put a Comment in to manually review the Note when pulling a list...and then edit your list to include multiple listings per Constituent Record.
Attribute works great for me, and I like not having to drill down into Gift Attributes, or remember to add that Gift Attribute every time. We also list by donor, not by gift, so if that Gift Attribute text wasn't exactly the same, that would cause problems when pulling our list.
Also worth a mention...when I first set the Attribute system up (here and at my previous org), I used a series of Export/Imports to populate that field on every record. Still do that when we have a significant number of new records added at one time. Otherwise, I just do it as I enter new Constituents.1
Categories
- All Categories
- Shannon parent
- shannon 2
- shannon 1
- 21 Advocacy DC Users Group
- 14 BBCRM PAG Discussions
- 89 High Education Program Advisory Group (HE PAG)
- 28 Luminate CRM DC Users Group
- 8 DC Luminate CRM Users Group
- Luminate PAG
- 5.9K Blackbaud Altru®
- 58 Blackbaud Award Management™ and Blackbaud Stewardship Management™
- 409 bbcon®
- 2.1K Blackbaud CRM™ and Blackbaud Internet Solutions™
- donorCentrics®
- 1.1K Blackbaud eTapestry®
- 2.8K Blackbaud Financial Edge NXT®
- 1.1K Blackbaud Grantmaking™
- 527 Education Management Solutions for Higher Education
- 1 JustGiving® from Blackbaud®
- 4.6K Education Management Solutions for K-12 Schools
- Blackbaud Luminate Online & Blackbaud TeamRaiser
- 16.4K Blackbaud Raiser's Edge NXT®
- 4.1K SKY Developer
- 547 ResearchPoint™
- 151 Blackbaud Tuition Management™
- 1 YourCause® from Blackbaud®
- 61 everydayhero
- 3 Campaign Ideas
- 58 General Discussion
- 115 Blackbaud ID
- 87 K-12 Blackbaud ID
- 6 Admin Console
- 949 Organizational Best Practices
- 353 The Tap (Just for Fun)
- 235 Blackbaud Community Feedback Forum
- 55 Admissions Event Management EAP
- 18 MobilePay Terminal + BBID Canada EAP
- 36 EAP for New Email Campaigns Experience in Blackbaud Luminate Online®
- 109 EAP for 360 Student Profile in Blackbaud Student Information System
- 41 EAP for Assessment Builder in Blackbaud Learning Management System™
- 9 Technical Preview for SKY API for Blackbaud CRM™ and Blackbaud Altru®
- 55 Community Advisory Group
- 46 Blackbaud Community Ideas
- 26 Blackbaud Community Challenges
- 7 Security Testing Forum
- 1.1K ARCHIVED FORUMS | Inactive and/or Completed EAPs
- 3 Blackbaud Staff Discussions
- 7.7K ARCHIVED FORUM CATEGORY [ID 304]
- 1 Blackbaud Partners Discussions
- 1 Blackbaud Giving Search™
- 35 EAP Student Assignment Details and Assignment Center
- 39 EAP Core - Roles and Tasks
- 59 Blackbaud Community All-Stars Discussions
- 20 Blackbaud Raiser's Edge NXT® Online Giving EAP
- Diocesan Blackbaud Raiser’s Edge NXT® User’s Group
- 2 Blackbaud Consultant’s Community
- 43 End of Term Grade Entry EAP
- 92 EAP for Query in Blackbaud Raiser's Edge NXT®
- 38 Standard Reports for Blackbaud Raiser's Edge NXT® EAP
- 12 Payments Assistant for Blackbaud Financial Edge NXT® EAP
- 6 Ask an All Star (Austen Brown)
- 8 Ask an All-Star Alex Wong (Blackbaud Raiser's Edge NXT®)
- 1 Ask an All-Star Alex Wong (Blackbaud Financial Edge NXT®)
- 6 Ask an All-Star (Christine Robertson)
- 21 Ask an Expert (Anthony Gallo)
- Blackbaud Francophone Group
- 22 Ask an Expert (David Springer)
- 4 Raiser's Edge NXT PowerUp Challenge #1 (Query)
- 6 Ask an All-Star Sunshine Reinken Watson and Carlene Johnson
- 4 Raiser's Edge NXT PowerUp Challenge: Events
- 14 Ask an All-Star (Elizabeth Johnson)
- 7 Ask an Expert (Stephen Churchill)
- 2025 ARCHIVED FORUM POSTS
- 322 ARCHIVED | Financial Edge® Tips and Tricks
- 164 ARCHIVED | Raiser's Edge® Blog
- 300 ARCHIVED | Raiser's Edge® Blog
- 441 ARCHIVED | Blackbaud Altru® Tips and Tricks
- 66 ARCHIVED | Blackbaud NetCommunity™ Blog
- 211 ARCHIVED | Blackbaud Target Analytics® Tips and Tricks
- 47 Blackbaud CRM Higher Ed Product Advisory Group (HE PAG)
- Luminate CRM DC Users Group
- 225 ARCHIVED | Blackbaud eTapestry® Tips and Tricks
- 1 Blackbaud eTapestry® Know How Blog
- 19 Blackbaud CRM Product Advisory Group (BBCRM PAG)
- 1 Blackbaud K-12 Education Solutions™ Blog
- 280 ARCHIVED | Mixed Community Announcements
- 3 ARCHIVED | Blackbaud Corporations™ & Blackbaud Foundations™ Hosting Status
- 1 npEngage
- 24 ARCHIVED | K-12 Announcements
- 15 ARCHIVED | FIMS Host*Net Hosting Status
- 23 ARCHIVED | Blackbaud Outcomes & Online Applications (IGAM) Hosting Status
- 22 ARCHIVED | Blackbaud DonorCentral Hosting Status
- 14 ARCHIVED | Blackbaud Grantmaking™ UK Hosting Status
- 117 ARCHIVED | Blackbaud CRM™ and Blackbaud Internet Solutions™ Announcements
- 50 Blackbaud NetCommunity™ Blog
- 169 ARCHIVED | Blackbaud Grantmaking™ Tips and Tricks
- Advocacy DC Users Group
- 718 Community News
- Blackbaud Altru® Hosting Status
- 104 ARCHIVED | Member Spotlight
- 145 ARCHIVED | Hosting Blog
- 149 JustGiving® from Blackbaud® Blog
- 97 ARCHIVED | bbcon® Blogs
- 19 ARCHIVED | Blackbaud Luminate CRM™ Announcements
- 161 Luminate Advocacy News
- 187 Organizational Best Practices Blog
- 67 everydayhero Blog
- 52 Blackbaud SKY® Reporting Announcements
- 17 ARCHIVED | Blackbaud SKY® Reporting for K-12 Announcements
- 3 Luminate Online Product Advisory Group (LO PAG)
- 81 ARCHIVED | JustGiving® from Blackbaud® Tips and Tricks
- 1 ARCHIVED | K-12 Conference Blog
- Blackbaud Church Management™ Announcements
- ARCHIVED | Blackbaud Award Management™ and Blackbaud Stewardship Management™ Announcements
- 1 Blackbaud Peer-to-Peer Fundraising™, Powered by JustGiving® Blogs
- 39 Tips, Tricks, and Timesavers!
- 56 Blackbaud Church Management™ Resources
- 154 Blackbaud Church Management™ Announcements
- 1 ARCHIVED | Blackbaud Church Management™ Tips and Tricks
- 11 ARCHIVED | Blackbaud Higher Education Solutions™ Announcements
- 7 ARCHIVED | Blackbaud Guided Fundraising™ Blog
- 2 Blackbaud Fundraiser Performance Management™ Blog
- 9 Foundations Events and Content
- 14 ARCHIVED | Blog Posts
- 2 ARCHIVED | Blackbaud FIMS™ Announcement and Tips
- 59 Blackbaud Partner Announcements
- 10 ARCHIVED | Blackbaud Impact Edge™ EAP Blogs
- 1 Community Help Blogs
- Diocesan Blackbaud Raiser’s Edge NXT® Users' Group
- Blackbaud Consultant’s Community
- Blackbaud Francophone Group
- 1 BLOG ARCHIVE CATEGORY
- Blackbaud Community™ Discussions
- 8.3K Blackbaud Luminate Online® & Blackbaud TeamRaiser® Discussions
- 5.7K Jobs Board