Review workflows for legally relevant website content

Why legal texts need a review step

For legally relevant content, it is not only the result that matters but the path to it: who reviewed, who approved, on what basis? A traceable review step separates the draft from the binding version and makes approval a documented event rather than a silent “save.”

Building blocks of auditable approvals

• Sequential reviews: several review steps in sequence, each with its own note and timestamp.
• Threshold approvals: publishing only becomes possible once a defined number of approvals is present.
• Ban on self-review: whoever authored a change cannot approve it themselves — the four-eyes principle is structurally enforced.

An approval process in practice

Suppose a shop's terms change a clause on delivery times. A traceable flow might look like this:

• Someone creates a draft from the current version with the changed clause.
• A first review checks it and leaves a note; a second review confirms.
• Only once the threshold of two approvals is met does publishing become possible.
• Publishing creates an immutable snapshot, e.g. terms v5 with an approval date.
• Delivery via the Public Delivery API serves v5 from then on — website, app and order email pull the same version.

The author of the change never appears as an approver in this chain — the four-eyes principle is structurally enforced, not just convention.

From approval to an immutable snapshot

At the end of the review there is not an editable state but a frozen one: the approved version becomes an immutable snapshot with a version number. This makes it unambiguous later what was actually approved — the basis for version proof and live reconciliation. More in legal text versioning without copy-paste chaos and on the feature page legal text versioning.

Typical weaknesses in the approval process

• Approval by word of mouth or email, with no link to the specific version.
• Author and approver are the same person.
• After approval the text is still “quickly” changed — the snapshot no longer matches.
• It is not documented which version was approved when.

Boundary

TermShelf does not produce legally binding content and is not a substitute for legal advice. The review process organizes responsibility and traceability; the substantive review of the content remains the task of qualified counsel.