Setting Up Appeal Codes
Options
Hi,
So far this community has been amazing with advice, and as a new user to RE I need all the advice I can get. So here I go again.
I would like to know how sites are using appeal codes. Do you have a set number of appeal codes that are used year after year or do you set them up each year with the year embedded in the code. i.e. DM16NEWS (Direct Mail 2016 Newsletter). I am looking at setting up a new gift coding process, currently we set up appeals each year. Does anyone have appeal codes that are used year after year, adding to the list when appropriate. Here's an example of what I am thinking:
CAMPAIGNS: "Hospital", "Research Centre", "CMN", or "Rehab Centre" (our 4 main fundraising branches)
APPEALS: "Spring Newsletter", "Fall Newsletter", "Equipment Appeal", "Mental Health Appeal", "Event", "Telefund", "Unsolicited", etc.
Packages: "Golf tournament", "Letter A", "Letter B", "Phone Call", "Race"
FUNDS: Unrestricted, Oncology, Equipment, ER, etc.
SUB-GROUP: Sponsorship, Event, Donation
This seems a lot cleaner then creating new codes each year, and easier for reporting. Does anyone do anything like this?? What are the potential downfalls?
Thanks, Rita
So far this community has been amazing with advice, and as a new user to RE I need all the advice I can get. So here I go again.
I would like to know how sites are using appeal codes. Do you have a set number of appeal codes that are used year after year or do you set them up each year with the year embedded in the code. i.e. DM16NEWS (Direct Mail 2016 Newsletter). I am looking at setting up a new gift coding process, currently we set up appeals each year. Does anyone have appeal codes that are used year after year, adding to the list when appropriate. Here's an example of what I am thinking:
CAMPAIGNS: "Hospital", "Research Centre", "CMN", or "Rehab Centre" (our 4 main fundraising branches)
APPEALS: "Spring Newsletter", "Fall Newsletter", "Equipment Appeal", "Mental Health Appeal", "Event", "Telefund", "Unsolicited", etc.
Packages: "Golf tournament", "Letter A", "Letter B", "Phone Call", "Race"
FUNDS: Unrestricted, Oncology, Equipment, ER, etc.
SUB-GROUP: Sponsorship, Event, Donation
This seems a lot cleaner then creating new codes each year, and easier for reporting. Does anyone do anything like this?? What are the potential downfalls?
Thanks, Rita
Tagged:
0
Comments
-
We do both. Ongong appeals are generic - e.g., Honorarium, Unsolicited, Donor Trip... Others do have dates embedded - e.g., MN201509 for the Marketing Newsletter for Sept 2015.
In very limited instances we use Packages to clarify the generic appeal - e.g., a Package of Rwanda2014 for the Donor Trip appeal to specify the 2014 Donor Trip to Rwanda0 -
Rita, you will find orgs do it both ways - same appeal code and one for each year. It needs to be based on the orgs needs.
While I like the idea of using the same, for most of mine I have the year. This is because the appeal especially at year end crosses our fiscal year end. So I'm not easily able to query filter by just the appeal name. December letter can get result in gifts to 2015 fund received in 2015 and in 2016. And after our cut off date, gifts go into 2016 fund. So, easiest for me is unique appeal names. Need to do what works.
Have some others that are generic and used every year.0 -
We use generic appeals. For those related to Events, we use a package for each year.0
-
We have three categories of appeals: ongoing, direct mail, and event.
Ongoing:
This includes things like Honor/Memorial (appeal = HM), third party fundraising (3PF), General (General, natch), etc.
My predecessor felt it necessary to create new iterations of these for every fiscal year (e.g., HM FY15). I, however, find that to be basically useless and labor intensive. I've switched us over to just using the same appeal year after year.
Direct mail:
Appeals are set for each new piece sent out, with packages denoting the ask level of each piece.
Nomenclature:
BD0715 A2
Appeal means: "Base Donors" July 2015 appeal, and the package A2 typically means an ask array of something like $15-$35
Note: My predecessor just used three digit appeal codes that went up sequentialy with each new piece (e.g. 437, 438, etc). Do not do this. If your'e going to have a code, make it mean something. There's no reason not to make data meaningful.
Event:
We create appeals for each year's event (e.g., Gala FY15, Gala FY16, etc.). I saw someone on here say that they use one appeal and denote different years via packages, but what we do is use package to track different types of giving within the event. So for our yearly gala, I have separate packages for silent auction, live auction, ticket sales, corporate sponsor, individual sponsor, cash call, etc. This helps year-over-year reporting a great deal. We know exactly what pieces of the event did better or worse than years past, and then we can decide how we want to strategize that piece of the event for the next year.
Overall, the goal is always to capture more data in a way that is not labor intensive. Data is good, but complicated data is unreliable because there's a higher rate of error.
Final note: don't overlook "appeal category" and "package category." These can be invaluable when trying to report on similar appeals and packages year over year, and there's lots of creative ways to use them.
1 -
[deleted]0
-
We use new appeal codes each year, for the most part. This helps us compare year to year results for a particular mailing. It's useful when you are looking at your donor trends or thinking about planning the next year's mailing calendar.0
-
Rita- JoAnn is right, orgs do it both ways depending on their needs. T
That said,personally, it seems redundant to me since you can pull reports based on date. I have the same appeals that are used year after year and do not have the year embedded in the appeal code.
I have, in the past, inherited databases that had embedded a year in every code and had used all these letters in the codes: AF09P (Annual Fund Appeal 2009 Parent), problem was, as there were different DB managers along the way, the shifted the format and were not consistent with what had been utilized before their arrival. It made deciphering and find all the appeals codes for reporting VERY difficult! I spend months housekeeping to figure out the coding and clean it up. So please, for yourself and whoever comes after you in a million years, please find a clear concise way of coding -- and/or keep a journal of the codes accessible for all in your department0
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