top of page

How to explain a delay to a client with clarity

Nov 5
9 min read

The deadline is approaching, and the work will not be ready. You need to explain a delay to a client, but you do not yet have every answer. Waiting can feel safer than delivering uncomfortable news. It also leaves the client planning around a date that may no longer be realistic.

A useful update gives the client something to work with: what changed, how it affects their plans, what you are doing, and when they will hear from you again. The goal is a shared understanding of the situation and the next decision.

You can be direct, considerate, and accountable without pretending to control every dependency.
Woman in a rust-colored blazer speaking toward an open laptop at a desk with a notebook and glass of water.
Prepare the facts and the next update time before starting a client conversation.

How to explain a delay to a client clearly

Before opening your email or joining a call, separate the facts from your assumptions. A project may be at risk without a revised delivery date being confirmed. Say that plainly. An early warning and a firm revised commitment serve different purposes, and the client needs to know which one you are providing.

Prepare five pieces of information. Keep each brief enough to say aloud without reading a script.

  1. The change: Name the deliverable and the date affected.

  2. The impact: Explain what the change means for the client's next step.

  3. The cause: Share the relevant, verified reason in plain language.

  4. The response: Describe the action underway and any realistic options.

  5. The next contact: Give an exact time for an update, even if the delivery date is still uncertain.

For example, imagine a project coordinator responsible for a product packaging proof. The final proof was due Tuesday, but a required quality check has identified a problem with the insert. This is an invented practice scenario, not a SUAS client story. The coordinator needs to explain the effect on the proof, rather than narrate every internal conversation.

An opening could be: "The packaging proof will not be ready Tuesday as planned. The insert did not pass our quality check, and we are checking a revised version. I know your team needs the proof before approving the launch photos. I will confirm the earliest reliable delivery date by 2 p.m. tomorrow."

Prepare a message the client can use

Lead with the change, then acknowledge the effect

Put the important news in the first two sentences. A long introduction about how busy everyone has been makes the client search for the actual update. Name the affected work and acknowledge the consequence you know about. If the consequence is unclear, ask one focused question rather than assume the delay is minor.

Try: "Does this affect a fixed review meeting or another deadline on your side?" The answer may change which option is useful. An interim proof might help an internal discussion while still being unsuitable for final approval. Explain that limitation before offering it.

Use ownership language without assigning blame

State what your team owns: the communication, the investigation, or the next action. Avoid promising control over a supplier, approval process, or colleague's unfinished work. "I am checking the revised proof with production" is clearer than "They are holding everything up." Keep confidential internal details out of the explanation.

One specific apology is usually enough: "I am sorry we did not flag the risk sooner." Then move to the response. Repeated apologies can take attention away from the information the client needs.

Accountability becomes visible when your next action matches what you said you would do.

Offer options with honest limits

An option is useful when the client understands what it does and does not solve. Instead of "We can send something early," explain which part is available, how it can be used, and what remains unfinished. Check feasibility and approval before offering a new commitment.

In the packaging scenario: "We can share the outer sleeve proof tomorrow for your design review. The insert would remain pending, so that version would not be ready for final production approval." If there is no workable alternative, say so. A clear constraint is more useful than a choice that cannot be delivered.

Two adult colleagues discussing a white packaging prototype at a table with a closed laptop and blank paper.
Check the work with colleagues before offering a revised commitment to a client.

Practice before the real conversation

Use a short rehearsal to check whether your message is understandable. Stand Up and Speak's adult public speaking courses describe coach-led practice and feedback for workplace communication, interviews, and presentations. You can also practice the structure below with a colleague before a difficult update.

  1. Write the first two sentences: the change and its immediate effect.

  2. Say the cause in one sentence, using only facts you have confirmed.

  3. Explain the action underway and the next update time.

  4. Ask your practice partner to repeat what they now expect from you.

  5. Revise any wording that led them to expect more than you can promise.

Listen for vague phrases such as "soon," "hopefully," and "we are on it." Replace them with a concrete action or a clear statement of uncertainty. "I will check the test result at noon and update you by 2 p.m." gives the listener a usable expectation. It does not imply the entire project will be complete by then.

For a team exercise, give two colleagues the same fictional delay. Ask each to draft a four-sentence update independently. Compare the promised dates, the stated cause, and the client action requested. Any mismatch shows where the team needs agreement before speaking externally. Keep the exercise focused on clarity rather than polished performance.

Eight questions about communicating a client delay

1. When should I tell the client that a deadline is at risk?

Tell them when you have a credible reason to believe the agreed date may be affected and the information would help them plan. You do not need to wait for complete certainty. Explain the difference between a risk and a confirmed delay so that an early warning does not sound like a final decision.

You might say: "Tuesday's proof is at risk because the revised insert still needs checking. We have not confirmed a new date. I will update you tomorrow by 2 p.m." Before sending, check who is responsible for the client relationship and align internally on the facts. Internal coordination should support a timely update, not become a reason for silence.

2. What should I say when I do not know the revised date?

