Received a 200-page contract for review? Manual analysis of such volume takes a week, and lawyers miss up to 15% of high-risk clauses—especially when wording is buried in appendices. We built Clause Risk Assessment—a system that processes a document in an hour, highlights every risk, classifies it by category and criticality, and recommends alternative wording.
Our solution is an ensemble of NLP models: a BERT-based clause-type classifier, a threshold detector, and an uncertainty analyzer. The model was trained on thousands of real contracts annotated by expert lawyers. Result: 95% precision on high-level risks, 92% recall. Over several years of work, we've processed more than 10,000 contracts, ensuring consistent quality. For an average legal department, the cost savings on contract analysis range from 500,000 to 1,500,000 RUB per year.
How AI Determines Clause Risk
Each clause goes through a pipeline of three models. The first classifies the condition type (liability, penalty, confidentiality). The second extracts numerical thresholds and checks for anomalies. The third evaluates semantic uncertainty—phrases like "reasonable efforts" or "in the party's discretion." The final risk level (critical/high/medium/low) is computed as a weighted sum with industry benchmarks.
class ClauseRisk(BaseModel): clause_text: str clause_type: str risk_level: Literal["low", "medium", "high", "critical"] risk_category: str # financial | operational | legal | reputational risk_description: str # what exactly the risk is norm_reference: str | None # legal norm reference if violation alternative_wording: str | None # suggested better wording is_negotiable: bool # whether to push for a change Risk Categories: Examples from Practice
We identify four base categories. For each, the model outputs specific indicators.
| Category | Clause Examples | Typical Risk Level |
|---|---|---|
| Financial | Unlimited liability, 1% daily penalty, buy-back obligation | Critical/High |
| Operational | Non-termination, impracticable obligations, excessive reporting | High/Medium |
| Legal | Violation of Article 310 of the Civil Code, non-jurisdiction in RF, non-compliance with 152-FZ | Critical/Medium |
| Reputational | Ban on public mentions, vague confidentiality | Medium/Low |
What Is the Risk Pattern Library?
It's a knowledge base built from real contracts—over 500 patterns annotated by lawyers. The system uses these for precise matching. Typical "red flags":
- "Shall not be liable under any circumstances"—attempt to exclude willful misconduct.
- "Has the right to unilaterally change"—violates Article 310 of the Civil Code.
- "Penalty of 1% for each day"—disproportionate sanction.
- "Governing law: [foreign jurisdiction]"—risk of recognition of judgments.
Example clause analysis: input "Supplier shall not be liable for any indirect damages, including lost profits, even if advised of the possibility of such damages." Model output: type limitation_of_liability, risk_level critical, category financial. Explanation: "Exclusion of all indirect liability without exception for intentional breaches—contradicts Article 401 of the Civil Code of the Russian Federation. It is recommended to limit liability to direct damages up to the contract value." Alternative wording: "Supplier shall be liable for direct damages caused by its non-performance or improper performance, up to the total contract value. Liability for lost profits is excluded, except in cases of willful misconduct or gross negligence."
Why Is Comparison with Company Position Critical?
The company uploads its standard position: acceptable caps, preferred governing law, standard termination notice. The system automatically compares each clause against the benchmark and highlights deviations with color coding: green—matches, yellow—needs attention, red—critical discrepancy. A lawyer can review the contract in 1–2 hours, focusing on high-risk clauses. Without AI, a full review takes 4-6 hours, and up to 15% of risks go unnoticed. According to KPMG, contract analytics automation reduces legal department workload by 60%.
AI analysis is 3x faster than manual review and 60% more effective than keyword search. Our system is 5x more accurate at detecting high-risk clauses compared to regex search.
Time Comparison: Lawyer vs AI
| Mode | Time per contract (100 clauses) | High-risk missed by human |
|---|---|---|
| Lawyer only | 4–6 hours | ~15% |
| Lawyer + AI | 1–2 hours | <3% |
AI doesn't replace the lawyer but provides superpowers: instead of reading every clause, they only check highlighted risks.
Work Process
- Analytics — collect contract corpus, label typical risks, tune thresholds for the industry.
- Design — adapt the model to the client (choose language model, customize patterns).
- Implementation — integrate via REST API, test on a pilot set.
- Test — lawyers verify 100% of results, provide feedback for retraining.
- Deploy — run on your infrastructure or cloud, train lawyers, hand over documentation.
What's Included
- API documentation with request/response examples.
- Trained model report with metrics (precision, recall, F1).
- Containerized solution for on-premise or cloud.
- 3 months of support and retraining based on feedback.
Estimated Timelines
From 2 weeks for a basic version to 2 months for deep customization. Cost is calculated individually—depends on data volume and integration complexity.
Get a consultation: send one real contract—we will return a full risk report in 2 days. Evaluate quality before purchase. Contact us to discuss implementation—our engineers will prepare a custom proposal.