Client Updates Shouldn’t Depend on You Remembering

Ask a client what it’s like to work with your firm and they won’t describe your legal strategy. They’ll describe the waiting. And if the only thing that breaks the waiting is the owner remembering to follow up, then silence isn’t an accident in your client experience — it’s the default you shipped.

Nothing is wrong with the case. The petition is filed, the agency is processing, the matter is exactly where it should be. But the client doesn’t know that. All the client knows is that they signed, they paid, and the firm went quiet. So they call. And the call lands on the one person whose calendar can least absorb it: you.

The fix isn’t a better memory or a guiltier conscience. It’s designing the stage itself so the update goes out whether or not anyone remembers it.

An update that depends on memory is a promise your firm breaks by default.

Law Firm Architects · Client Experience Principle

01Silence is what the client actually receives

The longest stage in most matters is also the quietest: Pending and Monitoring. The work is done, the waiting is structural, and there is nothing new to report. Firms read that as “no reason to reach out.” Clients read it as abandonment.

That gap has a real cost, and it compounds. Every week of silence raises the odds of an anxious inbound call, and every inbound call is an interruption the firm never scheduled. You end up paying for the update twice — once in the client’s eroded trust, and again in the owner’s fractured afternoon.

• “Any news?” calls cluster in the stages where the firm designed no touchpoint.
• Each unprompted status call routes to the owner, because nobody else was named.
• The clients who get updates are the ones who complain, not the ones who wait politely.
• Reviews and referrals track how informed the client felt, not how the matter resolved.

02Memory is not a communication system

When updates run on recall, the firm communicates in exactly one pattern: bursts of attention after guilt, followed by long stretches of nothing. The clients you thought about this week hear from you. The rest don’t. That isn’t a cadence — it’s a lottery, and your most patient clients hold the losing tickets.

The tell is easy to spot. If your team ever says “we should probably touch base with the Hendersons,” the update is running on memory. A designed update never occurs to anyone. It fires.

03Build the update into the stage

Treat the client update like any other beat in your operating system. Inside Pending and Monitoring — and any stage that runs longer than two weeks — define three fields and stop relying on conscience:

Owner. One role — not a name, and not the attorney by default — is accountable for the update going out. A case manager or paralegal can own a status touchpoint; it requires zero legal judgment.

Cadence. A fixed interval the client is told about at onboarding: “You’ll hear from us every two weeks while the agency processes, even if nothing has changed.” The no-news update is the one that builds the most trust, because it proves the system is watching.

Trigger. The stage itself starts the clock. Case enters Pending and Monitoring → the cadence begins → the system prompts the owner — or sends the templated update itself — until the stage exits. Nobody decides to remember. The stage decides.

04Start with one stage this week

You don’t need a client-experience overhaul. Pick the single stage where your clients wait the longest. Write one templated update for it, name the role that sends it, set the interval, and wire the stage entry to start the clock. From that day forward, every client in that stage hears from your firm on schedule — forever — and you never think about it again.

That’s the quiet test of a designed firm: the client feels constantly attended to, and nobody at the firm is spending attention to do it. The system remembers, so you don’t have to.