• Replies 3 replies
  • Subscribers 411 subscribers
  • Views 140 views
  • Users 0 members are here
Related

Tracking former/past workers on Plans

Former Member
Former Member $organization

Hi everyone,

We are trying to figure out the most effective and least disruptive way to track past workers for a given plan.  Taking advantage of the new functionality (and new staff), we are reviewing our plans and doing a lot of reassignment of plans.  We don't want to lose the history of who the worker was (and there is no way to inactivate a worker on a plan).  I also don't want to come up with a system which makes it complicated in any way for anyone to run a Plan Summary report.  Some staff have been just unchecking the "portfolio" box for the outgoing worker, and someone suggested creating a worker role "Past Worker" which would default to not being in their portfolio, but both of those are problematic, as you can't specify worker type to effectively remove them from an officer's portfolio in a basic Plan Summary run.  I created a plan step type called "Portfolio Transfer" which requires a description, the step date, a worker, and notes (other dates and warn days not available), but it's an extra step in an already manual process which likely will be overlooked.  Has anyone tackled this yet?  Thoughts?

Thanks in advance!

Parents
  • $organization

    What about creating a new Worker Type of “Former Blah Blah”?

     

    Marie

     

    ---

    Marie Kocher | Development Assistant

    Kansas City Ballet | Todd Bolender Center for Dance & Creativity

    500 W. Pershing Road, Kansas City, MO 64108

    816.216.5582 (D) | 816.931.2232 x1382 (O) | 816.931.1172 (fax)

    kcballet.org

     

    From: Tessitura Development Forum [mailto:forums-development@tessituranetwork.com] On Behalf Of Carla Moy
    Sent: Thursday, February 05, 2015 6:49 PM
    To: Marie Kocher
    Subject: [Tessitura Development Forum] Tracking former/past workers on Plans

     

    Hi everyone,

    We are trying to figure out the most effective and least disruptive way to track past workers for a given plan.  Taking advantage of the new functionality (and new staff), we are reviewing our plans and doing a lot of reassignment of plans.  We don't want to lose the history of who the worker was (and there is no way to inactivate a worker on a plan).  I also don't want to come up with a system which makes it complicated in any way for anyone to run a Plan Summary report.  Some staff have been just unchecking the "portfolio" box for the outgoing worker, and someone suggested creating a worker role "Past Worker" which would default to not being in their portfolio, but both of those are problematic, as you can't specify worker type to effectively remove them from an officer's portfolio in a basic Plan Summary run.  I created a plan step type called "Portfolio Transfer" which requires a description, the step date, a worker, and notes (other dates and warn days not available), but it's an extra step in an already manual process which likely will be overlooked.  Has anyone tackled this yet?  Thoughts?

    Thanks in advance!




    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!

  • $organization in reply to Marie Kocher

    I might not entirely understand what you'd like as your final result but can you use Plans Maintenance to catch all of this worker's movement in one go? If you create a step type of 'Portfolio Manager Updated' could you bulk update a list of the outgoing staff member's Plans with this Step and an action and assignee? Then you don't need to remove the worker as such but there is a historical note of a change in portfolio manager and a resulting action? 

    As above, If you add a worker type 'Past Staff' then bulk update the outgoing staff member's worker type to this, it keeps the worker there for reference. Plan Summary could be run against a list to pick up Plans in this status/step type to ensure no-one falls through the gap. 

    For 'floating plans', we have an additional 'ghost' worker called 'Prospect Potential' which we can transfer ownership to whilst in portfolio limbo and constantly check & pull reports on. I don't know if that would be useful? 

     

Reply
  • $organization in reply to Marie Kocher

    I might not entirely understand what you'd like as your final result but can you use Plans Maintenance to catch all of this worker's movement in one go? If you create a step type of 'Portfolio Manager Updated' could you bulk update a list of the outgoing staff member's Plans with this Step and an action and assignee? Then you don't need to remove the worker as such but there is a historical note of a change in portfolio manager and a resulting action? 

    As above, If you add a worker type 'Past Staff' then bulk update the outgoing staff member's worker type to this, it keeps the worker there for reference. Plan Summary could be run against a list to pick up Plans in this status/step type to ensure no-one falls through the gap. 

    For 'floating plans', we have an additional 'ghost' worker called 'Prospect Potential' which we can transfer ownership to whilst in portfolio limbo and constantly check & pull reports on. I don't know if that would be useful? 

     

Children
No Data