The difference between Termination Reason and Leave Type

This is helpful to know. Also, your Type can be used to define your attrition metrics. 

For us, we have 12 “Types” and (Voluntary/Involuntary, Regrettable/Non-Regrettable, Pass Probation/Did Not Pass Probation/NA). 

Historically, our company has counted voluntary leavers that were outside their probation period so we were able to set up our metrics to match. 

For the Reasons, we use the same ones that we have on our exit survey but it’s an easy way to look at them to see if there are trends. 

Hi,

This is super useful, it would help me if someone could point me to where the Leave Types are tied to the attrition metrics?

Thanks

Simon

Hi ​@Simon Walker 

I’m not sure if we have that exact information available, but you can read more about our attrition indicators here: View attrition indicators

🤓

hello! 
by chance, continuing this thread, do you know if it’s possible to somehow update the historical data?
I mean that we are cleaning up now the leave types and termination reasons, and at some point of time we’d need to “correct” the historical data so that we can have a consistent data base throughout the time. 

Hi ​@dammerung! If the fields need to be updated: you’ll need to trigger the termination flow again and change the fields in the flow.
This will update the information to the correct items you need, in the Lifecycle table for the users.
We do not have a bulk option to update termination details.

Hello, this is useful but I don’t understand how we differentiate between the various leaves (Leave / Parental / Termination) to make the reason and type relevant. Currently we have the same drop-downs appearing for all of the above and this doesn’t make sense. Have we set this up incorrectly?

Hi ​@MarkBoormanRecursion you would need to update this via System Settings > Data Management > People’s Data Fields and locate the list for the Leave Type and Reason. 

Hi ​@Kiare Tavarez , I can update the leave reasons and the termination reasons in data management but the Termination reason and the Leave reason seem to have the same list linked, and I can not edit the list in one without it automatically updating the list in the other.  Any Ideas?

That’s exactly my issue with this. I raised a support ticket but it seems that this is currently how the lists work, which is confusing as we want to open this up to MSS. However, I understand that a lot of clients have raised this and they are looking to add this to their change log. 

​@Celine Bocchi and ​@MarkBoormanRecursion I have this same issue with the combined Termination/Leave Reason list. It’s not logical to me and is skewing our data.

Did you find a workaround?

I attempted to create a new field for one of them but the Leave/Termination Flows require this field to be included, which would then mean duplication and confusion for the team. I tried to delete the field altogether, but it won’t let me do that either.

Thanks!

hi ​@Claire Newell  in the end I just added exactly the same fields to both and explained to everyone that it is just an old legacy thing of Bob’s that they haven’t gotten rid of yet, and to put the same reason twice.