Telling a client early that a launch is at risk is the right instinct. But an early message that only says “we may be late” hands the problem to the client without the information they need to act on it. The useful update is the one they can make a decision from.
The risk is known before the deadline
Most launch slips are not surprises to the people doing the work. Someone usually sees it coming days before the date: an integration that is not behaving, a supplier file that has not arrived, a review that keeps getting pushed. The question is not whether the risk is known, but how long it stays inside the delivery team before the client hears about it.
There is a natural pull to wait. The team hopes to recover the time, nobody wants to raise an alarm that turns out to be unnecessary, and an honest “we might miss it” feels like a failure in itself. Waiting rarely helps. The later the warning, the fewer options are left, and the client loses the time they needed to adjust their own plans.
An illustrative situation
To make this concrete, here is an illustrative situation rather than a real engagement. A retailer plans to launch a new category on a Friday. On Tuesday, the delivery team finds that a large share of the new products are missing an attribute the storefront filters rely on, and the supplier who owns that data cannot correct it until the following week.
The team now knows the launch is at risk. What they say next, and when, decides whether the client can still choose a sensible path.
What the client has to manage internally
A launch date is rarely only a technical milestone. For the client, it is connected to work that other people are planning around: campaigns booked to go live, emails scheduled, store teams briefed, and senior colleagues expecting to hear that it happened.
When a date moves, the client has to manage that internally, often with people who were never close to the work. An update that only says “there is a delay” leaves them to work out the consequences and the alternatives on their own, under time pressure, and to explain a decision nobody has framed for them.
- Commitments in motion Campaigns, promotions and communications that depend on the launch date.
- People who need to hear first Stakeholders who will ask what happened and what is being done about it.
- Their own approvals Decisions the client cannot make alone, and that take time to get.
An update that can be forwarded
The most useful test of a risk update is whether the client could forward it to their own leadership without rewriting it. That means it has to stand on its own, in plain language, and answer the questions they will be asked.
- What has happened The issue, in one or two sentences, without technical detail the reader does not need.
- What it affects The launch date and anything else that depends on it, such as campaigns or other channels.
- The options Usually more than one: launch on time with a reduced scope, move the date, or launch with a known limitation and a fix to follow.
- Our recommendation Which option we would choose and why, so the client is not left to weigh everything alone.
- The decision needed What we need from the client, from whom, and by when, for the recommended option to still be possible.
In the illustrative situation above, that might mean offering to launch on Friday with only the products whose data is complete, moving the remaining products into the next release once the supplier has corrected them, and asking the client to confirm by Wednesday so the reduced range can be checked in time.
Ownership after the warning
Sending the update is not the end of the responsibility. The warning should come with a named owner, a time for the next update, and a clear point at which the plan will be confirmed or changed again.
Once the client has decided, the delivery team owns making that option work: tracking the open items, flagging early if the new plan is also at risk, and closing the loop when the launch, or the reduced launch, goes live. The aim is that nobody has to chase for news, and that the client hears about the next risk as early as they heard about this one.
Clear scope, named owners and agreed escalation paths do not prevent every problem. They make sure that when one appears, the people who have to decide get what they need while there are still choices to make.
See how we agree scope, owners and escalation paths before work begins.
How we work
