The Certificate of Completion
The human-readable proof attached to every sealed document. Who signed, when, and how the record verifies.
Every completed envelope produces a certificate of completion. A page attached to the sealed PDF that summarizes the signing record in human-readable form. It is the document you hand a lawyer, an auditor, or a counterparty who asks "prove it."
What the certificate shows
- The parties. Every recipient, their role, and their outcome (signed, approved, declined).
- The timeline, sent, viewed, consented, signed, each event with its timestamp.
- Identity evidence. How each signer was verified: email, access code, the gates they passed.
- The record fingerprint. The integrity hash of the signing record, the anchor for verification.
- Protection state. Whether watermarking and screenshot protection were active during signing.
- A support reference. The envelope identifier support can use to pull the underlying record.
How it's produced
At the moment the last required recipient finishes, Docshark seals the envelope: the signed document, the certificate, and the audit evidence are bound into the final PDF package. From that point the package is fixed. The sealed PDF is what everyone downloads and what verification checks against.
Using the certificate
- Attach it to your records. The sealed PDF is the document of record; keep it with the contract file.
- Hand it to challengers. "prove they signed" is answered by the certificate plus a verification pass.
- Check it yourself. Upload the sealed PDF at the verification page to confirm nothing was altered after sealing.
The machine-readable twin
The certificate is the human summary; the audit evidence JSON is the complete machine record. Every event in the hash chain. Download both from the envelope detail page.