TEAMS - Calculation of Team Autostatuses

There are two Autocalculated statuses in TEAMS: ‘Performance’ and ‘Retention'

Autostatuses are calculated for each level:

  1. Stream level – all team members, connected with the Stream only

  2. Project level – all team members, connected with Project and child Streams

  3. Account level - all team members, connected with Account and child Projects

  4. Business Unit level - all Employees, connected with Business Unit and child Business units, Accounts and Projects

Team Performance autostatus (Performance Meet+ Index)

The status is calculated based on team members' Performance Evaluation provided in TEAMS. Performance value can be changed in the Personal Profile or from the Performance Evaluation perspective.

Performance with border.png
123.png

The logic of calculation

Autostatus is set based on an index. 

Performance Meet+ index = (Sum of team members per level with performance values higher or equal "Meet expectations") / (Amount of all active team members per level)

After the index is calculated - the status according to this index is set:

  1. 0 <= index < 0.5 then Autostatus is RED

  2. 0.5 <= index < 0.8 then Autostatus is AMBER

  3. 0.8 <= index <= 1 then Autostatus is GREEN

Only active at the moment team members are included into the calculation.

Mapping between Performance index and Health score

Please find the table with mapping between the Performance index and Health score below:

Performance index (%)

Health score

Performance index (%)

Health score

100

5.00

[98-100)

4.90

[96-98)

4.80

[94-96)

4.70

[92-94)

4.60

[90-92)

4.50

[88-90)

4.40

[86-88)

4.30

[84-86)

4.20

[82-84)

4.10

[80-82)

4.00

[78.5-80)

3.90

[77-78.5)

3.80

[75.5-77)

3.70

[74-75.5)

3.60

[72.5-74)

3.50

[71-72.5)

3.40

[69.5-71)

3.30

[68-69.5)

3.20

[66.5-68)

3.10

[65-66.5)

3.00

[63.5-65)

2.90

[62-63.5)

2.80

[60.5-62)

2.70

[59-60.5)

2.60

[57.5-59)

2.50

[56-57.5)

2.40

[54.5-56)

2.30

[53-54.5)

2.20

[51.5-53)

2.10

[50-51.5)

2.00

[45-50)

1.90

[40-45)

1.80

[35-40)

1.70

[30-35)

1.60

[25-30)

1.50

[20-25)

1.40

[15-20)

1.30

[10-15)

1.20

[5-10)

1.10

[0-5)

1.00

Team Retention autostatus (Attrition Risk Index)

The status is calculated based on individuals' Risk of Leaving and Critical Role on Unit statuses in TEAMS. The Risk of Leaving and Critical Role on Unit can be changed in the Personal Profile. Both sections should be filled in.

The logic of calculation

Autostatus is calculated if 30% and more of team members have set Risk of Leaving and Critical Role on Unit (both statuses should be filled in): ((Sum of team members with set Risk of Leaving and Critical Role on Unit values per level) / (Amount of all active team members per level) >=0,3).

If this value is lower than 0,3 - Autostatus GREY is set for this level automatically.

Otherwise: 

Autostatus is set based on the index. 

The System will compare the Risk of Leaving and Critical Role on Unit values:

Risk of Leaving

Critical Role = Low

Critical Role = Moderate

Critical Role = High

Critical Role = Critical

Risk of Leaving

Critical Role = Low

Critical Role = Moderate

Critical Role = High

Critical Role = Critical

Leaver

0

0

0

0

High

1

0

0

0

Medium

1

1

1

0

Low

1

1

1

1

If team member's Impact on the Project is undefined or isn't actual the system calculates as Impact = Low.

Attrition Risk Index = 1 - (sum of points according to the table above for every team member with set Risk of Leaving and Critical Role on Unit) / (Amount of active team members with set Risk of Leaving and Critical Role on Unit)

After the index is calculated - status according to this index is set:

  1. 0,2 < index <= 1 then Autostatus is RED

  2. 0,05 <= index <= 0,2 then Autostatus is AMBER

  3. 0 <= index <= 0,05 then Autostatus is GREEN

Only active at the moment team members are included into the calculation.

Recalculation triggers

Recalculation of both these autostatuses are triggered by:

  1. Updating profile (Performance Evaluation, Risk of Leaving or Critical Role on Unit values)

  2. Deactivation of profile

  3. Activation of deactivated profile