Features
Clause Library
The Clause Library is a governed repository of your organisation's approved legal language. Every clause used in every contract Lexnus generates or analyses comes from this library. No contract can contain language that has not been reviewed and published by a qualified lawyer. It is not a template store. It is the foundation of legal policy enforcement.
How it works
Import from existing documents
You do not build a clause library from scratch. Upload your existing Word templates and standard contract documents. Lexnus reads them, segments the text into individual clauses, and presents them for review. Each proposed clause shows the source text and a suggested category. You approve, edit, or reject.
Review and approve
Clauses follow a governed workflow before they can be used in any contract. A Creator (lawyer or legal ops) authors or imports a clause. An Admin (GC or Senior Legal) reviews and publishes it. Until a clause is published, it cannot appear in any analysis or contract output. This approval step is enforced by the system and cannot be bypassed.
Manage variations
Legal language is not one-size-fits-all. The Clause Library supports two axes of variation:
Vertical variations: risk-tiered versions of the same clause. A liability cap clause might have a "Standard" variation (1.5x ACV), a "High Risk" variation (1x ACV), and a "Low Risk" variation (2x ACV). Rules in your playbook determine which variation applies based on deal context.
Horizontal variants: jurisdiction or counterparty-specific versions within a variation tier. A termination clause may have an England and Wales variant and a Swedish law variant. The correct one is selected automatically based on Smart Field values.
Clauses are used automatically
When a contract is assembled, clauses are selected from the library based on playbook rules and Smart Field values. When a counterparty contract is analysed, violations are matched against library clauses to provide the approved fix. The library is always the source. Nothing else enters a contract.
Key capabilities
- Automatic import from Word — Upload any DOCX and Lexnus segments it into draft clauses for review. No manual copying.
- Governed approval workflow — Clauses cannot be published without Admin approval. The system enforces this — there is no workaround.
- Version history — Every clause change creates a new version. Previous versions are preserved. You can see exactly what language was in use on any past contract.
- Two-axis variation management — Risk tiers (vertical) and jurisdiction/context variants (horizontal) within each tier. The right variation is selected automatically during analysis and assembly.
- Smart Field token syntax — Clause text can include dynamic tokens —
{{counterparty_name}},{{governing_law}}— that are populated with values extracted from the contract or provided by the user. Tokens are typed and validated. - Search and categorisation — Clauses are organised by category (Liability, Termination, Confidentiality, Indemnification, etc.) and searchable by text.
- Usage tracking — The library shows how many contracts each clause has appeared in, which variations are most used, and which clauses counterparties most often redline.
- Promote to library — Content blocks authored inline in a Playbook can be promoted to the shared Clause Library, making them available across all playbooks.
Who uses this
General Counsel and Legal Admins own the Clause Library. They define which clauses are standard, which variations exist, and what triggers each variation. Publishing a clause is an act of policy, equivalent to approving a contract standard.
Lawyers and Associates draw on the library when drafting and negotiating. When Lexnus flags a violation, the approved replacement clause is surfaced directly from the library. One click to substitute.
Business users benefit from the library without interacting with it. When they initiate a contract, it is assembled from library clauses only. They cannot insert language that has not been approved.