A Stage Isn’t a Label. It’s a Control System.

Open your case management system and read the stage names. Discovery. Drafting. Filed. They look like a system. They aren’t one. They’re labels — column headers over a pile of work that still runs on one person’s judgment. Usually yours.

Here’s the test: when a case sits in a stage, does your team know what to do without asking you? Do they know when the work starts, who owns it, and what has to be true before the case moves on? If the answer to any of those is “they check with me,” you don’t have stages. You have labels with your phone number attached.

When the trigger, the actions, and the exit are defined, the stage runs itself. When they aren’t, the stage runs on you.

Law Firm Architects · Delegation Machine, Lesson 3

01A name on a board is not a system

Renaming columns feels like process design. It isn’t. A label answers one question — where is this case? — and leaves the three questions that actually move work unanswered: when does this stage begin, what happens inside it, and when is it allowed to end. Those answers live somewhere. In an undesigned firm, they live in the owner’s head, which means every case in every stage is one interruption away from a hallway consult.

That’s why delegation keeps failing. You hand off the work, but you keep the answers — so the work comes back to you wearing a question mark.

02The three parts of a control system

A designed stage is a control system with exactly three parts. Not a task list. Not a checklist taped to a monitor. Three engineered components:

• Entry trigger. The specific event that moves a case into the stage. Not “when someone gets to it” — a defined signal: retainer signed, documents received, filing confirmed. The stage starts itself.
• Stage actions. What happens inside the stage, owned by a role — not by whoever is least busy, and not by you. The role knows the actions because they were designed, not remembered.
• Exit condition. The statement of what must be true before the case moves on. Not a feeling of doneness. A condition anyone can verify without summoning the owner.

Define all three and something structural changes: the stage stops being a place where work sits and becomes a machine that work moves through. Your staff stop asking “what’s next” because the stage already answered.

03Ownership is the output

The point of the three parts isn’t tidiness. It’s ownership. A role can only own a stage end to end when the stage has ends — a defined way in and a defined way out. Give your paralegal a label and they can only ever be your assistant inside it. Give them a control system and they can run it, close it, and hand it off without you in the loop.

This is the same spine we build in Tracks, Stages & Beats: structure isn’t bureaucracy, it’s the thing that makes delegation physically possible.

04Design one stage this week

Don’t redesign the firm. Pick one stage in your highest-volume case type — the one that generates the most questions aimed at you — and write down its three parts. What event moves a case in? What actions happen inside, and which role owns them? What must be true before it leaves?

One page. One stage. The first time a case enters, runs, and exits that stage without a single question reaching your desk, you’ll understand the difference between naming the work and designing it — and you won’t go back to labels.