Stop silent auto-renewals.
Approve the exact version.
Sign it once.
A missed notice window renews a contract on terms nobody chose. Votum reads each date from the clause that sets it and warns the owner 90 days out. Every approval is tied to the version the approver saw, and the other side redlines in plain Word.
One contract, as Votum tracks it
Draft
Imported, drafted or checked in from Word. Every version is SHA-256 hashed.
In review
Approvers act by rank. Changes requested parks the chain here until resubmit.
Changes requested ↺
Approved
The last step signs off on the exact version it was shown.
Signing
A DocuSign envelope goes out in routing order.
Executed
Completion closes the workflow and marks the contract executed.
Renewal
Reminded 90 days out and again in the last three. Renewing opens a new version.
Stop re-reading contracts
to find a date.
Import DOCX or PDF in bulk, scanned pages included, or start from a draft or the Word add-in. Nothing is overwritten: each change is a new hashed version, and any two compare line by line.
AI reads only the paragraphs likely to hold a date and reports what it found, with a confidence score. Code, not the model, works out “two years from effective”, and flags a day/month that could go either way or a date before the contract starts. You confirm, edit or reject each date, and rejected ones stay on record.
51/51
calendar dates captured in one 671k-character filing, from 5.9% of its text — measured on that document, not a guarantee for yours.
14.2 Term. This Agreement commences on the Effective Date and continues for a period of two (2) years, unless renewed under clause 14.3.
- Effective
- 01 Apr 2026confirmed
- Term
- 2 yearsread by model
- Expiry
- 31 Mar 2028derived by code
- Notice deadline
- 01 Jan 202892% confidence
- Clause 14.3 renewal
- 04/05/2027day/month ambiguous
A first read of every contract,
with the quote beside it.
On import, the counterparty, total value and currency are filled from the opening pages, free of charge. Each must appear in that text, and they only fill fields you haven’t set. Correct them any time.
Analyze full contract reads the whole current version into a one-screen digest: parties, term, payment, termination and unusual clauses. Flagged risks must quote the contract, and a digest tied to an older version is hidden until refreshed.
Playbook review checks the contract against positions from your clause library, up to 30 at a time. Each one comes back compliant, deviates or missing, with the contract’s own words as evidence. A result that skips a rule or misquotes the text is rejected, not shown.
- Parties
- Asha Components Pvt Ltd · Northgate Logistics
- Term
- 2 years from the Effective Date
- Payment
- Net 45 days from invoice
- Termination
- Either party, 30 days' written notice
- Unusual
- Uncapped indemnity, clause 12.4
Against your playbook
- Liability capped at 12 months' feesDeviates
“shall be unlimited in respect of any indemnified claim”
- Governing law: IndiaCompliant
“governed by the laws of India”
- Data-return on exitMissing
No matching text
A change request shouldn’t restart approval.
Reject only when the deal is dead.
Rules send an imported contract to the right approvers by value and currency; the highest priority wins, and a tie is flagged rather than guessed. Each approver decides on the exact version in front of them.
When
contract_value > 50,00,000 · INR
Rank 1
Procurement lead
Rank 2 · parallel
Finance head · Legal counsel
Rank 3
General Counsel
Approve
Next rank opens. Same-rank steps run in parallel and open together.
Continues
Request changes
Chain parks at that step with the comment. Resubmit resumes there, earlier approvals intact.
Parked, not ended
Reject outright
Ends the workflow and returns the contract to draft. Kept for deals that are genuinely over.
Terminal
Nothing for the other side
to learn or install.
Send a .docx with tracked changes already switched on, by email or a 14-day upload link. No login, no add-in, no install on their side.
When it comes back you see every insertion, deletion and comment by author. Accept them and you get a new version, ready for a fresh approval chain.
9.1 Either party may terminate this Agreement on thirty (30) ninety (90) days’ written notice.
R. Mehta · Counterparty
“Our board needs the longer window.”
The .docx stays the contract.
Not a copy rebuilt from text.
Votum keeps the original file for every uploaded or checked-in version. Download any version as .docx, and when a version has its own file, the signing envelope uses it rather than a plain-text render.
Accepting tracked changes edits the file itself. Insertions, deletions, moves and formatting revisions are resolved; tables, styles, numbering, headers, footers and comments are kept. A revision it can’t resolve safely, such as a merged table cell or a numbering change, comes back to you to accept in Word first. It is never guessed.
Checking in from the Word add-in uploads the whole document, with pending tracked changes and comments still in it. Version comparison reads the text; formatting differences are not diffed.
- word/document.xml
- 14 revisions resolved
- word/styles.xml
- Kept
- word/numbering.xml
- Kept
- word/header1.xml · footer1.xml
- Kept
- word/comments.xml
- Kept
- Table 3 · cell merge revision
- Accept in Word first
Renewals you decide on,
not ones that happen to you.
Sign without leaving Votum
The approved version goes out as a DocuSign envelope in routing order, and the envelope history stays on the contract. Completion marks it executed and closes its workflow.
- T−90 daysLead reminder
- Notice deadlineLast day to give notice
- T−3 daysUrgent reminder
- ExpiryOr renewal date
A dashboard shows what expires or renews in 30, 60 and 90 days. Owners are reminded 90 days out and again inside the last three. Renewing opens a new version and reuses the last approval chain.
“Who approved which version?”
Answered from the record, not inboxes.
| 01 | An activity trail with names on it Approvals, change requests, comments and lifecycle events with actor and timestamp, exportable as JSON. |
| 02 | Reports a GC can take upstairs Open records, renewal-date coverage, approval turnaround, and pending steps by assignee. |
Governed at every step
- Every decision is recorded against one hashed version
- Unlimited users on every band
- Contracts and files stored in India
- ISO 27001 certified · on-premise or private-cloud deployable
Cost follows the contracts you hold,
not the people who touch them.
Choose a band for the contracts you actively manage. Expired, terminated and archived contracts don’t count, and AI date extraction is included. Creators, approvers, reviewers and viewers are all unlimited.
- The first 10% over your band is free.
- Beyond that, extra contracts bill at your band's own per-contract rate, never a penalty rate.
- No per-user fees: add the whole legal team, procurement and business approvers.
| Active contracts | Per month | Per contract |
|---|---|---|
| Up to 100 | ₹14,000 | ₹140 |
| Up to 250 | ₹29,000 | ₹116 |
| Up to 500 | ₹50,000 | ₹100 |
| Up to 1,000 | ₹82,000 | ₹82 |
| Up to 2,500 | ₹1,65,000 | ₹66 |
| Up to 5,000 | ₹2,60,000 | ₹52 |
| 5,000+ | Group-wide licence → | |
Full-contract AI analysis and playbook review are metered on actual usage. An imported contract counts as active from import.
Know which contracts renew next.
Bring a batch of live contracts and we’ll import them, show which notice dates fall in the next 90 days, and walk one through the whole chain — draft to signed envelope — on your own data.
ISO 27001 certified · MeitY empanelled