Features
From bringing in existing texts to live drift checks.
TermShelf covers the lifecycle of already-published legal texts — from structured maintenance through review and approval to delivery as HTML, JSON or PDF and live drift checks across websites, apps and transactional systems.
What is Legal Content Operations?
- TermShelf as the Legal Content Operations layer
- Legal Content Operations is the ongoing operation of published legal texts: managing them centrally, versioning, approving, publishing precisely, delivering via an API and continuously checking the live version against the approved one. TermShelf is that operations layer — not a legal-text generator and not a substitute for legal advice.
Feature landing pages in detail
Go deeper on the core building blocks — each with a definition, concrete use cases and FAQ.
- Public Delivery APIDeliver legal texts as HTML, JSON and PDF — with version pinning and ETag caching.
- Transactional Legal Text DeliveryTerms, withdrawal & co. in order confirmations, contracts and checkout flows.
- Legal Content Drift ScannerDetect outdated legal texts on websites live — per site, language and market.
- Legal text versioningDraft, approval and immutable versions with an audit trail.
- Multi-brand legal text managementMultiple brands, websites and languages in one structure.
Workflow overview
Seven steps that fit together.
Bring in texts
Structure
Version
Approve
Publish
Deliver HTML/JSON/PDF
Drift check
A
Workspace & structure
The target structure defines where a legal text applies — for a specific website, language, region, or commercial variant.
- Workspaces
- Brands
- Products
- Sites
- Domains
- Locales
- Markets
- Site profiles
B
Documents & structured content
Bring your own legal texts: self-authored or externally provided texts are not managed as loose HTML blocks but as structured documents with sections and validated content blocks.
- Bring in existing texts
- No free HTML paste
- Sections and typed blocks
- Stable keys
- Document types
- Search and filter
C
Variants & overrides
Variants enable targeted deviations without copying entire documents.
- Base document
- Locale, market, profile variants
- Replace or suppress inherited blocks
- No duplicated full texts
D
Versioning & history
Every approved version remains traceable. Restorations create new drafts rather than overwriting history.
- Immutable snapshots
- Version numbers
- Diffs between versions
- Version pinning on delivery
- Restoration as a new draft
- History is never modified
E
Review & approval
Approvals are not hidden in informal chats or emails but mapped as an auditable workflow.
- Single reviewer
- Sequential review
- Threshold approval
- Self-review not allowed
- Decisions and notes
F
Publishing
Publishing happens with target precision for specific sites, languages, markets, or profiles.
- Target-aware publication
- Asynchronous publishing
- Published artifacts
- Rollback via controlled pipeline
G
Public Delivery API
Published content is available via a fast, read-only delivery interface — as HTML, JSON or PDF.
- HTML fragments for websites, apps and emails
- JSON for your own templates and rendering logic
- PDF artifacts for attachments and receipts
- ETags and cache headers
- Version pinning
H
Transactional Legal Text Delivery
Deliver legal texts where contracts are created — in order confirmations, contract emails, sign-up flows and checkout steps.
- Embed HTML into transactional emails
- Fetch JSON for your own mail templates
- Attach approved PDF artifacts to mails
- Stable reference to a specific version
I
Scanner & findings — Legal Content Drift
Legal content drift happens when the version visible in production no longer matches the approved version. Live drift checks make that gap visible.
- Crawl of public customer sites
- Comparison with approved version
- Drift detection per site, language and market
- Open, assign and triage findings
Drift examples
- — Terms v4.2 approved — live still v3.9.
- — German current, English outdated.
- — Relaunch links to the old privacy page.
- — Order confirmation attaches old PDF.
- — Email footer renders stale withdrawal copy.
J
AI-assisted change suggestions
AI-assisted suggestions can prepare possible updates. Changes are never applied or published automatically.
- Suggestions as recommendations
- Adoption is decided by users
- No automatic adoption
- Not a substitute for legal advice
- Legal review recommended
K
Webhooks & integration
Publication and lifecycle events are integration-ready.
- Publication events
- Signed webhooks
- Replayable deliveries
- Integration with external systems
L
Operations & event stream
Operational events remain traceable — failed jobs can be retried under control.
- Workspace event stream
- Retry for failed jobs in the customer app
- Replay for failed webhook deliveries
- No hidden mutation of history
Note on AI-assisted change suggestions
- Suggestions are non-binding recommendations.
- Changes are never automatically adopted or published.
- Acceptance, adjustment, or rejection is decided solely by users.
- Legal review by qualified counsel is recommended.
- TermShelf is not a substitute for legal advice.
Start the workflow in TermShelf
Manage and publish legal content with full control.
TermShelf brings privacy, legal notice, terms, and other website documents into a structured workflow.