Page Comparison

The main goal of the auto-escalation function is to automatically move the proposal to the higher level of the employee who decides on its approval under the following conditions:

• The employee assigned to the previous level has not taken action for a prescribed period of auto-escalation.
• The employee who has not taken action is not the last level of approval. 
• The proposal amount is outside the area of the previous employee level’s responsibility.

MLP Rules and the Approval Workflow

MLP rules check each proposal to determine the appropriate approval workflow:

1. First, it checks the trade and category of each proposal.
2. Then, it checks the MLP Level to see who should receive the proposal, which Actions users in that MLP Level can take (approve, reject, place on hold, or return back), and the maximum proposal amount (or Limit) allowed for each action.
3. Once the MLP Level user takes action, the rule determines if the proposal should be either forwarded or sent back (returned) to other levels.
4. Finally, when the user takes action, the proposal is set to a certain proposal status.You may also determine the number of days each MLP Level has to take action before the proposal automatically escalates to the next stage in the approval process. 
   

Navigate between the tabs to have a look at the examples with the 3 variants of proposals amount and how the auto-escalation will work for each of them.

Here is an example of how to fill in the template for auto-escalation.