Prepare a first signature request without rushing the handoff
Read the guide →Guide preview
Confirm the source, recipients and required actions before issuing the request.
Separate notification trouble, declines and revisions without creating duplicate work.
Separate notification trouble, declines and revisions without creating duplicate work.
New to the topic? Begin with the first guide. Otherwise, go straight to the question you need to answer.
Confirm the source, recipients and required actions before issuing the request.
Recover access to the original request when appropriate; do not manufacture a replacement agreement.
A missing notification is not evidence that the original document request failed.
Use reminders to clarify an outstanding action, not to substitute for a status check.
Treat a decline as a substantive outcome, not a technical error to work around.
Check the required-party matrix and actual document before calling a multi-signer handoff complete.
A revised document is not a harmless continuation when earlier signatures can be lost.
Preserve the original facts and use an authorized correction path; do not simply forward access elsewhere.
Use a clearly labelled sample to verify roles, required fields and the retained output before real work.