Features

Legal Playbooks

A Legal Playbook in Lexnus is a structured, version-controlled set of rules and clauses that defines your organisation's legal policy. Every contract Lexnus analyses, inbound or outbound, is evaluated against your active playbook automatically. The playbook is the source of truth. The AI interprets contract language against it. The playbook decides what passes.

How it works

1

Build your playbook from existing contracts

You do not build a playbook from scratch. Upload your existing Word templates and signed contracts. Lexnus reads them, extracts the standards implicit in your language: the liability caps you accept, the clauses you always insist on, the governing law you never compromise on, and drafts your first playbook automatically. You review, adjust, and publish. Under an hour. No implementation project.

2

Write rules in plain language

Rules are written in plain language and enforced deterministically. Examples:

  • "Aggregate liability must not exceed 1.5x annual contract value."
  • "Governing law must be England and Wales for all EU counterparties."
  • "Termination for convenience requires at least 90 days notice."

Rules reference Smart Fields, structured data points extracted from each contract, so comparisons are precise and consistent. The AI interprets contract text to extract those values. The playbook rule then evaluates the value. Pass or fail. No ambiguity.

3

Assign clauses

Each playbook contains an ordered set of clauses drawn from your governed Clause Library. Clauses can be conditional, included only when specific Smart Fields match, and nested to form a complete contract structure. Every clause in your playbook has been reviewed and approved by a qualified lawyer before it can be published.

4

Publish and enforce

Once published, a playbook is immutable. Future edits create a new draft version. The published version governs all analysis until superseded. Every analysis result is traceable to a specific, frozen policy state, which is critical for audit.

Key capabilities

  • Automatic extraction — Lexnus reads your existing contracts and builds your first playbook draft. No blank-slate setup.
  • Plain-language rules — Rules are written in natural language, not code. Legal teams write them directly.
  • Deterministic enforcement — Policy enforcement is rule-based, not AI-driven. The AI interprets contract text; the playbook judges it. Pass/fail is binary.
  • Version control — Every published playbook is an immutable snapshot. Full version history. Every analysis result links to the exact policy version it was evaluated against.
  • Conditional clause inclusion — Clauses can be included or excluded based on Smart Field values. The playbook adapts to deal context without requiring manual configuration per contract.
  • Multi-playbook support — Separate playbooks for different contract types: NDA, MSA, employment agreement, procurement. Each governed independently.
  • Approval workflow on publish — Playbook changes require Admin approval before taking effect. No policy change goes live without authorisation.

Who uses this

General Counsel and Legal Ops build and own playbooks. They define the rules, assign clauses, and publish new versions when policy changes. The playbook is their primary tool for encoding institutional legal knowledge into a system that enforces it automatically.

Lawyers and Associates work against published playbooks during contract review and negotiation. When a counterparty contract is analysed, the playbook tells them exactly what is wrong and what the approved fix is.

Business users in sales, procurement, and HR benefit from playbooks indirectly. When they initiate a contract, it is assembled from the playbook's approved clauses. The rules are already built in. They cannot accidentally generate non-compliant language.

Frequently asked questions

What is a Legal Playbook in Lexnus?

A structured, version-controlled policy document containing rules and approved clauses that govern every contract your organisation creates or receives. When a contract is analysed, it is evaluated against your active playbook. Violations are flagged. Gaps are identified. Nothing leaves without compliance.

Does Lexnus use AI to enforce the playbook?

No. Policy enforcement in Lexnus is deterministic and rule-based. The AI model interprets contract text and extracts structured values: liability caps, notice periods, governing law, from natural language. The playbook rule then evaluates those values against your policy. Enforcement is not probabilistic.

How long does it take to build a playbook?

For most legal teams with existing Word templates and signed contracts, the automated extraction produces a workable first draft in under 15 minutes. Review and publish in under an hour. No implementation project. No onboarding fee.

Can I have multiple playbooks?

Yes. Playbooks are scoped by contract type. You can maintain separate playbooks for NDAs, MSAs, employment agreements, supplier contracts, and any other contract type your organisation uses. Each is governed independently.

What happens when I update a playbook?

Edits create a new draft. The published version remains active until you publish the new version. Every analysis result is permanently linked to the playbook version it was evaluated against, so your audit trail is always accurate.

Can a business user change or override a playbook?

No. Playbooks are owned by Admins and Creators (legal roles). Business users interact with playbooks only through contract generation and analysis flows. They cannot view or modify playbook rules or clauses.

Free tier available. No card required. Generally available 31 August 2026.