The matter keeps moving when nobody is looking at it.
Bernio watches the sources you have approved, bound to the entities this matter actually concerns, and puts what it finds where the work is.
What stays true no matter which model runs.
Approved sources only
Monitoring runs against a defined set of feeds. It does not roam the open web.
Bound to the matter
Entities, keywords and jurisdictions come from the matter record, and the scope is visible and editable.
Retrieval-grounded
Every finding carries the document it came from. Nothing surfaces on a model’s recollection.
Nothing about the matter leaves
Queries are built from declared terms and logged. Your documents are not sent anywhere to be matched.
What a finding does
It changes the file, it does not fill an inbox.
A finding lands against the authority or issue it affects. An authority distinguished on appeal reopens the strategy issue that relied on it, with the ruling attached.
- Delivered in the matter, not by newsletter
- Linked to the issue or deadline it changes
- Escalation path for what needs a partner today
Where it appears
In the matter, in front of the person who can act.
Findings sit next to the approval gates, the deadlines and the team — so what a client needs to be told is visible in the file rather than in somebody’s reading list.
- Inline in the matter chat and the record
- Deadlines at risk raised to the partner
- Every query logged with the terms it ran on
Sources
Nine classes, switched on per matter.
Case law, legislation, regulator guidance and dockets. Media and social. Sanctions and PEP lists, registries, insolvency and IP — each with its own frequency.
Scope
The query is as narrow as the matter is.
Entities come from the parties and the confirmed chronology; jurisdictions are bound explicitly, so a US docket does not answer an EU question.
Cost
What watching costs is visible before it is incurred.
Frequency is set per source class, and the cost of each is shown next to the switch.
A clause is the usual answer. Ours is a clause and an architecture.
On every tier. The matter boundary, the approval gate and the signed record are enforced in the runtime — hosted, in your own infrastructure, or on Bernio Pro.
- ABA Model Rule 1.4US
A lawyer must keep the client reasonably informed and promptly inform them of decisions requiring informed consent.
Findings attach to the matter and the issue they affect, so what the client must be told is visible in the file.
- ABA Model Rule 1.3US
A lawyer must act with reasonable diligence and promptness in representing a client.
Continuous watch on the authorities and dockets a matter depends on is a system property, not a task competing with billable work.
- GDPR Art. 5(1)(c)EU
Personal data must be adequate, relevant and limited to what is necessary for the purpose.
Queries are bound to declared entities and jurisdictions and are inspectable, so screening scope is a documented decision.
Point it at a matter that is already running.
We configure the sources with you and you see the first week of findings before anything is committed.
Development status
Bernio is in active development with design partners — firms running real matters through the platform and shaping what is built next — and the first commercial contracts are being signed on founding terms. The capabilities described on this page are built and can be demonstrated on a matter type your team handles. Bernio Pro — the on-premise appliance — is an engineering prototype and is not yet commercially available, so any capability on this site that depends on it is marked as such. Descriptions of the product are not warranties; the binding terms for any deployment are those set out in the applicable written agreement.