Which mechanism in CLM enables escalation when a participant is unavailable during approvals?

• A. Deleting the contract
• B. Canceling the workflow
• C. Sending reminders only at the end
• D. Escalation in routing configuration

Answer: (D)

Escalation in routing configuration is the mechanism that handles approvals when a participant is unavailable by automatically re-routing the task to a backup or additional approver after a defined time. You configure time-based escalation rules and designate who should be contacted if the primary signer doesn’t act, so the workflow moves forward and SLAs are met. This directly addresses unavailability by ensuring someone else steps in, rather than stalling the process. Deleting the contract or canceling the workflow would stop or remove the process, not enable timely approvals, and reminders at the end don’t provide a proactive path to escalation when someone is unavailable.