Skip to content
Insights/Article

When an Approver Takes Leave or Leaves the Company, What Happens to Tasks in the System?

Key takeaway

Do not share accounts. Scope and log delegation, and let an authorized administrator transfer open work. Disable access at the agreed termination point and check existing sessions; do not delay revocation while waiting for handover. Preserve original approval history.

Two paths when an approver is away: time-limited delegation and item-by-item transfer, with shared accounts crossed out

The opening approval-handover story is hypothetical; its people and events do not describe a real client.

The finance lead is on leave for two weeks. On day three, a payment due date arrives and the approval is stuck; the supplier starts calling. A colleague goes to the administrator: give me her password, I will approve it and explain when she is back. The administrator hesitates, then hands it over. The payment goes out that day, and the approval record shows the name of the person on leave.

That solves the day and leaves three problems: the record is untrue, responsibility is unclear, and the password cannot be taken back. An approver being away is normal business. The system should have formal delegation and transfer, not a shared account.

Why a shared account is not a solution

An approval record matters because it says who decided, when, and on what information. A shared account points that record at someone who was not operating the system. After the fact, nobody can tell whether the approver, the deputy, or someone else using the same account made the decision.

Sharing also makes permissions impossible to reclaim. Once the password is out, changing it disrupts everyone using the account; not changing it leaves access valid after departure. In an audit, all actions sit under one name with no explanation.

Delegation is not sharing. With delegation, the system knows "A is approving on behalf of B," and the record keeps both.

Delegation: time-limited, scoped, recorded

Temporary delegation needs four things:

Whom it covers: the original approver and the delegate. The delegate is usually named by the approver or their manager.

What it covers: only certain approval types or all of them. Payments, contracts, HR, and pricing differ in sensitivity and should not default to "everything." Scope should select by approval type, amount range, or organization.

How long: a start and an end. It expires automatically; nobody has to remember to turn it off. Extended leave can renew it, with each renewal recorded.

How the record appears: the approval shows "delegate A approved on behalf of approver B," not just one name. Notifications go to both.

A delegate should not re-delegate unless the system explicitly allows and records the chain. A delegate also should not approve requests involving their own interest, such as delegating someone to approve their own expense claim; those go to a manager.

Transfer: list open items, do not approve them in bulk

For a role change or long absence, delegation is not enough; tasks need transferring. Start by listing what is open: which requests wait for the original approver, how long each has waited, its amount or risk, and whether a deadline is near.

Then decide item by item: who receives it, whether an additional approver is needed, and whether the original approver should give an opinion first. Do not provide an "approve all, then transfer" button. Bulk approval turns individual judgment into one click and carries the most risk.

After transfer, the new approver sees the full history and attachments, not a bare task. Opinions already given by the original approver remain; a transfer does not erase them.

Notify the requester too. They are entitled to know their request changed hands, especially after a long wait.

Departure: revoke access on time and hand open work to an administrator

Access termination and work handover are coordinated processes. Unfinished work must not keep a departed account active.

  1. Revoke access at the agreed termination point. Disable sign-in, remove delegation and obsolete roles, and verify the handling of existing sessions and connected applications.
  2. Stop new assignments. Route urgent decisions to the nominated owner.
  3. Let an authorized administrator inventory and reassign open work. Record each receiver and any management review without requiring the departing person to sign in.
  4. Preserve history and business records. Retain original approval attribution and record who transferred each item. Handle drafts and attachments by business ownership and retention requirements, rather than automatically deleting or transferring everything.

Microsoft's access-revocation documentation distinguishes blocking new sign-ins from handling existing sessions. Other identity systems require checks appropriate to their own mechanisms.

When the approver returns, reclaim the delegation

Delegation expires automatically, but early returns, extended leave, and disputes during the delegation are common. On the return day, check whether delegation has ended, which requests were approved during it, and whether any exception needs the approver's confirmation.

If the delegation period included a conflict of interest or an out-of-scope approval, review it rather than waiting for an audit. A manager or named reviewer checks the amount, the counterparty, and the basis.

Delegation, transfer, and reassignment solve different problems

Method

Fits

Duration

Scope

Approval record

After return

Temporary delegation

Short leave, travel

Fixed start and end; expires

Named approval types or amount range

Shows delegate and original approver

Expires; sample approvals made during it

Long-term transfer

Role change, long sick leave

Until the role changes

Open items listed and transferred one by one

Keeps original opinions and transfer record

Does not auto-restore; authorize by the new role

Departure reassignment

Resignation, position removed

One-time

All open tasks

History keeps the original approver

Not applicable

The three do not substitute for one another. Using transfer for short leave churns assignments; using only delegation for departure means the delegation dies with the account and tasks stall again.

A handover checklist

[Approval handover checklist]

1. Scope
- Which approval types, amount ranges, and organizations the approver owns:
- The open-task list and how long each has waited:
- Which tasks must move today and which can wait:

2. Method
- Delegation or transfer; duration and scope:
- Whether the delegate may re-delegate:
- Whether any request requires recusal:

3. Records
- Does the approval show both delegate and original approver:
- Are the original approver's opinions and history kept:
- Was the requester notified of the change:

4. Reclaim and review
- Does delegation expire automatically on return:
- Are approvals made during delegation sampled:
- Is the departed account disabled and history retained:

Take the approval type that stalls most often and rehearse both delegation and transfer once. If the rehearsal still ends with someone asking for a password, the handover mechanism is not actually usable. How roles and permissions are defined separately belongs in the scope of business system development; how tasks are transferred and acknowledged is covered in the handover design discussed in the system preparation guide.

Responsibility when an approver leaves has parallels with the role matrix in who owns an enterprise AI project, but this article does not cover AI projects. Approval boundaries for AI agents are discussed in permissions, approval, and human takeover for AI agents.

Sources

Let's talk about your project

Websites / Business systems / AI applications

Chat on WhatsApp