Glossary
Document generation
Also called: template generation, document assembly
Document generation produces a finished document by merging structured data into an approved template. Unlike a mail merge it always uses the current approved template version and files the output as a controlled record, which is what prevents retired clauses reappearing.
Document generation explained
The failure it prevents
Someone opens a previous document, changes the names, and sends it. That is how most business documents are actually produced, and it is how a clause the legal team retired eighteen months ago reappears in a signed agreement. The old copy on someone's desktop is the source of the problem, and no amount of policy prevents it.
Generating from the repository's current approved template removes the possibility, because the old version is not available to generate from.
What distinguishes it from a mail merge
A mail merge produces a file. Generation produces a controlled record: numbered, versioned, permissioned, with the captured values stored as searchable metadata and a retention rule attached on creation. The merge is the easy part; the filing and governance are where the time goes.
Template version recording
The output should record which template version produced it. When a clause turns out to be wrong, that field is what lets you identify every document generated from the affected version — which is the difference between a targeted remediation and a full portfolio review.
Where the output lands
A generated document should arrive in the repository already numbered, classified, permissioned and carrying its retention rule — not as a file someone then has to file. That is the difference between a generation feature and a merge, and it is where most of the saved effort actually is.
Driving it from another system
The higher-value pattern is generating from data that already exists elsewhere — an HR system, an ERP, a CRM — through the API, rather than re-entering it into a form. Re-entry is both slow and a source of error.
FAQ
Document generation: common questions
Can templates be authored in Word?
Usually, and it is the sensible choice — the people who own template wording are comfortable in Word, and forcing them into a different editor is a reliable way to have templates maintained outside the system.
What about documents that need heavy customisation?
Generate the standard parts and expect editing afterwards. A template that tries to cover every variation becomes unmaintainable, and the last twenty per cent of customisation is rarely worth automating.
Related terms
- Approval workflowAn approval workflow is a configured path a document must clear before it can be relied on, defining the steps, the approvers and the order.
- e-FormAn e-form captures structured data through defined fields with validation, rather than collecting it as text inside a document.
- Electronic signatureAn electronic signature is data attached to or logically associated with a document that indicates the signer's approval of it.
- EscalationEscalation is the automatic reassignment or notification that occurs when a workflow step is not actioned within a defined period.
- Policy acknowledgementPolicy acknowledgement is a recorded attestation that a named individual has read a specific version of a specific policy, at a given time.
Last reviewed: August 28, 2026. Browse the full glossary.