Tracks, Stages & Beats

Ask ten people at a law firm to describe how a case actually moves, and you’ll get ten different maps. That’s not a people problem. It’s the sound a firm makes when it has no spine.

Every matter in your firm travels a path. The problem is that the path is invisible — held in fragments across a paralegal’s habits, an associate’s inbox, and the founder’s memory. When the structure is missing, the work still happens, but it happens differently every time, with quality that swings depending on who caught it. The fix is not a thicker SOP binder. It’s a spine: three layers that name the work so clearly that the next step is never a question.

We call those layers tracks, stages, and beats. Get them right and the firm stops improvising. Here’s what each one is and why the order matters.

A firm without a spine doesn’t have a process. It has a habit that mostly works.

Law Firm Architects · Operating Philosophy

01Tracks — the lanes

A track is a lane a matter can travel down — a practice area or case type that genuinely runs differently from the others. An uncontested estate plan and a litigated guardianship are not the same animal, and pretending they share one workflow is how firms end up with a process that fits nothing well.

Most firms need fewer tracks than they think. The test is simple: if two case types move through meaningfully different steps, they’re different tracks. If they only differ in the details of a document, they’re the same track with different beats. Naming the tracks first keeps you from designing one bloated mega-process that tries to cover everything and serves no one.

02Stages — the sequence

Inside every track, a matter moves through a sequence of stages: intake, build, file, advance, close. A stage is not a to-do list. It’s a phase with a clear entry, a clear exit, and a single answer to the question “whose job is it right now?”

Stages are where ownership lives. The moment a matter crosses from one stage to the next, accountability changes hands — on purpose, with a trigger, not because someone happened to remember. When every stage has an owner and a definition of done, the handoff stops being a verbal favor and becomes part of the design.

• Entry trigger: the event that pulls a matter into the stage.
• Owner: the one role accountable while the matter sits here.
• Definition of done: the condition that lets it move forward.
• Exit trigger: what fires the handoff to the next stage.

03Beats — the actions

Beats are the individual actions inside a stage: the engagement letter, the filing, the status call, the calendar entry. This is the most granular layer — and the only one where automation and delegation actually live.

Here’s the part most firms get backwards: they automate beats before they’ve designed the tracks and stages above them. That’s how you end up with a Zap that fires a flawless email at exactly the wrong moment. Beats are the last layer you design, not the first. Once the lane and the sequence are clear, the beats almost write themselves.

04Why the order is the whole game

The spine works because each layer constrains the one beneath it. Tracks decide which stages exist. Stages decide which beats belong. When you build in that order, every action has an obvious home and an obvious owner. When you build out of order — starting with beats, the way most “let’s automate something” projects do — you get a pile of tasks with no structure to hold them.

05Build your first spine this week

You don’t need a full reset to feel the shift. Take your highest-volume case type — that’s one track. On a single page, write the stages it moves through from intake to close. Under each stage, list the beats. Name an owner for every stage. That one map is usually the first time your team sees the entire path at once.

The moment the spine is visible, the conversation changes. People stop asking “what do I do next?” and start asking “is this the right next step?” — which is the only question a designed firm should ever have to answer.