Legal · GC and law firm

Records counsel can rely on.

Hand a regulator, an auditor or a diligence team records that are timestamped and traced to the person who made each change, and dossiers that are hash-sealed.

No card · EU-hosted · 5 minutes to a first classification
Audit trailArt. 12 · Art. 72
29.09.2026 09:12Classified AI systemRecruitment assistant → High Risk
29.09.2026 11:47Updated obligationAssign human oversight person(s) → Complete
29.09.2026 11:51Uploaded evidenceOversight rota.pdf
29.09.2026 16:30Signed off the residual riskA. Morgan
SealedDaily anchor · 29.09.2026 · 4 rows
sha256sha256 fingerprint bf89cbac35190d9ad25aac7b61ef9fb6ad1f7033008ec179304d9db75eadbc26
Chained to the day before
Illustrative trail · the anchor is the real hash of these rows
What legal teams ask us for

The same record answers each of these.

What we hear

“The client says they're 'mostly compliant'. Show me what they actually have.”

What the product does

One regulator-view dossier per system: classification, obligations, evidence and the hash chain.

What we hear

“The M&A target's AI estate is a black box. We need a diligence summary in 48 hours.”

What the product does

Diligence reads the seal at a public verify URL, with no portal access to negotiate.

What we hear

“If a national authority asks for documentation, can we produce it inside the deadline?”

What the product does

Every change is already logged, and every dossier entry numbered.

What changes for counsel

Built for the conversation that starts ‘show me’.

01

Tamper-evident audit trail

A hash chain anchored daily; verification reports any break instead of hiding it.

02

Regulator-view dossier

Written for a regulator, with article references in the margin.

03

Per-action audit log

Every change, with the user, the time, and the value before and after.

04

Multi-client access for firms

Many client organisations in one firm account, walled per engagement.

In practice

Three legal settings, one record.

Use case 01

A boutique firm advising fifty SMEs on EU AI Act readiness.

  • One playbook: free check → classification → obligations → evidence.
  • The deliverable: a dossier PDF with a verify URL.
Annex IV — Technical DocumentationRecruitment assistant
§1General DescriptionArt. 11
§2System Elements & Development ProcessArt. 11
§3Training, Validation & Testing DataArt. 10
§4Testing & Validation ResultsArt. 15
§5Human Oversight MeasuresArt. 14
§6Risk Management SummaryArt. 9
§7Cybersecurity MeasuresArt. 15
§8Pre-determined Changes & Continuous LearningProvider narrative · to write
Sealedsha256sha256 fingerprint e4d4b64e5aeabf734f6512c3249ff428c83229491c30f20c63c233614049e0227 of 8 filled from the register
Illustrative file · the sections are the builder's own; §8 is always yours to write
Use case 02

A diligence team examining an AI-native target.

  • The target hands over a verify URL; no portal access needed.
  • The hash chain shows nothing was quietly edited.
  • Findings feed straight into the warranty schedule.
Audit trailArt. 12 · Art. 72
29.09.2026 09:12Classified AI systemRecruitment assistant → High Risk
29.09.2026 11:47Updated obligationAssign human oversight person(s) → Complete
29.09.2026 11:51Uploaded evidenceOversight rota.pdf
29.09.2026 16:30Signed off the residual riskA. Morgan
SealedDaily anchor · 29.09.2026 · 4 rows
sha256sha256 fingerprint bf89cbac35190d9ad25aac7b61ef9fb6ad1f7033008ec179304d9db75eadbc26
Chained to the day before
Illustrative trail · the anchor is the real hash of these rows
Use case 03

An in-house GC answering a national authority's request.

  • The audit log shows every action in the inspection window.
  • Phase-gate attestations record exactly when each phase passed.
  • The response pack can be put together in a working day.
Quality management systemArt. 17
QMS documented through written policies and procedures from the policiesArt. 17(1)
Post-market monitoring system included from the monitoring planArt. 17(1)(h)
Procedure for reporting serious incidents included from the incident procedureArt. 17(1)(i)
Systems and procedures for data management covered from the data recordArt. 17(1)(f)
Risk management system (Art. 9) included from the risk planArt. 17(1)(g)
One PDF
Organisation compliance report
sha256sha256 fingerprint c008cbfadd5b9161b70f68cb8fcb441be44ab13e9a046cd8890c7dfcd3443fe3
Illustrative system · the parts are Article 17(1)’s
What counsel leans on

Features that hold up when the evidence is examined.

Straight answers

EU AI Act compliance for law firms: questions counsel ask

Is the audit trail tamper-evident?

Yes. Every change is logged with the user, the time and what changed, and the log is hash-chained and anchored daily. A break in the chain is shown, not hidden.

Can a third party check a dossier without an account?

Yes. Every sealed dossier carries a public verify URL, so a regulator, auditor or diligence team reads the seal directly, without portal access.

Can a firm manage several client organisations?

Yes. One firm account holds many client organisations, each with its own systems and obligations, and permissions are enforced at the API.

Does Veritome replace legal review?

No. Classification involves judgement no software resolves definitively, and the documents are drafts built from what the client records. Every screen names its article, so counsel can review the work.