Contract review
“What are our termination rights across all four supply agreements?”
Answers across every document in the matter at once, with a citation per agreement, and flags where the clauses differ.
How Jurisyn works
Jurisyn answers a question by retrieving passages from documents the person asking is authorised to open, drafting an answer that stays inside those passages, and attaching a citation to each statement. Nothing else is invented, and everything is logged.
The mechanism
Retrieval first, generation second, citation always
Most legal AI failures come from the same place: the model is asked to answer from memory, so it produces something that sounds like the right answer. Jurisyn inverts the order. It finds the passages first. The model’s only job is to state what those passages say and point at them.
The question is checked against the asker’s permissions
Before any search runs, Jurisyn resolves who is asking and what they can open, live from your document management system. The permission check is not cached and not approximated. A revoked matter goes dark on the next question, not on the next re-index.
Passages are retrieved from the permitted set only
Search combines meaning-based retrieval with exact term matching, so a question phrased in plain English still finds the clause that uses the defined term. Results are ranked, then re-ranked against the specific question, and the top passages are carried forward with their document, page and paragraph references intact.
The answer is drafted inside those passages
The model receives the retrieved passages and the question, and is constrained to answer from them. Where the passages conflict, Jurisyn shows the conflict rather than resolving it silently. Where they do not cover the question, it says the documents do not answer this, and shows what it found.
Every statement is matched back to its source
After drafting, each sentence is checked against the passage it claims to rest on. A sentence that cannot be matched does not ship. This is the step that turns a plausible answer into a checkable one.
The exchange is written to the audit log
Question, answer, documents retrieved, permissions applied, timestamp, user. Exportable as CSV or JSON, and retained for as long as your policy requires.
What people ask it
The work it takes off the pile
Matter handover
“Bring me up to speed on this file.”
A chronology built from the documents themselves, each entry linked to the correspondence or filing it came from.
Due diligence
“Which of these leases have change-of-control clauses?”
Sorts a data room by a specific question and shows the clause in each document that decided the answer.
Drafting support
“How have we drafted this indemnity before?”
Pulls precedent from the firm’s own closed matters, respecting client confidentiality between them.
Where it lives
Specifications
- Surfaces
- Slack, Microsoft Teams, and a browser workspace. No new app for fee earners to learn.
- Document systems
- iManage, NetDocuments, SharePoint and OneDrive, Google Drive, SMB file shares.
- File types
- PDF including scanned and OCR’d, DOCX, DOC, email and attachments, XLSX, plain text.
- Languages
- English. Hindi and Kannada document support in development.
- Identity
- SAML and OIDC single sign-on. Microsoft Entra ID, Okta, Google Workspace.
- Access model
- Permissions read live from the document system on every query. Ethical walls preserved.
- Hosting
- Managed by Jurisyn in your chosen region, or deployed into your own cloud tenancy.
- Audit
- Full query and access log, exportable as CSV or JSON.
Compared
Against the alternatives
| Jurisyn | General AI chatbot | Searching by hand | |
|---|---|---|---|
| Where answers come from | Only your matter documents | Public training data, plus whatever gets pasted in | Your matter documents |
| Citation on every statement | Yes — document and page | No — often invented | Yes, if you note it down |
| Respects matter-level access | Yes, checked per query | No | Yes |
| Client confidentiality | Documents stay in your systems | Uploaded to a third party by the user | Intact |
| Audit trail | Every question, answer and file logged | None the firm can see | None |
| Time to a sourced answer | Seconds | Seconds, then hours verifying | Thirty minutes to half a day |
See it answer a question from your own files
A demo runs on a folder of your documents, not ours. Thirty minutes, no slides, and you keep the index or we delete it — your call.