How do you code non working constituents
How are people marking constituents that used to have a primary business associated with them but have now retired.
I'm thinking of putting it in a note but wondered what others do
Comments
-
@Joanne Felci we use the relationship Date From/Date To with a relationship of former or retired partner or employee. We also add a Note that the person retired from said company. We then usually have to change primary/preferred email address and mailing address.
2 -
@Joanne Felci Great question.
In the db I inherited they have done a variety of things.
- New primary Org relationship of “Retired” and date from
- On last org relationship added “Retired” in front of data in the position field
- On last org relationship move position to our previous position attribute on the relationship and put ‘Retired’ as new position.
- Just put a ‘date to’ on current
These all still remained marked as primary org relationship.
Because we do a phonathon I found option 2 to be the best. It provides phonathon vendor with company and their position as we have a number that do matching gifts. When it's not there I was always getting updates/corrections that they were retired or who their employer was so $ could be matched.
4 -
@Joanne Felci I think for retirement, it's safe to use the position field. We also have a relationship of “Retired/Former Employee” that we use. That way, it still shows up as a relationship, and people in NXT can see it.
3 -
thanks for everyone's responses!
We are going to go with an organizational relationship with RETIRED - (NAME OF COMPANY) and if we know the date they left the company put that in the From field…also selecting Retired from the position pull down.
0 -
@Joanne Felci
? We do something similar: we use a Relationship Position type of “Former contact”.0
Categories
- All Categories
- 6 Blackbaud Community Help
- 211 bbcon®
- 1.4K Blackbaud Altru®
- 402 Blackbaud Award Management™ and Blackbaud Stewardship Management™
- 1.1K Blackbaud CRM™ and Blackbaud Internet Solutions™
- 15 donorCentrics®
- 360 Blackbaud eTapestry®
- 2.6K Blackbaud Financial Edge NXT®
- 655 Blackbaud Grantmaking™
- 576 Blackbaud Education Management Solutions for Higher Education
- 3.2K Blackbaud Education Management Solutions for K-12 Schools
- 941 Blackbaud Luminate Online® and Blackbaud TeamRaiser®
- 84 JustGiving® from Blackbaud®
- 6.7K Blackbaud Raiser's Edge NXT®
- 3.7K SKY Developer
- 248 ResearchPoint™
- 120 Blackbaud Tuition Management™
- 165 Organizational Best Practices
- 240 Member Lounge (Just for Fun)
- 34 Blackbaud Community Challenges
- 37 PowerUp Challenges
- 3 (Open) PowerUp Challenge: Grid View Batch
- 3 (Closed) PowerUp Challenge: Chat for Blackbaud AI
- 3 (Closed) PowerUp Challenge: Data Health
- 3 (Closed) Raiser's Edge NXT PowerUp Challenge: Product Update Briefing
- 3 (Closed) Raiser's Edge NXT PowerUp Challenge: Standard Reports+
- 3 (Closed) Raiser's Edge NXT PowerUp Challenge: Email Marketing
- 3 (Closed) Raiser's Edge NXT PowerUp Challenge: Gift Management
- 4 (Closed) Raiser's Edge NXT PowerUp Challenge: Event Management
- 3 (Closed) Raiser's Edge NXT PowerUp Challenge: Home Page
- 4 (Closed) Raiser's Edge NXT PowerUp Challenge: Standard Reports
- 4 (Closed) Raiser's Edge NXT PowerUp Challenge: Query
- 796 Community News
- 3K Jobs Board
- 54 Blackbaud SKY® Reporting Announcements
- 47 Blackbaud CRM Higher Ed Product Advisory Group (HE PAG)
- 19 Blackbaud CRM Product Advisory Group (BBCRM PAG)




