Solution Guides

Forward a Signing Task: Signer Delegation Without Breaking the Audit Trail

How signer delegation works in eSign.AI: the Advanced Settings switch, the Transfer action on the signing page, what the activity log records, and the documents where the switch should stay off.

eSign.AI Solutions Team8 min read

The named signer is not always the person who can sign

A deal does not stall because nobody wants to sign. It stalls because the person whose name is on the envelope is travelling, on leave, has left the company, or moved to a role where signing authority now sits with someone else. The document is correct, the fields are placed, and the envelope is waiting on one human who is not available. There are two ways out. The sender can cancel the envelope and build a new one with the replacement named from the start. Or the signer can hand the task to a colleague themselves, inside the same envelope, keeping one continuous record. eSign.AI supports the second route, but only when the sender has allowed it. The permission is off by default on every new envelope, and it changes what a signer is able to do on the signing page.

Opt-in

Signer transfer on a new envelope, every time

Advanced Settings

Where the sender grants the permission

Transfer

The action a permitted signer uses

One envelope

Record kept, rather than cancel and re-send

What the permission actually changes

Three consequences follow from switching it on, and each one has a governance cost attached.

It is a per-envelope decision, not an account setting

The permission is granted while the envelope is being prepared, in the Advanced Settings panel alongside the other signer permissions. It is shown as 允許簽署人轉交簽署任務 in the Traditional Chinese interface, and the wording follows the interface language you are using.

Nothing carries over to the next envelope. A sender who wants delegation available on a class of documents has to grant it on each one, which is the right default: the envelopes that need a fixed individual and the envelopes that need flexibility are rarely the same document type.

The signer chooses the replacement, not the sender

Once permitted, a signer who cannot complete the task opens the signing page and uses Transfer in the toolbar, naming the person who should take over. The sender does not approve that person in advance and is not asked to confirm the choice at the moment it happens.

That is the trade the permission makes. You gain the ability to unblock a signature without rebuilding the envelope, and you give up prior control over who the substitute is. Where the counterparty must be a specific legal person, the permission should stay off and the sender should reassign from their side instead.

The envelope continues, and the handover stays visible

The envelope is not cancelled and rebuilt. The outstanding signature fields pass to the new signer, and the activity log keeps initiation, the transfer with the outgoing and incoming names, and the subsequent signing as separate entries with timestamps.

That single continuous record is the reason to prefer delegation over cancel-and-resend when the only thing that changed is the person. Two envelopes produce two histories: one abandoned, one complete, with nothing in either explaining why the first stopped.

Reassign from the sender side, or delegate from the signer side

Both routes get the document signed. They differ in who chooses, what happens to the record, and what you can prove afterwards.

Sender cancels and re-sendsSigner forwards the task
Who decides the replacementThe sender, before the document goes out againThe current signer, at the moment they cannot sign
What happens to the envelopeCancelled or voided, then a new envelope is built with new recipients and newly placed fieldsContinues as it is; the outstanding fields pass to the new signer
What the record shows afterwardsTwo envelopes: one abandoned, one completed, each with its own historyOne envelope whose log shows initiation, the transfer with both names and a timestamp, and the signing
When it is the right routeThe wrong person was named, or the commercial terms in the document changedThe named signer is travelling, on leave, has left the company, or the signing authority moved to someone else

Granting the permission and using it

The sequence below is the one in the walkthrough video, from envelope preparation to a completed signature by the substitute.

01

Open Advanced Settings while preparing the envelope

Add the document, the recipients and the signature fields as usual, then open Advanced Settings. The delegation option sits with the other signer permissions, next to options such as allowing a signer to edit the signature name and country or region restrictions.

02

Turn on signer transfer for this envelope

The switch is off on a new envelope. Turn it on only when the person who signs may legitimately differ from the person who was named. Sending the envelope is unchanged either way.

03

The signer uses Transfer on the signing page

A permitted signer opens the signing page and finds Transfer in the toolbar. A signer on an envelope where the permission was not granted does not get the action, so the sender keeps control by leaving the switch off.

04

Name the person taking over

The signer identifies the replacement and confirms the transfer. The substitute receives the standard envelope notification for a signing task, so the handover does not depend on the two colleagues talking to each other outside the system.

05

Check the handover in the activity log

The envelope panel records the initiation, the transfer with the outgoing and incoming names and the time it completed, and the new signer's view and signature as separate entries. Export that log with the signed file when the signing authority question may be raised later.

Watch the transfer happen

The four-minute walkthrough shows a sender enabling the permission in Advanced Settings, a signer forwarding the task to a colleague, the activity log recording both names, and the completed envelope returning with the signed file. The interface in the recording is Traditional Chinese.

Where the permission should stay switched off

Delegation solves an availability problem. It creates a problem wherever the identity of the signer is itself the point.

Documents that name a specific individual

Notarial acts, court filings, statutory declarations and affidavits are valid because a particular person signed them. If the document text names the signer, a forwarded task produces a signature that does not match the document, and the mismatch is visible on the face of the file. Keep the switch off and reissue the document with the correct name instead.

Envelopes waiting on a seal or signature approval

Where a corporate seal or an internal approval has been submitted and is awaiting a decision, the relevant signing areas are locked and the Transfer action may be unavailable. The transfer becomes possible again once the approval finishes. Attempting the handover mid-approval produces a confusing state rather than a faster one.

Signatures whose whole purpose is authority evidence

Board resolutions, credit facilities and guarantees are signed to prove that a named officer held authority on a date. Delegation is not automatically wrong here, but the transfer entry becomes part of the evidence, and you need the activity log alongside the signed file to show who held the task when. If your evidence package cannot carry that log, keep the switch off.

Common questions

Answers assume an ordinary commercial contract signed through an eSignature workflow.

No. A new envelope has signer transfer switched off. The sender grants it per envelope in Advanced Settings, so an envelope that never needed delegation is never exposed to it.

Team discussing the right eSignature approach for a business

Explore the right eSignature approach for your business

Talk to our team about eSignature requirements, compliance considerations, and document workflows across your target markets.