Avoid filling the gap with a reassuring guess. Explain what you are waiting to learn, who is checking it, and when the client will hear from you.

Separate a confirmed update time from an estimated delivery time. These are two different commitments.

Try: "I cannot confirm the delivery date until the revised insert passes its check. Production is reviewing it tomorrow morning. I will contact you by 2 p.m. with the result and the next step." If your update time arrives without the answer, contact the client anyway. Explain what is still unknown and set the next useful contact point.

3. How much detail should I give about the cause?

Give enough verified detail to explain the effect and support a decision. A client usually needs the relevant reason, not a full account of internal disagreements. Avoid technical shorthand unless you explain what it means for their deliverable.

"The insert failed its fit check" is more useful than "We have a production issue." Follow it with the consequence: "We need to revise it before sending a proof for approval." If the cause is still being investigated, say that. Do not name a root cause, blame a supplier, or share confidential information merely to make the explanation sound complete.

4. What if the delay depends on someone outside my team?

Describe the dependency neutrally, then explain your own next action. The client needs to know how you are managing the situation. "We are waiting for the revised component and have asked for confirmation by noon" gives more direction than "It is out of our hands."

If the client needs to supply something, make the request specific and respectful: "We need your approval of the revised dimensions before the next check can start." Confirm how that affects the timeline. Avoid implying that a new date is guaranteed simply because the missing item arrives. Other steps may still need to happen.

5. Should I use email, a phone call, or a video meeting?

Use the channel that supports the conversation the situation needs. A significant change affecting several decisions may benefit from a call or video meeting where the client can ask questions. A straightforward update may work well in email. Consider the client's usual preferences and the urgency.

For an urgent issue, do not wait several days for an ideal meeting slot. Send the essential facts through the established channel and offer a conversation. After a call, provide a brief written recap of the revised understanding, any decisions, and the next update time. Make it easy for the client to correct a misunderstanding.

6. How do I respond if the client is upset?

Let the client finish explaining the impact before you defend the process. Reflect the concrete concern: "You had arranged a photography session around Tuesday's proof." Acknowledging that disruption does not require agreeing with every accusation or making a promise you cannot keep.

Then return to what can be decided: "The outer sleeve proof is available tomorrow, but the insert is not ready for approval. Would reviewing the sleeve help your team, or do you need the complete proof?" If a request involves compensation, contract changes, or an exception, involve the person authorized to decide. Do not offer terms on the spot simply to end an uncomfortable conversation.

7. What if we already missed the deadline or need to revise it again?

Name the missed commitment directly. "We missed the Tuesday delivery date, and I did not update you before it passed" is clearer than "There has been some confusion." Explain the current position without recycling the same unsupported estimate. If an earlier assumption changed, identify it.

For example: "The revised insert needs another check, so the date I gave yesterday is no longer reliable. I am confirming the remaining steps with production today." Explain how your next commitment will be checked before you make it. A second change calls for more precision about the process and uncertainty, rather than stronger assurances.

8. How can I keep the update from sounding scripted or evasive?

Prepare the facts and the order, then speak in your normal professional voice. Use the client's deliverable and decision in the wording. "Your packaging proof" and "approval for the photo session" are more useful than broad phrases such as "your valued business" or "unforeseen circumstances."

Read your draft aloud once. Remove phrases you would never say in conversation and any sentence that repeats an apology without adding information. Ask a colleague: "What do you think I have promised?" If their answer goes beyond what you intended, revise the wording. A natural delivery still needs accurate boundaries.

Turn the conversation into a useful written recap

After the conversation, record the understanding in a short message. A recap should distinguish decisions already made from options still under review. If the client has not agreed to a revised date, do not write as though they have.

For the fictional packaging project: "Thank you for discussing the proof today. We agreed that your team will review the outer sleeve tomorrow while the insert check continues. The complete proof date remains unconfirmed. I will send the check result and next steps by 2 p.m. tomorrow. Please let me know if this differs from your understanding."

Keep that recap with the project record so the next person responding to the client can see the same commitments. If circumstances change before the promised update, contact the client with the new information. Use the recap as a shared reference, not a substitute for a conversation when a decision needs discussion.

A final check before you send

Review the update from the client's perspective. Can they identify what changed without searching? Is every date labeled as confirmed, estimated, or still unknown? Have you explained the effect on their next step? Have you asked for only the decision or information you actually need?

  • Confirm the facts with the people doing the work.

  • Check that every option is feasible and authorized.

  • Replace vague timing with a specific update commitment.

  • Remove blame, confidential details, and unsupported reassurance.

  • Put the promised follow-up in your calendar and keep it.

Your message does not need to resolve the entire delay in one conversation. It needs to leave the client with an accurate picture and a dependable next point of contact. Clear wording, realistic commitments, and consistent follow-through give both sides a better basis for the next decision.

Related posts


Build a clearer approach with your team

Stand Up and Speak offers executive coaching, team workshops, and ongoing training tailored to organizational goals. Explore the corporate communication programs to discuss how your team wants to communicate more clearly.

Comments


bottom of page