Definition
What Is Read-First?
The firm brain can see the file before it is allowed to draft or send. Visibility first. Writes later, behind a person.
Updated September 9, 2026.
Written by Jonathan Mahler · Reviewed by Jonathan Mahler, Founder of FirmOps. Operator notes, not legal advice.
Read-first is an operating rule for law firm AI: the system is allowed to see approved files, mail, and matters before it is allowed to draft, send, or change a record. It is not a product feature. It is the order of trust. A firm that skips it is asking a model to act on a paste.
Key Takeaways
- Read-first means visibility across approved systems before any write.
- Clio, Filevine, and the document store stay the system of record. The brain reads them. It does not replace them.
- A chatbot that waits for paste is not read-first. It is amnesia with a send button.
- Human approval is the gate on the way out. Read-first is the gate on the way in.
- ABA Formal Opinion 512 still requires competence and confidentiality when a lawyer uses generative AI.[1]Formal Opinion 512
How read-first works
The firm brain connects to the stack the firm already runs: case management, documents, email, sometimes billing. Scoped tools. Logged calls. No scavenger hunt.
On day one the brain answers questions from the file. What is stuck on this matter. Which records request went out. What the last client update actually said. It does not send. It does not change a stage. It does not create a payment.
Drafts come second, and only after the file is in view. A letter of representation pulled from the matter is a different object from a letter invented in a chat window. The first one can be checked against the file. The second one cannot.
Writes come last, and only behind a person. That is approval gates, not read-first. Owners mix the two up. One is what the model is allowed to see. The other is what it is allowed to do.
Why the order matters
Most firms buy a seat, then paste a fact pattern into ChatGPT. That is shadow AI. The model has no matter number, no conflict check, no document list. It sounds sure anyway.
Read-first inverts that. The firm names the systems of record. FirmOps wires read access. Staff ask the brain about the file they already have. The paste habit dies because the file is already there.
Opinion 512 tells lawyers they must understand the tools they use and protect client information.[1]Formal Opinion 512 You cannot do either if the tool never sees the real file and staff keep pasting it into a consumer tab.
Example
A records-follow-up job. Without read-first, a paralegal copies provider names from Clio into a prompt, gets a draft, and hopes the list was complete. With read-first, the brain reads the matter, the provider list, and the last outbound letter, then parks a draft. A person reads it and sends. The CMS is still the system of record. The brain did not become a second file.
That is the Conduit pattern: 47 intake steps collapsed because the file was already connected, not because someone typed faster.
The thing people get wrong
Read-first is not "the AI is read-only forever." It is the first deployment mode. As the firm trusts the layer, drafts appear, then approval-gated writes. A firm that starts on writes is skipping the only cheap test: can this thing see the truth.
Read-first vs a chatbot vs CMS AI
A chatbot sees whatever someone pasted today. Its first job is to talk. The failure mode is confident fiction.
A CMS AI feature sees what that one app already stores. Its first job is to answer inside Clio or Filevine. It is still blind to the inbox and the document store unless that vendor built the bridge.
A read-first firm brain sees approved systems across the stack. Its first job is to answer from the file with no send. The failure mode is skipping this step and starting on writes.
Keep Clio or Filevine. They stay the system of record. Details: CMS AI vs a firm brain.
Read-first is also not a data dump into a vendor that trains on your matters. Scoped tools. Logged calls. The minimum access that answers the job. If a connector wants the whole tenant "just in case," that is not read-first. That is a second copy of the file.
Frequently Asked Questions
What does read-first mean for a law firm?
The AI layer can read approved systems before it is allowed to draft or send. Visibility first. Writes later, behind a person.
Is read-first the same as an approval gate?
No. Read-first is inbound: what the model may see. An approval gate is outbound: what a human must release.
Does read-first replace Clio?
No. Clio, Filevine, or SmartAdvocate remain the system of record. The brain reads them.
How do we start?
Request a demo with one recurring job. If the file cannot be read, it is not a first build.
The Bottom Line
Read-first is how a firm brain earns the right to draft. If the model cannot see the file, it should not touch the file. Managed Firm Brain starts there. Request a demo if you want that gate on one real bottleneck.
Related terms
- What is a firm brain?
- Approval gates
- Shadow AI
- Law firm AI policy
- MCP for law firms
- Legal AI adoption
- Glossary
Article Sources
- Formal Opinion 512 Accessed September 9, 2026. ↩
Get the Managed Firm Brain Notes
Follow the practical path: live workflow builds, CRM-aware automation when the data is ready, and supervised work after approval.
Demo Context
What to watch for in the Managed Firm Brain walkthrough
Live-Lab Proof
How Conduit informs the first external deployments
Fit Criteria
API-ready systems, workflow scope, and approval gates
Next step
Bring one job the brain should be able to see.
If the file cannot be read, it is not a first build. The demo is one recurring workflow on the stack you already run.