The whole matter, handled in modules.

Paste the matter facts — client name, scope of work, fee basis — and receive a full engagement letter skeleton built on UK templates: scope, fees, complaints procedure, data-handling notice, and termination clause, ready for partner review and sign-off before it goes to the client.

On day one the firm receives a ready-to-review compliance pack: UK GDPR Art.13/14 client privacy notice, data-handling policy, DSAR response workflow, DPIA, transfer-impact assessment and a draft annual AI-use report — mapped to the SRA Code of Conduct and ICO guidance. Every template opens inside the app with your firm's details already filled in; edit the placeholders and download each as Word or PDF — drafts for partner sign-off, not documents written from scratch.

Drag a whole folder onto the matter — sub-folders and all — or the zip a client emailed, and every file inside is read where it can be. Thirty-one formats are recognised: PDFs including photocopies and phone scans, Word, Outlook .msg exports, .eml and mbox archives, Excel and OpenDocument, RTF, XML, web pages, iCalendar and vCard, photographs, and WhatsApp chat exports rendered as a dated conversation with each message attributed to who sent it. The nine formats a browser genuinely cannot read — .doc, HEIC iPhone photos, scanner TIFFs, Outlook .pst files, audio and video among them — say so by name and tell you exactly what to do instead. No file is ever silently ignored, and an email whose substance sits in its attachment says the attachment was not read. From what is read you receive a structured matter card — parties, key dates including any live deadline, claim type and the facts themselves — each fact carrying the passage it came from, and that passage is checked against the document: one genuinely in the file is quoted, one that is not is labelled as worked out rather than copied, so an invented quotation cannot pass for a real one. The matter's jurisdiction is not taken from the model — it is detected from the text's own signals and chosen by you, within the markets your firm is licensed for. Every fact is a proposal a fee-earner accepts, corrects or rejects before it is written to the matter file. After the matter is open it keeps working: a document added to it is read for facts the moment it lands, and the proposals wait in the matter's Proposals tab. A document identified as written by an AI assistant is never allowed to propose a fact about your case.

Client files remain on the solicitor's own disk; the privilege gate classifies Legal Professional Privilege status before any content leaves the browser, shows exactly what would be sent to the AI provider, and blocks egress unless the solicitor explicitly approves it for that document, that prompt, that moment — satisfying the SRA Code of Conduct duty of confidentiality by architecture rather than policy.

Click "prepare case" on any matter and receive a typed case-graph — parties and their roles, claims and counter-claims, evidence items linked to the documents on file, authorities cited or proposed, and the date spine from first instruction to next deadline — as a draft skeleton ready for the fee-earner to review and edit rather than rebuild from scratch.

Name the counterparty on a matter and the card builds by itself. On a UK matter it queries Companies House for the company profile and the officer list, carrying each officer's appointment and resignation dates exactly as the register records them. That needs your firm's own Companies House credential. Give it the company number and it reads that company; give it only a name and it returns the closest matches, labelled as a name search rather than as a confirmed identification. Where the register reports more entries than came back, the card marks that section incomplete rather than showing a short list as the whole record. The Gazette — and the SRA Register, where you have named the solicitor on the other side — publish no machine interface, so the card deep-links them and marks them "check by hand" instead of counting them as checked. Every line names the register it came from, links to it, and records when that register was read, so you can verify any of it at source. Where a register could not be reached — an outage, or a credential the firm has not connected — the card states that as a gap and counts how many there are. It never hands back a quiet empty card that could be read as nothing adverse found.

Before any payload leaves the browser, the pseudonymisation pass strips names, National Insurance numbers, NHS numbers, passport numbers, UK postcodes, phone numbers, bank account details and other personal data, replacing them with stable tokens so the AI works on the matter without seeing who the parties are — satisfying UK GDPR Art.5(1)(c) data-minimisation duties without any extra step from the fee-earner.

Click the compliance check on a matter and receive a posture report against the SRA Code of Conduct — which Principles touch the work done, where the firm's published AI-use position is consistent with actual matter activity, where a COLP would want a note — plus a draft Annual AI-Use Report built from real matter-activity logs rather than a template filled in from memory; every consequential AI action is additionally gated by a solicitor pre-action approval card logged to the matter ledger.

Run the adversary pass on any draft — a particulars of claim, a defence, a transaction advice — and receive a structured critique across thirteen angles: procedure (CPR service and form requirements), evidence (burden and admissibility), limitation (Limitation Act 1980 periods), quantum, legal authority, counter-claim, Part 20 claims, disclosure (CPR 31), costs exposure (Precedent H / Part 36 / CPR 44-47), regulatory exposure, ethics, commercial pressure and commercial optics — each finding anchored to the relevant statute, rule or authority.

Each authority cited by the AI is checked live against The National Archives' Find Case Law register — confirming the judgment exists at that neutral citation — before the solicitor approves and exports. A case the register does not hold blocks the export as a possible fabrication, and a check that could not run blocks it too — the gate fails closed rather than waving anything through. Statutes are handled the other way, by deep-link to legislation.gov.uk for you to confirm, because a case-law register cannot answer for an Act. An authority the AI left unflagged, or one you have not yet confirmed, holds the document at an amber-warn gate where you choose Cancel or Export Anyway — and the decision is logged to the matter ledger as evidence of the firm's citation due-diligence duty post-Ayinde. Find Case Law holds most courts from 2001 and is not every judgment ever handed down. A miss can mean outside coverage, a misstated citation, or a fabrication — the product says "not found", never "does not exist". Contains information licensed under the Open Justice - Licence v2.0 The check is enforced at export; the confirmation against the live source is the solicitor's — which is exactly the human verification the court in Ayinde required.

