In an Approval Path, what is the purpose of escalation rules?

• A. To log the approvals but not affect routing.
• B. To automatically terminate the approval process after a fixed time.
• C. To route approvals to alternate approvers when the primary approver is unavailable or delays.
• D. To prevent any changes to the approval path after creation.

Answer: (C)

Escalation rules in an Approval Path are about keeping the workflow moving by rerouting when the primary approver can’t act within the allotted time. They define when an escalation should occur and who should take over—often an alternate approver or a designated group—so the approval doesn’t stall and the process meets its SLAs. This automatic re-routing ensures timely decisions even if the main signer is unavailable, on leave, or delays approvals.

Escalation is not primarily about logging approvals or ending the process, and it doesn’t lock the path from changes. It’s a dynamic mechanism to redirect the review to someone else who can approve, or to send reminders and continue the workflow without unnecessary bottlenecks.