Spaces

Delay and change notices for software and IT firms

These delay notices help a software or IT firm tell clients clearly about a slipped release, a longer fix or a change in scope. Fill in the details and copy a message that keeps trust.

Runs in your browser. Nothing you enter is sent anywhere or saved.

Before you start

Software projects slip. A third-party service changes, a bug is deeper than expected, a key engineer is ill. Clients can forgive almost any of this. What they find hard to forgive is learning about it late, or from someone else. A calm, early notice is the cheapest way to keep a good relationship.

Fill in the boxes, pick the notice that matches the situation, and edit it so it sounds like you. These are for clients who are already working with you or who asked to be told. Each notice says what changed, why, and what happens next.

Release delayed

A quick note from [business]. [item] will now be ready [newdate], a little later than planned. We would rather deliver it properly than rush it. We will update you here if anything changes again.

Fix taking longer than expected

An update on the fault with [item]. It is deeper than we first thought. Our engineers are still working on it, and our best current estimate is [newdate]. We will tell you if that moves.

Waiting on the client

A friendly note from [business]. Work on [item] is paused until we receive what we asked for. Once we have it, we can aim for [newdate]. If it helps, we can talk it through.

Scope has changed

Thanks for the new request. Adding it changes [item], and so the date moves to [newdate]. A person at [business] will confirm any change to the price before we go ahead.

Third-party service problem

A heads up. A service that [item] depends on is having problems outside our control. We are watching it closely, and expect to resume by [newdate]. We will write again as soon as we know more.

Say it early, say it plainly

Clients hear bad news better when it arrives early and in plain words. A notice that explains why, gives a new date and says when the next update will come feels like control, not excuse-making.

Avoid technical fog. The client at {business} does not need to know which library failed, only what it means for them and what you are doing.

Do not promise a new date you cannot hold

A second delay is much worse than the first. Be careful.

  • Add a little slack to the new date, rather than the best case.
  • Say "our best estimate" if the date is not firm.
  • Agree any change in price or scope with a person first.
  • Set a time for your next update and keep it.

FAQ

Who should send a delay notice?

The agent can send a prepared notice when a person has confirmed the facts. The date, and any change to price or scope, should always come from someone who knows the project.

Should we tell a client about a delay we might still recover from?

Usually yes, briefly. A short heads up that the schedule is at risk is far better than silence followed by a late surprise.

How do we handle a client who is upset about the delay?

Acknowledge it plainly, avoid excuses and offer a call with someone senior. A person should handle any talk of credits or contract terms.

More free tools for software and tech support firms

Read the guide: Answer client messages at your software and IT firm, from outages to scoping.