Automate Document Signing Workflows with Adobe Acrobat Pro DC
By: George Nicholas and Matthew Darby
We’ve tested and like Adobe Acrobat Pro DC (document cloud) and Adobe Sign as a useful and reasonably priced solution for automating document signing workflows. Here’s a simple example involving a fictitious service provider preparing and completing a contract with a client.
A service provider (“XYZ Company” in the example screen shots) creates a contract for a new client (“ABC Corp.”) and opens in Acrobat Pro. The service provider signs the contract with a click and then prepares the signature block for client (under client’s name) by adding a signature field, the client’s email address and a box checked that signature is required. A title field may be added to complete the signature block following the same protocol. The contract is now ready to send to the client.
The service provider clicks the Adobe Sign button and is then prompted to send the contract to the client. The client receives an email with instructions and link to the service provider’s secure document cloud to sign the contract. In the document cloud the client is prompted to sign the contract.
The client then adds signature, name and title and clicks to sign.
Once the document is signed a contract document file is automatically generated from the original file and the new file name now includes the word “signed” (e.g. XYZ_Company_ABC_Corp_services_agreement-signed). The signed contract document is now locked and cannot be edited. When opened the document will reflect at the top that it is certified by Adobe Sign and a certificate has been issued as follows:
Adobe Sign automation continues by emailing and attaching the signed and certified contract document in PDF format to both the client and service provider. This final document is also appended with an Adobe Sign document history including: (1) document name, creator, date, status as signed and transaction ID; and (2) the date and time of transaction events showing document was sent, opened, signed and that each party was provided with the final signed and certified contract via email.
Clearly much thought went into the design of this electronic document signing process in view of the Uniform Electronic Transactions Act adopted by 47 states including Texas and the electronic transactions laws of the other three states but always consult your lawyer before entering into any agreement.
George Nicholas is the Chief Executive Officer of Apian Systems and a lawyer.
Matthew Darby is the Chief Technology Officer of Apian Systems and a computer scientist.
DISCLAIMER. Apian Systems is not engaged in the practice of law and does not provide legal services or legal advice to any person or entity. All of our litigation related support, consulting or eDiscovery services are provided either for law firms or counsel within corporate legal departments and these particular services are provided for these clients at their request and direction. All discussions of laws, statutes or rules on this website or in our blog posts are provided for general educational purposes only and shall not constitute legal advice for any particular person or entity.