Jump to section
Delays happen in every file. The registry is backed up. The other side is slow producing disclosure. A judge's decision is reserved longer than anyone expected. These are ordinary events in legal practice, and your client almost certainly understands that the legal system moves at its own pace. What they are much less able to tolerate is finding out about the delay from you three weeks after you knew.
How you explain an unavoidable delay determines whether a client stays confident in you or starts pulling their trust back. Done poorly, a delay explanation becomes confirmation of the fear they were managing: that they are not a priority, that things are slipping, that they should have hired someone else. Done well, it is proof of exactly the opposite. Here is what the difference looks like in practice.
Tell Them Before They Ask
The single most important thing you can do with a delay is communicate it before the client notices it. The moment you know the registry timeline has blown out, or that the other side will not deliver documents on time, or that a proceeding has been adjourned, that is when the client message goes out. Not after you have figured out the full plan, not at the end of the week, not "when you have a moment." Today.
Clients who hear about delays before they ask tend to absorb them as part of the normal rhythm of legal work. Clients who discover delays by asking, or by receiving paperwork from the court without warning, absorb them as evidence that you are not watching their file. The factual content of the message is the same. The emotional context is completely different. Being first with the bad news is one of the most powerful things you can do for a client relationship, and it costs you only the courage to send the message promptly.
If you are already running a regular update cadence, the delay notification fits naturally into that rhythm. A client who already hears from you weekly experiences a delay announcement as a variation in the ongoing story, not as a sudden rupture.
Tip. Write the delay message the moment you learn the news, even if you only send a brief acknowledgement while you work out the full picture. "I have just learned that X has happened and I am working out what it means for your timeline. I will write to you more fully by end of day Thursday" is infinitely better than silence for three days while you plan.
What a Delay Message Should and Should Not Do
A good delay explanation has four parts, and they go in a specific order. The structure matters because the parts that reassure the client belong at the top, not buried after procedural detail they cannot follow.
- Name the delay plainly. Say what has happened in one sentence. No softening, no jargon, no passive voice. "The court has adjourned your motion from March 14 to April 28" is clear. "There has been a scheduling issue affecting our anticipated timeline" is not.
- Explain why, briefly. You do not need a full account, just enough to make the cause feel external and identifiable. "The registry is working through a backlog following the holiday period" or "the other side has requested additional time to produce the documents" tells the client this is a system problem or an opposing party problem, not a firm problem.
- Say what happens next. Every delay message needs a new timeline, even if that timeline is provisional. "We now expect to receive their materials by the end of February, at which point I will write to you with the next steps" is a concrete anchor. A message that ends with uncertainty leaves the client in the same position they were in before they read it.
- Confirm what you need from them. Usually it is nothing. Say that explicitly. "There is nothing you need to do. I am watching the new timeline closely and will be in touch immediately if anything changes." If there is something they need to do, name it clearly and give the deadline.
What clients most want to know when a delay happens
What a Delay Message Should Not Do
Equally important is what to leave out. A delay explanation should not over-apologize. One genuine acknowledgement of the inconvenience is appropriate. Repeated apologies, or language that catastrophizes the delay, make it sound worse than it is and invite the client to feel proportionally worse about it. Say you are sorry the timeline has moved, then move on to what happens next.
It should also not project blame onto the other party in language that sounds inflammatory. "The other side is being entirely unreasonable and we expect to have to bring a motion to compel" might be accurate, but framing it that way in a client email escalates their anxiety without giving them anything useful. Say what happened, name who caused the delay factually, and leave the characterization for your legal strategy.
Do not make promises you cannot keep to soften the blow. "I expect this will only push us back by a week" is comforting if true and corrosive if the week becomes a month. A conservative estimate, given honestly, is always better than an optimistic one that does not hold. Clients can adjust to realistic bad news. They struggle to recover trust when the realistic news arrives after the optimistic version has already failed.
The Phone Call Versus the Email
For most routine delays, a clear, well-written email is the right medium. It gives the client a record they can re-read, it does not require you both to be available at the same moment, and it avoids the live conversation becoming more fraught than the news warrants. For significant delays, ones that change the matter materially or that the client will experience as a serious blow, a phone call is the right first move.
A phone call says: this was important enough that I called you rather than sent an email. It gives the client a chance to react, ask questions, and hear your voice, which carries reassurance that written text cannot. After the call, follow up with an email that summarizes what you discussed, the new timeline, and any next steps. The follow-up email is the record. The call is the relationship.
Clients who are already anxious or who have a history of feeling uninformed on the file should almost always get a call first. If you are not sure, default to the call. The time it takes is repaid many times over in the goodwill and the questions you avoid later. This is directly connected to the broader skill of explaining next steps in a way that calms rather than unsettles.
Note. After a significant delay call, always send a follow-up email that same day. "As we discussed this afternoon" and a brief summary gives the client a written anchor for what was said and protects you from a later dispute about what was communicated.
Rebuilding Momentum After a Disruption
A delay well-explained does not end the matter; it creates a brief gap in momentum that needs to be consciously restarted. After the delay lands, increase your update frequency slightly for a week or two. Not because anything is happening differently, but because the client is recalibrating their timeline and their sense of control. A couple of short check-ins during that period confirm that the file is still active and that the delay has not caused you to disengage.
The clients who later say a delay was handled well are almost never the ones who were told there was no delay. They are the ones who were told immediately, told honestly, given a clear new timeline, and then heard from regularly until the file was back in stride. That is the whole recipe: early, plain, structured, and followed through.
For the rest of what goes into a well-managed client relationship, the Client Experience archive covers everything from the first week through to closing the file well. Delays are just one chapter in a long story, and how you handle them shapes whether the client tells that story as a good one. If you are building or refining how your firm manages client communications, A1 CMS keeps your matter communications, deadlines, and client contacts in one organized place.
