Legal, Risk & Compliance · Module
Contracts (CLM)
Request, draft, review, sign and track contracts so their terms become governed work
Contracts runs the full lifecycle on the shared party, product and file records, from intake to renewal. AI extracts clauses and reviews them against your playbooks as advisory, cited suggestions that counsel approves.
What it does
Contracts (CLM) is designed to run the whole contract lifecycle: request, draft, review, negotiate, approve, sign, store, track obligations and renew. Requests start from the record that needs paper: a CRM deal, a Sales quote, a Procurement PO or vendor, a Recruit offer or a portal, capturing type, counterparty, value, entity, dates and urgency.
Contract types (NDA, MSA, SOW, DPA, vendor, employment, lease, channel partner) carry required and custom fields. Templates use variables from record data, conditional sections and clause slots with entity and jurisdiction variants. The clause library holds approved clauses with fallback positions, guidance and version history, and playbooks set required clauses, acceptable ranges, fallback ladders and escalation owners per contract type.
Review and negotiation
Counterparty paper is ingested from DOCX or PDF with OCR and clause segmentation. AI extracts parties, dates, value, term, renewal, notice period, governing law, liability cap, indemnity, termination, payment and data protection terms, each linked to its source span. Playbook review flags deviations with severity and suggested fallbacks; every flag cites clause text and is advisory. Redlines go out only with lawyer approval. Negotiation can happen in the Docs editor, a Word add-in or a counterparty portal.
Signature and after
Approval routing uses the DoA matrix, deviations, entity and counterparty risk. Signing runs through One3 Sign or an external connector, with Aadhaar eSign and DSC via a licensed provider and e-stamping via partners per state (to be verified). Executed contracts land in a permission-aware repository with full-text, metadata and semantic search. The obligations register tracks deliverables, payments, SLAs, reporting, insurance and data protection duties, and at GA these become governed proposals in Billing, Service Desk, Projects, GRC and Procurement. Renewals and notice dates trigger a renew, renegotiate or terminate decision.
What is different
Contracts sits on the same records as the business, so obligations are executed rather than remembered. Legacy archives come in through Migration Factory with a human verification queue. Planned for W3 (Year 2).
Features
What Contracts (CLM) includes
Contract intake from records
Request forms and a Request contract Action from CRM deals, quotes, POs, vendors, offers and portals.
Templates with conditional logic
Variables from record data, conditional sections, clause slots, versioning and entity or jurisdiction variants.
Clause library and playbooks
Approved clauses with fallbacks and guidance; playbooks with required clauses, acceptable ranges and escalation owners.
Editor with redlines and Word add-in
Tracked changes, comments, version compare, DOCX import and export, and negotiation inside Microsoft Word.
Third-party paper ingestion
Counterparty DOCX and PDF with OCR, converted into comparable text with clause segmentation.
AI clause extraction
Key terms extracted with links to source spans and confidence bands.
AI playbook review (advisory)
Deviation severity and suggested fallbacks, every flag citing clause text; lawyer approval on outbound redlines.
Approval routing
Rules on type, value, deviations, entity and counterparty risk, with diffs and risk summary in the Approvals Inbox.
Signature and e-stamping
One3 Sign or external eSign, Aadhaar eSign and DSC via licensed provider, e-stamping via state partners (to verify).
Repository and search
Full-text, metadata and semantic search over drafts and executed contracts with a related records panel.
Obligations register to owning apps
Obligations with owner, due rule and evidence, turned into proposals for billing schedules, SLAs, deliverables and controls.
Renewals, amendments and hierarchy
Notice-date computation, renewal decisions, MSA → SOW → amendment hierarchy and effective-term computation.
Matters and self-service contracts
Matter records linking contracts, parties, deadlines and outside counsel; self-serve NDAs when no field deviates.
Legacy bulk import
Folders, drives and CLM exports through extraction and a human verification queue, with a reconciliation report.
Workflow
Third-party paper review
- 1
Counterparty paper is uploaded and segmented into clauses
- 2
Key terms are extracted with source spans
- 3
Playbook review flags deviations and suggests fallbacks
- 4
Counsel accepts or edits suggestions
- 5
Redlines are sent only after lawyer approval
- 6
Approval routing runs before signature
Workflow
Renewal decision
- 1
Renewal and notice dates are computed from the contract and amendments
- 2
A renewal brief compares usage with contract terms
- 3
The owner decides to renew, renegotiate or terminate
- 4
Notice letters or new drafts are generated
AI
AI skills and Digital Employees
Clause and key-term extraction
Values linked to source spans; low-confidence values need human confirmation.
Playbook review
Advisory deviation flags with cited clause text and fallback suggestions.
First draft from template
Template assembly with fallback clause selection.
Obligation extraction and reminders
Obligation proposals with owners and due rules, plus internal reminders and evidence chasing.
Repository copilot
Cited answers across contracts, such as which contracts have uncapped liability.
Digital Employees that use this module
- AI Contract Review Assistant
- AI Contract Drafter
- AI Obligations Tracker
- AI Contract Renewal Watcher
- AI Litigation & Matter Assistant
They act through the same governed Actions as people; risky steps wait for approval.
Frequently asked questions
Does AI approve contract positions?
No. Review output is advisory and cites clause text. Redlines go to counterparties only with lawyer approval.
Can we negotiate in Word?
A Microsoft Word add-in is planned for GA in W3, with playbook review, clause insert and version sync.
Is Aadhaar eSign supported?
It is planned through a licensed eSign provider. Availability and terms must be verified before release.
Can we import our existing contracts?
Yes. Migration Factory is planned to import folders, drives and CLM exports, with AI extraction and a human verification queue.
See Contracts (CLM) in your workflow
Tell us about your team and the outcomes you want. We will walk you through the apps, the Digital Employees and the plan for your industry.