Welcome to Forums Sign in | Join | Help | Forums
in Search


Best Practices - coding Trustees and Former Trustees

Last post 11-13-2008 5:04 PM by Sage Evans. 1 replies.
Page 1 of 1 (2 items)
Sort Posts: Previous Next
  • 11-13-2008 12:07 PM

    Best Practices - coding Trustees and Former Trustees

    We are beginning a thorough scrubbing of our database and are looking to see what other organizations do with Trustees and Former Trustees.

    Currently, we have Trustee as a constituent code and when they are no longer a Trustee it changes to Former Trustee.  with that process we lose the dates that they were a Trustee. 

    We were considering using attribute, but that doesn't provide enough options for information.  This information needs to be able to be queried on as well, so notes aren't the best plan.   

    We would like to see how other people code them and where the historical information is entered. 

    Any suggestions would be greatly appreciated.  

    Heidi 

     

  • 11-13-2008 5:04 PM In reply to

    • Sage Evans
    • Top 100 Contributor
    • Posts 79
    • Organization: Grand View University
    • Products:  The Raiser's Edge

    Re: Best Practices - coding Trustees and Former Trustees

     We currently use the dates aspect of the constituency codes - changing them as you do from Trustee to Past Trutee.  As long as the Past Trustee is at the top of the list it will pull correctly for funding reports, and the dates help us remember when the changes in status were made.

     Do you have negative impacts with using the dates?  I'd be interested in hearing about that.

    Sage Evans
    Advancement Database and Records Manager
    Grand View University
    Filed under:
Page 1 of 1 (2 items)