Skip to content
Interface language: English
Imperium / Signal

How to tell a customer about a delay when you do not yet have a new date

Explain a confirmed delay, its effect on the customer and the time of the next update without inventing a completion date.

Article language: English

A woman in a light suit with one hand on a small stone door beside a glowing lamp.
In this article

The hardest delay message often comes when you already know today's deadline will be missed but do not yet know what you can honestly put in its place. The draft says “immediately”, then “tomorrow at the latest”, then “we are doing everything we can”. The customer still does not know whether to cancel their meeting.

You can send useful information before setting a new delivery date. Say what is confirmed, how it affects the recipient and when they will receive the next checked update. Internally, establish who will actually return to the customer at the promised time.

First name what has changed

Imagine a studio preparing product photographs for a new online store. The client expects the complete package on Tuesday. On Monday afternoon the studio discovers a problem with some files and is checking which images can be recovered from available copies. It knows it will not deliver the complete package as planned. It has no basis yet for promising a new date.

The recipient first needs to understand the scope of the change. Is the entire package delayed or selected products? Can confirmed photographs be used already? Are previously delivered materials also affected? If this is not established, say which part is still being checked. A general “delivery is delayed” leaves all interpretation to the client.

Only after defining scope does it make sense to describe action. “We are checking file copies for six products; the remaining photographs are ready to hand over” gives the recipient different planning options from “we are working intensively on a solution”. In this fictional case we do not assume every file can be recovered. The description should distinguish the check being performed from its possible result.

Explain the cause at the level needed to understand the situation. The customer need not hear the whole history of folders and program names. They do need to know whether the missing element affects their intended use. Technical detail helps when it changes their action, allows them to assess scope or explains why a new date cannot yet be confirmed.

The next update time can be set earlier

In GOV.UK Notify's communication on an Excel and CSV file issue, an update on 20 October 2026 identified the affected function, a fix being tested and the time of the next message. It did not present that time as the repair date. This is a historical example of communication; the incident was marked resolved on 21 October.

The photo studio can make a similar distinction: “By 11:00 tomorrow we will report the copy check and the next plan.” This deadline concerns a contact the company can organise. It is not a promise of a finished package. It needs an owner and reminder so the next message does not depend on whether good news happens to arrive.

If the full result remains unknown at 11:00, the client should still receive an update. State what was checked, what remains unknown and the next action. Do not turn the promise into an empty ritual of sending “no change”. Choose a time meaningful to the recipient that allows the company to provide a checked state, even if incomplete.

GitLab's customer-service guidance recommends saying when the next contact will occur on a blocked case and agreeing the rhythm to the recipient's needs. Separately, it warns against promising a fix date solely from an assigned milestone. This is one support team's practice, not a universal response time for every company.

Do not copy somebody else's update frequency. For material needed to launch a store in the morning, one day may matter differently from material planned for next month. Ask about the recipient's nearest action. The company should know which decision needs the message instead of choosing a rhythm solely for its own inbox.

The message should enable the customer to decide

The recipient may be waiting to launch product pages, commission advertising or approve further work. In our example establish whether they need all photographs immediately or can use the ready portion. The company can offer a partial handover but should not assume on its own that this is enough.

An illustrative first message could read:

We will not deliver the complete photo package on Tuesday. We are checking file copies for six products; the rest is ready. By 11:00 tomorrow I will return with the check result and the next plan. Please let me know whether receiving the ready portion would help with the planned store launch.

This is a draft for an invented case. Before using it, check the scope, availability of the ready portion and ability to contact at the stated time. The message does not decide contractual responsibility or other legal consequences of a particular delay. We are concerned here with information needed for further action.

Do not bury the change between apologies and praise for a long relationship. A short acceptance of responsibility for communication may be appropriate, but should not replace content. “I am sorry for the change of plan” works best next to a clear statement of what changes and what comes next. Three paragraphs of regret without scope can further irritate someone who must now move a meeting.

If asked for a new date, answer directly whether it can be confirmed. Do not turn lack of grounds into “probably tomorrow” merely because the conversation is uncomfortable. If giving a forecast, label it as a forecast and explain the condition for checking it. The recipient should distinguish it from an agreed commitment. Also check the team's meaning of forecast confidence (in Polish) before a casual “we will probably make it” becomes the basis of a customer message.

