dhSign - Certificate of Completion | dealhead Help Center

The Certificate of Completion (CoC) is an automatically generated audit document that accompanies every document executed using dhSign in dealhead.

The CoC provides a complete, tamper-evident record of how and when a document was signed, who participated in the signing process, and what actions occurred during execution. It is designed to support audit, compliance, and verification needs.

When a Certificate of Completion is Generated

A Certificate of Completion is generated automatically when a document reaches Executed/Final status.

This occurs after:

All required Signatories have completed their signing prerequisites
Signatures are released, either manually or at Milestone completion
The Executed/Final document is created

The CoC is generated at the same time as the Executed/Final document and can be downloaded alongside it.

How the Certificate of Completion is Used

The Certificate of Completion is commonly used for:

Legal and compliance review
Internal or external audits
Verifying document integrity
Providing evidence of signing activity and timing

The CoC does not replace the Executed/Final document. Instead, it serves as supporting documentation that explains how the executed document was produced.

What the CoC Contains

The Certificate of Completion is a standalone PDF and includes the following sections.

Document Identifiers

The CoC includes identifiers that uniquely bind it to the executed document:

Document ID: A dh-prefixed UUID (UUID v4) that also appears on every page of the Executed/Final document.
Filename and SHA-256 hash: The exact filename of the Executed/Final PDF and its SHA-256 hash. This allows Users to independently verify that the document has not been altered.
Completed timestamp: The date and time when the execution workflow completed, recorded in UTC.

Signatory Information

For each Signatory, the Certificate of Completion records:

A representation of the signature (full or partial image)
Signatory name and email address
e-Signature adoption timestamp and IP address, if applicable
e-Signature approval timestamp and IP address, or “N/A” for External Signature Pages
Whether approval was provided by an authorized proxy under an Attorney-Client Relationship
Authentication method used during signing, such as multi-factor authentication
The document dhVersion at the time approval was provided

External Signatories are clearly identified as having provided External Signature Pages.

dealhead Document Information

The CoC includes contextual information from the dealhead workspace, including:

Document title
Project name
Associated Milestone
Participating Teams
The dhVersion that was promoted to Executed/Final

Signature Event Log

The Certificate of Completion includes a chronological event log capturing key actions that occurred during the signing workflow.

Examples of recorded events include:

Signatory added or removed
Signature mapped or erased
Signature approved or withdrawn
Signature page uploaded or deleted
Milestone completion, when signatures are released at Milestone completion
Manual generation, when signatures are released manually
Executed/Final document created

Each event includes a timestamp, the acting User, and a descriptive message.

Document Integrity & Compliance

The Certificate of Completion is designed to support document integrity verification and electronic signature compliance.

It includes:

Instructions for recomputing the SHA-256 hash to verify the integrity of the Executed/Final document
A statement of compliance with ESIGN and UETA requirements
A reference to the document’s in-app History for additional audit detail