Make the intake specific
Supply the parties, document kind, jurisdiction, obligations, dates and reference material. Review imported content and retain its source identity before using it in a new matter.
Workflow index
Start from any of the 29 named drafting types, inspect a contract without generating text, or enter the separate compliance-artifact workflow. Each named type has a direct selector. Use Custom when your document does not fit a named type.
Choose a document type, supply matter-specific facts, then review the draft. Public specimens are examples, not reusable legal templates or legal advice.
A contract playbook records the issues a reviewer should inspect and the positions the organization permits. It should distinguish an approved position from a fallback that still needs approval.
| Part | Worked detail |
|---|---|
| Issue | Confidentiality duration in a fictional supplier agreement. |
| Preferred position | The duration supplied by the organization’s approved policy, with its source and scope. |
| Fallback | A different duration only if the named reviewer approves the exception. |
| Evidence and version | Link the rule, affected clause, current draft and actual reviewer decision. |
Do not invent an organization’s legal policy from a general example. A clause check, playbook reference and final approval are different states. Recheck the review against the saved document after a change, and have qualified counsel assess matter-specific terms.
A worked workflow
The captured run comes first and is a separate fictional NDA, whose three-year change no playbook here permits. The brief and steps after it are their own example: a fictional playbook prefers a twenty-four-month confidentiality period and permits a twelve-month fallback only after the designated reviewer approves it. A separate supplied clause calls for return of material within ten days of a written request.
A separate run from the brief further down this section: a supplied fictional NDA was imported as version 1. Its confidentiality clause changed from two years to three, employees changed to personnel, and a five-business-day compelled-disclosure notice was added. Structural validation ran before the change was applied and saved as version 2. The actual redline contains three native Word insertions and two deletions.
The parties and instructions are fictional. The three-year period is the instruction in this run, not a position a playbook permits. Structural validation is not legal approval: five high-risk review items remained unresolved, including an intentionally broken Section 9.9 reference. Approval and signing were not completed. This capture does not establish a confirmed obligation or the legal suitability of the example terms.
Read the relevant immutable playbook position, finding, source anchor and any permitted fallback.
Inspect: A finding is a review aid. It does not establish that a fallback was approved or that a precedent applies to this matter.
Inspect the proposal and required decisions, then apply the permitted change against the current draft version.
Inspect: The saved wording and reviewer decision must match. A later source change can require the finding or approval to be rechecked.
Review the extracted action, responsible party, owner, trigger, timing and source before confirming it.
Inspect: With no written-request date supplied, keep the relative ten-day period and do not invent a calendar due date.
Use the supported agreement-pack and obligation view, then inspect the downloaded register or calendar where offered.
Inspect: Check the saved status, source excerpt, document version and retained change history. A reminder or exported date is not proof that the underlying legal interpretation is correct.
Fictional playbook and timing examples. Obligation extraction and tracking require matter-specific legal review and do not certify compliance.
This is a real Lex export for invented parties. Inspect the input and clauses as a worked example, with professional review kept separate from automated drafting and checks.
A mutual non-disclosure agreement of 14 numbered clauses between two invented parties: definitions, what counts as confidential information, exclusions, the receiving party's obligations, permitted disclosures, return of materials, remedies, term, survival, governing law, notices and signature blocks. Its first page says it is a worked example, not a legal document.
Draft a Mutual Non-Disclosure Agreement between Larkfield Analytics Ltd (Party A) and Fenwick & Dale Stores Ltd (Party B). Governing law: England and Wales. Effective date: 2027-01-15. Term: Two years from the effective date. Confidentiality: Three years after disclosure. A mutual agreement: each party may disclose and receive confidential information. State on the first page that the parties, people and addresses in this agreement are invented and that it is a worked example, not a legal document. The notice email address of Larkfield Analytics Ltd is notices@larkfield-analytics.example and of Fenwick & Dale Stores Ltd is notices@fenwick-dale.example (both invented).
Read mechanically against the intake, not by a lawyer: all 12 facts the intake gave are in the draft, nothing is left as a placeholder, and it states no term the intake did not give.
Supply the parties, document kind, jurisdiction, obligations, dates and reference material. Review imported content and retain its source identity before using it in a new matter.
Use the legal workspace's permitted structural tools, Draft Checks and review paths. Compare proposed changes with the saved draft and original material; unsupported Word edits must be handled explicitly.
Have qualified counsel review enforceability, local requirements and the actual commercial intent. Check the current approval state and the downloaded document after a change.
Select the target clause and give Ask Lex a bounded instruction. Missing facts remain visible for review. Inspect the before-and-after proposal, required clause checks and any explicit outside-matrix or mandatory-clause override before versioned application. Use the legal workspace's structural allowlist rather than assuming every general content-editor block is available.
Inspect immutable playbook versions, anchored findings, provenance and precedent variants before staging a change. Matters retain original sources, quotation findings and source-version comparisons. Review extracted obligations for timing, ownership and source revision; negotiation turns and agreement-pack review cells have their own decisions and current-version requirements.
Original-format Word export, tracked changes against an original and saved-version redlines are separate paths. Unsupported edits must be surfaced rather than silently claimed as preserved. Inspect the layout, validator notes and downloaded file, then retain its delivery receipt. Counsel's review applies to the actual matter and version.
Every contract in Lex, drafted or imported, gets an AI contract review: each clause the document type expects marked present, weak or absent; up to 25 risks with a level, the party each falls on, why it matters and replacement wording; and provisions that cannot both be followed. Every quotation is checked against the contract text, findings are decided before approval, and there is no single risk score. The same review reads the key terms and obligations with the words they quote and proposes them into the Agreement Pack. Review every document puts up to 25 documents of an Agreement Pack, or up to 200 in a matter, into one table with your own questions as columns and an Excel export. Approvers can be named in order, and signing supports up to 10 signers with an optional signing order and automatic reminders; it is a simple electronic signature, not a qualified one. A qualified reviewer still decides what the contract says.
Lex does not provide legal advice or certify compliance. The public specimen is not a universally reusable legal template. Word fidelity depends on the supported original-document and saved-version path; unrestricted Power Edit and image insertion are not legal editing features.
Read the fictional pilot intake, compare the draft clause with the reviewer’s corrections, then open the real tracked-change Word export.
Inspect the example and files →
Fictional, hand-authored demonstration inputs. The files were created by the actual product export services; this does not establish AI output quality or customer outcomes.
Choose a workflow
Draft creation, contract completeness checking, and compliance artifact preparation are different workflows with different outputs.
guided confidentiality/IP, services, corporate/equity, employment, real-estate, finance, and general legal documents, including custom drafting. Start from parties, terms, governing context, and optional references.
Paste contract text to check expected clause coverage and execution-readiness signals. The checker does not generate legal text or decide enforceability.
Use the compliance flow for checklists, evidence matrices, working papers, filing support notes, and policy drafts. Reviewers verify every fact and conclusion.
More ways to begin inside Lex
Inside a Lex account, the dashboard and navigation offer three more starting points beside drafting from scratch. Each still ends in qualified review.
Lex can also start from a contract you already have. On the Review a Contract screen, paste the text or upload the file, choose the contract type, and Lex runs its rule checks and the AI contract review against it. A DOCX upload is kept privately so the edited contract can be exported back in its original Word format.
An imported contract also gets the AI contract review: each expected clause marked present, weak or absent, risks with the party they fall on and replacement wording, and provisions that cannot both be followed, with every quotation checked against the contract text.
Agreement Packs connect related documents, proposed party and obligation facts, version-bound approval receipts, and execution records on the same matter. Fields stay proposed until a reviewer confirms, disputes, or marks them inapplicable.
Matters is a personal workspace for one client matter. Upload up to 200 source document versions, search their stored text, and record findings as exact quotations tied to the source version and character position, arranged by issue and in a chronology, then download a bundle of reviewed work products. Matter findings retain exact source-version links. A draft has a separate in-app Cited sources view for supplied-file sentence support; neither establishes legal authority or statutory compliance.
Added at the end of October 2026
Once contracts are in Lex, three more workflows run on them. Each records what it did and leaves the decision with a qualified reviewer.
Review every document on an Agreement Pack reviews up to 25 documents and puts key terms, playbook results and risk counts in one table, each reading quoted from its document. Add your own questions as columns, run the same review across the documents in a matter (up to 200), and export the table to Excel. If plan capacity runs out, the run stops and keeps every finished row.
Approvers can be named in order, with two rules that add an approver when they apply: one for high-risk findings and one for a liability cap above an amount you set. Once approvers are set, the drafter cannot approve the contract, each approval is tied to the exact version, and the next approver is notified in Gixo and by email.
Signing supports up to 10 signers, an optional signing order, an emailed code each signer enters, automatic reminders and a completion certificate; it is a simple electronic signature, not a qualified one. After signing, an agreement can be amended, terminated or marked expired, and a renewals view lists agreements whose expiry or notice deadline falls in the next 90 days.
Direct selectors
Common starting points: NDA, Master Services Agreement, Shareholder Agreement, Employment Agreement, or Custom drafting. The complete categories are below.
Non-Disclosure Agreement, IP Assignment Agreement, License Agreement, Data Processing Agreement
Master Services Agreement, Statement of Work, Service Level Agreement, Consulting Agreement, Reseller Agreement
Shareholders Agreement, Share Purchase Agreement, Joint Venture Agreement, Partnership Agreement, Memorandum of Understanding, Simple Agreement for Future Equity
Employment Contract, Non-Compete Agreement, Invention Assignment Agreement, Employment Offer Letter, Separation Agreement
Lease Agreement, Property Sale Agreement
Loan Agreement, Promissory Note
Terms of Service, Privacy Policy, Power of Attorney, Settlement Agreement, Contract Amendment, Custom Legal Document
Document-intent index
Choose the matching type in the create flow. The index below lists the facts and terms to prepare, with a guide where a matching public page exists. For another document, choose Custom and describe its purpose, structure, parties, and governing context.
The public examples show product structure and review surfaces. They are intentionally labelled as specimens rather than templates so a buyer is not encouraged to reuse draft language without matter-specific and jurisdiction-specific review.
Contract obligation management starts by turning a proposed extraction into a record someone has checked. Lex Agreement Packs keep obligations with the related agreement; they are separate from the obligation-comment follow-up portfolio.
Executed packs need the appropriate amendment or new-pack path when commitments change. Reminder dispatch begins after execution; message acceptance is not inbox delivery. Calendar imports do not reliably remove earlier events or recurring series: remove the listed old entries and verify replacements. These are saved agreement records and explicit reviewer actions, not an enterprise-wide contract repository or unattended monitoring.
Inspect the contract review controls and read the drafting and Word-handoff guide.
Compare contract versions. Use Compare to inspect saved revisions. With Lex review access, Review mode keeps the document read-only while you inspect findings and record decisions; it does not certify legal correctness.
Review clause edits before applying them. A manual edit or staged Ask Lex proposal shows the before and after wording. Replacement normally keeps subsections unless you include them; removal and changed numerical terms need acknowledgement. Validate the proposed text again after changing it, then decide whether to Apply to the saved version it was previewed against.
Approve the version you reviewed. The contract approval workflow ties the approval receipt to the exact saved version. With no approvers named, one approver's receipt records the decision; approvers can also be named in order, with two rules that add an approver for high-risk findings or for a liability cap above an amount you set, and then the drafter cannot approve, the next approver is notified in Gixo and by email, and the receipt records the whole chain. Resolve findings and open items before approval; later text or source changes require fresh review. This is a reviewer decision, not a legal verdict.
Decide the AI review findings. Every contract in Lex, drafted or imported, gets an AI contract review that reports expected clauses as present, weak or absent, risks with the party they fall on and replacement wording, and provisions that cannot both be followed, with every quotation checked against the contract text. Each finding is decided before approval; an edit leaves the review as the review of the earlier version until you review the changes.
Update obligations after source documents change. An Agreement Pack can compare prior obligations with current saved source versions. Pair changed clauses, confirm revised records and retain the history. An executed pack needs a new agreement or amendment pack.
Review upcoming and recurring obligations. Prepare a named-period worklist from saved owners, statuses and supported dates. Review the source snapshot and calendar replacements, then retain the accepted register, calendar and review summary. This preparation does not approve or execute an agreement and is not an unattended scheduler.
Before replacing a calendar, remove the listed old events and recurring series, import the reviewed replacement and verify the result. Importing a new calendar does not reliably cancel the previous events.
Structured first draft, accountable review
Start the 14-day, no-card Lex trial to evaluate structured intake, drafting, the AI contract review, deterministic Draft Checks, review, and export. Gixo prepares work for review; it does not provide legal advice, certify compliance, or replace professional judgment.

Updated