Signing & execution
Review signing evidence and the audit trail
Use the owner audit view and evidence PDF to review recorded signing events, then understand what an integrity check can and cannot establish.
After you send a signing request, the envelope owner can review its recorded activity in the e-sign workspace. The record can include event types, timestamps, actor labels, and available signing context such as an IP address or user agent. Some context can be absent, so check the individual event rather than assuming every field is present.
Example only · anonymised
Signature Certificate
Completion and audit evidence record
Document
Example services agreement
Status
Completed
Signer evidence
| Signer | Method | Signed at | Recorded IP |
|---|---|---|---|
| Aarav Mehta | Drawn signature | 16 Aug 2026, 10:24 IST | 198.51.100.24 |
| Nisha Rao | Drawn signature | 16 Aug 2026, 10:31 IST | 198.51.100.61 |
Signing timeline
Signing request sent
Workspace owner · 16 Aug 2026, 10:08 IST
Signature completed
Aarav Mehta · 16 Aug 2026, 10:24 IST
All parties completed
Wizard Legal record · 16 Aug 2026, 10:31 IST
Review the record
- 1Open the completed or in-progress envelope from the e-sign workspace and select its audit trail.
- 2Check the event sequence, signer activity, timestamps, and any available context against the document and the process you expected.
- 3Use Verify integrity when it is available. A verified result means the stored sealed events currently match the SHA-256 chain; it is not a legal-opinion or identity-verification result.
- 4If an older record is shown as legacy unsealed, its historical events can be displayed but are not sealed by the current chain. If an integrity check is invalid, do not rely on the evidence until it has been investigated.
- 5Download the evidence PDF only when the workspace marks it ready, and retain it with the final document and relevant transaction records.
What the record does not decide
- An audit record does not by itself prove a signer's legal identity, authority, or intention.
- It does not replace the document-specific requirements for the final version, witnesses, stamping, notarisation, registration, or professional review.
- A provider-backed certificate or signature should only be relied on after the applicable provider workflow is enabled and its separate requirements have been completed.
- Keep the signed document, evidence record, and any related approvals or communications together so the broader transaction can be reviewed later.