Substitute Approvers: Covering Approvals Without Losing Control

A substitute approver is a named colleague temporarily authorized to approve or reject requests on behalf of an approver who is unavailable, with every decision recorded on the audit trail as taken on that person's behalf, so coverage never costs you evidence or control. This guide covers when you need substitution, how it works step by step, the control rules that keep it safe, and how it compares to the alternatives teams usually try first.

Every approval workflow has single points of failure: the one manager who must sign the payment while she is on annual leave, the CFO traveling when a contract lands, the department head who resigned mid-process with requests sitting in his queue. Substitution is how a governed process absorbs an absent approver without pausing the business or breaking the rules. For the broader framework of routing and stages, read Approval Workflows: The Complete Guide; for the failure pattern this feature exists to kill, see How to Find and Fix Approval Bottlenecks.

What is a substitute approver?

A substitute approver covers one approval slot: one approver, at one stage, on one pending request. While coverage is active, the request appears in the substitute's own "Requires My Approval" queue, and they can approve or reject it on the original approver's behalf. When the approver returns, or the request finishes, coverage simply ends.

The distinction matters: substitution is not permanent reassignment of the workflow, not a shared login, and not an administrator overriding the process. It is scoped, reversible, and evidence-backed. The original approver keeps their slot; the substitute acts inside it, under the same routing rules and the same approval matrix that governed the request all along. The difference between the request detail's named chain and what actually happened is preserved, not papered over.

Why single-point approvers break workflows

In an email-based process, an absent approver means silent stalls. Requests sit in an inbox nobody is watching, deadlines pass, and the pressure builds until someone bypasses the process entirely, a text-message approval, a shared password, a "just pay it, I'll confirm later." Each of those workarounds solves today's delay by destroying tomorrow's evidence.

The stall is rarely visible in the moment, that is what makes it dangerous. Aging visibility and alerts catch stuck requests after the fact; substitution removes the most common cause before it starts. Both together are covered in Aging Alerts and Workflow Deadlines and Escalation.

How substitute approvers work

1. Coverage is added at the step, for that request

From the request's detail view, coverage is attached to a specific approval step, not to the workflow, the department, or the account. It can be added while the request is pending, for the step currently in progress or any later step. The step's own approver can add cover for their slot; administrators can add cover for any slot. Who holds which role is covered in User Roles Explained.

2. The substitute's queue lights up

The moment coverage is added, the request appears in the substitute's "Requires My Approval" queue alongside their own assignments, they do not need to be granted any wider access, and the request does not need to be forwarded anywhere. They are notified in-app and by email, so cover is never silent. How the queues are organized is covered in Navigating the Approvals Tabs.

3. Decisions are recorded on-behalf

When the substitute approves or rejects, the audit trail records two identities: who took the action, and whose slot they exercised. The approval satisfies the original approver's requirement, the matrix does not change, the stage does not change, only the person acting at it does. The coverage event itself is also an audit entry: who was added as substitute, for whom, at which step, and by whom. The result is a trail that answers the auditor's real question, "the named approver was in Lisbon, so who actually approved this?", with evidence instead of memory. The evidence layer itself is covered in Unbroken Audit Trails.

4. Coverage resets with each approval cycle

If a request is sent back, rejected, or an approval reversed, the stage reopens for a fresh decision cycle. Slots that were satisfied before, including covered ones, need a new decision in the new cycle; a substitute cannot lean on an approval that has since been revoked. How reversals work without breaking the record is covered in Smart Revoke.

The control rules that keep substitution safe

Delegation is where approval processes most often lose their controls, so substitution ships with rules that make the safe path the only path:

The deeper principle is the one from Segregation of Duties: no arrangement should let one person quietly control more of the process than their role allows. Scoped, recorded substitution extends coverage without extending anyone's authority, which is also why it passes the control tests described in Internal Controls for Approvals.

Substitute approvers vs the alternatives

How to add a substitute in Approvdit

1. Open the pending request and find the approval step that needs cover, the full anatomy of the request view is in The Request Detail View.
2. On that step, choose a substitute from your organization's active users. If you are the step's approver you can cover your own slot; administrators can cover any slot.
3. The substitute is notified in-app and by email, Email Notifications keeps everyone else on the request informed as normal.
4. They approve or reject from their own "Requires My Approval" queue; the audit trail records who acted and on whose behalf.
5. When the approver returns, remove the coverage, the slot reverts to its named owner, and the audit trail keeps the full history of what happened during the absence.

Common mistakes

• Choosing a substitute who creates a conflict. The requester covering their own approval, or two roles collapsing into one person, is a segregation-of-duties violation wearing a delegation costume.
• Coverage without telling anyone. Substitution notifies the substitute and records the event precisely so cover is never informal.
• Leaving coverage active for months. Substitution is for absence, not a standing reassignment, stale coverage quietly becomes a second owner of the slot.
• Expecting substitution to relax the matrix. The same approval rules govern every decision, whoever takes it, see Approval Conditions: All vs Any.
• Confusing substitution with access management. Coverage is scoped to one step of one request; permanent role changes belong in User Management.

Frequently Asked Questions

What is a substitute approver?

A named colleague temporarily authorized to approve or reject on behalf of an unavailable approver, at one step, on one pending request, with every decision recorded on-behalf on the audit trail.

Who can add a substitute?

The step's own approver can add cover for their slot; administrators can add cover for any slot on a pending request.

Can the original approver still act while covered?

Yes, their slot takes priority, and if they approve it themselves the requirement is satisfied either way. Substitution is a backup, not a transfer of ownership.

What happens if a request is sent back after being approved?

The stage reopens for a fresh approval cycle, and slots that were satisfied earlier, including covered ones, need a new decision. See Smart Revoke.

Is the substitution itself recorded?

Yes, who was added as substitute, for whom, at which step, and by whom, alongside every on-behalf decision taken under the coverage. The trail remains tamper-evident throughout.

Approvdit supports substitute approvers natively, per-step coverage, on-behalf audit records, and the same matrix controls on every decision, so approvals keep moving when people cannot. Book a live demo to see substitution running on your own approval chain.