Supervised, by design
Autonomous in the work, never in the judgement or the relationship. Wemmick does the drafting; your partners and lawyers keep the client conversation, and a lawyer holding the practising certificate stays accountable for every document that leaves the building. Six things make that true in the system, not just in policy.
- 01
Nothing leaves without a lawyer's approval
A draft cannot be exported until someone holding the lawyer role has approved its latest version. Every approval is recorded with the reviewer, the draft version, and a hash of the text they signed off.
- 02
Clauses start as DRAFT
A new or edited clause in the library ships marked DRAFT. Assembly refuses to use it in a real matter until the supervising lawyer has reviewed it and recorded their approval.
- 03
Every model call is audited
Each call to a model writes an event: the job, the model, the full prompt, the raw output, and the outcome. The audit log is append-only — the application has no permission to edit or delete a past event.
- 04
Nothing leaves your firm
Wemmick makes no outbound network calls at runtime. No telemetry, no analytics, no external services. Client data stays on your own systems, in your own records.
- 05
The AI runs on your systems too
The models Wemmick uses run on your own systems, alongside your data. No prompt, draft, or client detail is sent to an outside AI provider, and the whole system can run with the network unplugged.
- 06
What the lawyer still owns
The client relationship, the clause library, the red-flag rules and thresholds, and every approve, return, or edit decision belong to the supervising lawyer. Wemmick builds the machinery; the lawyer directs the practice of law and sits with the client.
See what your lawyers get back.
Tell us about your practice and we will walk you through Wemmick on a will from interview to export, and show where the week goes instead.