Integrations
What the assistant reaches inside the system you already run.
Bracton connects through the interface your case management system provides, under permissions you set, reads what that interface exposes and no more, and writes nothing back without a person approving it.
- No connector is promised until that system's access terms are held in writing, and the answer goes into your agreement.
- Your own document store is the primary route, whatever sits underneath.
- Most systems expose matters, documents, correspondence, key dates and time, enough for the sweep, the drafting and the time recovery.
- Some expose the ledger thinly or not at all, and the accounts work waits until you move.
Illustrative. Three screens from the working software, on invented files. The platform, screen by screen.
System by system
Six systems were checked against their own published developer material in July 2026 and again on 10 September 2026, and each row states what that vendor has published.
Why the first column matters
A reference a third party can read without signing anything lets the reach be stated before a proposal.
| System | Published developer reference | What that means today | What is promised before you sign |
|---|---|---|---|
| Clio | Open. Documentation a third party can read without registering. | The reach can be described from the reference before a proposal, and confirmed against your own account during it. | A written statement of what the connector reads and what it does not, in the agreement for your system. |
| Actionstep | Open. Documentation a third party can read without registering. | As for Clio. The reach is described from the reference and confirmed against your account. | A written statement of what the connector reads and what it does not, in the agreement for your system. |
| LEAP | Unconfirmed. A developer console exists and reading its reference means registering for access. | What it exposes is not known from outside. The document store route applies until access is held. | Nothing about the connector until LEAP's access terms are held in writing, and the document store route meanwhile. |
| Proclaim | Not reachable. Published claims of open integration with no developer reference behind them. | The reach cannot be stated from public material. The document store route applies. | Nothing about the connector until Access Legal's terms are held in writing, and the document store route meanwhile. |
| Osprey Approach | Not reachable. Published claims of open integration with no developer reference behind them. Osprey's price plans describe read only API access on its Premium and Enterprise plans. | The reach cannot be stated from public material and depends on the plan your firm is on. The document store route applies. | Nothing about the connector until Osprey's terms are held in writing, and the document store route meanwhile. |
| Visualfiles | Not reachable. Published claims of open integration with no developer reference behind them. | The reach cannot be stated from public material. The document store route applies. | Nothing about the connector until the vendor's terms are held in writing, and the document store route meanwhile. |
| Another system, or none | Varies, and is checked when you name it. | The document store route works whatever sits underneath, and a firm with no case management system is a candidate for the platform rather than the assistant. | A written statement of the route after the system is named and checked. |
What each piece of work needs to reach
| The work | What it reads | Where most systems stand | Where the platform stands |
|---|---|---|---|
| The morning list and the drift report | Matters, key dates, activity on each file and who holds it. | Exposed by most systems, so the sweep runs. | From the platform’s own record, with nothing in the way. |
| Drafts in your house style | Correspondence, documents and your own precedents and past advice. | Exposed by most systems. Precedents are configured for your firm either way. | The same. |
| Lost time recovered | Correspondence, calls, the diary and existing time entries. | Exposed by most systems, so unrecorded work is found and drafted. | The same, with entries waiting for acceptance. |
| The client account work | The client and office ledgers, the cash book and the postings. | Exposed thinly or not at all by some systems, so the accounts work waits until you move. | The assistant reads and writes the ledger and can block a save that would breach the accounts rules. |
What this page is not
It is not a list of connectors that exist. No connector has run against a real firm's system, and the product status page states every connector as not yet decided.
What exists is the route
The document store first, the interface where its terms are held, and a written statement of what the connector reaches.
Nor is it a promise that your system exposes what the table says. Vendors change their interfaces and terms, and your agreement carries the answer for your firm.
What the assistant does once connected is on the assistant page. If your agreement ends within the year, put the date in the contract diary.
Contact
Name the system you run
Tell us which system you run and when its agreement ends.
Discuss the system you run Or see the assistant run first