Document Intelligence
Spot the changes before your legal texts quietly go stale.
Legal texts rarely age because someone edits them — they age because the law, the website or the version delivered live moves on. Document Intelligence watches those three signals, assesses what they could mean for your brands and documents, and turns them into reviewable findings and proposed changes.
What is Document Intelligence?
- Document Intelligence
- Document Intelligence is TermShelf's observation and assessment layer — the second half of the product alongside managing, versioning and delivering legal texts. It connects three signals — legal changes (Legal Change Monitoring), website changes (Website Change Monitoring, Beta) and divergence in the version delivered live (Legal Content Drift) — checks in the context of the relevant brand, language and target variant whether a review might be needed, and records the outcome as an evidence-backed review finding. A confirmed finding can become a proposed change. It makes no legal determination and changes or publishes nothing on its own.
A legal text can go stale without anyone touching it.
The text in the repository stays as it was — the context around it does not. That is why the gap usually surfaces late: in a customer question, an audit or a complaint.
The legal context moves
New requirements, deadlines or mandatory disclosures affect document types you published long ago — without anyone on the team hearing about it.
The business reality moves
A new service, a new payment method, a new form or a new audience appears on the website. The legal text still describes the previous state.
The delivered version moves
A relaunch, a cache or a copied page shows something other than the approved version — in one language, on one domain, in one email.
Three signals, kept apart.
They originate in different places and mean different things. TermShelf keeps them distinct in the product, too.
- LegalChange
The law changes.
TermShelf tracks publicly available legal sources and consolidates them into traceable change events — maintained platform-wide rather than researched again for every customer.
- What is detected
- A consolidated event about a legal change, with potentially affected document types, deadlines and review questions.
- What it becomes
- A relevance assessment against your brand and the documents you actually publish — and, where it may matter, a review finding.
Boundary: An event reports a possible need for review. It does not establish that a change is binding for you.
Legal Change Monitoring in detail - WebsiteChangeBeta
Your website changes.
Between two checks of a monitored website, TermShelf compares what is new: detected services and embeds, plus verifiable statements on your own pages. This signal is currently available as a beta.
- What is detected
- New or changed services and statements — an additional payment or analytics service, a newsletter form, an upload, a new offering.
- What it becomes
- A change context with evidence — URL and verbatim quote — and the question of whether your published legal texts still cover that reality.
Boundary: A website change is not an instruction to edit a legal text. Pure layout or marketing edits do not create a review item.
Website Change Monitoring in detail - Legal Content Drift
The live version diverges.
The live check verifies that what is publicly visible really is the approved version — per site, language and market.
- What is detected
- Missing, unreachable or ambiguously linked legal pages, plus content that diverges from the published version.
- What it becomes
- A drift finding with evidence — often with a clear operational answer: republish, or reconnect the source.
Boundary: The check is technical and operational. It does not assess whether the content is legally correct.
Legal Content Drift Scanner in detail
WebsiteChange is not Legal Content Drift.
WebsiteChange describes a change in the business reality around a legal text. Legal content drift describes a divergence of the legal text itself — between the live and the approved version. One raises a content question, the other a delivery question.
Beta applies to WebsiteChange only.
Website Change Monitoring is labelled beta: available and usable, but still under active development — detection, assessment and the degree of automation can change. Legal Change Monitoring and Legal Content Drift do not carry that status, and Document Intelligence as a whole is not a beta.
Website Change Monitoring in detailRelevance, not a mass alert
Not every change affects every document.
A signal on its own says little. What matters is whether it touches the brand, the documents and the target contexts you actually publish for. TermShelf therefore evaluates against the version that is really delivered — with snippets and overrides resolved — rather than against a generic template.
Context taken into account
- Brand
- Document type
- Language
- Market
- Site profile
- Snippets & overrides
- Document applicability
The basis is a descriptive brand profile that TermShelf derives from your website and published texts and that you approve before it is used.
From signal to decision
- Change detected
- Assess relevance
- Identify affected documents
- Review finding
- Proposed change
- Human review
- Approval & publication
Instead of pushing every change onto every legal text, TermShelf checks where a review could actually be required.
What teams use Document Intelligence for
Keep track of legal changes
Instead of scanning newsletters and legal portals by hand, relevant legal changes arrive in one place — assessed in the context of your own brands and published documents.
Notice new services on the website
An analytics or payment service was embedded but the privacy policy never mentions it. The website check surfaces the gap instead of burying it in a ticket backlog.
Prove it after a relaunch
The live check shows whether the approved version really is visible everywhere after a relaunch — per site, language and market.
New feature, new review need
An upload, an account, a newsletter is added. TermShelf raises the question of whether the published texts still cover that reality.
Document review decisions
Every finding carries status, evidence and history. Even the decision that nothing needs doing stays traceable.
Get changes pre-drafted
Where a concrete edit holds up, TermShelf prepares it as an unpublished draft — editable, approval-bound, discardable at any time.
How TermShelf helps
Document Intelligence is not an alert firehose but a chain with clear hand-off points — and the last step always belongs to a person.
Signals instead of searching
Legal changes are collected and consolidated platform-wide; monitored websites are checked regularly. You don't have to go looking.
Assessed in brand context
Every signal is weighed against an approved brand profile and the documents you actually publish before it becomes a finding.
Findings with evidence
A finding states the trigger, the affected document, the evidence and the open review questions — with status, ownership and history.
Pre-drafted proposed changes
A confirmed finding can turn into a concrete proposal you adopt as an editable draft.
One review path, not a second one
Proposals run through the same approval and publishing process as any other change — versioning included.
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 Document Intelligence does not do
- It does not change legal texts automatically — every adoption is a deliberate decision.
- It publishes nothing automatically. Approval and publication remain the existing process.
- It does not provide legal advice and makes no legal determination.
- It does not promise to catch every relevant change — the analysis works on bounded, evidence-backed excerpts.
- It is not a legal-text generator and not a cookie/consent tool.
- It does not assess whether a piece of content is legally correct.
Two outcomes, two meanings.
A finding is a question. A proposed change is a draft wording. Both stay input for your decision.
There may be something to check here.
A finding states the trigger, the affected document, the evidence and the open review questions. You can confirm, park or dismiss it — with status and history. It changes nothing in the document.
This is what the change could look like.
A proposed change spells out a concrete edit in a specific place. It is only created from a confirmed finding and stays a proposal: adopt it as an unpublished draft, edit it, or discard it.
AI assists — it does not decide.
Relevance assessment and proposed wording are prepared with AI support and tied to evidence. The value sits in the chain around it: detect, contextualise, evidence, review, approve. Proposals are non-binding and do not replace professional or legal review.
Human in the loop
Intelligence without losing control.
TermShelf automates observing, contextualising and preparing. The decision stays in the existing workflow — the same one every manual change passes through.
Finding
Review
Draft
Approval
Publication
TermShelf prepares reviews and possible changes. Adoption and publication happen only after your decision.
- No automatic adoption
- No automatic publication
- Review stays with you
The loop
Operating legal texts means publishing — and keeping watch.
Managing and delivering is one half. The other is whether what you published still matches reality. Document Intelligence closes the loop — and restarts it when needed.
Manage
Deliver
Observe changes
Assess relevance
Review
Publish
Verify live
… and observe again. Legal Content Operations is never a one-off.
Frequently asked questions
- What is the difference between WebsiteChange and Legal Content Drift?
- WebsiteChange describes a change in the business reality around a legal text — a new service or offering on the website, for example. Legal content drift describes a divergence of the legal text itself between the live and the approved version. WebsiteChange raises a content question, drift a delivery question.
- Does TermShelf change legal texts automatically?
- No. Document Intelligence produces review findings and — from confirmed findings — proposed changes. A proposal is never applied automatically and never published automatically. Adoption, approval and publication are explicit user decisions inside the existing workflow.
- Does TermShelf detect every relevant legal change?
- No, and that cannot be promised. The analysis works on monitored sources, bounded excerpts and verifiable evidence. It is built to surface the need for review earlier — it promises neither completeness nor a legal outcome.
- Does Document Intelligence replace a legal review?
- No. Findings and proposals are non-binding preparation for a human decision. The legal assessment remains the task of qualified counsel; TermShelf is not a substitute for legal advice.
Read on
- Feature: Legal Change Monitoring — LegalChange in detail
- Feature: Website Change Monitoring — WebsiteChange in detail
- Feature: Legal Content Drift Scanner
- Feature: Multi-brand legal text management
- Guide: Keeping legal content current — the three change triggers
- Guide: From change signal to review finding
- Guide: What is Legal Content Drift?
- Guide: Preventing legal content drift
- Help: Document Intelligence analysis runs
- Help: Review and adopt proposed changes
Notice change while it is still small.
Let TermShelf watch legal changes, website changes and live drift — and decide yourself what follows from them.