As an alternative to manually creating a review cycle every time an employee is due for their performance review, you can instead automate the process by setting up Rules. For example, you can set up a rule to create a review cycle every time an employee hits the 3 month mark at your company.

To access Rules, click on the Automation tab from the reviews homepage. 

From there, click on Create Rule to start setting up your rule. 

Give your rule a name, like "6 Month Performance Check-in," and then select what will trigger a review cycle being created. You can choose for employees to be reviewed at the 1, 3, 6, or 12 month mark. For example, if you were to choose "6 months" and an employee started on March 15th, on July 15th (6 months later) a review cycle would be created for their 6 month work anniversary.

Optionally, you can also make the rule repeating. That means if you've selected 6 months, a review cycle will be created for each employee on their 6 month work anniversary, and then every 6 months after that.

Note: You can only create one recurring rule by start date. 

Without selecting "repeating", only 1 review cycle will be created at first 6 month mark for an employee. You may want to do this so that after the initial 6 month review, you can put employees are a company-wide cycle to avoid many review cycles being created.  

After selecting your trigger, choose what type of review you want, just like how you would when launching a review cycle manually. Click the save button, and your rule will be saved. 

Now, when employees are up for review, the review cycles will be created automatically (in draft mode) and all admins in Lattice will get an email informing them of who's up for review. 

Admins can then go to the review cycles that have been created, which will already have the name, type, and participant pre filled. Admins can then edit any of the pre-filled fields as well as fill out the remaining fields then launch the review cycle. 

Advanced Topics

Employees whose start date is past the 28th day of the month:  
Let's say you have an employee whose start date is August 30th, 2016 and you have created a rule for their 6-month work anniversary. 6 months later would be February 30th, 2017. But that date does not exist (Feubary only has 28 days (most years)). In these cases, we run their review cycle on the last day of the month instead. So their next review cycle would be created on February 28th, 2017. This means the last day of the month will see a bit more review cycles created than average.

Did this answer your question?