What a template holds
The document, the field positions, and named roles — "counterparty", "countersigner" — rather than named people. At send time you fill each role with a real person. That is what makes a template reusable rather than a saved envelope.
Templates
New template
| Template | Roles | Fields | Used (90d) | Updated |
|---|---|---|---|---|
| Mutual NDA | Counterparty, Countersigner | 6 | 14 | 2 months ago |
| Engagement letter | Client, Partner | 9 | 22 | 3 weeks ago |
| Statement of work | Client, Delivery lead | 11 | 31 | 5 days ago |
| Contractor agreement | Contractor, Company | 8 | 4 | 7 months ago |
When to make one
- The third time you place the same fields on the same document.
- When the document is one a non-specialist sends — a template removes the chance of a missing field.
- When the layout is fiddly. Placing fields on a twelve-page agreement once is much better than eleven times.
- Not when the document changes materially each time. A template of a document that always gets edited is a trap.
Templates are not versioned
Updating a template replaces it. Envelopes already sent keep the document they were sent with — that is correct and important — but there is no history of what the template used to be. If your legal team revises a standard agreement, keep the superseded PDF somewhere yourself; the module will not.
What this does not do
No versioning
One current version, no history.
No approval before use
Anyone with the module can edit a template.
No variable text
Roles are placeholders for people, not for clauses or values.
No template folders
A flat list.
Questions
Can a template have three roles?
Yes.
Does editing a template change sent envelopes?
No.
Can we lock a template?
No.