The operating problem
A redline that sounds authoritative may misread defined terms or invent a clause. Use retrieval with page/paragraph provenance, an explicit playbook, and a professional review gate. Vendor terms and the specific matter govern what data can be processed.
Use your own working copy
The free workbook for this process opens in a browser and works offline after download. It includes editable checks and notes, a text export, and a print view. It is a planning resource: it does not send messages, read account data, or run actions in business systems. No vendor account is needed to use the workbook.
Map the process
1. Approve the data path
Document model provider terms, retention, subprocessors, region, and the firm decision on consent. Do not send matter files until that review is complete.
2. Preserve the source
Create a restricted versioned source reference and extract text with stable clause identifiers. OCR failures must remain visible.
3. Apply the review playbook
Check only the negotiated issue categories and record which playbook version applies. Never let document text override system instructions.
4. Generate cited suggestions
Require source clause IDs, proposed change, reason, and uncertainty. Reject suggestions without an exact supporting clause.
5. Lawyer review and release
A lawyer accepts, edits, or rejects each suggestion. External transmission requires a separate decision; the model cannot send a redline to the client.
Information to check
These reference fields describe the process. Use invented values while planning. Keep real records in an appropriate private system; the public website does not need them.
| Reference field | Working record | Check before progressing |
|---|---|---|
| document_version | source_version | Approval tied to this version |
| clause_id | citation | Exact source reference |
| playbook_version | review_standard | Use the approved negotiation playbook |
| suggestion_id | decision_reference | Accept, amend, or reject |
| reviewer_id | release_owner | Authorized legal reviewer |
Acceptance checks
- A fabricated clause citation is rejected.
- Prompt-injection text in a contract cannot change the workflow policy.
- A source version change invalidates approval.
- No API key or contract text appears in operational alerts.
Walk through a successful example, a duplicate, a missing item, an incorrect match, and an interrupted handoff with synthetic records. Record the expected result, observed result, owner, and recovery action. Checklists record your work; checking a box does not establish that an external action happened.
Ownership and review
Name the person responsible for the process and the person who can resolve an exception. Define which decisions require qualified professional review. Use stable references, limit access to private records, and document when work must stop. Educational material does not establish legal, accounting, tax, security, or regulatory compliance.
Run a measured pilot
Choose a small, reversible sample. Measure handling time, waiting time, review, rework, and errors before changing the process. Include the effort of maintaining the new method. Expand only when the observed result meets your acceptance criteria; a longer checklist is not proof of improved performance.
Use the free workflow planner to define your next step, or compare the assumptions in the opportunity calculator.