Keep the context behind every signature.

Answer the questions that arrive after signing

An operations colleague may need to know whether every party signed. A customer may ask when their agreement completed. A reviewer may want to understand a recipient correction. Keeping the document’s recorded activity together gives your team a concrete starting point for those questions.

TrustInk records envelope events and signing activity, including recipient consent when a signature is submitted. Signer records include signing timestamps and the captured IP address and browser information. The workspace also exposes recipient viewing and signing progress. Interpret these details in context: a recorded IP address alone does not establish a person’s identity.

Distinguish the document from its evidence

The completed PDF contains the captured field values and an appended completion record. TrustInk stores a SHA-256 hash of the delivered completed file. Comparing that hash with the downloaded file helps establish whether you are handling the same bytes as the recorded artifact.

The audit log links records using hashes and supports an integrity check that recomputes the chain. This provides a way to check consistency within the recorded history. It does not turn a typed or drawn signature into a qualified digital signature, and the hash check is not an independent identity verification service.

Keep a useful record with the completed agreement

After completion, the sender can download a standalone Certificate of Completion. It identifies the envelope and document, records completion information and includes signer details, the completed-file hash and the audit-chain head at the time of issue. Keep it with the completed PDF in the system your organisation uses for agreement records.

An agreement still in progress is a different record: some people may have signed while others have not. Check the envelope status before treating a downloaded PDF as the final agreement. A standalone completion certificate becomes available only after the envelope is completed.

Match the signing process to the transaction

Decide who should receive the document, whether an access code is appropriate and how your team will review the finished record. TrustInk requires affirmative consent to electronic signing and checks required fields before accepting a submission. Those controls help create a clearer process around the agreement.

Choose document wording, authentication and retention arrangements that fit your organisation’s requirements. The product provides recorded evidence for review; it does not promise that every document or transaction meets every jurisdiction’s requirements.

Common questions