Glossary
Approval workflow
Also called: document approval, approval chain
An approval workflow is a configured path a document must clear before it can be relied on, defining the steps, the approvers and the order. Its purpose is consistency: the same document type follows the same path every time, and the result can be evidenced afterwards.
Approval workflow explained
Sequential, parallel, or both
Sequential chains suit escalating authority — a manager, then a director, then a committee. Parallel steps suit independent review, where legal and technical sign-off do not depend on each other and queueing them only adds days. Most real templates use both.
Thresholds belong in the workflow
A policy that says invoices over a certain value need two approvals is a hope. A workflow that reads the value from metadata and adds the second approver automatically is a rule. Encoding the threshold in the configuration rather than the procedure is the difference between a control that operates and one that operates when someone remembers it.
What makes an approval evidenced
The approver acting in their own authenticated session, against a specific document version, at a recorded time. Approvals recorded on someone's behalf, or against "the document" rather than a version, are the two ways an approval record becomes unusable in an audit.
Reminders and the awkward middle
The difference between a two-day approval and a two-week one is almost never the approver's decision time. It is the interval before they notice. Reminders on a schedule, escalation to a named alternative, and a personal queue of what is waiting on you are unglamorous and are where most of the value sits.
FAQ
Approval workflow: common questions
How many approval steps is too many?
More than three for routine documents. Each step adds delay and diffuses accountability, and long chains are usually a symptom of unclear authority rather than genuine risk.
What happens when an approver leaves mid-workflow?
The step is reassigned, which should be logged with a reason, or escalated automatically by the reminder schedule. What must not happen is the instance stalling silently.
Related terms
- 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.
- EscalationEscalation is the automatic reassignment or notification that occurs when a workflow step is not actioned within a defined period.
- Policy acknowledgementPolicy acknowledgement is a recorded attestation that a named individual has read a specific version of a specific policy, at a given time.
Last reviewed: 28 August 2026. Browse the full glossary.