How-to
Reading the audit certificate on a signed PDF
Every signed PDF ends with an audit certificate page showing exactly who signed when, from where, and the full chronology of events.
Jump to section
What's on the audit certificate
When the last signer signs, the system produces a final PDF with everyone's signatures embedded in the document, plus an extra page at the end — the audit certificate.
For each signer
- Name and email
- Role (signer, approver, etc.)
- Exact timestamp of signing (in UTC)
- IP address at the time of signing
- Browser and operating system used
Chronological event timeline
Every event from envelope creation to completion:
- Created — when, and which admin created it
- Sent — when each recipient received their link
- Viewed — first time each recipient opened the document
- Signed — when each recipient signed
- Completed — when the final signer signed
Each entry includes who did it and the timestamp.
Why it matters
Under UK Electronic Communications Act 2000 and EU eIDAS, a Simple Electronic Signature is legally valid if you can demonstrate:
- Intent to sign — the recipient took an action (drew a signature) that signified agreement
- Document integrity — what they signed is what they intended to sign
- Identifying the signer — to a reasonable degree
The audit certificate captures the intent (when they signed) and the document integrity (a signed PDF you can store). The signer's identity is tied to the email address used — fine for employment contracts, offer letters and NDAs. For higher-assurance signing (property purchases, M&A deals), you'd use a more advanced electronic signature with separate identity verification.
Downloading
The signed PDF is available from the envelope detail page once everyone has signed. Signers also get a copy emailed to them after they sign.
What if the document is tampered with later?
The signed PDF is a normal PDF — anyone with the file can technically alter it. Tamper-resistance comes from keeping your copy safe (in HR's document store) AND your audit log entry showing when the original was signed.
For tamper-resistant signatures at the byte level (Qualified Electronic Signature under eIDAS), you'd need a dedicated signing service with cryptographic certificates. That's outside Blankitt's scope today.