Adding constituents - who do you add / criteria?
Hello all ?
Could anyone share their criteria for who they add to RE? My initial thoughts are:
ADD TO RE IF
- They donate directly or buy event tickets directly
- They raise funds or volunteer for us IF we have a full name and valid contact details
- They are staff at our org
- They are on one of our committees
- They attend an event and supply their full name and valid contact details
I'd love to hear what your thoughts are on these / any other criteria (e.g., adding those who have given via sponsoring someone (e.g., Just Giving / Raisely etc.), adding those who want to receive regular emails from you etc.)
It would be fab to hear from a variety of different orgs.
Thanks all ?
Comments
-
@Suzie Capps
anyone that has gift obvsiouly get in REanyone that join our physical event (exception is guest of a registered guest where we do not have any other contact info of, they will remain as nonconstituent guest)
we add staff, board member, lay leader, prospect that we have more than just name (at least need another contact info such as phone, email, address)
3 -
@Suzie Capps - Agree with Alex, there needs to be an additional stipulation that someone only gets added to RE if they have contact info, only a name isn't much help with future fundraising initiatives.
0 -
@Suzie Capps The criteria differs wildly from organization to organization, so I won't speak too much to that, but I can say that there is a minimum amount of information needed for us to create a record.
- Full name
- 1 form of contact (address, email, phone)
- Constituency
Your constituent code table should define who is in your database. There's nuance to things such as gift donors or event attendance that may be determined by your business practices. For instance, some organizations create full constituents for spouses, while others do not. I don't know if creating records for staff is necessary until it's necessary, if that makes sense. I generally go with the thought of if I think they need a record and I have the necessary information, then it's probably a good idea to create that record.
If I'm asked to create a record that seems incomplete, then I require context. Creating records to go back and merge later seems silly.
1
Categories
- All Categories
- 6 Blackbaud Community Help
- 213 bbcon®
- 1.4K Blackbaud Altru®
- 403 Blackbaud Award Management™ and Blackbaud Stewardship Management™
- 1.2K Blackbaud CRM™ and Blackbaud Internet Solutions™
- 15 donorCentrics®
- 360 Blackbaud eTapestry®
- 2.6K Blackbaud Financial Edge NXT®
- 656 Blackbaud Grantmaking™
- 577 Blackbaud Education Management Solutions for Higher Education
- 3.2K Blackbaud Education Management Solutions for K-12 Schools
- 940 Blackbaud Luminate Online® and Blackbaud TeamRaiser®
- 84 JustGiving® from Blackbaud®
- 6.7K Blackbaud Raiser's Edge NXT®
- 3.7K SKY Developer
- 249 ResearchPoint™
- 119 Blackbaud Tuition Management™
- 165 Organizational Best Practices
- 241 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)



