Escalation with SLA Timeout

Visual Flow

Rendering diagram…

When to Use This Pattern

Use escalation with SLA timeout when:

• Tasks have deadlines that matter (regulatory, contractual, customer-facing)
• You've experienced process stalls from unresponsive approvers
• Management needs visibility into bottlenecks
• You want to enforce accountability without manually chasing people

How It Works

A timer runs alongside each task. If the assignee doesn't respond before the timer expires, the workflow escalates — either to a backup person, the assignee's manager, or by auto-approving/rejecting.

Implementation Guide

Step 1: Define the SLA Tiers

Create a tiered escalation schedule:

Level	Trigger	Action	Notification
Reminder	50% of SLA elapsed	Send reminder email	Assignee only
Warning	80% of SLA elapsed	Send urgent notice	Assignee + manager
Escalation	100% of SLA elapsed	Reassign or auto-decide	Assignee + manager + process owner
Critical	150% of SLA elapsed	Force-complete with audit flag	All stakeholders

Step 2: Implement the Timer

Use one of these approaches:

1. Parallel branch with delay — Run the task and a delay timer in parallel. If the delay completes first, trigger escalation.
2. Scheduled check — A separate workflow runs every hour, checking for overdue tasks.
3. Built-in task timeout — Some products (K2, Workflow Cloud) have native task timeout settings.

Step 3: Configure Escalation Actions

Choose what happens at each tier:

• Reassign — Move the task to the assignee's manager (resolve via org chart lookup)
• Add approver — Keep the original assignee but also assign to a backup
• Auto-approve — Approve automatically if the risk is low (flag for audit)
• Auto-reject — Reject and require re-submission (strict compliance scenarios)

Step 4: Notify and Log

Every escalation event should:

• Send a notification explaining why escalation occurred
• Log the event in an audit trail
• Update a dashboard or report (for SLA compliance tracking)

Tips & Best Practices

• Exclude non-working hours. Calculate SLA in business hours, not calendar hours. Account for holidays and time zones.
• Escalate the task, not just the notification. Simply CCing a manager is ineffective — they need to be able to act on the task directly.
• Track escalation frequency. If the same person or step triggers escalations frequently, it signals a staffing or process design issue.
• Provide a "snooze" option. Let assignees extend the SLA by a day if they need more info, rather than letting it escalate unnecessarily.