FundSvcs Community

 View Only
  • 1.  Best Practices for Alumni Data: Ethnicity, DOB, and Student Record Imports?

    Posted 01-28-2025 10:01 AM

    I'm seeking input from other fundraising professionals (especially higher education) regarding data practices in alumni databases. Specifically:

    • Do you include ethnicity and date of birth (or at least year of birth) in your alumni records?
    • Do you import student records into your database while they are still students, or wait until after graduation?

    I'm particularly interested in understanding:

    • The business purposes or philanthropic strategies served by including ethnicity and date/year of birth.
    • Any associated security risks or liabilities with importing these data points. (Is inclusion worth that risk?)
    • Whether the inclusion of these data points is defendable and aligns with best practices.

    We currently do not import ethnicity or date/year of birth and are evaluating whether doing so would be a responsible and strategic decision. I'd appreciate insights into who uses this data, how it's applied, and how it's managed. 

    Thanks in advance for any input on these topics. 



    ------------------------------
    Kathryn Rusak
    College for Creative Studies
    krusak@collegeforcreativestudies.edu
    ------------------------------


  • 2.  RE: Best Practices for Alumni Data: Ethnicity, DOB, and Student Record Imports?

    Posted 01-28-2025 10:10 AM
    Kathryn, a question to ask yourself is, do you have plans to use these data points if you decide to pull them in? I think there can be a "responsible and strategic" use for the data. However, there's no point in going to the effort if you do not have a plan to use the data.

    My clients and I have pulled in all of these elements from time to time, but only when we had those plans could we ensure the proper data protection. Your CRM already has built-in security protocols. The question is whether you have implemented appropriate confidentiality agreements and security levels.

    John

    John H. Taylor, Principal
    John H. Taylor Consulting, LLC
    2604 Sevier Street
    Durham, NC     27705

    919.816.5903 (cell/text)

    Serving the Advancement Community Since 1987






  • 3.  RE: Best Practices for Alumni Data: Ethnicity, DOB, and Student Record Imports?

    Posted 01-28-2025 10:24 AM
    • DOB, yes we store. Given the days of SSNs being in databases (good riddens!), the DOB becomes a great identifier when doing appends. If you plan to work with a data partner for data appends, the DoB will be helpful.  Additionally, for campaign counting, the DoB becomes important for counting planned gifts (CASE guidelines say 65+). 
    • Ethnicity, we store as well, but only self-identified.  We get data from the student information system (self-identified), and we've gotten it through some engagement activities. We have a very active Black Alumni Society and Latinx Society.   
    • We load students (and parents) as students; actually before they even step on campus. As soon as they pay deposit, we load them and their parents so we can do wealth screening. We remove the students after census that end up not attending NC State. 
    • Regarding security, your CRM should have some level of security. Additionally, your data governance should have different security levels/framework on various data elements. DOB is a "red" data element for us, so we are very restrictive on who that is provided to.  If we are going to share it with a vendor, that vendor has to be vetted through security and compliance to receive "red" or "purple" (SSN, biometrics, etc.). 
    • I personally think they are defendable, provided, to John's point, you have a business case for needing it.  At NC State, we do.

    Jeff





  • 4.  RE: Best Practices for Alumni Data: Ethnicity, DOB, and Student Record Imports?

    Posted 01-28-2025 12:37 PM
    In addition to John and Jeff's responses on DOB/ethnicity, 

    Regarding student records, your decision point may largely be impacted by the resources you have and what you would intend to do with those records. Usually, the reasoning for importing student records would be for connecting parent relationships, tracking scholarship awards, or for engagement prior to graduation. Consider though that all of these additional records will also require upkeep and maintenance at scale, and some platforms' licensing costs are tied to overall record counts.


    Matt Bain

    AVP, Management Consulting

    A MissionWired Company

    Join our Mailing List

    Connect with us on Social:

    LinkedIn | Facebook

    866-941-9874 x 168

    0cc4c400dc1f43f598d6e506195cfda6@zurigroup.com?anonymous&ep=signature" style="margin: 0">
    0cc4c400dc1f43f598d6e506195cfda6@zurigroup.com?anonymous&ep=signature" style="color: #0078D4; text-decoration: none; margin: 0">Book time to meet with me






  • 5.  RE: Best Practices for Alumni Data: Ethnicity, DOB, and Student Record Imports?

    Posted 01-29-2025 08:46 AM

    Jeff provided most of the responses I would give you - we even have the same process for loading students and parents in order to wealth screen. I would add that DOB is a very useful data point for research as well as a way to differentiate between parents and children or even unrelated people with the same name who attend your institution. I can't imagine how many records we might have merged if we didn't have DOB as a strong indicator that they were different people.



    ------------------------------
    Lianna Bodzin
    Colorado School of Mines
    lbodzin@mines.edu
    ------------------------------



  • 6.  RE: Best Practices for Alumni Data: Ethnicity, DOB, and Student Record Imports?

    Posted 01-29-2025 10:50 AM

    Hi Kathryn,

    Lots of good advice shared so far!  Some additional thoughts:

    • For DOB, I recommend limiting the amount of information that is shared, even internally.  Often the year is enough information to provide.  Even rating vendors will often work with just the year, as opposed to the full date.  Year and month may be required internally (for birthday greetings, etc.) but that can be done without revealing the actual date - that is the one field I suggest holding back on consistently (so that the birthdate cannot be compiled from a series of extracts).  Of course, externally you would still want signed confidentiality statements (and full security review if the entire date is released) but I always suggest trying not to release more than is needed in the first place.
    • Ethnicity is fine to obtain from the registrar, but there should be some transparency at time of collection on how that data is used.  If the registrar passes that data on to advancement, then that should be explained at time of collection (and yes, this could cause some complexity with historical data). 
    • Student data you will want to obtain before they are on campus, especially if it is to solicit parents.  Again, if you are collecting this information at enrollment to be used for advancement that should be transparent.  Potentially stating this is shared with alumni engagement and advancement to better engage and provide services. Also, under FERPA some students state that they do not want their "directory" information shared.  Institutions interpret this "opt-out" in various ways.  You may want to consult your legal counsel on the ability of the registrar to release this data to advancement. 

    Hope this is helpful.  You are on the right track by asking these questions. 

    Terry Callaghan

    AVP, Zuri Group



    ------------------------------
    Terry Callaghan
    Zuri Group
    terry@zurigroup.com
    ------------------------------