Skip to content
LogoLogo

Legal

Use case 1: Contract review against a playbook

The problem. Every incoming contract is read clause by clause against a standard playbook, by hand.

SettingValue
GoalCompare an incoming contract against our playbook and list every deviation with its risk level.
Knowledge baseContract playbook, standard clause library, fallback positions, approved precedents
OutputJSON: { clause, ourStandard, theirVersion, deviation, risk, fallbackAvailable } list
InstructionsQuote the exact text of both versions. Never paraphrase a clause. Never recommend acceptance. Flag anything not covered by the playbook as UNCOVERED.
ToolsGoogle Drive to read, Google Docs to write the review note

Use case 2: Obligation and date extraction

SettingValue
GoalExtract every obligation, deadline, renewal date and notice period from an executed agreement.
OutputJSON: { obligation, party, dueDate, noticePeriod, sourceClause } list
ToolsGoogle Sheets to populate the obligations register, Google Calendar to create reminders
InstructionsEvery row must cite the clause it came from. If a date is relative, state the trigger rather than computing a date.
SettingValue
GoalAnswer routine internal questions about company policy and standard terms, and route everything else to a lawyer.
Knowledge baseCompany policies, standard terms, published guidance notes
InstructionsAnswer only what the documents cover. State in every answer that this is information, not legal advice. Route anything about a dispute, a regulator or a specific negotiation to the legal team without attempting an answer.
ToolsSlack, to reply in a legal help channel

Use case 4: Discovery and disclosure triage

SettingValue
GoalClassify documents by relevance to defined issues and flag anything potentially privileged.
OutputJSON: { relevance, issues[], potentiallyPrivileged, rationale }
InstructionsErr heavily towards flagging privilege. A false positive costs a review; a false negative costs a waiver.
ConcernSetup
ConfidentialityOne knowledge base per matter, shared with a matter specific group. Never share broadly.
PrivilegeKeep trace: read_payloads with the legal team only. Everyone else gets trace: read at most.
No advicePut the disclaimer in a shared skill so every legal agent carries the same wording.
ProvenanceTraces record which passages produced each answer, and are exportable.
RetentionDeletes are soft, so a record of activity survives even after an agent or knowledge base is removed.