Version history
LiveChain successive drafts of a contract together, and compare any two clause by clause.
- ✓Numbered version chains linking successive drafts of a contract
- ✓A new version is uploaded onto the chain and passes every check the first upload did — accept list, size, storage quota, antivirus — before the same analysis pipeline runs on it
- ✓The new version hangs off the latest in the chain whichever version you uploaded against, inherits its matter, and lands in negotiation when the parent was not yet signed
- ✓Clause-level semantic comparison of any two contracts
What it is.
When a counterparty returns a revised draft, upload it as a new version of the contract you sent. The versions chain together with a number each, so the negotiation history sits in one place instead of as five files called final_v3_REVISED.
Comparison is clause-level and semantic rather than a character diff: it reads both documents and reports what was added, removed and modified as a list of clause changes. That is the right shape for contracts, where a re-worded indemnity matters and a re-flowed paragraph does not.
Three steps.
End to end.
Link it to the contract it supersedes, and it becomes the next version in the chain.
Read the chain for a contract, or across the vault.
Pick any two contracts — versions of the same document or not — and get a clause-level list of what changed.
What you get.
- ✓Numbered version chains linking successive drafts of a contract
- ✓A new version is uploaded onto the chain and passes every check the first upload did — accept list, size, storage quota, antivirus — before the same analysis pipeline runs on it
- ✓The new version hangs off the latest in the chain whichever version you uploaded against, inherits its matter, and lands in negotiation when the parent was not yet signed
- ✓Clause-level semantic comparison of any two contracts
- ✓Added, removed and modified counts plus the per-clause detail
- ✓Redline templates carry their own version history with change notes, restore, and a unified text diff
Quick answers.
No. A version is created when a new draft is uploaded and linked to the one it supersedes — there is no autosave that snapshots a document as you work on it.
Not in the vault. Earlier versions remain available to read and compare, but there is no restore action on a contract. Redline templates do have restore.
There are no document comments to preserve — see the collaboration page for what does and does not exist there.
More in Vault & Document Management.
AES-256 encryption at rest, TLS 1.2 or later in transit, stored in AWS ap-south-1 (Mumbai, India).
Per-document share links with an expiry, a view cap, granular permissions, and recipient-tagged watermarking.
Every upload is a document with a category — agreement, evidence, court order, correspondence, identity — and the category decides what runs. Nothing is analysed unless you ask.
A contracts dashboard where every figure states its basis, and a request desk where triage is decided by your rules, not a model.