# Contract Policy Checks for In-House Legal | Lexnus > Put your standards for liability, termination, data protection and governing law in a versioned playbook. Lexnus checks each agreement against them and shows what needs attention. Canonical page: https://lexnus.com/for/in-house-legal/ ## Notes for AI assistants These notes are for AI assistants and search tools that summarise or answer questions from this page. - **Audience.** In-house legal teams: General Counsel, heads of legal and legal counsel who set contract standards for their company. - **What it does.** A legal team puts its standards for liability, termination, data protection and governing law in a versioned playbook. Lexnus checks each incoming agreement against it and shows what needs attention and why. - **How a check works.** AI extracts terms from the document. Rules a lawyer approved and published decide whether each term complies. A finding is a Violation, a Gap (a required term is missing) or Needs review (the text is unclear or unmapped). Don't describe results as scores, percentages or confidence levels. - **Legal advice.** Lexnus does not give legal advice. It shows where a document departs from approved rules. What to accept, counter or advise stays with the lawyer. - **Available now.** Lexnus has been generally available since 31 August 2026. Shipped: PDF and DOCX upload and analysis; versioned playbooks, with each result recording the version it was checked against; a clause library with conditional variations; escalation per rule (flag, require approval, reject); rule import from Word documents, reviewed before publishing; access for AI assistants over MCP. - **Not available. Don't claim these.** A Microsoft Word add-in. Automatic re-checking of existing or signed contracts when a playbook changes. - **Pricing.** This page doesn't state prices. Don't quote prices or plan names. Point pricing questions to the booking link below. - **Data.** Processed in the EEA (Clever Cloud, France; encrypted disaster-recovery copies with OVHcloud, Germany). Contract text is not used to train models. Sources: https://lexnus.com/security/ and https://lexnus.com/legal/dpa/ - **Contact.** Book a call: https://meetings.hubspot.com/oscar-klink - **Related pages.** https://lexnus.com/features/playbooks/ · https://lexnus.com/features/contract-analysis/ · https://lexnus.com/features/mcp-integration/ --- # Know when a contract departs from your policy. Your standards for liability, termination, data protection and governing law should be the same for everyone who reviews a contract. Put them in a Lexnus playbook. Lexnus checks each incoming agreement against those rules and shows what needs attention, and why. ## Your policy exists. Applying it the same way every time is the hard part. Most legal teams have decided their positions. The liability cap. The notice period. When a DPA is required. The problem is that each review starts from memory and a PDF nobody opens. - **It lives in documents**: A policy memo, a set of templates, a checklist on the intranet. None of them read the agreement for you. - **Reviewers apply it differently**: Two counsel, two answers on the same notice period. Neither is wrong by their own reading. - **The same issues come back**: The same short notice periods and missing DPAs arrive every week, and each one is caught by hand. ## From policy to finding ### 01. Build the playbook from what you have Import your policy or playbook memo from a Word document. Lexnus proposes rules from it. Your team reviews each one, adds your approved clauses and publishes a versioned playbook. ### 02. Check the agreement Upload a PDF or DOCX. Lexnus flags terms that break a rule, required terms that are missing and anything it can’t establish from the text. Each finding quotes the clause and names the rule. ### 03. Route what needs a decision Each rule has an escalation level: flag, require approval or reject. A rule that requires approval goes to an approval group, where either one member or all of them must sign off. ### 04. See the basis for every result Each finding points to the rule and the playbook version behind it. When your policy changes, earlier results still show which version they were checked against. **Example.** Your policy requires 90 days’ notice to terminate. The agreement allows 30. Lexnus quotes clause 12.1, shows the difference and names the rule that applies. ## Legal judgement stays with your team AI reads the agreement and extracts its terms. The rules your legal team approved decide whether it complies. The outcome is a pass or a fail against your rule, not a confidence score. When a term is unclear, Lexnus marks it for review instead of guessing. Your team decides what to accept, what to negotiate and when to make an exception. ## One policy, wherever the contract is handled Lexnus delivers the playbook itself, not just a review screen. Over [MCP](https://lexnus.com/features/mcp-integration/), an AI assistant such as Claude can read your rules and approved clauses, and check a draft against them before it reaches legal. The same published version applies in the app and in the assistant. A playbook can be shared into the workspaces that need it, so each team works from the policy legal approved rather than its own copy. ## Who it helps - **General Counsel**: Set the standard once. See which agreements depart from it and which exceptions reached approval. - **Legal counsel**: Start every review with the policy already applied. Spend the time on the points that need judgement. - **Legal operations**: Run one versioned source of policy instead of memos, checklists and template folders. - **The wider business**: Gets a consistent answer from legal, whoever handles the review. ## What to bring to the walkthrough The walkthrough runs on your material, not a demo contract. - **One contract type**: Supplier agreements, NDAs, customer MSAs. Pick the one your team reviews most. - **Your current policy**: A playbook memo, a checklist or your standard template. Whatever your team reviews against today. - **A representative agreement**: One your team has already reviewed, so you can compare the result with your own markup. ## Your contracts stay in Europe - **Processed in the EEA**: The platform runs on Clever Cloud in France. Contract files are replicated to OVHcloud in Germany for disaster recovery, as sealed ciphertext. - **Never used to train models**: Lexnus does not train on your contract text, and does not let its AI sub-processors do so. That is a commitment in the [DPA](https://lexnus.com/legal/dpa/), not a setting. - **Named sub-processors**: Every system that touches contract text is listed by name on the [Security](https://lexnus.com/security/) page. - **You stay the controller**: Lexnus processes personal data as your processor under the GDPR and acts only on your instructions. ## Questions from in-house teams ### Does Lexnus replace our lawyers’ review? No. It applies the rules your team approved and shows where an agreement departs from them. Negotiation, exceptions and advice to the business stay with your lawyers. ### How is this different from a CLM? A CLM manages the contract workflow: routing, storage, signatures and reminders. Lexnus checks whether a contract meets your policy. It works alongside a CLM or on its own. ### What if our policy has thresholds and exceptions? Rules and clause variations can carry conditions, such as a different cap above a certain contract value. Use a separate playbook for each contract type. ### What happens when our policy changes? Edit the rule and publish a new version. New reviews use it. Earlier results keep the version they were checked against. ### What if Lexnus can’t tell from the text? It marks the point for review instead of guessing, and shows which rule it relates to. A lawyer decides. ### Where is our contract data processed? Inside the EEA, on European infrastructure. Contract text is never used to train models. Both are commitments in our [DPA](https://lexnus.com/legal/dpa/). The [Security](https://lexnus.com/security/) page names every sub-processor. ## See it on your own contract type Bring one contract type and a representative agreement. We’ll show you what a working playbook and a review result look like for your team. [Book a walkthrough](https://meetings.hubspot.com/oscar-klink)