What an e-signature audit trail contains, with a real example
By SoloWOS teamPublished Updated
IN SHORT
An e-signature audit trail is the record of every step of a signing: when the document was sent, opened and signed, by which email address, from what IP address and device, plus a fingerprint (hash) of the original and final file. It is the evidence that links a person to a signature if the signature is ever disputed.
Prices and limits as of .
Key takeaways
- The audit trail, not the signature image, is what proves who signed: the email link, the consent, the timestamps, the IP address and device.
- A SHA-256 fingerprint of the final PDF lets anyone check that the file you hold is the one that was signed.
- US law lets you keep signed contracts electronically if the copy stays accurate and accessible (ESIGN, 15 U.S.C. § 7001(d); UETA § 12).
- Keep the signed PDF and its certificate together for at least the contract's life plus your state's limitation period (4 years for written contracts in California).
When a client says "I never signed that", the signature image settles nothing: anyone can paste an image. What settles it is the record around it. This page shows what that record looks like in SoloWOS, line by line, and how to use it. It belongs to our contracts and signatures guides; the law behind it is in are electronic signatures legal?.
Annotated example: a certificate of completion
Below is the event log of a fictional two-signer contract, as SoloWOS prints it in the certificate of completion that comes with every signed PDF. Names, emails and IP addresses are made up.
| Time (UTC) | Event | What it proves |
|---|---|---|
| 2026-10-05 14:02:11 | Draft created, by Ana Ruiz | Who prepared the request and when |
| 2026-10-05 14:06:40 | Sent for signature | The moment the document was frozen: the original SHA-256 is computed from this file |
| 2026-10-05 14:06:41 | Invitation emailed, to Ana Ruiz | Signer 1 received a private link at her own address |
| 2026-10-05 14:07:30 | Agreed to sign online, Ana Ruiz, IP 203.0.113.24 | Consent to electronic records, required before signing |
| 2026-10-05 14:08:02 | Signed, Ana Ruiz, IP 203.0.113.24 | Signer 1's signature, with the network it came from |
| 2026-10-05 14:08:03 | Invitation emailed, to Tom Becker | Signer 2 was invited only after signer 1 finished (signing order) |
| 2026-10-08 14:08:05 | Reminder emailed, to Tom Becker | An automatic reminder went out after 3 days |
| 2026-10-08 18:41:17 | Opened the document, Tom Becker, IP 198.51.100.7 | The client viewed it from the emailed link |
| 2026-10-08 18:43:55 | Agreed to sign online, Tom Becker, IP 198.51.100.7 | The client's consent, with the same IP as the view |
| 2026-10-08 18:45:12 | Signed, Tom Becker, IP 198.51.100.7 | The client's signature |
| 2026-10-08 18:45:13 | Completed | The final PDF was produced; the signed SHA-256 is computed from it |
Above the event log, the certificate lists the document title, a request ID, the sender, the page count and the created, sent and completed times. A section per signer repeats their status, consent time, signing time, IP address and device (the browser's user agent). An integrity section prints two SHA-256 values: one for the PDF exactly as it was sent, one for the final signed PDF.
How the fingerprint works
A SHA-256 hash is a 64-character value computed from every byte of a file. Change one comma and the value changes completely. To check a signed contract, run `shasum -a 256 contract-signed.pdf` on a Mac or Linux (or `certutil -hashfile contract-signed.pdf SHA256` on Windows) and compare the result with the signed SHA-256 printed in the certificate. If they match, the file is the one that was signed. In SoloWOS, the "Verify integrity" button on a completed request recomputes both fingerprints from the stored files for you.
Using the audit trail if a client disputes a signature
- Download the signed PDF and the certificate of completion, and check the fingerprint as above.
- Point to the chain: the invitation went to the client's own email address, the document was opened from that link, consent and signature followed minutes later from the same IP and device.
- Add what surrounds it: the emails where the client discussed the terms, the invoice they paid after signing, the deposit. Courts look at all of it.
- If it goes to court, the certificate is evidence your side offers to authenticate the signature. Under Federal Rule of Evidence 901, evidence only needs to be sufficient to support a finding that the item is what you claim; distinctive characteristics and the circumstances count. State courts have similar rules.
- For a large amount, talk to a lawyer before you reply in writing.
How long to keep the audit trail
The ESIGN Act lets you keep a contract electronically when the electronic record accurately reflects the information and stays accessible for later reference (15 U.S.C. § 7001(d)); UETA § 12 says the same at state level. No federal rule names one retention period for client contracts. A workable rule: keep the signed PDF and certificate for the life of the contract plus the statute of limitations for written contracts in the governing state. In California that is four years from the breach (Code of Civil Procedure § 337); other states differ, so check yours. Some freelancer laws add their own: California's Freelance Worker Protection Act makes the hiring party keep the contract at least four years, Columbus five.
Store the signed PDF and the certificate side by side, outside the e-signature tool too: a cloud folder per client works. If you ever cancel the tool, you still have the evidence.
What an audit trail can't prove
- Identity beyond the email inbox. A standard audit trail proves the person controlled that email address and device, not that they showed ID. SoloWOS doesn't do ID checks.
- Exact location. An IP address points to a network, often a provider's, and can be a VPN.
- Authority to sign for a company. Make sure the signer's title is right and, for large contracts, ask who is authorized to sign.
In SoloWOS
Every request you send for e-signature produces the certificate shown above, in English or in your workspace's language. Signers sign in the order you set, reminders can go out every 2, 3 or 7 days (at most 3 automatic ones per signer), and an optional expiration date closes the links. If a signer declines, that's logged too. Basic ($2/month) includes 3 requests a month and Solo 15 for $15/month. For the difference between this kind of record and a certificate-based signature, read electronic vs digital signature.
Questions
Is an audit trail the same as a certificate of completion?
Mostly. The audit trail is the log of events; the certificate of completion is the document that presents it, usually a PDF attached to or delivered with the signed file, with the signer details and file fingerprints.
Can the sender edit the audit trail?
Not in SoloWOS: events are recorded by the system as they happen, and the certificate is generated when the last signer finishes. The fingerprints would also show if the signed PDF were changed afterward.
Does the IP address prove where someone signed?
No. It identifies the network the request came from, which can be an internet provider, an office network or a VPN. It is useful as a consistency check (the same IP for opening, consenting and signing), not as proof of location.
How long should I keep signed contracts?
At least for the life of the contract plus your state's limitation period for written contracts, which is four years in California. Keep the signed PDF and the certificate together, and keep a copy outside the e-signature tool.
Sources
Facts checked against these sources on October 18, 2026. Rules and amounts change, so confirm them at the source before you file or sign.
- 15 U.S.C. § 7001, ESIGN Act general rule of validity and record retention (§ 7001(d))
- Uniform Law Commission: Electronic Transactions Act (UETA, including § 12 on retention)
- Federal Rule of Evidence 901, Authenticating or identifying evidence
- California Code of Civil Procedure § 337 (four years for a written contract)
- California SB 988 (2024), Freelance Worker Protection Act, Business and Professions Code § 18100 et seq.
Last reviewed:
SoloWOS tools mentioned here
More on contracts and signatures
- Are e-signatures valid with clients abroad? EU, UK, Canada, Mexico and BrazilE-signature rules for contracts with clients in the EU, UK, Canada, Mexico and Brazil: the law in each, signature levels, exclusions and a checklist.
- Electronic signature vs digital signature: the differenceAn electronic signature is any mark you adopt to sign; a digital signature uses cryptography and a certificate. What each proves and which you need.
- Freelance payment protection laws by state and city (2026)Freelance Isn't Free laws in 2026: NY State, NYC, California, Illinois, Seattle, LA, Minneapolis and Columbus. Thresholds, contracts, deadlines, remedies.
- How to know if someone opened your PDF (and what tracking can't tell you)A PDF attachment can't reliably report opens, and Apple Mail Privacy Protection broke email tracking. What a tracked link shows instead, and its limits.
Run your client work from one account
14 days free, no card needed · Then Basic for $2/month.
Start your free trial