Intake
Open a fictional DOCX and confirm the role, round and versions.
NDA negotiation workspace
Client instructions, lawyer decisions and a clear route to return.
Working matter queue
Keep client/document targets and the next action visible. Waiting on client instructions does not pause the target.
0 open0 overdue0 due within 24 hours
Targets show in your browser timezone. Enter each client's agreed target; this queue does not assume a standard SLA.
This browser saves only the matter labels, targets and working status. Save a matter file for its documents, correspondence and decisions; opening a queue item asks for that file. “Mark returned” records your action and can be reversed. It does not send documents or verify delivery. This queue provides in-app flags, not background notifications.
Client mandate
The instructions for this NDA stay with this matter.
Instruction source & client exceptions
Counterparty requests remain requests until supported by approval evidence. Client instructions can be saved as a reusable pack in the Instructions stage.
Recorded assignmentDemo reviewer
Direct return after the lawyer completes the review.
Start with a document
Simple Word documents, up to 6 MB
Choose a fictional NDA
Read and review it in this browser. Replacing a draft keeps this matter and compares the previous baseline; use New matter for a different instruction.
No document loaded.
Use fictional documents with simple body text and no existing revisions, comments or external resources.
Review context
Set the position for this negotiation round
Negotiation history
Use the latest clean DOCX as your baseline. Later rounds require a record of prior positions.
Matter details
Compare negotiation draftsPrevious wording against the current baselineOptional
Compare extracted body text locally. Formatting, headers, footers, numbering and layout are outside this comparison. It never changes your current document or approvals.
Load a current NDA first.
Email contextOptional · negotiation history and instructions0 emails
Load your NDA first, then add fictional correspondence. Inspect each message and choose what to include in AI review. Emails are background evidence; requests do not become approved exceptions.
.eml or .txt · up to 5 messages, 4,000 characters each and 6,000 total. For Outlook .msg files, save a plain-text copy or paste the thread. Attachments and remote content are ignored.
Paste an email thread
The draft is not included until you add it.
Load a fictional NDA to add email context.
Document.docx—
Document textParagraph references
Example rules and findings need a human review.
Client instructions & positions
Apply the client instruction pack, then confirm the position for this round.
Client & document SLA
Saved with this client and document type in the instruction pack. Elapsed hours run continuously. For working-hour calendars, weekends, holidays or agreed extensions, record the agreed manual target; no calendar is assumed.
Applying a pack sets the client mandate and rules for this matter and clears current review decisions. It keeps your assignment, drafts and email context.
Rule files & examples
Use fictional instructions only. The local check matches exact phrases; it does not interpret legal meaning. Rule files support 1–8 rules up to 20 KB; client instruction packs up to 30 KB.
0 document0 findings0 approved changes0 escalations
Start with the current draft
Load a fictional NDA or reopen a saved matter to inspect the source alongside its review findings.
Return pack & checks
Resolve decisions, complete independent checks, then prepare your record.
Review not run
Run a review to build the issue queue.
Remaining checks
Preview handover draft
This is a draft internal handover. Review it before sharing; it is not sent automatically.
Escalation & handover record
Record each escalation decision in its finding first. This record does not verify reviewer identity or provide legal sign-off.
Check the full document and both Word outputs before handover.
How the review works
A local wording check with human decisions
Instructions
Check your rules. Round 1 uses preferred wording, round 2 fallback and round 3 final, with earlier positions used if a later one is empty.
Review
Run the exact-phrase check, inspect the source, approve changes and record escalation decisions. Then open Return for the Word outputs, issue matrix and handover checks.
Session activity
- No review activity yet.
Save a matter file to reopen its documents, context, playbook and decision record. Reopened records require fresh checks and decision confirmation; the AI code and consent are excluded.
Privacy & controls
Local rules and optional cloud AI
Local processing
Your workspace name, lawyer name, default review route and matter-queue labels, deadlines and status can be saved in this browser. Documents, client instructions, emails, approvals and AI codes are excluded from these preferences. Parsing, local phrase checks and exports run in browser memory. The local check does not submit documents or playbooks to the server. Optional AI sends fictional document excerpts, selected email context and playbook rules to Cloudflare. Saved emails are read locally; attachments and remote content are not opened. The website does not persist these documents or messages.
Human approvals
No amendment is approved automatically. Ambiguous or unsupported matches require a human decision. An absent phrase is not proof of compliance.
Fictional data only
This pilot has no accounts or independent security certification. It is not ready for confidential client matters.
Optional AI safeguards
AI review requires your private pilot code and explicit confirmation that the document is fictional. The free allowance can run out. AI suggestions still need a human review and approval.
Pilot scope
Controlled evaluation on the free plan
Available
Browser-saved workspace preferences, reusable client instruction packs, local matter save/reopen, draft comparison, email context, prioritized issue decisions, return checks and Word exports.
Before client use
Independent legal and Word-format testing, access controls, client permissions and security assessment are required.