Audit trail
A signature is only as good as the evidence that it happened. Every document carries a history of what occurred, when, and to whom — recorded by the platform rather than entered by anyone.
What gets recorded
Section titled “What gets recorded”The timeline on the History card shows these events:
| Event | Recorded as |
|---|---|
| Document was created | {name} ({email}) created the document. |
| Signer was notified | All signers were notified to sign the document. |
| Document signed | A signer completed their signature — the sentence says with which kind of signature (for example, {name} ({email}) signed the document with Signature with Digital Mobile Key (CMD).) |
| Document completed | All steps are completed and the document has been successfully signed. |
| Document was rejected | {name} ({email}) has rejected signing the document. |
| Document was cancelled | {name} ({email}) cancelled the document. |
| Document has expired | The document {name} expired on {date} |
| A signer’s turn came up | {name} ({email}) was activated by the signing order and can now sign. |
| Signer promoted with their own round | {name} ({email}) now signs in a round of their own. |
The platform records more than this — for example each recipient added, the processing before sending, and the notices sent when someone declines or cancels. Those events go into the hash chain described below, but have no line of their own in the timeline.
The record shows not only that someone signed, but that they were properly asked — which is the part that matters if a signature is ever disputed.
When someone declines, or cancels, the reason they gave appears alongside the event under Motive.
How the history is chained
Section titled “How the history is chained”Every event is recorded with a hash — a SHA-256 fingerprint — computed over the hash of the same document’s previous event, the document, the recipient, the event type, the status, the event data and the instant it was recorded. A document’s first event has no predecessor; every later one is tied to the one before it.
That is what makes the history verifiable:
- Altering a line changes the hash it should have, and it no longer matches what was stored.
- Deleting or inserting a line breaks the next line’s link to the previous hash.
Verification rebuilds the chain from the first event to the last and stops at the first line that does not match. It runs when the Completion Report is generated, and the result goes into the sealed report: the verdict, the number of verified entries and the hash of the last event (Chain root hash (SHA-256)).
The platform itself only ever adds lines to the history: it refuses to save any change to, or removal of, a line that is already there. The one exception is the permanent deletion of the document, and even then the history is copied, with its hash chain, into an evidence record that outlives the document — see Data retention and privacy.
The chain uses no secret key: someone able to write directly to the database who recomputed every later line would get a consistent chain. It is the last event’s hash, fixed in the sealed report, that would stop matching.
An older document may have events recorded without a hash. Verification skips them; if none of the document’s events has a hash, the report says the chain is not verifiable rather than inventing a verdict.
Where to find it
Section titled “Where to find it”Open a document and go to its audit view. Above the timeline (History) are the Participants — the signers and, separately, the Copy Recipients — and the document’s Details, which also give access to the Completion Report of a completed document.

Related
Section titled “Related”- Signature levels — what each level proves
- Document lifecycle — the states behind these events
- What is in the completion report — where the chain verdict is kept