Legal
Law firms and notarial offices handle contract review, clause extraction, risk classification, and case intake at a volume that makes careful manual review slow, and a rushed one risky. This page sets out how such a workflow would be planned and run on inTheEU Assist, not a record of a completed deployment.
How the workflow would be structured
Contracts and case documents would be ingested into a case-scoped knowledge pack, with an agent configured to extract clauses, classify risk, and surface case facts. Each proposed fact or classification is entered with a status of proposed, tied to the specific document it was drawn from, and never treated as established until a lawyer reviews it.
An agent handling case intake would work from the firm's own templates and precedent, so its proposed drafts and classifications reflect how the firm actually practises, not a generic model's assumptions.
Where human approval sits
Every extracted clause, risk classification, or drafted output would require an explicit sign-off from the reviewing lawyer before it is treated as part of the case record. An output that has not been reviewed does not carry the weight of the firm's work product, and the platform is built to keep that distinction visible rather than implicit.
What this draws on today, and what it does not
Case-scoped document ingestion, the proposed-to-approved review lifecycle for extracted facts and flags, and the signed audit chain tying an output back to its source document and its reviewer are working parts of the platform. What is not part of this: any pre-built legal reasoning or automated legal opinion. The lawyer's own judgement remains the professional authority throughout; the platform makes the basis for that judgement traceable and the sign-off provable.
Some of the architecture underlying this capability set is documented in filings still in progress. This page describes what the platform is designed to do, at a level appropriate for planning a pilot, not an implementation specification.
Platform features and interface are subject to continuous improvement. Descriptions in this guide may not reflect the exact layout or wording of the latest released version.