We look at ALL the employee’s Lifecycle Status records, then compare each record with the one previous to it - in order not to miss any changes done within a period.
Per record, we look at an employee in the selected period and make sure the employee was employed (LC Status = Employed / Leave / Garden leave / Parental leave) and check if this employee existed in the previous record:
-
Didn’t exist in the prev record = LC Status is empty and the employee was never in the system therefore the current record of the employee counts as a join
-
Employee Existed in the prev record
-
In case lifecycle Status = Terminated, Hired ( in the prev record) then the current record of the ee counts as a join
-
In case the employee’s Lifecycle Status = Employed / Leave / Garden leave / Parental leave (in the prev record) and now Lifecycle Status = Employed then the employee record is not counted as a join
**Back-to-back**: the only exception is in cases where the employee was not in headcount (terminated) a day before and the next day is on headcount. In this case we will not count the employee record as a join.
This case should provide a solution for relocation cases/contractors that become company employee’s, where the employee is terminated and employed right after.
Examples:
-
Simple case
Date range: 1.1.2022 - 31.12.2022
| Effective Date | LifeCycle status | EE id | |
| 1.3.2022 | Employed | 123 | |
| 1.6.2022 | Terminated | 123 | |
| 1.9.2022 | Employed | 123 |
In 2022 we’ll count the employee 123 as joined twice: once in 1.3.2022 (new Lifecycle record which is in headcount, no previous status) and in 1.9.2022 (new Lifecycle record which is in headcount, and previous Lifecycle status of no in headcount)
Note:
*On a yearly view the employee will be presented only once in the grid, with its recent Lifecycle status (employed, start date: 1.9.2022) . Customers will be able to see both records on a monthly view.
*In cases the employee joined, terminated then joined again at the same month only the most recent Lifecycle record will be presented in the grid
-
Back-to-back
Date range: 1.1.2022 - 31.12.2022
| Effective Date | LifeCycle status | EE id | |
| 1.3.2022 | Employed | 123 | |
| 1.6.2022 | Terminated | 123 | |
| 2.6.2022 | Employed | 123 |
In 2022 we’ll count the employee 123 as joined once: only in 1.3.2022 (new Lifecycle record which is in headcount, no previous status) and we’ll ignore the record from 2.6.2022
(since the employee joined the next day after he was terminated)
-
Ignore leave cases:
Date range: 1.1.2022 - 31.12.2022
| Effective Date | LifeCycle status | EE id | |
| 1.3.2022 | Employed | 123 | |
| 1.6.2022 | Paternal Leave | 123 | |
| 1.9.2022 | Employed | 123 |
In 2022 we’ll count the employee 123 as joined Once: once in 1.3.2022 (new Lifecycle record which is in headcount, no previous status) and we won’t count the record from 1.9.2022 (since the employee was on headcount both in the 1.6.2022 and 1.9.2022 )