The Field That Lets Staff Close Without You

Your team can’t close a stage because nobody ever told them what closed means. So they do the safe thing. They ask you. Every case, every stage, the same quiet checkpoint routes back to your desk, not because the work is hard, but because the finish line was never drawn.

That checkpoint feels like management. It isn’t. It’s a design gap wearing a manager’s clothes. And it has a fix that fits on one line.

01The field nobody fills in

Open any firm’s case board and you’ll find stage names. Intake. Active. Pending. Review. Closed. You’ll usually find owners too, at least the informal kind. What you’ll almost never find is the one field that actually makes a stage function: the exit condition.

An exit condition is a written statement of exactly what must be true before a case leaves a stage. Not a vibe. Not a hunch. A test. Without it, “done” is a judgment call, and in most firms only one person is trusted to make that call. You.

A stage without an exit condition is a door with no latch. It never really closes. It just waits for you to walk over and shut it.

Law Firm Architects · Process Design

02Why the case always routes back to you

When a stage has no exit condition, your staff can’t tell the difference between almost done and done. So they stop at almost, and they escalate. This is the follow-up loop, and it is the single most expensive habit in an undesigned firm. You aren’t managing the case. You’re standing in for a field that was never filled in.

Here’s the tell. If your team routinely finishes work and then waits, you don’t have a motivation problem or a talent problem. You have a missing field. The case is ready to move, and the only thing blocking it is that no one wrote down what ready means.

• Work is finished, but the case sits, because no one is sure it’s allowed to move.
• Two people run the same stage to two different finish lines.
• Cases stall in a stage that nobody agreed was actually complete.
• Every handoff turns into a question pointed straight at the owner.

03What a real exit condition looks like

A real exit condition is testable, binary, and owned. Anyone on the team can read it, look at the matter, and answer yes or no without interpreting your preferences. “All medical records requested and receipt confirmed in the system.” “Signed engagement letter uploaded and initial payment cleared.” Those are conditions. “Intake looks good” is not.

The test is simple: could a competent person who is not you decide whether the stage is complete? If the answer depends on your opinion, you haven’t written an exit condition. You’ve written another reason to be interrupted.

04Default vs. Designed

The shift is small on paper and enormous in practice. One field, written once per stage, changes who the firm depends on.

05Write one this week

You don’t need a new platform to fix this. You need one sentence per stage. Take your highest-volume case type and walk it stage by stage. For each one, write the single condition that must be true to leave it. Make it binary. Make it observable in whatever system you already use.

Then hand the list to your team and watch how many questions stop arriving at your desk. This is the highest-leverage hour in your month. Nothing else returns owner time this fast, because you’re not adding a tool or a person. You’re removing yourself from a decision that never needed you in the first place.