The Handoff Protocol

The work inside your stages is probably fine. Intake gets done. Prep gets done. The filing goes out on time. What kills the case is the space between stages — the silent stretch where a finished piece of work sits on someone’s desk, complete, correct, and going nowhere, because nobody designed how it travels to the next pair of hands.

Here is the default handoff at most firms: the paralegal finishes the prep, mentions it in a hallway or a Slack ping — or doesn’t — and assumes the next person has it. The next person doesn’t know it’s theirs. Three days later the owner asks “where are we on Martinez?” and restarts the physics by hand. The stage worked. The transition failed. And the owner paid for it.

A handoff that isn’t confirmed isn’t a handoff. It’s a hope.

Law Firm Architects · The Delegation Machine

01The gap is a design surface

Firms that get serious about operations design their stages — entry triggers, owners, exit conditions — and then leave the space between stages as dead air. That’s backwards. The transition is not the absence of work; it is a unit of work with its own failure modes. Every time a case crosses from one stage to the next, information has to move, ownership has to move, and momentum has to survive the trip. None of that happens by default. It happens by design or it happens by luck.

Treat the handoff as a designed object — a protocol, not a courtesy — and the gap stops being where cases go to stall.

02The four fields of a designed handoff

A designed handoff documents four things. Not a binder. Four fields, written once per transition, that answer every question a handoff can raise.

• What information moves — the exact payload the next stage needs, not “the file.”
• In what format — the checklist, the summary, the packet. Same shape every time.
• To which role — a named role receives it, not whoever seems free that day.
• How the sender knows it was received — the confirmation that closes the loop and releases the sender.

The fourth field is the one nobody writes and everybody pays for. Without confirmation, every sender is still half-holding the work, every receiver might not know they have it, and the owner is the only person who can tell the difference — by asking, case by case, forever.

03Default vs. designed

Put the two states side by side and the hallway handoff stops looking casual and starts looking expensive.

04The owner becomes the exception handler

Here is what the protocol actually buys you. When every transition has completion criteria built in, a case that is moving needs nobody’s attention. The sender finishes, packages, passes, and gets confirmation. The receiver starts because the trigger fired, not because someone remembered. The system is quiet — and quiet means working.

The owner’s job changes shape. Instead of sweeping every case for stalls, you get pulled in only when a handoff genuinely breaks — a confirmation that never came, a payload that arrived incomplete. That is a design decision: the escalation path is part of the protocol, and it fires on exceptions, not on anxiety.

Map your highest-volume case type this week and count the transitions. Each one is either a designed handoff or an open bet that somebody notices. Write the four fields for the worst gap first — the one that generates the most “where are we on this?” — and watch that question disappear from your day. The follow-up loop isn’t a personality trait of your firm. It’s a tax charged by undesigned transitions, and the protocol is how you stop paying it.