docusign-clm

Sending is the point of legal exposure, so verify every recipient's email, recipient type, routing order, tab placement, and authentication first. Place internal approvers ahead of the counterparty in sequential routing, and never weaken authentication to speed signing.

Sent means the envelope is out to recipients; delivered only means a recipient opened it in the viewer, not that they signed; completed means every recipient finished and the agreement is executed. Signed is a recipient state, not an envelope status.

No. A completed envelope is the executed agreement and cannot be un-completed or voided. Corrections require a new signed envelope such as an amendment, and the original record and Certificate of Completion remain permanent.

Use this Skill's CLM guidance when DocuSign CLM (formerly SpringCM) is the contract lifecycle suite. If the CLM suite is Icertis or SAP Ariba Contracts, their authoring and approval logic lives in those skills, and this Skill covers only the DocuSign signature envelope.

A bounced recipient email sets that recipient's state to auto-responded, stalling the envelope at that routing step. Read per-recipient action states rather than the envelope roll-up, then correct the address or re-route to unstick it.

A PowerForm lets anyone with the URL initiate a binding envelope, so it is wrong for authority-sensitive agreements. Bulk send replicates one template into hundreds of envelopes, multiplying any template defect, so verify on a single send first.