What makes an e-signature legally binding?
An e-signature holds up when you can prove the signing happened the way you say it did: the signer intended to sign, agreed to do business electronically, can be tied to the signature, and the signed record stayed intact.
In the United States, the federal ESIGN Act says a signature or contract can't be denied legal effect solely because it's electronic, and it defines an electronic signature as one adopted with the intent to sign the record. ESIGN also requires that a retained electronic record accurately reflect the original and stay accessible in a form that can be reproduced later. The Uniform Electronic Transactions Act (UETA), which states adopt as their own law, applies only when the parties have agreed to transact electronically and sets rules for attributing a signature to a person. In the EU, eIDAS says an electronic signature can't be denied legal effect or admissibility as evidence just because it's electronic. It adds higher tiers: an advanced electronic signature must make any later change to the signed data detectable, and a qualified electronic signature has the same legal effect as a handwritten one. None of these laws require a specific vendor. They require evidence, and that is what an audit trail provides.
What should an e-signature audit trail record?
At a minimum: a timestamped record of each step in the signing, how each signer was authenticated, where each action came from, and a tamper-evident seal on the finished document.
In practice, that means events for when the document was sent, viewed, and signed by each party; the authentication method, such as an email link, an SMS one-time passcode, or stronger identity verification; the IP address tied to each action; and a cryptographic hash of the completed document, so any change after signing is detectable. Many platforms package this into a completion certificate or audit report that travels with the signed PDF.
If you collect signatures from consumers, record the consent step too. When a law requires that information be given to a consumer in writing, ESIGN lets you deliver it electronically only after the consumer affirmatively consents, having first been told about their right to paper records, how to withdraw consent, and the hardware and software needed to access the records. Log which disclosure was shown and when it was accepted. For a full event list and a JSON model you can adapt, see Anvil's e-signature audit trail schema.
How do you prove a signed document hasn't been altered?
Compare a hash of the file you have today with the hash recorded when signing finished. A cryptographic hash like SHA-256 changes completely if even one byte of the file changes, so a match shows the document is the one that was signed.
When a platform also applies a digital certificate to the signed PDF, you get a second check: PDF readers such as Adobe Acrobat check whether the signed content was altered after signing, beyond any changes the signer allowed. Store the original hash separately from the file, so anyone who alters the document can't quietly rewrite the evidence too. For a step-by-step version, see how to prove a signed PDF hasn't been altered since you stored it.
How should you store signed records for a SOC 2 audit?
Keep the signed PDF, its completion certificate, and the underlying event log together, in storage where changes are blocked or logged, with access controls and a written retention policy.
A SOC 2 report is an independent auditor's examination of a service organization's controls relevant to security, availability, processing integrity, confidentiality, or privacy, measured against the AICPA's Trust Services Criteria. In a Type II examination, the auditor tests whether those controls operated effectively over a period, so be ready to show who can access signed records, how changes are prevented or recorded, and that records are kept as long as your policy says. Being able to export audit evidence on demand, as a readable PDF and in a machine-readable format, makes it easier to answer an auditor's sample requests.
Which e-signature platforms provide compliance-grade audit trails?
E-signature platforms typically generate audit evidence automatically. The differences are in what they capture, how you can export it, and what certifications back the platform.
DocuSign, for example, produces a Certificate of Completion for completed envelopes that includes timestamps and IP addresses, and Adobe Acrobat Sign keeps a history and an audit report for every agreement that can be downloaded as a PDF. When you compare options, focus on the evidence: can you export the audit record in both human-readable and machine-readable form, can your compliance team pull it over an API, how long are records retained, and does the vendor hold the certifications you need, such as SOC 2 Type II, or sign a BAA if you handle health data.
If you are building document workflows in software and want the audit trail handled for you, Anvil's Etch E-sign is one API-first option. Every Etch packet generates a tamper-evident audit trail with timestamps, signer identity, IP address, and a document hash. Packets can include multiple PDFs and signers, signing can be embedded in your app and white-labeled, and Anvil is SOC 2 Type II certified and GDPR compliant, with BAAs available for teams handling protected health information.
Back to All Questions