A timeline the other side cannot take apart.
Every event carries its date, its source document, the custodian it came from — and stays out of the approved chronology until a lawyer confirms it.
What stays true no matter which model runs.
Nothing enters unsourced
An event without a source document cannot be created. The link goes into the reviewed record, with page and custodian.
Proposed is not confirmed
Extracted events are excluded from Strategy and from export until a practitioner confirms, edits or rejects them.
Conflicts surface
Where two events contradict, the chronology says so and points at both. It does not quietly pick the later one.
Uncertainty is stated
“Sep 2022 · month only” is a different fact from a day, and is carried as one.
Built from review
It cannot reach what nobody looked at.
The chronology is assembled from documents that have been through review, at the significance threshold you set. Privileged sources are excluded from any build intended to leave the firm.
- Threshold set from review coding
- Privileged sources excluded from external builds
- New events proposed in batches, never inserted
Downstream
The same events, wherever they are argued.
A confirmed event is the unit the rest of the platform works from — Strategy cites it, monitoring watches the authorities attached to it, and a retraction propagates to everything that relied on it.
- References are live links, not copied dates
- A retracted event flags what cited it
- Exports carry the document references
Conflicts
A resolution issuing 1,200 shares against a cap of 1,000 is the case.
Bernio links both events and leaves the resolution to the practitioner, recording who made it.
Gaps
Silence is a finding, and is reported as one.
Fourteen months with no documents between a dispute notice and a request for arbitration is measured and flagged.
Precision
Dates are carried at the precision the document supports.
Month-only, quarter-only and inferred dates are marked, so nothing is argued at a precision the record cannot bear.
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.
- FRCP 26(b)(3)US
Work-product protection depends on the material being prepared in anticipation of litigation and handled as work product.
The chronology is built and held inside the firm’s perimeter, with privileged sources excluded from external builds.
- FRE 901(a)US
The proponent must produce evidence sufficient to support a finding that an item is what they claim it is.
Every event points at the document, page and custodian it came from, so the authentication path is part of the timeline.
- GDPR Art. 5(1)(d)EU
Personal data must be accurate, and inaccurate data rectified or erased without delay.
A retracted or edited event updates every downstream citation, and the change is itself recorded.
Give us a bundle and a dispute.
We build the chronology from your own documents, in your environment, and show you what it flags.
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.