Fix the Exception Queue Before You Add Automation
Staff route around tools when exceptions have no owner. Name the exception and the owner before you add another automation.
Founder of Conduit Law (non-attorney), COO · Co-Founder, FirmOps
Reviewed by Jonathan Mahler
One workflow
Request demo
Bring one recurring bottleneck. If it is a good first firm-brain build, the next step is a live demo, not a pitch deck.
Most firms buy another automation when staff start routing around the one they have. The email goes out. The CRM stays quiet. The task had no owner, so the tool never saw it. Another login will not name that owner.
I operate the business side of Conduit Law, a Denver personal injury firm operating in four states. I am the founder, and I am not an attorney. We operate the firm so owners can practice. Conduit Law is the proof. The offer is a Managed Firm Brain: read the systems the firm already has, prepare the next step, and stop where a human has to decide. The exception queue is the list of stops the software was never written to finish.
Key Takeaways
- An exception is a task the written rule does not cover, or a task the rule covered and the system still passed.
- If the owner is "the team," the item has no owner.
- Staff routing around the tool is the signal. A quiet system of record next to a loud inbox is how you see it.
- Name the exception, name one owner, put a clock on the unowned list. Then automate.
- A boxed template ends at the happy path. The operator begins where the template stops.
- Lawyers stay responsible for generative AI they use. The queue does not transfer that duty. I do not hold the legal gate.
What counts as an exception
People use the word for anything late. That is not a workflow. Late work that already has a rule and a named owner is a missed task. Chase it. Do not redesign the firm around it.
An exception is the item the written rule does not cover. It is also the item the rule covered, and the system still passed. A missing document. Two systems that disagree. A condition nobody encoded. A draft that looks finished and is not. If you cannot say which of those you mean, staff will file the same item in two places, and one of those places will be an inbox.
Write the definition down. One paragraph is enough. At Conduit the path is written, and the item that does not fit the path, or that the path passed and a person still had to catch, is an exception. It gets a name, an owner, and a clock. It does not get a new channel and a hope that someone will notice.
A law firm exception handling workflow is that paragraph plus the owner. It is not a feature inside the tool you already regret. If the definition lives only in someone's head, you do not have a workflow. You have a habit, and habits do not survive a busy Tuesday.
The hallway is louder than the file
When staff email instead of logging the ticket, or call instead of updating the CRM, the tool did not lose a feature war. The queue lost an owner. The leading indicator I watch is dull on purpose. The system of record gets quieter than the hallway. Threads close in email. Clio does not get the note. The next person opens the file and cannot see work that already happened.
You can see that pattern in a week if you look at the file, not the vendor dashboard. The dashboard counts the path it was coded to count. It does not count the path staff invented beside it. I do not want a detection average. The item that matters is the one that sat while two people assumed the other list had it.
If the same shape shows up again, that is a rule gap. Training the person who routed around the tool does not close a gap in the rule. Retrain when one person skipped a path everyone else still uses. Redesign when the path cannot hold the item. Firms mix those up because both feel like "staff are not using the system."
The queue, before you buy the next tool
A queue feature can pause, reassign, and escalate. It still will not name the owner. If the owner field says the team, you bought a prettier inbox. This is the picture I want an owner to have before the next software conversation. One row, one name.
| What showed up | Who it looks like it belongs to | Who has to own it | If nobody claims it |
|---|---|---|---|
| Task the written rule does not cover | The team | One named person | It dies in a shared inbox |
| System passed an item a person still had to catch | The model | A human gate | The miss reaches the client or the file |
| Staff finished the job in email or on a call | Whoever was free | The system of record | The next person cannot see it |
| A lawyer needs to know, not to rebuild the process | The attorney's afternoon | A short flag, prepared by ops | A timekeeper gets pulled off the file to reconstruct it |
Read-first is the inbound rule. If the system cannot see the file, it should not draft the next step, and it should not pretend the exception is handled. Approval gates are the outbound rule. A false pass belongs on a gate, not inside a new automation that will pass the same item faster.
The sequence, and the number I will not give you
Owners ask for the headcount math. At what volume does the queue need a dedicated person, instead of a line on the weekly review. I will not publish that number. Anyone quoting a matter-count threshold is guessing with your payroll. The failure mode does not need the guess. If the weekly review cannot clear the aged list, the queue already needs a person whose job is the queue. Shared responsibility is how items sit.
- Write the definition. What counts as an exception, and what is just late.
- Name one owner per exception type. Not a channel. Not a rotation that forgets whose week it is.
- Put a clock on anything with no owner. An aged list a named person already reads. Not a report nobody opens.
- Split awareness from resolution when a lawyer needs to know. Ops prepares the facts and the question. The attorney gets the flag, not the scavenger hunt, and not the job of fixing the process.
- Only then automate the path that now has an owner. Automating an unowned path gives you a faster way to drop the same ball.
Step four is the handoff firms get wrong in both directions. They hide the exception from the lawyer until it is a mess, or they hand the lawyer the mess and call that collaboration. Awareness is not the project. The operator prepares the facts. The attorney decides the legal point, if there is one, and goes back to the file. I do not pull a timekeeper into why the CRM did not update. That question is mine.
The false pass we already lived
The miss that hurts is not a model writing a weird sentence. A person reading the draft catches that. The miss that hurts is a firm assuming the system already handled a job it was never scoped to handle.
We lived a plain version, and it was an owner problem, not a model problem. A Clio matter did not get opened. The welcome sequence still fired, twice or not at all, because nothing in the path was allowed to stop and ask a named person whether the file existed. Follow-up that should have been on a clock was not on a clock. The tools were connected. The exception was not owned.
Intake at Conduit used to be 47 steps, every one a place to drop someone. I built a lot of that path down before AI came out, one API limit at a time. The model arrived later and sat on the path that already existed. It did not invent an owner for the steps that still lacked one. A clean draft can look like the job is done. That is how an unowned step becomes a dropped file.
One gate exists because automation created a false pass. The welcome sequence assumed a matter. The matter was not there. If the flag arrives without the facts, the reviewer has to reconstruct the file before they can decide. That reconstruction is the bottleneck, not the decision. If the flag arrives with the file attached, the review is a decision. I do not publish a stopwatch for it.
There is a competence reason to be stubborn about the false pass, and it is not mine to invent. This is an operator note, not a bar opinion, and not legal advice. The document is ABA Formal Opinion 512, issued July 29, 2024.[1]American Bar Association Standing Committee on Ethics and Professional Responsibility. "Formal Opinion 512." July 29, 2024. The ABA's same-day release says the opinion requires lawyers and law firms using generative AI to "fully consider their applicable ethical obligations," including competent representation, confidentiality, communication with the client, and reasonable fees. It also describes Model Rule 1.1: lawyers should understand the benefits and risks associated with the technologies used to deliver legal services to clients.[2]American Bar Association. "ABA issues first ethics guidance on a lawyer's use of AI tools." July 29, 2024. The opinion does not hand you an exception queue. I am not going to pretend it does. What it refuses is the idea that the tool's pass is the lawyer's pass. I am not the lawyer. I do not hold the gate where the output is legal advice. That request routes to a licensed attorney, including the times someone is behind and wants the shortcut.
Where the template ends
A workflow template covers the path the vendor already coded. When the matter is odd, the document is missing, or two systems disagree, the template stops. Sometimes it opens a ticket. Sometimes staff go back to the tabs. That ticket is not an owner. It is a suggestion that someone, somewhere, might look.
That is where the template ends. The operator begins. FirmOps is that operating work. FirmOps is not an MSO. It is not a boxed product you seat and then staff yourself. The firm brain reads the systems you already run, including the exceptions the template will not finish. Clio stays the system of record. We do not pull the stack out and hand you a replacement. If you want software and no one watching the queue, we are the wrong shop.
Three pulls this week
If you want to know whether your exceptions have owners, you do not need a new tool. Pull three things you already have.
- Unassigned or stale tasks in the system of record. If you do not have that view, use the inbox that substitutes for one. Count items with no named owner.
- Client-touch items from the last week that have no named next owner in the file.
- Jobs that closed in email or chat and never landed back in Clio, or in whatever system of record you actually trust.
If those three are ugly, do not buy another automation. Name the owner first. I will not quote Conduit's counts on a public page. The shape is the point. A quiet CRM next to a loud inbox is the queue, whether or not a vendor labeled it.
Who this is not for
Say no early if the ask is any of these.
- You want another tool to retire the workaround without naming an owner.
- You want the operator to sign the legal judgment. I will not. I am not an attorney.
- You want the case management system replaced. Keep Clio, or whatever system of record you already trust. We do not sell a swap.
- You want a template, and you will operate the exceptions yourself. That is a software purchase. This is not that purchase.
The fit is plainer. You want the business side operated so the people who practice law can practice. You will keep a named human on the items the happy path cannot finish. One recurring exception first, not a catalog of everything a model can draft.
Where this fits
This sits inside the wider law firm operations work, next to intake, the file, and the running of the week. The firm brain is the layer. The gates are how a false pass stays visible on a Tuesday when someone is behind. Conduit is where it runs in production. The Conduit case study is the public shape of that, without the private file.
Bring one exception your staff already route around. We will say what the definition is, who should own it, and what must not be automated yet. Request demo, or email hello@firmops.io.
Questions owners actually ask
What is a law firm exception handling workflow?
A written path for the item the happy path cannot finish. A definition of what counts, one named owner, a clock on anything unowned, and a handoff that does not dump the reconstruction on a timekeeper. It is an operating discipline. It is not a feature you turn on inside a boxed tool.
What counts as an exception, versus a missed task?
A missed task already has a rule and an owner. Chase it. An exception is a task the written rule does not cover, or a task the rule covered and the system still passed. If two people would file it in different places, you do not have the definition written down.
Who should own the exception queue?
One named person per exception type, chosen by the authority the decision needs. Not a shared inbox, and not "the team." Legal advice still routes to a licensed attorney. The operator can prepare the flag. The operator does not hold that gate.
When does the queue need a dedicated person?
When the weekly review cannot clear the aged list. I will not quote a matter-count that flips you from a shared review to a hire. Shared ownership is the failure mode. Items sit while two people assume the other queue has them.
How do you tell a lawyer without making it their project?
Ops prepares the facts and the question. The attorney gets a short flag, decides the legal point if there is one, and goes back to the file. Awareness is not the same job as fixing the process. Do not hand a timekeeper a scavenger hunt.
Will another automation tool stop staff from routing around the CRM?
Not if the exception still has no owner. Staff route around a tool when the tool cannot hold the item and nobody is named to catch it. Automate the path after it has an owner. Before that, you are buying a faster drop.
What can I audit this week without buying software?
Unassigned or stale tasks, client-touch items from the last week with no named next owner, and jobs that closed in email or chat and never landed in the system of record. If those three are ugly, name the owner before you add a tool.
Does this replace Clio?
No. Clio stays the system of record. The inbox and the documents stay where they are. The firm brain is a supervised layer across them, not a replacement system.
The thing people get wrong
They automate the happy path and call the rest a training issue. The rest is the queue. A new tool does not assign an owner. A vendor dashboard does not show the path staff invented beside it.
The Bottom Line
Fix the exception queue before you add automation. Write what counts. Name one owner. Put a clock on the rest. Request demo if you want that sequence on one real workaround, not a tour of another login.
Article Sources
FirmOps cites primary sources on factual claims. Operator notes are not legal advice.
- American Bar Association Standing Committee on Ethics and Professional Responsibility. "Formal Opinion 512." July 29, 2024. Accessed November 3, 2026. ↩
- American Bar Association. "ABA issues first ethics guidance on a lawyer's use of AI tools." July 29, 2024. Accessed November 3, 2026. ↩
Keep moving up the operating system
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
About Jonathan Mahler
Jonathan Mahler is the founder of Vertana (FirmOps is a Vertana brand) and the non-attorney founder and Firm Manager of Conduit Law. He runs the systems of a live PI firm every day, then turns reusable patterns into practical Managed Firm Brain workflows: approved context, supervised drafts, approval gates, and a path into deeper automation when the first workflow proves value. Meet Jon and Elliot.
Related Articles
What is a firm brain?
A firm brain is a purpose-built operating layer for one law firm, implemented in partnership, then run for that firm. Not a chatbot. Not a boxed product.
AI Approval Gates for Law Firms: What Stays Human
Firms buy AI and skip the approval layer. A PI firm operator maps the two gates that run in production, who holds each one, and the minimum version to retrofit.
Read-First AI for Law Firms (Before You Automate a Send)
Vendors sell the send. Operators start with visibility. The read-first audit on Clio, email, and intake, what disqualifies a firm, and the gates that stay human.
Request demo
Bring one recurring bottleneck and see whether it is a good first firm-brain build. If the first workflow is concrete, the next step is a live build session, not a broad advisory project.
Live demo | Human approval before external action