What makes an audit trail worth anything
Most audit trails are a list. The useful property is that nobody — including the vendor — can quietly change it.
Evidence · 2026-10-20 · 6 min read
Every e-signature tool produces an audit trail. Almost all of them are a table of events the vendor wrote and the vendor stores. In a dispute with a third party that may be plenty. In a dispute where the record itself is questioned, a list the vendor could have rewritten is not much of an answer.
Three properties to look for
- Append-only. Corrections are added as new entries rather than editing old ones, and the storage layer enforces it rather than the application promising it.
- Chained. Each entry commits to the one before it, so changing an entry invalidates everything after it.
- Anchored. Signed checkpoints commit to the whole set, so *deleting* an entry is detectable too — which a chain alone does not give you, because a truncated chain is still a valid chain.
Why the third one matters
This is the part most implementations miss. If each record points back at the previous one, altering record 7 breaks records 8 onward and is obvious. But simply removing records 8 onward leaves a shorter chain that still verifies perfectly. Only a commitment to the complete set — a signed checkpoint over an ordered tree of all the entries — catches that.
And then: can you check it yourself?
Verification that only happens inside the vendor’s dashboard is verification by assertion. The useful version ships you the public key, the digests and the method, so you or your lawyer can recompute everything offline, years later, with no account.