Glossary
Escalation
Also called: workflow escalation
Escalation is the automatic reassignment or notification that occurs when a workflow step is not actioned within a defined period. It exists because the delay in most approval processes is not decision time but the interval before the approver notices.
Escalation explained
What it actually fixes
The difference between a two-day approval and a two-week one is almost never how long the approver spent deciding. It is how long the item sat unnoticed. Escalation addresses the interval rather than the decision, which is why it produces a larger improvement than anything else in a workflow configuration.
Reminders before escalation
A reminder to the assigned approver, then a second, then escalation to a named alternative or a manager. Escalating immediately produces resentment and undermines the process; escalating never produces stalled instances nobody is accountable for.
Two reminders and then an escalation is a reasonable default, with intervals set per document type — an invoice approaching a discount deadline needs a tighter schedule than a policy review.
Avoiding noise
Escalation that fires constantly is ignored, and an ignored control is not a control. If a step escalates routinely, the problem is the assignment rather than the timing: the approver is wrong, overloaded, or the threshold is set so low that trivial items reach them.
A report of steps that escalated is therefore a diagnostic of the workflow design, not just an operational alert.
Recording it
Escalation and reassignment should both be logged with a reason, so the audit trail shows why an approval was given by someone other than the original approver.
FAQ
Escalation: common questions
Should escalation reassign or just notify?
Notify first, reassign only if the delay continues and the configuration names an alternative. Silent reassignment confuses accountability, which is why the reassignment must be logged.
What if the escalation target is also absent?
Escalate to a role rather than an individual where possible, so anyone holding that role can act. Chains that escalate to a single named person fail when that person is on leave.
Related terms
- Approval workflowAn approval workflow is a configured path a document must clear before it can be relied on, defining the steps, the approvers and the order.
- Document generationDocument generation produces a finished document by merging structured data into an approved template.
- e-FormAn e-form captures structured data through defined fields with validation, rather than collecting it as text inside a document.
- Electronic signatureAn electronic signature is data attached to or logically associated with a document that indicates the signer's approval of it.
- Policy acknowledgementPolicy acknowledgement is a recorded attestation that a named individual has read a specific version of a specific policy, at a given time.
Última revisão: 28 de agosto de 2026. Browse the full glossary.