WolfSDKWolfXLWolfPPTWolfDocxWolfRender

WolfDocx - contract generation

How can Python generate many legal contracts from one Word template?

For high-volume legal contract generation in DOCX, use WolfDocx Commercial mail merge when your reviewed Word template contains MERGEFIELD fields. It produces one document per record and publishes the batch only after its checks pass. This workflow is not a claim to a throughput lead: no comparative contract-generation benchmark is supplied here.

Separate contract drafting from contract population

Keep the approved legal wording, styles, and field formatting in the template. Python supplies client names, dates, and other agreed values rather than reconstructing the contract paragraph by paragraph. This makes the boundary explicit: the template defines the document, and the records define which values change for each recipient. It does not decide which legal terms a client needs.

Prepare a valid Word document with two real merge fields, ClientName and EffectiveDate. Ordinary text that looks like a placeholder is a different template format. The example creates a records file itself; run it in a fresh working directory containing that template and with WolfDocx Commercial available. These mail-merge functions are not exports of the MIT wolfdocx 0.1.0 pip package.

Generate one contract per record

import hashlib
import json
from pathlib import Path

from wolfdocx.mail_merge import merge_documents, parse_mail_merge_request

# Create this template in Word with real MERGEFIELD fields named
# ClientName and EffectiveDate, not literal {{ClientName}} text.
source = Path("contract_template.docx")
data = Path("contracts.json")
data.write_text(json.dumps({
    "records": [
        {"id": "contract-acme", "values": {
            "ClientName": "Acme Corp", "EffectiveDate": "2026-11-09"
        }},
        {"id": "contract-north", "values": {
            "ClientName": "North Ltd", "EffectiveDate": "2026-11-10"
        }},
    ]
}), encoding="utf-8")


def sha256(path):
    return hashlib.sha256(path.read_bytes()).hexdigest()


report = merge_documents(parse_mail_merge_request({
    "source": str(source),
    "source_sha256": sha256(source),
    "output_dir": "generated_contracts",  # Must not already exist
    "data": {"path": str(data), "sha256": sha256(data)},
}))
assert report.passed, report.code
print(report.counts)
# generated_contracts/contract-acme.docx and contract-north.docx

Each record has an id and a values map. The id becomes the output filename, so choose unique identifiers that do not expose unnecessary client information. Supply exactly the values expected by this template. Add further recipients to the records list, not by repeatedly overwriting the template or one output file.

What happens before the batch becomes visible?

The request binds both input files to SHA-256 hashes. WolfDocx works from a template snapshot, stages each recipient, reopens the staged output for verification, and checks the input identities again before publishing the new directory. A refused request does not publish a partial recipient batch or replace an existing destination. Check the report before treating the contracts as generated.

Repeating fee rows and nested record data belong to the mail-merge region workflow, not to a loop that copies raw XML between documents. Start with the scalar fields above, then review the separate mail-merge guide before adding repeating regions. Keep any later approval, electronic signature, or delivery step outside this generation call.

What throughput evidence is available?

This page supplies no contracts-per-second figure and no ranking against docxtpl or docx-mailmerge. The existing WolfDocx mail-merge guide also states that no throughput comparison against those libraries has been published. A sample batch proves neither production capacity nor a latency target. Evaluate your own reviewed template, record sizes, storage, and failure handling before planning a production queue.

What it does not do

  • It does not draft legal clauses, choose jurisdictional wording, or replace legal review.
  • It does not interpret Jinja2 templates. Use docxtpl for templates written in that syntax.
  • Missing or unknown record values, unsupported field instructions, and signed templates can refuse the batch.
  • It does not sign, email, or render the contracts to PDF. A successful merge is not proof of Word-identical pagination.

Next: mail-merge regions and field behavior, literal-placeholder table templates, and merge separately approved Word files.

Get WolfDocx

WolfDocx Community is MIT-licensed and free, including commercial use. It edits existing .docx files in place in pure Python and does not render pages or convert to PDF. WolfDocx Commercial does not change those rights.

pip install wolfdocx

WolfDocx Commercial is an organization-scoped subscription. WolfDocx Community installs from public PyPI with pip install wolfdocx. WolfDocx Commercial installs from the authenticated WolfDocx package index with a per-purchase credential, issued on the checkout success page after payment and reissued through https://wolfxl.com/recover.

Review the scoped before-and-after memo files in the reporting walkthrough, or ask about your document before purchasing if compatibility is uncertain.

See WolfDocx Commercial

Related tasks