Best practice? - end of relationships/affiliations

We inactivate, but I’d say this is kind of an artifact policy from previous software: we set up our Tessitura in light of an established policy (rather than determined our organizational policy based on what might have the best results in Tessitura).  In the end, you just have to attend to inactive/active vis-à-vis relationship types in your reporting, list building, etc.  It works either way if you have a consistent documented organization-wide policy that everyone follows. 

John Trimble
Data and Prospect Manager
Dallas Symphony Orchestra
Morton H. Meyerson Symphony Center
Schlegel Administrative Suites
2301 Flora Street
Dallas, Texas 75201

214-871-4041 - phone
214-981-2988 - fax

j.trimble@DalSym.com
www.dallassymphony.com

From: Tessitura Development Forum [mailto:forums-development@tessituranetwork.com] On Behalf Of Tim Chandler
Sent: Monday, May 26, 2014 2:45 AM
To: John Trimble
Subject: [Tessitura Development Forum] Best practice? - end of relationships/affiliations

Hi all,

I'm just wondering what some other users do when it comes to the end of relationships/affiliations. We really only use this function to record employers/employees, including board members. We have been having a discussion on whether we should be inactivating a relationship when someone's employment ends or just putting in a start and finish date.

My immediate preference is to inactivate as it still keeps the record on the individuals account and doesn't show up as an active affiliation when you load the employer's record. Are there any advantages when it comes to reporting for either method?

Thanks,
Tim 

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Development Forum. You may reply to this message to post to the Development forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

We inactivate, but I’d say this is kind of an artifact policy from previous software: we set up our Tessitura in light of an established policy (rather than determined our organizational policy based on what might have the best results in Tessitura).  In the end, you just have to attend to inactive/active vis-à-vis relationship types in your reporting, list building, etc.  It works either way if you have a consistent documented organization-wide policy that everyone follows. 

John Trimble
Data and Prospect Manager
Dallas Symphony Orchestra
Morton H. Meyerson Symphony Center
Schlegel Administrative Suites
2301 Flora Street
Dallas, Texas 75201

214-871-4041 - phone
214-981-2988 - fax

j.trimble@DalSym.com
www.dallassymphony.com

From: Tessitura Development Forum [mailto:forums-development@tessituranetwork.com] On Behalf Of Tim Chandler
Sent: Monday, May 26, 2014 2:45 AM
To: John Trimble
Subject: [Tessitura Development Forum] Best practice? - end of relationships/affiliations

Hi all,

I'm just wondering what some other users do when it comes to the end of relationships/affiliations. We really only use this function to record employers/employees, including board members. We have been having a discussion on whether we should be inactivating a relationship when someone's employment ends or just putting in a start and finish date.

My immediate preference is to inactivate as it still keeps the record on the individuals account and doesn't show up as an active affiliation when you load the employer's record. Are there any advantages when it comes to reporting for either method?

Thanks,
Tim 

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Development Forum. You may reply to this message to post to the Development forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!