How to Write the Delay Update Nobody Wants to Send

# How to Write the Delay Update Nobody Wants to Send

The factory email arrived three weeks ago. You read it, felt sick, and told yourself you would post an update once you had something concrete to say.

You still do not have anything concrete. The comments are starting. Someone has used the word "scam", which is wildly unfair and has nevertheless been read by everyone.

Here is the thing nobody tells you before your first campaign: the delay is not what loses backers. The silence is. People who buy unfinished products already know that unfinished products run late. What they cannot tolerate is not knowing, because not knowing is indistinguishable from being ignored, and being ignored is indistinguishable from being cheated.

So the update you are dreading is the one that fixes most of this. Below is the structure we use.

Post before you have the answer

The instinct is to wait until you can deliver good news, or at least certainty. That instinct is wrong and it is expensive.

A backer who hears "we have hit a problem, we do not yet know how long, we will confirm by the 20th" on the day you learn it has been treated as an adult. A backer who hears nothing for six weeks and then gets a polished explanation has learned that you go quiet when things go wrong — which is the single most damaging thing they can learn about you, because every future silence will now be read as bad news.

You do not need a solution to post an update. You need to say what you know, what you do not, and when you will know more.

The six parts

Every delay notice we write has these six, in this order. It is deliberately unglamorous.

1. Say it in the first two lines. What is late, and by how much. No preamble, no "we have some news to share", no paragraph of gratitude first. If someone reads only the first sentence — and most will — they should already know what happened.

If you do not know the length yet, say that in those same two lines: "We have hit a delay in moulding. We do not know yet how long it will add; we will confirm by 20 December."

2. The real reason, without blaming anyone. One short paragraph. What actually happened. Not the factory's fault, not the shipping company's fault, not a supply-chain abstraction. Blaming your supplier reads as blaming someone the backer cannot see, and it raises the obvious question of who chose them.

3. The new date, and where it came from. This is the part that separates a credible update from a hopeful one. Not "we now expect March" but "the factory confirmed the revised mould date on 3 December, which puts shipping in March".

A date with a source behind it can be believed. A date with nothing behind it is a guess, and backers have seen enough guesses to recognise one. If you do not have a confirmed date, do not invent one — say when you will confirm, and then confirm on that day even if the answer is "still waiting".

4. What you are doing about it. Concretely. Flying to the factory, qualifying a second supplier, splitting the shipment so one region goes early. This is where you show the problem has your attention rather than your apologies.

5. What they can do. Where to ask questions, and how fast you reply. If there is a refund route, state it plainly; if there is not, do not imply one.

6. Thanks — short. No grovelling, no hype about how amazing the product will be when it finally arrives. One or two sentences. Over-apologising reads as performance, and a sudden burst of enthusiasm after bad news reads as deflection.

A skeleton you can fill in

Subject: Production delay — new shipping window, and why Our shipping has moved from January to March. Here is what happened and what we are doing. During the final tooling run, [what went wrong, in one or two plain sentences]. The factory confirmed the revised schedule on [date]. That puts production finishing in [month] and shipping beginning in [month]. This date comes from [the factory's confirmation / the forwarder's booking], not an estimate on our side. What we are doing: [the specific actions]. If you have questions, [contact], and we answer within [timeframe]. [Refund position, only if you have one.] Thank you for your patience. The next update will be on [date], whether or not there is news by then.

That last line matters more than it looks. A promised next update converts an open-ended wait into a defined one, and it is the cheapest trust you will ever buy. Then keep it, even when the update is "nothing has changed".

What actually triggers refund requests

From the delay notices we have written and the comment threads that followed them, the triggers are consistent and almost none of them is the delay itself.

