Define the contract set before asking for terms
A supplier folder may contain an executed master agreement, two order forms, an unsigned amendment, and a schedule downloaded from a portal. Asking an AI tool for the liability cap across the folder can produce a fluent answer that mixes incompatible versions.
Start with one agreement family. Identify the contracting entities and the documents said to govern that relationship. This is a document-control exercise before it becomes a legal interpretation exercise. Keep a separate list of material that has been supplied for background only.
Choose fields that expose document relationships
| Field | Record | Check |
|---|---|---|
| Document status | Executed, draft, or uncertain | Inspect signature and delivery evidence |
| Effective date | Exact wording and source | Distinguish it from the file date |
| Amended provisions | Clause numbers and replacement text | Check defined terms and schedules |
| Precedence | Express hierarchy wording | Escalate conflicts and gaps |
Include a source reference for each extracted fact. Keep the lawyer's conclusion about the operative terms in a separate column, with an owner and a review status.
Work through a narrow amendment example
Assume the master agreement caps liability by reference to annual charges. A signed amendment changes only the confidentiality carve-out, while an unsigned draft proposes a new monetary cap. A combined summary that adopts the draft cap creates a false negotiating position.
Extract the amendment's scope, any language preserving the rest of the agreement, and evidence of execution. Report the proposed cap as a draft issue rather than an agreed term. If the business says the draft was accepted by another route, request the relevant evidence and refer the legal effect to the responsible lawyer. Do not infer acceptance from the presence of the file.
Separate extraction from interpretation
Use a focused request such as: identify each document that purports to amend clause 12, quote the replacement wording, and list any unresolved status questions. Avoid a single instruction to decide which document wins. The narrower output is easier to verify and less likely to conceal an assumption.
Judicio's Review Matrix supports up to 25 questions in one matrix. Begin with a compact set about identity, status, dates, amendment scope, and precedence. Add questions about commercial risk after the operative document set has been checked.
Maintain the record through negotiation
When a new turn arrives, preserve the previous review result and add the new document to the agreement family. Compare the changed provisions and update only the affected conclusions after verification. An extracted row should show why it changed.
For in-house teams, hand the business a current-position summary and an exception list. For external counsel, state the documents reviewed and the assumptions that remain with the client. Neither recipient should have to reconstruct the version history from an attachment folder. Keep drafting instructions linked to the approved conclusion, not directly to an unreviewed extraction.
Sources and next steps
This is an editorial workflow guide for legal professionals. The suggested checks are our practical recommendations, not a statement that a regulator requires a particular software workflow.
Explore Review Matrix and Document Review, or review Judicio's regional coverage and limitations. Check the underlying source and your organisation's approved process before relying on an output.