Hello everyone, this idea was delivered in Service Pack 36. Please check out the What's New to learn more about the new Gender code table field, including a sneak peak into phase 2 areas to be delivered in a future service pack.

Hi all, I want to comment that this is still a really important issue (see also the merged idea noted above). We need to ensure we are able to address our consituents as they wish to be addressed, including their gender, title and pronouns, all of which could exist in any combination. Thanks!

Hello everyone! We are going to be conducting customer preview calls in late May, starting around May 17th through the end of the month. We are looking for a few more participants to be included. If you would like to participate in a session (no more than 30 minutes), then please send me an email at daisy.alarcon@blackbaud.com with your availability. Thank you!

Hello Joe, we don't have copy of the prototype to share, but I can share with you that after our research and discussions with customers we will implement this as a new code table field in place of the existing Gender field. All of the functionality that you are now familiar with in other code table fields would be available with the new Gender code table field.

Hello! Is there any way to get a copy of the prototype? Thank you!

Hello! We have a quick update to share: we have completed prototyping sessions with customers, as well as the technical research with our engineering teams. We have an estimate of effort that we are looking to plan for execution in 2023. We will continue to keep you all posted on this idea item as we reach our next milestones of progress. Thank you!

Hello everyone! We are kicking off our prototyping sessions and scheduling now starting September 12th through September 23rd. If you would like to participate in a session (no more than 30 minutes), then please send me or Pat Conley an email at daisy.alarcon@blackbaud.com / pat.conley@blackbaud.com with your availability and we will schedule a meeting with you to view the prototypes and provide us with some quick, direct feedback. Thank you!

Hello everyone, Daisy here from the Blackbaud Product team. We have some great news to share: we have officially wrapped up discovery! Thank you to everyone who participated. We will now kick off the prototyping and technical feasibility phase of this work. In the meantime, we still want to hear from you! Everyone is invited to please fill out this short 2 minute survey on how your organization uses Gender. Thank you in advance for your feedback.

Update: Discovery is kicking off in the next two weeks! We will be reaching out to set up discovery sessions to dive into your requirements in more detail.

Update: We plan to start discovery on this in late Q2.

Note: SickKids Foundation has produced a user story (as part of the Canada BBCRM User Group) which has been submitted to Blackbaud Product Management. Several organizations have reviewed the user story as well. Now it's over to Blackbaud Product Management to review this user story.

I too would like to see this user story prioritized, especially given this idea now has 97 votes. We all collectively owe this to our donors.

Please count me in on the discovery. Please consider adding an options for capturing pronouns as part of this work as several have suggested. We would like pronouns to be able to be displayed prominently on the constituent records (ideally at the top of the screen next to their name).

@Gibbs Gibson: As far as handling only common Anglo names: you can add more defaults to handle any name you want. I work for a Jewish organization that commonly uses a lot of names that are not in the standard list, but we have added some to make our lives easier. Go to Constituents > First Names and you'll see a list of the defaults, where you can add or edit the default genders for first names. Of course, this does nothing about the problem that is at the heart of this idea, but it sounds like it might make your life easier.

Please prioritize this to be available by Jan 2022 or sooner. Year end appeals bring a new slate of donors that need this option. It makes all of us look antiquated and outdated. I think Salesforce has offered this since 2019. https://www.salesforce.org/blog/6-ways-to-put-equality-in-your-crm/

Count me in on the discovery. I work at a higher ed where the focus would be to capture how the constituent would like to be addressed, but we are not a specifically LGBTQ+ org. I would recommend including folks from such orgs, as well as a varitey of other types of orgs, as we are all going to have different needs. Handling pronouns and titles, as well as the issues with assuming gender based on first name should also be discussed.

We are planning to start discovery on this item next year. The exact time frame is still uncertain, but we will be reaching out for participants once we get started.

Please do /something/ on this front or at least plan to address it. The current field is pretty flawed--not only are the options hardcoded in ways little else is in the database, but they populate automatically based on assumptions about only common Anglo names. It is not great in several dimensions.

Hi Kelli - we do indeed continue to monitor the idea bank! And we have particularly noticed the recent uptick in interest in this one. We are reviewing our 2022 plans but have not made any final decisions.

Since someone recently asked about this in the forum, just popping back in to see if there is any movement, or if anyone ever looks at the ideal bank. This is LONG overdue. The attribute customization is not a solution. The Gender field should run on a code table, like most other fields do. Why exactly was it hard-coded to begin with? Keep up blackbaud!

Can we please implement this change ASAP so we can be more inclusive in our communications to our constituents? Can we also make it configurable so we can add as many options as needed?