Legal Change Monitoring
When the law changes, the real work is only starting.
The alert is the easy part. The harder question is whether it concerns your brands at all — and which legal text, in which language and market, someone should look at. Legal Change Monitoring brings change signals into the context of the texts you actually publish and turns them into a review finding.
What is Legal Change Monitoring?
- Legal Change Monitoring
- Legal Change Monitoring is the LegalChange signal of TermShelf Document Intelligence. Publicly available legal sources from Germany and the EU are followed platform-wide and consolidated into deduplicated change events. Each event is then held against an approved brand profile and the documents a brand actually publishes; where it may matter, an evidence-backed review finding is created. TermShelf makes no legal determination, changes nothing on its own and promises no completeness.
A legal change scales badly across several brands.
Once an organisation runs several brands, websites, markets, languages and business models, the alert itself is the easy part. The hard question comes after it: where exactly should someone look now?
Not every legal team works this way — but every version of it gets more expensive with each additional brand and target context.
A mass email is not an assignment
"Everyone please check" spreads the uncertainty instead of narrowing it. Who should look at which version of which document stays unanswered.
Blanket review costs most where there is nothing
Reviewing every document of every brand just in case makes the effort grow with the portfolio — even when only a fraction can be affected at all.
Shared text blocks blur together
One passage is shared across brands, another exists only as a brand-specific variation. In a list of document titles that difference is invisible.
The state of play sits next to the text
The ticket, the spreadsheet and the inbox each know something about the case that the document does not. Later it is hard to evidence why the decision was to change nothing.
The core idea
A legal change does not mean: edit every legal text.
A change event is, at first, only a platform-wide signal. Only in the context of a concrete brand does it become the question of whether a review makes sense at all — and if so, for which document in which expression.
Change event
Consolidated signal from public legal sources
Assessed per brand
Brand A
B2B SaaSPossibly relevant
A published document type falls within the event's scope — a review finding with evidence and open questions.
Brand B
B2C shopPossibly relevant
Affected, but in a different expression: another language, another market, different text blocks.
Brand C
Internal platformNo finding
The brand profile and the published documents offer no point of contact — no review item is created.
Outcome
A finding instead of a mass alert
What remains is a review item with an addressee: this document, this brand, this language, these open questions.
TermShelf does not decide whether a change is legally required. It structures where a review could make sense — and where, on the available evidence, nothing needs to be started.
Context-aware relevance
What gets assessed is the version you actually deliver.
TermShelf does not simply put a change event next to a document title. It assesses the expression a brand really publishes — with text blocks and brand-specific variations resolved, in the relevant language and target context. A generic template would hide exactly the differences that matter.
Context taken into account
- Brand
- Brand profile
- Document type
- Language
- Market
- Site profile
- Text blocks & variations
- Document applicability
The basis is a descriptive brand profile — what the brand offers, to whom, in which contexts. TermShelf proposes it from your website and published texts; it is only used once you have approved it. It is descriptive metadata, not a legal classification.
Where the signals come from
TermShelf follows a curated selection of publicly available official and semi-official sources from Germany and the EU — maintained platform-wide rather than researched again for every customer. Incoming items are deduplicated and consolidated into stable change events; early stages such as bills and ongoing procedures are carried as exactly that, not as settled law.
- Federal courts
- Federal Constitutional Court
- Federal Law Gazette
- Ministries
- Data-protection authorities (BfDI, DSK)
- EDPB
- EUR-Lex & EU Official Journal
- CJEU
That selection is deliberately bounded. TermShelf does not crawl all German and European law and does not promise to capture every relevant change.
What teams use Legal Change Monitoring for
Assign instead of forward
Instead of pushing an alert to everyone, a review item is created per affected brand and document — with the trigger, the evidence and the open review questions.
Rule out brands that are not concerned
The biggest time saving sits with the brands where no finding is created. They never enter the process in the first place.
Keep effective dates in view
Where the source provides them, a change event carries effective and action dates — as context for the review item, not as a legal assurance.
Treat language and market versions separately
What gets assessed is the version actually delivered. A German and an English expression of the same brand can raise different review questions.
Evidence your review decisions
Every finding carries status, ownership and history. Even a deliberate "nothing to do here" stays traceable later.
Get changes pre-drafted
Where a concrete edit holds up, TermShelf can prepare it as an unpublished draft — editable, approval-bound, discardable at any time.
How TermShelf helps
Legal Change Monitoring is not an alert firehose but a chain with clear hand-off points — and the last step always belongs to a person.
Sources curated centrally
A curated selection of public official and semi-official sources from Germany and the EU is followed platform-wide — not researched again for every customer.
Consolidation, not raw alerts
Several reports about the same change are merged into one event, with potentially affected document types, effective dates and review questions.
Brand relevance before document analysis
Every event is first held against a brand profile you have approved. What offers no point of contact for a brand creates no review item there.
Assessed against the delivered version
The check runs against the expression really published, with text blocks and brand-specific variations resolved — not against a generic template.
Findings with evidence
A finding states the trigger, the affected document, the evidence and the open review questions — with status, ownership and history.
Switched on deliberately
Analysing your documents has to be enabled explicitly and can be turned off again at any time. Nothing happens without that consent.
What Legal Change Monitoring does not do
- It does not promise to catch every relevant legal change — the source selection is deliberately bounded.
- It does not determine whether a change is binding for you or requires an edit.
- It does not provide legal advice and is not a substitute for qualified counsel.
- It changes and publishes no legal texts on its own — adoption and approval stay explicit decisions.
- It is not a legal-text generator and does not rewrite documents on suspicion.
- It distinguishes bills from decided changes and never presents a draft as settled law.
From signal to review item — in separate steps.
Each step has its own purpose and its own hand-off point. The path does not end in the text automatically; it ends at a decision.
Always
Change event
Brand relevance
Affected documents
Review finding
Human review
Up to here nothing in the document changes. A finding can be confirmed, parked or dismissed — with status, ownership and history. Even the decision that nothing needs doing stays traceable.
When confirmed and included in the plan
Confirmed finding
Proposed change
Draft
Approval
Publication
Pre-drafted proposed changes are part of the plan from Professional upwards. A proposal lands as an unpublished draft in the existing approval workflow — editable, discardable at any time. Without that plan tier the findings remain and stay readable; only the proposals are not created.
A finding and a proposed change are not the same thing.
Keeping them apart is not a formality but the governance benefit: the question comes first, a draft wording at the earliest afterwards — and only once someone has answered the question with yes.
There may be something to check here.
A finding names the change event as the trigger, the affected document in its concrete expression, the evidence and the open review questions. It asserts no legal consequence and changes nothing in the text.
This is what the edit could look like.
A proposed change spells out a concrete edit in a specific place. It is only created from a confirmed finding, stays a proposal, and becomes a draft only after you deliberately adopt it.
Prepare, yes. Decide, no.
Relevance assessment and wording are prepared with AI support and tied to evidence. There is no automatic adoption and no automatic publication: a prepared draft runs through the same approval and versioning path as any manual change. TermShelf does not provide legal advice.
Check cadence
The plan sets how closely TermShelf checks.
The relevance check on legal changes is anchored to the brand, not to an individual website: all websites of one brand share the same clock. Higher plans check on a tighter cadence and additionally allow an on-demand check.
Included from Professional upwards. Free and Starter include no automatic check on legal changes.
Professional
Check cadence
monthly
Business
Check cadence
weekly
Agency
Check cadence
daily + manual
Enterprise
Check cadence
daily + manual / prioritized
What a cadence means
- TermShelf runs the check at this cadence.
- A tighter cadence surfaces a possible need for review earlier.
- Change events already on record are assessed against your brands.
What it does not mean
- Not that every legal change is detected within that window.
- Not that a change was published or took effect on that day.
- Not that coverage is complete — TermShelf does not promise that.
Multi-brand
Three brands, one event, three different answers.
Brands inside one organisation differ in business model, audience, markets and languages. Those differences are exactly what decides whether a change event has any point of contact at all.
Brand A
B2B SaaS, DE
Sells to businesses only. Consumer-facing events typically produce no finding here — the brand is left alone.
Brand B
B2C shop, DE/AT
Sells to consumers in two markets. One event can touch several document types here — and raise different review questions per market.
Brand C
Platform, international
Runs several languages and target contexts. Sometimes only one language version or one brand-specific variation is affected, not the whole document.
So an event does not turn into "go and touch every set of terms" but into a small number of concrete review items — each naming brand, document, language and target context.
What Legal Change Monitoring explicitly is not.
Two misunderstandings are close at hand. Both describe something other than what TermShelf does.
A feed answers only the first half.
A newsletter or legal portal tells you what may have changed. What stays open is whether that creates a need for review in your brands and the texts you publish. That second half is the part TermShelf tries to structure — in the context of your content, not as a general bulletin.
An alert does not produce a new legal text.
TermShelf does not rewrite documents because a change showed up somewhere. Legal Change Monitoring is one step inside the existing lifecycle of your texts — with review and approval in exactly the same place as for any other change. The content stays yours.
The path stays the same
Signal
Analysis
Finding
Optional proposal
Review
Approval
Publication
Three signals, one loop.
Legal Change Monitoring watches the legal context. Two further signals watch the other side: your own reality and your delivery.
- LegalChange
When the legal context changes.
Public legal sources are followed and consolidated into change events — assessed against your brands and published documents.
- WebsiteChange
When the business reality changes.
On a monitored website, new services, features or offerings stand out — raising the question of whether the published texts still cover them.
- Legal Content Drift
When the published version diverges.
The live check verifies that what is publicly visible really is the approved version — per website, language and market.
Frequently asked questions
- What is legal change monitoring?
- Legal Change Monitoring is the LegalChange signal of TermShelf Document Intelligence. TermShelf follows a curated selection of publicly available legal sources from Germany and the EU, consolidates the reports into deduplicated change events and checks them against an approved brand profile and the documents a brand actually publishes. Where it may matter, a review finding with evidence and open questions is created.
- Does TermShelf detect every legal change?
- No, and that cannot be promised. TermShelf follows a deliberately bounded selection of public sources and does not crawl all German and European law. The goal is to surface a possible need for review earlier — not to promise completeness. Watching the legal environment remains the task of the user and their advisers.
- Does TermShelf decide whether a legal change is binding for us?
- No. A change event reports a possible need for review. It does not establish that a change applies to you, is binding, or requires an edit. That assessment remains a professional and legal decision that TermShelf prepares but never makes.
- Are my legal texts changed automatically?
- No. Legal Change Monitoring produces review findings. Even a proposed change prepared from one is never applied automatically and never published automatically: it lands as an unpublished draft in the existing approval workflow and is only adopted and published after an explicit decision.
- What happens when a change may be relevant?
- A review finding is created that names the trigger, the affected document, the evidence and the open review questions. It can be confirmed, parked or dismissed — with status, ownership and history. Nothing in the document itself changes in the process.
- Can TermShelf prepare a change?
- When a finding has been confirmed and the plan includes pre-drafted proposed changes, TermShelf can formulate a concrete edit and prepare it as an unpublished draft in the document or in a brand-specific text variation. The draft is editable, approval-bound and discardable at any time. Without that plan tier the findings stay readable; only the proposals are not created.
- Which brands are checked?
- The active brands for which Document Intelligence is switched on. The basis is a descriptive brand profile that TermShelf proposes from your website and published texts and that you approve. If a brand offers no point of contact, no finding is created for it.
- How often does TermShelf check for legal changes?
- The cadence depends on the plan and ranges from monthly to daily; higher plans additionally allow an on-demand check. The cadence applies per brand — all websites of one brand share the same rhythm. It describes how often TermShelf checks and says nothing about when a change is published, becomes known or takes effect.
- Is Legal Change Monitoring legal advice?
- No. Findings and proposed changes are non-binding preparation for a human decision. The legal assessment remains the task of qualified counsel; TermShelf produces no legally binding content and is not a substitute for legal advice.
Read on
- Feature: Document Intelligence — all three change signals
- Feature: Website Change Monitoring — the WebsiteChange signal
- Feature: Legal Content Drift Scanner
- Feature: Multi-brand legal text management
- Guide: A law changed — which documents need reviewing?
- Guide: Keeping legal content current — the three change triggers
- Pricing: check cadences and included signals per plan
- Help: Document Intelligence analysis runs
- Glossary: legal change monitoring & review finding
Let legal change arrive where your texts already live.
Have TermShelf hold change signals against your brands and published legal texts — and decide yourself what follows from them.