This article will walk you through how to send a contract directly for signature. This functionality is exclusive to Ironclad Signature.
Things to Know Before Sending for Signature
Keep the following considerations in mind when sending directly for signature:
3rd party signature provider integrations are not supported. Documents uploaded and sent for signature are sent with Ironclad Signature.
Sending a document directly for signature bypasses processes defined in workflow configurations, including approvals. You will only have this option if your administrator gives you the correct permissions. If you are a signature coordinator, you can manage in-flight signature requests including reminders and reassignment.
Uploaded documents cannot be edited.
Email notifications cannot be customized.
Users can select from existing record types. Record types can be created in Workflow Designer, or edited post-execution in the Ironclad Repository.
Users can upload .docx or .pdf files.
Signers can reassign signature packets.
Key terms, automated signature request reminders, and signer verification are not available.
Upload a Contract for Signature
Signature requests are sent based on the defined signing order and with the default signature request emails.
On the Dashboard tab, select New > Upload for signature.
Upload a .docx or .pdf file.
TROUBLESHOOTING If you are having trouble with uploading a .pdf file, we recommend flattening it, uploading it, and placing tags on top of unsupported PDF elements before sending it for signature.
Follow the prompts on-screen to provide the Counterparty Name, contract type, and signers.
Optional: Toggle on Share a copy to share a copy of the signature request and finished signature packet to Ironclad users and groups.
Click Next.
Add signature tags to the document. At least one signature or initial tag is required per signer.
Select Send.