Legal text versioning
Version instead of copy — every approval traceable.
From draft through review and approval to publishing: TermShelf keeps every version as an immutable, dated snapshot. Restorations create new drafts, history is never overwritten.
What is legal text versioning?
- Legal text versioning
- Legal text versioning is the controlled management of a legal text's versions across its lifecycle: draft, review, approval and publishing. Every published version is an immutable snapshot with a version number and date. In TermShelf it therefore stays traceable at all times which version was approved and live when.
Typical use cases
End file chaos
No more "terms_final_v2_NEW.docx": every version carries a version number and an approval date.
Proof at contract conclusion
Later determine unambiguously which terms version applied to a specific order — via version number and date.
Controlled rollback
An older version is not quietly restored but re-approved as a new publication — the history stays complete.
Diffs between versions
Trace what changed between two approved versions.
Audit-safe approvals
Who approved what and when — including notes, with no after-the-fact mutation.
How TermShelf helps
Versioning is the foundation for review, delivery and live reconciliation: only what is unambiguously approved can be reliably delivered and checked.
Immutable snapshots
An approved version becomes an immutable snapshot with a version number — not a further-editable state.
Review and approval
Sequential reviews, threshold approvals and a ban on self-review make approval a documented event.
Audit trail
Approval and publication history show which version was live on which target and when — history is never modified.
Rollback as a new publication
Restoration creates a new draft from an older version; the old history remains untouched.
Version pinning on delivery
A specific version can be requested and stably referenced via the Public Delivery API.
What versioning does not do
- It does not produce legal texts and is not a substitute for legal advice.
- It does not overwrite history — even a rollback is a new, documented publication.
- It is not a general document management system; it is tailored to the legal-text lifecycle.
- It does not assess the content of a version, it keeps it traceable.
Frequently asked questions
- Does a published version stay immutable?
- Yes. Every approved publication is a dated, immutable snapshot with a version number. Later changes are created as new drafts and versions; the history is not overwritten.
- How does a rollback work?
- A rollback does not overwrite anything. Instead, an older version is restored as a new draft and re-approved and published. This keeps the full version history intact.
Every version traceable — without copy-paste.
Manage legal texts with draft, approval and immutable versions in one workflow.