Legal text versioning without copy-paste chaos

Why copy-paste, file names and CMS pages fail

The most common form of legal-text versioning is none at all: a CMS page is overwritten in place, a Word document is named terms_final_v2_NEW.docx, and the old version only survives in the trash or an inbox. The moment someone asks which version applied on a given day, it can no longer be reconstructed reliably.

File-name versioning has no approval, no publication date and no record of who changed what when. CMS pages overwrite the live state the instant you hit save. Both turn versioning into a matter of discipline rather than structure.

Separate draft, approval and published version

Reliable versioning keeps three states cleanly apart:

• Draft: the working copy — editable freely, with no external effect.
• Approval: a review step freezes the draft into an immutable version with a number and a timestamp.
• Published version: the approved version is taken live precisely for specific sites, languages or markets.

Only this separation lets you prepare a change without touching the live state — and document a live state without it silently shifting on the next edit. The feature page legal text versioning summarizes these three states.

Immutable versions, pinning and audit trail

In TermShelf every approved version is an immutable snapshot: it gets a unique version number and can no longer be edited — only a new version replaces it. Consumers can pin a specific version via ?version=N through the Public Delivery API and receive exactly that state.

The audit trail records who created, reviewed, approved and published a version. That makes it traceable which version applied at which point in time — the core question behind “which terms version applied at contract conclusion?”.

Rollback as a new publication, not a silent overwrite

When an older version should apply again, it is not copied back. Instead the old snapshot is restored as a new draft, approved again and published as a new version. The version history stays complete — even a rollback is a documented, dated step rather than a silent overwrite.

Concrete example: a customer orders on March 14. In April you notice a clause published in February needs reworking. Because every publication is dated and immutable, you can still prove which version was live on March 14 — independent of all later changes.

Boundary

TermShelf does not produce legally binding content and is not a substitute for legal advice. Versioning provides traceability over states and points in time; whether a particular state is substantively correct or complete remains a question for qualified counsel.