How are system alerts for due dates or SLA breaches configured in CLM?

• A. Set SLA/reminder rules tied to due dates; configure recipient lists and notification timing; test alerts.
• B. Enable alerts to all users by default
• C. Alerts are for signature-only events
• D. Alerts cannot be tested

Answer: (A)

Configuring alerts for due dates and SLA breaches in CLM comes down to three elements: setting SLA/reminder rules tied to the due date, defining who should be notified, and choosing when the notifications fire, followed by testing to confirm everything works as intended. You create rules that trigger at specific times relative to a due date—such as a reminder a few days before the due date or an escalation if the due date is missed. You specify the recipient list so only the appropriate people (for example, the assignee, their manager, or a compliance role) receive the alert, and you tailor the timing windows (days or hours before due, on due date, after due) to fit your process. Testing is essential to ensure alerts reach the intended recipients, display the correct content, and fire under the right conditions when due dates change or statuses update.

The other options don’t fit as well because alerts aren’t meant to go to everyone by default; they should target relevant participants to avoid noise. Alerts aren’t limited to signature events—they encompass time-based and SLA-related milestones across the lifecycle. And yes, you can test alerts to verify behavior before going live.