Recall 2.9: indexing draft iterations to track conceded positions
Executed agreements show the final compromise. Recall now indexes the version history to surface what was struck, amended, or conceded during the negotiation.
A database of executed contracts is an archive of compromises. If a partner asks what limitation of liability cap was agreed with a specific vendor, the final PDF provides the answer. If they ask what the original ask was, and what the firm gave up to secure the deal, the PDF is silent.
Recall 2.9 ships today. It extends our plain-language search architecture beyond the final executed agreement to include the draft iterations stored in a firm’s document management system (DMS). By mapping the delta between the first draft and execution, Recall now surfaces the negotiation history of any clause.
Mapping the delta from first draft to signature
Tracking a clause through six rounds of turns is not a simple string-matching exercise. Between the first iteration and the final version, paragraph numbering shifts. Definitions are capitalised. Sub-clauses are broken apart, merged, or moved entirely.
We use ZAAN-7B Counsel to maintain a semantic index of clause identity across document versions. If an assignment restriction begins in Section 11.2 of the main body, but opposing counsel moves it to Schedule 3 during the second turn, the trace view maintains the link. The model evaluates the substantive obligation, not the paragraph anchor.
When a user looks at a survival clause in the executed contract, Recall 2.9 provides a ‘Version Trace’ tab. This displays the text exactly as it appeared in the initial draft, alongside the specific inline redlines introduced by opposing counsel and accepted by the client. It reconstructs the timeline of the provision.
Querying the concession
This changes how a legal team interacts with its precedent database. Instead of searching merely for “broad MAC clauses in software acquisitions”, a user can query “MAC clauses where we successfully struck a pandemic carve-out”.
Recall parses the natural language query, identifies the target legal concept, and scans the version differentials. It surfaces matters where the initial draft contained the carve-out, a subsequent version showed it struck out, and the final version omitted it.
Consider limitation of liability carve-backs for gross negligence. A senior associate negotiating a SaaS Master Services Agreement needs to know if the firm has previously accepted a reciprocal carve-back with a specific enterprise vendor. By querying the negotiation history, Recall shows not just that the firm accepted it, but whether it was offered in the first draft or conceded in the final hours of the deal to break a deadlock. Every result includes a citation to the specific DMS document ID and version number.
Filtering the noise of internal drafts
A typical transaction generates dozens of internal versions for every single draft sent across the table. Indexing every minor save creates a noisy, illegible trace.
To resolve this, Recall 2.9 relies on the two-way DMS sync we refined earlier this year. We configure the indexer to look for specific triggers: documents attached to external emails, versions explicitly marked as ‘Final Draft’ or ‘Sent to Counterparty’ in the metadata, or drafts containing comments from external email domains.
We ignore the intermediate internal turns. The trace focuses strictly on the adversarial exchanges, keeping the interface clean and the database performant.
Calibrating the playbook
Firms spend significant time drafting playbooks that define fallback positions and redlines for Review. These documents frequently drift from reality. A playbook might insist on a strict 30-day cure period for material breach, but the negotiation history might show the firm concedes a 60-day period in 85% of transactions over a certain value.
By surfacing these patterns across a firm’s matter history, Recall provides the data required to calibrate the playbook. If a position is systematically conceded by the third turn, the initial redline is likely generating friction without altering the final risk allocation. Review can then be adjusted to flag the 60-day period as a ‘Note’ rather than a ‘High’ severity issue, saving first-pass review time.
Similarly, when Draft composes the next agreement, it can pull from the calibrated playbook, ensuring the firm’s opening position is aggressive but anchored in market precedent rather than outdated guidelines.
Permissions and ethical walls
As always, zero retention and strict access controls apply. Recall 2.9 enforces ethical walls at both index time and query time. If a user does not have permission to view the final agreement in the DMS, they cannot search its negotiation