Every document that moves through Lucid Signing carries a second document you never have to write: its audit trail. It is the running record of everything that happened to the file, from the moment it was uploaded to the moment it was sealed.
The events we record
The trail is an ordered, immutable log. Each meaningful moment in a document’s life becomes an entry:
- Created - the document was uploaded and prepared.
- Sent - signing links were issued to recipients.
- Viewed - a recipient opened the document.
- Signed - a recipient applied their signature and confirmed intent.
- Declined - a recipient refused, optionally with a reason.
- Completed - the last required signature landed.
- Downloaded and voided - after the fact.
What each entry stores
An event is only useful if it can answer “who, when and from where”. So every entry captures the actor’s email, their IP address, the browser user agent of the device they used, and a UTC timestamp. Read together, these place a specific person at a specific action at a specific moment.
Why it is stored separately
The trail lives apart from the document and cannot be edited from within the application. That separation is deliberate: an audit trail you could quietly rewrite would be worth nothing. When a document completes, the trail is sealed alongside the final PDF, so the record and the signature travel together forever.
What it looks like in practice
If you ever need to know exactly what happened to a document, you do not go hunting through inboxes. You open it and the story is right there: opened at 09:14 from Johannesburg, signed 90 seconds later, consent recorded, the same file hash from send to seal. That is the difference between a signature and a fully documented one.
Ready to send yours?
Free forever for three documents a month.