Proof and Pricing · Process reveal · Published Aug 9, 2026

The Quarterly System Review: The 90-Minute Protocol We Run With Clients

Installing a system is the easy part; keeping it working is where most operational efforts quietly fail, because systems drift, people improvise, shortcuts creep in, and a process that was airtight at install slowly springs leaks no one notices. So every quarter we run a 90-minute protocol that checks the systems the way you would check anything you depend on: risk first, then the pipeline, then the health of the systems themselves, ending with a short list of what to fix next. Here is the full agenda, revealed, so you can run it yourself.

Systems drift, so they need review. Every quarter we run a 90-minute protocol: it opens with risk (deadlines and SOLs at risk, anything that could become a claim), confirmed safe before anything else; then pipeline and KPIs, to see the firm's throughput and where it is stalling; then system health, checking each system is still used as designed and still fits the firm's current work; and it ends with a short, prioritized list of what to fix next quarter. Ninety minutes keeps it consistent and forces prioritization. We facilitate the protocol and surface the picture; the firm makes every decision, and all legal judgment is the attorney's. Each system supplements, never replaces, the firm's own processes and judgment.

The dirty secret of operational systems is that installing them is not the hard part; keeping them alive is. A system is a set of behaviors, and behaviors drift: the paralegal who followed the intake process perfectly in month one starts taking a shortcut in month four, the escalation that used to fire reliably gets muted because it was noisy once, the board that captured everything slowly accumulates matters that were entered informally. None of this is malice or incompetence; it is entropy, the natural tendency of any process to erode as people adapt it, forget parts of it, and work around it under pressure. A system that is never reviewed does not stay at install quality; it degrades, quietly, until one day it fails to catch the thing it was built to catch. The only defense is a regular review that checks the systems are still doing their job and corrects drift before it becomes a gap, which is why the quarterly review is not an optional add-on to our work but a core part of it, extending the ongoing-reporting discipline in the operations report guide.

Why systems drift

Understanding why systems drift is what makes the review effective, because the review is designed to catch the specific ways drift happens. Systems drift in three main ways. They drift in usage, as people stop following parts of the process, take shortcuts, or let steps lapse, so the system on paper and the system in practice diverge. They drift in fit, as the firm changes, new practice areas, new volume, new staff, while the systems stay as they were built, so a system that fit perfectly at install slowly stops matching the firm's actual work. And they drift in trust, as small failures or noisy alerts erode people's confidence in a system, leading them to rely on it less, which is self-reinforcing because a system relied on less catches less. A good review checks all three, is the system still being used as designed, does it still fit the firm, is it still trusted and relied upon, because each kind of drift is a different failure that needs a different correction.

The 90-minute protocol

The protocol is deliberately time-boxed to 90 minutes, because the biggest threat to any review is that it stops happening, and a review that eats half a day will not survive a busy quarter. Ninety minutes is enough to check what matters properly and short enough that a firm will actually hold it every quarter, which matters more than exhaustiveness, since a good-enough review held reliably beats a perfect review held once. The time-boxing also enforces prioritization: with a fixed budget, the review has to lead with the highest-stakes items and cannot drift into an open-ended discussion, which is exactly the discipline that keeps it useful. The agenda has four segments in a deliberate order, risk, pipeline, system health, and what to fix next, and the order is the most important design choice, because it guarantees that even if the review runs short, the most important thing was checked first.

Segment 1: risk

The review always opens with risk, and the reason is a design principle: the most important thing must be checked first, because time and attention are finite and anything left for the end of a meeting sometimes does not get reached. So the first segment confirms the risk picture: the deadlines and statutes of limitations at risk, anything approaching that is not safely handled, and anything that could become a claim, checked against the firm's risk numbers as in the deadline audit guide. Nothing else in the review gets attention until this is confirmed handled, because a slipping deadline outranks any pipeline optimization or system tweak. Leading with risk also sets the tone that the whole system exists to prevent catastrophic, preventable failures, and it means that even in the worst case, where the review gets cut short by an emergency, the one thing that absolutely had to be checked, that nothing dangerous is drifting, already was. The attorney owns the judgment on every risk item; the review simply guarantees the picture is surfaced and confronted every quarter.

Segments 2 to 4

With risk confirmed, the review moves through three more segments. Pipeline and KPIs comes second: a look at the firm's throughput, where cases are, how fast they are moving, whether conversion and progression are healthy, using the firm's numbers as in the KPIs guide, so the review sees not just safety but performance. System health comes third: a deliberate check of each core system against the three kinds of drift, is it still being used as designed, does it still fit the firm's current work, is it still trusted and relied upon, so that any erosion is caught and named while it is still a small correction. And the review closes with what to fix next: a short, prioritized list of the one to three most important improvements or corrections for the coming quarter, because a review that produces no concrete next actions is just a status meeting, and the value is in the deliberate, bounded commitment to fix the few things that matter most before the next review.

That is the whole protocol, and its power is in its ordinariness: it is not a clever framework but a disciplined, time-boxed habit that catches drift before it becomes a gap, holds every quarter because it is short, and always checks the most important thing first. We facilitate it because an outside facilitator keeps it honest and on-agenda, but the firm makes every decision and owns every conclusion, and any legal judgment, about a matter, a deadline, a risk, is entirely the attorney's; the protocol organizes the conversation and makes sure nothing important is skipped. Run it yourself or run it with us, but run it, because the alternative, systems installed once and never reviewed, is how good operations quietly decay, and the whole point of building systems is that they keep working, which they only do if someone checks, on a rhythm, that they still are. It connects directly to the ongoing partnership described in the Firm OS overview.

Where to go next

• The Operations Report

  The ongoing reporting behind it.

• The Deadline Audit

  The risk segment, in depth.

• The Owner's Scorecard

  The pipeline segment's numbers.

• The Firm OS

  The install the review keeps alive.

Frequently asked questions