Aeneia conceptual photography

If the customer plans further work after partial handover, agree how available material is labelled. In our studio the package may include photographs ready for use and shots still being checked. The recipient should distinguish them without comparing an email with dozens of file names. Otherwise the information about partial readiness disappears in the delivery method itself.

When the problem's scope changes, show the difference from the previous message. If checking confirms four products are affected rather than six, say which two can now be used. If it reveals a wider scope, disclose that too. An update should help the recipient change their plan based on a new fact instead of leaving them to reconcile two messages alone.

The internal message and external promise must meet

The person contacting the customer needs an up-to-date state from the people doing the work. “It should work” may mean a loose guess, a trial under way or the result of a checked portion. Clarify its meaning before the information goes outside. This is another case of a promise passing between sales and delivery (in Polish).

Establish who will prepare the next update and where they will obtain the facts. If the person leading the matter finishes work earlier, communication must pass to another person together with the time and scope of uncertainty. The customer should not have to explain again why they are waiting. Lack of continuity quickly leads to repeated questions about the same case (in Polish).

Keep channels consistent too. If the website says “materials ready” while the email says a missing portion is being checked, the recipient gets two versions of reality. In a small company, updating a particular view or giving a simple status explanation may suffice. There is no immediate need to build a public incident page for every order.

Internal change communication (in Polish) has a practical role: people handling contact should know the new state and what they can confirm. Informing a manager alone does not guarantee consistent answers at reception, in a form and in a sales conversation. Choose recipients based on who actually participates in the case.

For the next contact time, choose wording clear to both sides. “Tomorrow morning” may mean a different hour to someone waiting for a store launch and a studio starting later. In international work give the applicable time zone. This is not a minor editorial detail if the recipient's next decision depends on the message.

The company should also plan for a missed promised update. If the case owner does not receive a result in time, they should know whom to ask for the state and what they can truthfully communicate. The contact deadline should not disappear along with the hoped-for good news. A recipient can accept that the result is unknown; planning is harder when they must first discover whether the company remembers their case.

Before sending an update, compare its scope with the previous communication. Is the new date for contact or completion? Does “ready” still describe the same portion? Must the recipient confirm anything to use a partial option? A short read catches meaning changes that can appear when several people edit.

Keep an important telephone agreement in the channel used to manage the case too. The recipient may need to pass it to their team, and the company needs a shared basis for the next contact. Do not record the conversation as consent to an option if the customer merely asked for it to be checked. Confirmation should reflect the actual agreement.

Check promises written on the website

Sometimes the site itself creates pressure: “we will respond in an hour”, “ready the next day”, “immediate delivery”. If these statements apply only to some services or conditions, the recipient should understand that before enquiring. Review evidence for B2B offer claims (in Polish) and check which real scope each statement covers.

Aeneia Design can help organise expectations on the website and the route after contact. That includes service descriptions, enquiry acknowledgements and messages telling customers what happens next. Start with the specific difference between what the site announces and what the company can confirm.

A thank-you page after form submission (in Polish) is particularly useful to check. If it promises a response within a stated time, the company should be able to arrange that contact. If it says only that data was received, it should not sound like confirmation that work has begun. Keep the same language later in a delay message.

Look at communications through the eyes of a customer already awaiting a result. Can they find the right contact after the original deadline has passed? Does the acknowledgement explain that a response requires checking the case? If the site still invites them to submit a new sales enquiry, they may describe the whole situation again. Separate these needs so an existing case reaches continued support.

An update does not finish fixing the matter

Once the next plan is established, return to the customer with a specific result: what was checked, what can be delivered and what still needs agreement. If an earlier message was wrong, mark the correction. For a broader mistake, correcting information published by a company (in Polish) offers a useful approach: recipients should recognise what changed and which action the new state concerns.

Meeting the update time alone does not mean the relationship is repaired. The client may have incurred organisational cost or lost the opportunity to use material at the planned time. Repairing a relationship after a service error (in Polish) requires addressing their situation. A good message opens that conversation but does not replace further delivery.

The simplest test of a first message is whether the recipient knows more about their own next move after reading. If they know the affected scope, what is being checked and when the next information will arrive, they can make their own decision. The company still has a delay to resolve. It no longer adds the task of extracting the current state from the company to the customer's work.

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear