What the audit certificate of a signed document contains
What Drime Sign records for each signature request, what the audit certificate shows about the document, the signers and each event, and how to get it.
For every signature request, Drime Sign keeps an audit trail: who received the document, who opened it, who signed and when. When everyone has signed, this trail becomes the audit certificate, a PDF delivered with the signed document.
#Get the audit certificate
Once every signer has signed, open the document in Tools > Sign, then:
click the arrow next to Download (More download options), then Download audit trail for the certificate alone;
or choose Download signed PDF + audit (ZIP) for both.
See Follow and download signed documents.
#What it contains
Section | What you find there |
|---|---|
Document information | The document's name, the certificate ID, the signature level (simple or advanced), the dates the request was created and completed, the time zone of the dates, and the SHA-256 fingerprints of the original document and of the signed PDF |
Owner | The person who sent the request |
Signers | For each signer: name, email address, status, date of signature, the checks done (email or phone verified by a code), and the IP address, approximate location and browser used |
Signatures | The signature and initials each signer drew, typed or uploaded |
Attachments | The files signers added in attachment fields, with who added them |
Event log | Every step, with its date and who did it: document created, sent for signature, viewed, signed, declined, reminders, codes sent and verified, consent to sign electronically, all signatures completed, downloads |
Integrity verification | A summary of the checks made on the document when it was sealed |
The certificate is in French when your Drime account is in French, otherwise in English. Its dates follow the time zone of your account.
#What is written to the trail
Drime Sign records the events as they happen, before the document is completed:
sending, and each email reminder;
each time a signer opens the document, and each verification code sent or confirmed (see Verify your signers' identity with a code);
each signature, or a refusal;
changes to a signer's link (see Share a signing link yourself).
#Check a document against its certificate
The certificate prints the SHA-256 fingerprint of the signed PDF. On the verification page, app.drime.cloud/sign/verify, anyone can drop the PDF, or look the document up by that fingerprint. The PDF is checked, not stored.
#If it doesn't work
What you see | What to do |
|---|---|
Download audit trail is missing | The certificate is produced once every signer has signed. Check the request's status in Tools > Sign. |
A signer shows Declined | The signer refused to sign, so the document will not be completed. See When a signer declines. |
#Next steps
Was this helpful?