Every matter carries a persisted risk register. Deadlines are kept in four separate groups — limitation, procedural, contractual and regulatory — because a missed limitation cutoff is not relievable and most CPR deadlines are, and one undifferentiated list invites you to triage the recoverable one first. Findings sit on three axes: litigation exposure, regulatory exposure and evidential exposure. Every line names the field on the matter it was read from, the statutory basis the record carries — or says plainly that the record carries none, rather than guessing one — and the jurisdiction whose rules produced it. It recomputes as the matter changes. And when an input is missing or a calculation fails, it reports no risk level at all and tells you what is missing: it will not show a clean score for a matter nobody has read.

AI decisions on a matter are recorded to an append-only ledger, and so are the human decisions taken at the product's wired controls — accepted, rejected, edited, signed off, overridden, and the approval or refusal of an external action such as sending a document for signature. Recording is best-effort so it can never block a solicitor's work, and every export names the writes that failed rather than implying none did. The input is fingerprinted (a one-way hash over the whole input, never stored in the clear, so privileged text cannot leak into the export), the output kept as an excerpt, each row HMAC-signed and daily hash-chained — then exported in one click as a signed pack, in your own market's language, for SRA, ICO or in-house COLP review. The difference between telling a regulator "we have logs" and producing tamper-evident proof the log has not been altered. It evidences what was recorded and that the record is unaltered; it is not proof that the firm met an obligation.

Four views of the same matter without additional data entry: a four-layer calendar (court dates, statutory deadlines, client meetings and internal actions, drag to reschedule with a confirm step), a firm-caseload Kanban (drag a matter card to flip its status, persisted), a litigation timeline (every dated event on one horizontal axis, colour-coded by source, with Gantt range bars for events spanning a date range), and a case-as-graph view (parties, witnesses, counsel, documents and evidence drawn as nodes with edges — click any node to highlight its connections across the matter).

Trust-account view enforces the SRA Rule 8 five-week reconciliation cadence with a live discrepancy classifier and a COFA-ready PDF export; aged-debtor view buckets every unpaid invoice by age (current, 31-60 days, 61-90 days, over 90 days) so the partner reviewing the caseload knows which clients to chase this week; invoicing produces a UK PDF and JSON pack for accountant import; settlement-likelihood pulls similar matters with definitive outcomes; and a per-fee-earner efficiency dashboard quantifies hours saved by AI assistance per seat for the renewal conversation.

Open a matter, pick a document, and receive a fully-drafted starting point in one step: eleven HMCTS civil forms (N1, N9, N9A, N9B, N180, N181, N215, N225, N228, N244, N265) pre-populated from matter facts — nine ship with the blank PDF bundled; the default-judgment pair N225 and N228 pre-fill the same way once you upload the blank, which is free from the court service, and eight pleading drafters chosen from the matter screen — Particulars of Claim, Defence, Counterclaim, Defence and Counterclaim, Reply, Witness Statement, Statement of Costs N260 and Skeleton Argument. Eighteen workflows are offered on a UK matter, chaining documents into common matter shapes (LBA, Part 36 offer, default judgment N225/N228, N244 application, disclosure N265, mediation brief, freezing order, trial prep). Litigant-in-person mode carries through to the rendered documents as well as the AI-drafted ones: party-in-person signature framing, no SRA identity line, and the CPR 46.5 / PD 46 costs-cap basis on Precedent H instead of solicitor Guideline Hourly Rates. E-bundle preparation is in CPR PD 39A §3.2 shape. The contract library holds twenty-six templates across the five markets, nine of them English-law — NDA, Services Agreement, Employment Contract, Settlement Agreement, Witness Statement, Part 36 offer, Precedent H, Letter Before Action and CMC directions — each with its statutory anchors cited inline, and a filled template saves onto the matter so it goes through the same review, citation gate, signing and Word export as any draft.

The agent fleet surfaces inside Microsoft Word, Outlook and Excel, against the matter you pick. The Word ribbon drafts, stress-tests the wording you have selected, pulls counterparty intel, and files the open document to your document system. The Outlook task-pane — which you open on the message in front of you; it does not watch your mailbox — suggests which matter an email or calendar entry belongs to, files it to correspondence, drafts a matter-anchored reply, and reads dates out of the text for you to confirm before any of them reach the matter timeline. The Excel add-in checks a column of counterparty identifiers against that market's own company register and, if you tick the box, screens each name against the sanctions list your firm has imported — results written beside your selection. Companies House (with your firm's own credential) and the Polish KRS and Biała Lista VAT answer automatically; the German, Dutch and Spanish company registers are not connected, and a row for one of them says so and links you to the register rather than leaving a blank that reads as a clean check. A row that could not be checked is never written as one that was.

When a firm opts in — off by default, with an explicit confirmation required — the local agent journal records every AI invocation with input, output, routing and redaction count; the PII pseudonymisation pipeline strips National Insurance numbers, NHS numbers, passport numbers, UK postcodes, IBAN, email, phone and amounts before any disk write; and the firm receives a legal disclosure pack ready to fold into its existing privacy notice, DPA and sub-processor list — drafted to UK GDPR Art.13, SRA Code confidentiality obligations and LPP framing — so the COLP can sign off without external counsel review.

The matter is kept in a folder on the firm's own disk, not trapped in a vendor account. Each save writes through to that folder; reconnect restores changes; the matter's extracted knowledge travels with its documents; and the firm's precedents, playbooks and learning journal can be backed up and restored as one practice file. A failed folder write is surfaced rather than silently treated as saved.