Understanding why reviews are shown (or not shown) in the recommended reviews

How does the engine calculate recommendations?

For each employee, the engine checks which of their reviews are found in Poplee Performance (including imported review dates). To identify a review type, the engine uses the category associated with the campaign. This enables it to determine from the reviews completed whether an employee has, for example, already completed a professional review or not.

The engine calculates the recommendations each time you view the "recommendations" tab, to keep them up to date.

If an employee has a review in progress in the rule category, they will not be recommended. In fact, even if the review has not been completed, the employee will not be recommended, as the engine considers the employee to be in the process of completing the review. Therefore, it makes no difference whether the review is in preparation, execution, approval or validation. 

The engine takes refused reviews into account , we consider a refused review to be a valid review.

The engine does NOT take archived reviews into account. Effectively, if the review has been archived, the employee no longer has the option to complete the review, so the engine won't take this review into account. 

The engine does not take into account employees who are excluded from the rule at the date you are planning. 

The engine recommends only one review for each rule per employee. For example, if an employee has missed several professional reviews, the engine will still only recommend one professional review for them. 

For a recurring rule, the engine uses:

- the reference date (e.g. contract start date) if no review has been completed

- the date of the last review, if a review has already been completed. The engine will then look at the preferred completion date that you defined as HR administrator when you added the reviews to the campaign, and not the date when the review was actually completed. 

For example, you have a recurring annual review rule that is applied every year, and as HR admin you have scheduled a review for Valentin with a completion date set for May 1, 2021. In reality, Valentin was delayed and actually completed his review on July 1, 2021. Under this rule, Valentin will be recommended again from May 1, 2022 and not from July 1, 2022. We want the engine to use the date you defined, to avoid future reviews being postponed if the employee completes a review late.

Why has an employee not been recommended to me? 

There are several reasons why you may not see an employee recommended: 

• The employee already has a review in progress in the same rule category.
  
  
• The employee is excluded (permanently or temporarily) from the rule on the date you projected. 
  
  
• The employee is not part of your scope "Create a campaign and administer the campaigns whose owner is within the scope…".
  As you can only create reviews for employees who are within your scope, if an employee is not within your scope, you will not see them in the recommendations.

• The employee is not part of the target population defined by the rule filters (department, establishment, occupation category, contract type).
  
  
• The reference date used by the rule has not been entered for the employee.
  For example, if the rule is based on the contract end date and the employee has no contract end date, then they cannot be recommended.

• The employee does not have a current active contract date or an active contract in the future.
  
  
• If it is a one-off rule:
  • the rule was activated after the date on which the employee should have completed the review.
    For example, you may have a one-off rule for end of trial period reviews which need to be completed 3 months after the contract start date. Valentin arrived on January 1, and you activated the rule on June 1. Valentin should have completed his review on March 1, but the rule was not active at the time. Valentin will therefore not be recommended.

• • the employee already has a completed review in the rule category
    
    
• If it is a recurring rule: 
  • the employee already has a review in the same category as the rule, within the observation period for the rule.
    For example, if you have a recurring professional review rule that applies every two years from the start of the contract, and Valentin already had a professional review last year, then he will not be recommended for today since it will have been less than two years since he completed his review. 

• • the employee has a reference date within the observation period
    For example, if you have a recurring professional review rule that is applied every two years from the contract start date, and if Valentin arrived less than two years ago, he will not be recommended.