How QCDS Preserves Sent and Completed Request History After Later Edits

Send Now is the history boundary. QCDS freezes the transaction into an immutable Request snapshot so later changes to reusable Templates, Contacts, email templates, provider settings, or workspace defaults do not silently rewrite what was actually sent and signed.

What QCDS Freezes at Send

The Request snapshot preserves the exact transaction-specific documents, fields and creator elements, participant/role mapping, routing, timing/policy, branding, and message source used for that Request. QCDS records snapshot/integrity hashes that are later surfaced in Request Details and the Completion Audit Trail.

Completion is then built from that immutable snapshot plus the final signer-field/evidence records—not by reopening the current reusable Template and asking what it looks like today.

Later Template or Document Edits

Editing a reusable Template creates or advances Template draft/version state; it does not change the Template/document version frozen into an already-sent Request. Likewise, uploading a new document version preserves earlier immutable versions instead of overwriting the source used by the historical Request.

Later Contact Changes

A sent participant keeps the frozen Contact-derived snapshot used for transaction evidence. QCDS can still use certain current Contact values for operational behavior—for example, a corrected preferred language can affect later messages/signer-page presentation, and an approved email correction creates later delivery evidence.

Those operational corrections are recorded as later events; they do not erase the original participant snapshot or old delivery history.

Later Email, Provider, and Workspace Changes

Reusable Email Template edits do not rewrite the source frozen for an existing Request. Request-specific invitation edits remain Request-specific. Identity Verification is bound to the provider profile selected at send time, so changing Global/account provider configuration later does not migrate a pending sent Request to a different provider.

Workspace defaults such as expiration, reminders, language, or other creation-time defaults affect later preparation. The sent Request retains its own frozen policy/timing evidence, except where QCDS deliberately resolves a current operational value such as participant display language.

Completed PDF Regeneration Still Uses Historical Evidence

Regenerate Completed PDF rebuilds presentation from the same immutable Request snapshot and final stored signer values. It can create a new artifact revision, but it does not import later Template edits or alter signatures, signer values, timestamps, or signing evidence.

Community Discussion

Want to compare workflows, share practical tips, or discuss how you use this QCDS feature? Visit the QC Digital Signature Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.