Every version dated,
every approval final —
approve or it stops there.
51/51
calendar dates captured in a 671k-character filing — measured, not estimated
From an AI-drafted agreement or a check-in from Word, every version is hashed and every approval targets that exact snapshot — so a rejection stops the chain cold instead of leaving it half-approved.
Nothing is edited.
Everything is superseded.
Start approval on any AI-drafted or hand-written document, or check a file straight into CLM from the Word add-in. Either path writes a new, SHA-256 hashed version — the old one stays exactly as it was.
An AI pass then reads only the paragraphs likely to hold a date — clause headings, renewal language, the execution block — and reports each one with a confidence score and the exact clause it came from. Ambiguous day/month order and dates that land before the contract even starts get flagged, not guessed.
Confirm, edit, or reject each date from the contract page — rejected ones stay on record, they're never silently deleted.
AI draft · Start approval
Manual edit · re-uploaded
- Effective
- 01 Apr 2026 · confirmed
- Expiry
- 31 Mar 2028 · confirmed
- Notice deadline
- 01 Jan 2028 · 92% confidence
- Renewal clause 14.2
- Needs review · day/month ambiguous
One path continues.
The other one ends.
Steps run in rank order with their own deadlines. Approve every step and the workflow closes. Reject at any step and the whole chain terminates — there's no bounce-back for another try, only a fresh version.
Route
Pick a reusable rule template or build ranked steps by hand, each with its own deadline.
clm_workflow_steps
Act
The assigned approver works a focused inbox — approve or reject, with a comment, on that step alone.
clm_approval_actions
Close
Every step approved closes the chain. One rejection ends it outright — a new version has to restart it.
clm_workflows.status
Two things happen
without a second click.
Deadlines on the calendar
Manual step deadlines push straight into the starter's calendar the moment the workflow begins.
calendarPush.ts
Sent for signature
The current version renders to PDF and goes out as a real DocuSign envelope, signer by signer, in routing order.
clm_signature_envelopes
Nothing has to be
reconstructed later.
| 01 | Envelope history on the contract Every signer, every status change — no separate portal to check. |
| 02 | An action log with a name on it Every approve, reject, and cancel written down with actor and timestamp. |
| 03 | One click from draft to approval No re-entering metadata to get from document to version-linked contract. |
Governed at every step
- Approvals always target one hashed version snapshot
- Manual or rule-template routing, picked every time — nothing auto-routes on conditions
- ISO 27001 certified · on-premise or private-cloud deployable
Two intake paths, one contract: Word add-in check-inlands on the same record as Start approval.
Approve it once. Sign it for good.
Bring a contract your team actually reviews, and we’ll walk it through the whole chain — draft to signed envelope — on your own data.
ISO 27001 certified · MeitY empanelled