Template Changes and Sent Envelopes
Learn why editing a Verdocs template does not change the documents and fields in envelopes already sent.
Updating a template in Verdocs does not affect envelopes already sent. Each new envelope receives its own envelope documents, envelope fields, and recipient records. Later template edits do not replace the documents or field definitions in those sent envelopes.
How templates and envelopes relate
A template defines a reusable signing workflow: its documents, field placements, and roles. An envelope is an individual signing transaction, with its own documents, fields, recipients, and status.
Roles describe participants in the template, such as Buyer or Seller. Recipients are the participants for a particular envelope. Each EnvelopeField belongs to an EnvelopeDocument and identifies its recipient by role name.
When an envelope is created from a template, the distinction is:
| Resource | Relationship to the envelope |
|---|---|
| Documents | The envelope receives its own envelope documents. |
| Fields | The envelope receives its own envelope fields. |
| Recipients | The envelope has its own recipient records for the transaction. |
| Roles | Roles remain tied to the template; they are distinct from the envelope's recipient records. |
The envelope's relationship to its source template does not make its documents and fields a live view of that template. Editing the template does not synchronize those edits into envelopes already sent.
Example: updating a service agreement
Suppose you create and send an envelope from a service agreement template. You then replace the template's agreement document and move a signature field.
The sent envelope keeps its own agreement document and signature field placement. A new envelope created from the updated template uses the revised template documents and fields. You can therefore update the template for future transactions without changing the documents and fields in the envelope you already sent.
What this means for integrations
Use template edits to prepare future envelopes. If a document or field needs to change for a transaction already sent, editing the source template will not apply that correction to the existing envelope.
When retrieving an existing transaction, use its envelope documents and fields rather than reconstructing it from the current template. The template may have changed since that envelope was created.
This behavior describes the effect of template edits. An envelope still progresses through its own signing workflow, including recipients entering field values and completing their actions.
For a step-by-step implementation, see Server Workflow with Static Templates. For related concepts, see the Templates & Documents FAQ and the REST API reference.