Rendering diagram…
Use a serial approval chain when:
This is the most common approval pattern. If you're unsure which pattern to use, start here.
The request flows through approvers one at a time, top to bottom. If any approver rejects, the chain stops and the requestor is notified.
| Step | Actor | Action | On Approve | On Reject |
|---|---|---|---|---|
| 1 | Requestor | Submits request | → Step 2 | — |
| 2 | Manager | Reviews & decides | → Step 3 | → Notify requestor |
| 3 | Director | Reviews & decides | → Step 4 | → Notify requestor + manager |
| 4 | Finance | Final approval | → Complete | → Notify requestor + all approvers |
Map out who needs to approve and in what order. Common approaches:
Create a form that captures all the information approvers need to make a decision. Include:
For each approver in the chain:
Log every decision with:
| Product | How to Implement |
|---|---|
| Workflow Cloud | Use the Assign a task action in a sequence. Set waitForCompletion = true on each. |
| K2 | Use Task steps in a sequential workflow. Configure the Task form with Approve/Reject outcomes. |
| Automation On-Prem | Use Request approval actions chained in sequence with conditional branching on outcomes. |
Always include a timeout mechanism. A single unresponsive approver can stall the entire chain indefinitely. See the Escalation with SLA Timeout pattern.
Route purchase requests, expense reports, and financial approvals through different approval chains based on the dollar amount. Low-value requests skip senior approvers; high-value requests get more scrutiny.