Contract Versions
Follow the issued-version chain a contract seals when sent, with signed dates and the current version.
When you send a standalone contract for signing, ClientCasa seals an immutable version of the exact terms the client received. If you revise terms before they're signed, the prior version is superseded and a new one is sealed — so the Version history card always reflects what was actually sent and what was actually signed.
The Version History Card
On a contract detail page (/dashboard/contracts/[id]), the Version history card lists each issued version of the contract.
- Open a contract that has been sent.
- The Version history card shows each version as
v1,v2, and so on, newest first. - Each version carries a status badge and its Issued date.
- Once a version is signed, it shows a Signed date alongside the issued date.
- The live version — the one currently in effect — is marked with a Current badge.
A note confirms that each issued version is a sealed, immutable record of the exact terms.
Voided and Expired Terms
A contract's own status is the legal source of truth. When a contract is voided or expired, no version is marked Current, and the card shows a short note that the terms are no longer in effect:
- Voided terms: "These terms were voided — no longer in effect."
- Expired terms: "These terms expired — no longer in effect."
Terms That Belong to a Smart-File
If the terms are part of a smart-file rather than a standalone contract, their version history is managed on the owning smart-file. In that case the card shows a link to Open smart-file instead of an issued chain — the smart-file's own version history is the source of truth.
Related
- Send for Signing — how a contract moves to sent and signed.
- Contracts API — programmatic access to contract records.