Compare the signed technology contract with the last agreed issues list
Key facts
- Human involvement
- YellowClose supervision
- How AI is used
- Set the signed contract beside the issues list the parties last agreed and list each issue that the signed text does not address, or addresses in different words. Quote the clause and the issue. Do not propose replacement wording.
- What the lawyer must review
- Model Rule 1.1 requires the lawyer to bring the legal knowledge reasonably necessary for the representation. Formal Opinion 512 warns that a generative tool can produce plausible text that is wrong, so the lawyer checks every mismatch against the signed PDF before anyone relies on the list. Rule 1.6(a) and (c): contract text and the issues list are information relating to the representation and stay inside a tool configured to keep that information confidential.
- Written for / version
- United States versionUS
Who does what
| Role | What they do |
|---|---|
| Assistance | Potential support includes preparing preliminary structure or wording. Confirm the tool’s capability and permitted scope. |
| Lawyer | Set the scope, supervise the work closely, verify every part relied on, resolve omissions and exceptions, and approve the exact output. |
Checklist
- Trace every relied-on figure to its source, confirm dates and assumptions, and independently recalculate totals or derived amounts.
- Review operative clauses in the complete document, including definitions, cross-references, schedules and inconsistencies with the instructions.
- Confirm that the actual tool, feature and processing terms permit use of this information, including access, retention, training and disclosure conditions.
- Confirm the output against the client’s instructions and the complete relevant source material, including omissions or contradictions.
- Resolve exceptions and record the responsible lawyer’s approval of the exact output and intended use.