Release 3 min read

Draft 4.0: generating ancillary documents from a single term sheet

Drafting an SPA is only half the transaction. Draft 4.0 introduces suite generation, propagating deal parameters across escrow agreements and board resolutions without re-keying.

2026 · 10 · 31·admin

In April, Draft 3.9 introduced precedent-hovering for single contracts. Today, we are shipping Draft 4.0. The primary addition is transaction suite generation, moving our drafting surface from single-document composition to multi-document consistency.

A mid-market acquisition is rarely contained in one file. It is a Share Purchase Agreement (SPA), an Escrow Agreement, a Transition Services Agreement (TSA), restrictive covenants, and a stack of corporate approvals. Until now, Draft generated these sequentially. You prompted the SPA, then you prompted the Escrow Agreement. Deal parameters—buyer entity, purchase price, long-stop date—had to be verified in each generation.

Draft 4.0 introduces a shared parameter state for the entire transaction.

The parameter table as ground truth

The workflow begins by uploading the executed term sheet. Draft 4.0 uses ZAAN-7B Counsel to extract a structured brief of the deal: entities, consideration, closing conditions, and governing law. This is presented in a central parameter table.

Once the drafting lawyer confirms these values, they act as the ground truth for the entire suite. If the purchase price is adjusted during late-stage negotiations, you update the parameter table once. Draft 4.0 cascades this change across the SPA, the Escrow Agreement, and the board minutes.

It handles nomenclature variations automatically. If your SPA template defines the acquiring entity as “Purchaser” but your Escrow template uses “Buyer”, the model maps the parameter to the correct defined term without breaking the template’s internal logic. It does not blindly find-and-replace; it reads the definitions section of each target document and assigns the variable accordingly.

Managing conditional logic across the suite

Passing a string of text across documents is a mail-merge. Contract drafting requires legal logic.

If the term sheet includes an earn-out provision, the SPA requires specific drafting in the consideration clause. But the presence of an earn-out also dictates changes in the ancillary documents. The seller’s employment agreement may need a bespoke bonus waiver, and the Escrow Agreement may require a distinct release schedule.

Draft 4.0 evaluates the parameter table against your firm’s playbook. If it registers an earn-out, it selects the corresponding precedent blocks for all affected documents in the suite. We do not attempt to draft bespoke commercial metrics from scratch. The system inserts the firm’s standard earn-out architecture, leaving highlighted brackets for the financial targets that require counsel’s judgement.

Similarly, if the term sheet specifies a split signing and closing, Draft 4.0 automatically includes the necessary conditions precedent in the SPA and generates the separate closing certificates. If it is a simultaneous sign-and-close, those documents are omitted from the suite entirely.

Jurisdictional variations in cross-border deals

In multi-jurisdictional transactions, the suite often spans different legal systems. The master SPA might be governed by English law, but the local share transfer agreement must comply with the target’s jurisdiction.

Draft 4.0 allows you to set governing law at the document level within the suite. When generating a local transfer deed for a Swiss subsidiary, the system queries Recall for the firm’s Swiss precedents. It applies the standard Swiss boilerplate and execution blocks, while still injecting the correct global deal parameters from the central table.

This prevents the common error of accidentally carrying over English-law boilerplate into a document that requires strict local-law compliance. The model recognises the jurisdiction mismatch and defaults to the local precedent.

Citations back to the term sheet

Our core rule for Draft is that every generated clause must have a citation. In Draft 4.0, this principle extends across the transaction suite.

When a partner reviews the draft Escrow Agreement in Word, they can click on the escrow amount. The ZAAN add-in opens a side panel showing exactly where that figure originated in the term sheet, or which user manually updated it in the parameter table.

This traceability reduces the time spent cross-referencing drafts against the commercial agreement. Across our active accounts, we observe that checking ancillary documents for consistency accounts for up to a fifth of pre-closing drafting time. Much of this is mechanical verification: ensuring the long-stop date matches, verifying entity suffixes, checking that defined terms align.

Draft 4.0 shifts the software’s boundary from the document to the transaction. By centralising the deal parameters, we reduce the mechanical burden of consistency. The focus remains on the substantive allocation of risk.

See it on a contract you have already reviewed.

Send us a draft your team has already redlined and we will show you what ZAAN catches, and what it misses.