Electronic signature audit trail: what should it record?
An electronic signature audit trail is a chronological record connecting people, actions, authentication and the exact document version.
An electronic signature audit trail is the chronological record of a document transaction: which file entered the process, who was invited, what each person did, how identity checks ended and which completed file the evidence covers. Its value is practical: it should let a reviewer reconstruct the transaction without relying on memory.
The US ESIGN Act does not prescribe one audit-trail format. It does require retained electronic records to accurately reflect the information and remain accessible for later reproduction when another law requires retention. See 15 U.S.C. §7001(d). The trail is part of the evidence supporting intent, attribution, association and retention; it is not a legal conclusion by itself.
What gets recorded
A useful trail records the whole life of the agreement, not the moment of signing:
| Event | Why it is in the record |
|---|---|
| The document was uploaded, and what its bytes hashed to | Establishes what was sent, not what was later claimed to have been sent |
| Who was invited, in what order, and with what assurance level | "Who was asked" is a different question from "who signed" |
| Each invitation and reminder that went out | A signer who says they never received it is making a checkable claim |
| Each time a recipient opened the document | Opening is not agreeing, but never having opened it is a defence |
| Each identity check, passed or failed | A refused passcode attempt is the one an auditor goes looking for |
| Each field value as it was set, and by whom | Distinguishes what the sender pre-filled from what the signer typed |
| Consent to do business electronically | Required by several regimes, and trivially omitted |
| Completion, and the hash of the finished document | Ties the record to one specific file |
| Anything the routing skipped, and the rule that skipped it | A reviewer who never acted is the fact people query most |
If an approval step is skipped because an amount came in under a threshold, the record should say the approver was not required and identify the rule. Otherwise a later reviewer cannot distinguish a valid conditional route from a missing action.
Evidence checklist
| Review question | Evidence to preserve |
|---|---|
| Which document was presented? | Original version identifier and cryptographic hash |
| Who was asked to act? | Recipient identifier, delivery destination, role and routing order |
| What showed intent and consent? | The wording shown, affirmative action and timestamp |
| How was the person authenticated? | Method, result and failed attempts without storing unnecessary secrets |
| What changed during signing? | Field assignments and values, attributed to the acting recipient |
| What is the final record? | Completed-document hash, completion time, certificate and exportable event history |
Three properties that separate a record from a log
It is append-only. Corrections should be new entries rather than silent changes to old ones, so the chronology remains reviewable.
It is tamper-evident. Each entry should carry a hash that covers the entry before it, so removing or altering an entry anywhere breaks the chain from that point forward. Without this, "append-only" is a promise about the software rather than a property of the data.
What it claims and what it seals are the same set. Every material fact presented as tamper-evident should be inside the sealed data. When a certificate field is outside the seal, a verifier cannot use the seal to validate it.
Pactlyra has one definition of what the seal covers, and the certificate is sealed by calling it. A test edits every leaf of a real certificate one at a time and asks verification whether it noticed — so a fact added and left out of the seal fails on the day it is added, rather than in a dispute.
Questions to ask your current provider
- Can I export the trail in a form I can read without your software?
- Does the trail record failed authentication attempts, or only successful ones?
- If a recipient was skipped by conditional routing, does the certificate say so?
- Can I verify a completed document offline, without calling your API?
- If you went out of business tomorrow, what would I still be able to prove?
Question five tests portability. An exported record with documented verification can be reviewed even when the original account or service is unavailable.
What "verifiable" should mean
The strongest portable form includes the hashes, event chain, certificate and documented verification method in one export, with no network call or active account required. A certificate PDF may be a useful summary, but it should not be confused with independent verification of every claim it displays.
Pactlyra exports the completed file, certificate and evidence package together, and its evidence verifier runs without a Pactlyra account. Start a 7-day trial to test the flow with a non-production document.
Frequently asked questions
What is included in an electronic signature audit trail?
A useful trail includes the document version, recipients, delivery events, authentication results, consent, signing actions, field changes, routing decisions, completion time and final-document hash.
Is an audit trail required by the ESIGN Act?
The Act does not mandate a named audit-trail format. It does preserve requirements for accurate, accessible and reproducible electronic records when another law requires retention. A trail helps supply the evidence around the signature.
Is an IP address enough to prove who signed?
No. An IP address is one contextual signal and may be shared or reassigned. Attribution is stronger when delivery, authentication, intent, timestamps and the associated document all agree.
How can an audit trail be tamper-evident?
One approach hashes each event with the previous event's hash and seals the completed evidence set. Changing or removing an earlier event then causes verification to fail.
Should I download the audit trail?
Yes. Keep the completed document, certificate and exportable evidence together according to your retention policy, and confirm that they can be read and verified outside the vendor account.
Last reviewed 2026-10-15. Pactlyra produces a detailed evidence record for every completed document. Electronic signature validity depends on your jurisdiction, the document type, and how the transaction is carried out; nothing here is legal advice.