Change-based approvals

Not all approval chains are linear. Change-based, or conditional, approvals allow your team to create approval chains based on the submitter, or changes made within the scenario. 

A stage of the approval process can be included always, only if certain conditions are met, or to be excluded under certain conditions. 



You can set approval steps to trigger on ANY or ALL changes in a scenario, as well as the total COST of the scenario. You also have the option to leverage Carrot to customize your pathways if it does not meet any of the above requirements. 



To customize your approver for selecting ANY or ALL changes in a scenario, the approval chain logic will look at the job BEFORE changes in the scenario unless you specify change.after… 

Examples: 

Include this stage if ANY or ALL changes in a scenario involve a job that was originally in the engineering department before change, OR there is a new job created in the engineering department: 

department="engineering"

Include this stage if ANY or ALL changes in a scenario involve a job that was changed to being in the engineering department. This will NOT look at new jobs created in the scenario: 

change.after.department="engineering"



When determining an approver based on the cost of the scenario changes, the “cost” value that the approval chain references is the total cost of the scenario located at the top of the page. 

For example, If you are UPDATING an existing job and not changing compensation, that cost will stay at $0. 

If you are terminating a role and creating a backfill with the same compensation, the total cost will also remain at $0.



If you CREATE a new job and add compensation, the total cost will adjust accordingly. 

If you change the compensation of an existing open or active job, or terminate a job without a backfill, the cost will also adjust. 



Choosing the custom change identifier will default to reference the person submitting the request, unless you specifically reference scenario changes. 

When writing your custom Carrot logic, it will default to looking at the submitter unless you specify "scenarioChanges.any{}" or "scenarioChanges.all{}"

Examples: 

Include this stage if the person submitting this scenario is in the engineering department and whose title contains “manager”:

department="engineering"&& title:"manager"

Include this stage if the person submitting this scenario is in the sales department and whose title contains “director”, and if the job they are changing is in the sales department:

(department="sales" && title:"director") && scenarioChanges.any{department="sales"}





Packages: Headcount Planning  | Compensation Planning | HRIS