Trusted by over 10000 happy users
Add new versions to contracts that are already signed
Start a separate signing process for every change
Keep the full contract change history in one place
A transparent contract history, from the first signature to the latest change
Fewer scattered documents. More control over every change.
Award winning CLM software
FAQ
Yes. New files — an amendment, an updated attachment, a new version — can be added straight to a contract that’s already signed. From there, a separate signing process kicks in, while the original contract stays part of the full contract history.
A Signature Set is its own group of files with its own signing process, living inside the same contract. It’s how you add and sign new documents after a previous signing process is already done and dusted.
No. Amendments and changes go directly onto the existing contract. They stay connected to the original document, all part of one centralized history.
They’re preserved — nothing disappears. You can always access the original documents, every later change, and the signing processes that go with them.
Yes. A separate Signature Set can be created for a new file or group of files, so you can kick off a fresh signing process without re-signing versions that are already done.
Yes. Every contract-related action lands in the Activity Log — so you can trace the full sequence of changes and signing processes across the contract’s entire life.
Every related document, signed version, and activity stays in one place. Auditors and internal teams aren’t stuck comparing files across different folders or systems — the whole change history is centralized and easy to trace.
Anything that keeps changing after signing: amendments, extensions, updated terms, revised attachments — any document that needs to stay connected to the original agreement instead of floating off on its own.