Managing defined terms across a transaction suite
Inconsistent definitions across a master agreement and ancillary documents create structural risk. How to synchronise them.
In a standard acquisition, the principal share purchase agreement (SPA) rarely sits alone. It is accompanied by disclosure letters, transition services agreements, escrow agreements, and employment contracts. The commercial mechanics rely on defined terms meaning exactly the same thing across every document.
When “Material Adverse Effect” or “Closing Date” drifts in meaning between the SPA and an ancillary agreement, it creates an ambiguity that litigators will later exploit. Keeping these terms synchronised manually requires discipline, particularly when multiple specialists are drafting concurrently. This guide outlines how to configure ZAAN to enforce definition parity across a multi-document suite.
Establishing the master glossary
The first step is designating an anchor document. In most transactions, this is the SPA or the master services agreement. If you are using Draft 3.9 to generate the suite, you can designate the primary agreement as the definitions anchor for the matter workspace.
When you begin drafting an ancillary document, such as a transition services agreement, Draft will automatically pull from the anchor. If you type a capitalised term that exists in the anchor, Draft will recognise it. If you attempt to redefine it, Draft will flag a warning. This prevents the common error of redefining “Affiliate” in an employment contract when it has already been heavily negotiated and tailored in the SPA.
Configuring Review for cross-document parity
Often, ancillary documents are drafted by opposing counsel or specialist teams. When these drafts arrive, they must be reviewed against the master agreement.
Review 4.2 allows you to load the current draft of your SPA into the playbook as a temporary, matter-specific rule set. By setting the severity tier for ‘Definition Mismatch’ to High, Review will scan the incoming document for any capitalised terms. It will then compare the text of those definitions against the SPA.
If opposing counsel has inserted a carve-out in the definition of “Confidential Information” in the non-disclosure agreement that does not exist in the SPA, Review will flag it. The inline redline proposed in Word will simply revert the ancillary definition to match the master text, with a citation noting the exact discrepancy between the two files.
Tracing nested and circular definitions
Definitions are rarely flat. They nest. “Change of Control” relies on “Voting Stock”, which relies on “Subsidiary”, which relies on “Control”.
When reading a draft, ZAAN-7B Counsel maps this dependency tree. If a draft introduces a circular definition—where Term A depends on Term B, which in turn depends on an element of Term A—Review flags it as a logical error.
This mapping is particularly useful when reviewing markups. If opposing counsel strikes a seemingly innocuous defined term in schedule four, Review traces every instance where that term is relied upon in the main body. The flag will appear not just where the deletion occurred, but at the site of the most severe downstream consequence. If deleting “Key Personnel” quietly nullifies a termination right in clause 11, the reviewer is notified at clause 11.
Handling incorporated definitions by reference
Sometimes, an ancillary document does not repeat the definition but states: “Capitalised terms used but not defined herein shall have the meanings ascribed to them in the SPA.”
While this saves drafting time, it shifts the burden to the reviewer, who must now cross-reference constantly. When reading an ancillary document with this clause, Review 4.2 temporarily imports the SPA’s glossary into its working memory. If a reviewer hovers over a capitalised term in the ancillary document, the Word add-in displays the full text of the definition from the SPA. If the ancillary document uses a capitalised term that is neither defined locally nor in the SPA, Review flags it as an undefined term, categorised by default as a Medium severity issue.
Managing late-stage amendments
The highest risk of definition drift occurs in the final forty-eight hours of a transaction. The commercial parameters change, and “Target Working Capital” is redefined in the SPA at the last minute.
If the suite is indexed in the matter workspace, you can use Recall to locate every instance of the altered term across the transaction documents. Recall does not simply run a text search; it identifies where the concept is active and where the specific definition is invoked. You can then push an update via Draft to align the ancillary documents before execution.
Because ZAAN operates with a zero-retention architecture, this temporary cross-referencing index is held only for the duration of the active session in your firm’s encrypted tenant space. Once the matter is closed and the final versions are exported to your document management system, the working memory is destroyed.
A transaction suite is only as robust as its weakest definition; keeping them aligned should be a matter of architecture, not memory.