• Silence. The longest gaps produce the most refund requests. Every week without an update converts patient people into worried ones.
• No new date, and no date for a date. Open-ended waits feel infinite. "We will confirm by the 20th" ends that.
• A date that slips again with no warning. One slip is production. Two slips with no notice in between is a pattern, and that is when people stop believing the third date.
• Finding out somewhere else first. A backer who learns about your problem from a comment thread, a Reddit post or another backer has been told that you were not going to tell them.
• Vagueness. "Logistics challenges", "supply chain issues", "circumstances beyond our control". Those phrases are what people write when they are managing a reader rather than informing one, and readers know it.
• Blame. Pointing at the factory invites the reply you do not want.
• A tone that does not match the news. Exclamation marks over bad news. A delay buried under a stretch-goal announcement. Anything that looks like the news is being hidden gets found, and then the hiding is the story.

Notice what is not on that list: the delay, its length, and admitting you got something wrong.

How often, and where

While production runs, post every two to four weeks even when nothing has happened. "We are still waiting on the second sample; the factory expects it on the 14th" is a complete update and takes four minutes. Regular dull updates are what make an eventual bad update survivable, because by then you have established that you post either way.

Where you post depends on the market:

• Kickstarter and Indiegogo. The Updates tab, and email the same text. Do not make people click through to find out whether it is bad.
• Zeczec (Taiwan). The update, in Traditional Chinese, and the LINE group if the campaign has one. Taiwanese backers ask direct questions and expect direct answers, quickly. A reply that reads as evasive will be quoted back at you.
• Makuake (Japan). 活動レポート, in Japanese, with more detail than you would give elsewhere and a precise explanation of the cause. Japanese backers treat a delivery date as a commitment rather than an estimate, so the explanation and the new date carry more weight here than anywhere else. This is also the market where a translated-sounding apology does the most damage.

If you cannot write the update in the market's language yourself, get it written by someone who can before you post it, not after someone complains.

Where this goes wrong

Waiting for certainty. Covered above, and it is the one everybody does.

Writing it when you are angry at the factory. Write it, leave it overnight, read it again in the morning. The sentence you most want to keep is usually the one to cut.

Answering only the polite comments. The angry ones are read by far more people. They are also where a calm, factual reply does the most work. If a comment is abusive or threatening, do not engage publicly — take it to email.

Promising something you have not confirmed. A free add-on offered in a moment of guilt becomes a second obligation on top of the one you are already late on.

Hiding the delay inside good news. It gets found, and then you have two problems.

Letting it drift into a personal apology. Backers want the product and the facts. Long emotional passages shift the weight of the problem onto them.

FAQ

How soon should I tell backers about a delay? As soon as you know there is one, even if you do not know its size. The first update can be three sentences and a date by which you will know more.

What if I have no new date at all? Then the update is: what went wrong, that you do not have a date, when you will have one, and what you are doing in the meantime. Commit to that second date and keep it.

Should I offer refunds? That is a business decision and it depends on your platform, your terms and your cash position — so decide it before you write, not inside the update in a moment of guilt. Whatever you decide, say it plainly. An unclear refund position generates more messages than a firm no.

How do I handle someone calling it a scam in the comments? Reply once, publicly, calmly, with facts and no defensiveness: what happened, the current date, where the date comes from. You are not writing for that person. You are writing for the hundred people reading the thread.

Can I just email instead of posting an update? Post publicly and email. A public update is visible to people considering a late pledge and to anyone checking whether you are still there. A delay handled well in public is one of the few things that persuades a stranger you are trustworthy.

Does a delay hurt my next campaign? A delay handled badly does. Backers remember the handling far longer than the wait, and the update history on your old campaign stays public forever — which is exactly why the boring two-week updates are worth the four minutes.

What to do this week

If you are late and have not said so, write the six parts above, leave it overnight, and post it tomorrow. If you are not late yet, put a recurring two-week reminder in your calendar for the whole production period and start the habit before you need it.

PrelaunchGo keeps your backers, their orders and your updates in one place after the campaign, so the people you need to tell are the people you can actually reach. See how it works.

Related: what a pledge manager does, for the other half of the post-campaign job.