Compensation cycles include four different states.
1. Draft
In the Draft states, admins, compensation admins, and compensation cycle admins can edit the compensation cycle. Lattice will automatically create temporary custom roles for any compensation cycle admin added to the cycle.
When a cycle is launched from a Draft state, it is moved to the Active state.
2. Active
In the Active state, the following is true:
- Lattice will automatically create temporary custom roles granting visibility into compensation fields for recommenders and approvers for employees in their approval chain.
- Recommenders and approvers can draft and submit their pay recommendations and approvals.
- Admins can submit recommendations directly for any cycle participants.
- Any changes made in the Employee Pay page will automatically show up in the compensation cycle as the employee's current (pre-cycle) pay. This includes any pay changes synced from an external HRIS while the cycle is active.
In the Active state, admins can take the following actions to change the cycle's state:
- Close Submissions: This will move the cycle to the In Review state. Any users who had not submitted their assigned recommendations or approvals can no longer submit changes.
3. In Review
In the In Review state, users who are not admins can no longer make recommendations or approvals. Admins enter the In Review state after clicking Close Submissions.
In the In Review state, the following is true:
- Recommenders and Approvers cannot draft or submit pay recommendations and approvals, but they maintain visibility into what they previously submitted.
- Admins can still submit recommendations directly for any cycle participants to adjust their final new pay.
- Employees' current (pre-cycle) pay is locked. Any changes made in the Employee Pay page will not show up in the compensation cycle.
- Admins can enable statement sharing.
In the In Review state, admins can take the following actions to change the cycle's state:
-
Reopen submissions: This moves the cycle state from In Review back to Active. This will automatically unshare any statements previously shared. Once reopened, admins need to reshare statements. Any managers who had not submitted their assigned recommendations or approvals can now submit them.
Note: If any changes were made in the Employee Pay table after the cycle was moved to In Review, those changes will be pulled into the cycle automatically. This includes updates that reflect the employee's new post-compensation cycle pay, so a cycle In Review should not have submissions re-opened if new pay has already been uploaded into Lattice Employee Pay. - Share results: This opens the Sharing ability for admins to share with recommenders/approvers, direct managers, or employees directly.
4. Ended
In the Ended state, all data is locked and any new changes will not appear in the compensation cycle. Admins enter the Ended state after clicking End Cycle.
In the Ended state, the following is true:
- Sharing ends: Admins and most recommenders/approvers cannot share statements. If the recommender's default field-level permissions give visibility into compensation statements, they will be able to share statements even after the cycle has ended.
- Temporary roles close: Temporary permissions that give visibility into employee data are automatically removed.
- Export data: Admins can still export data as a CSV.
In the Ended state, admins can take the following actions to change the cycle's state:
- Reopen the cycle to admins: This moves the cycle back to the In Review state.