AI × Legal & Contracts
A legal assistant may help find clauses, compare language with an approved playbook, or draft an issue list. It may also omit a material term, cite the wrong authority, reveal confidential information, or present an inference as legal advice. Begin with retrieval and review support—not autonomous drafting, approval, signature, filing, or negotiation.
Contract Review Assistance
Define the document, jurisdiction, review purpose, approved playbook, and qualified decision-maker before selecting a model.
Uncontrolled document handling
Contracts are scattered across inboxes and drives → versions and governing law are unclear → confidential text is pasted into unapproved tools → a fluent summary is mistaken for a complete review.
Cited issue-list proposal
Use synthetic or de-identified fixtures first → retrieve only from licensed, approved sources → quote the exact clause and page → map it to a versioned playbook → abstain when evidence is missing → counsel decides and records the disposition.
Evidence package
Drafting, Renewal & Obligation Support
Keep generation inside approved templates and retrieval inside the authoritative contract set. A model should never invent a term, authority, deadline, party, or obligation.
The wrong template, entity, clause version, notice period, or commercial input can create a binding error; a generated reminder can miss an amendment or side letter.
Select from counsel-approved templates → lock required terms → schema-validate parties, dates, currency, jurisdiction, and source references → show a redline and evidence → require counsel and authorized business approval before any external use.
Pilot decision record
Reference architecture: proposal-only legal assistant
Use a dedicated least-privilege identity, tenant and matter isolation, encrypted approved storage, retention controls, licensed sources, document-level authorization, and secrets outside model context. Retrieve with page-level citations; schema-validate every issue and draft. Keep signing, filing, sending, deletion, template publication, and contract-system writes disabled. A named counsel reviews every output. Log access, source versions, model and prompt versions, citations, abstentions, edits, approvals, and incidents; enforce stop conditions, a kill switch, preserved originals, and tested rollback.
Evidence record to maintain
- Document types, jurisdictions, languages, source licences, confidentiality classification, retention rule, and authorized reviewers.
- Frozen representative, adversarial, and regression sets with risk-weighted results, material failures, and corrective actions.
- Architecture, access review, data-flow review, incident runbook, stop conditions, rollback test, and dated counsel approval.