Blog / Web management /
How to communicate a delayed website fix clearly
“Is the checkout fixed yet?”
It isn’t. You’re still waiting on the plugin vendor, and your original estimate passed yesterday.
Silence makes this feel worse. A confident guess can make it worse later. What helps is a clear update that tells the other person what’s happening right now.
A delay isn’t automatically a communication failure. It becomes one when people can’t tell what’s affected, who’s on it or when they’ll hear from you next. You don’t need a dramatic incident report for every small fix. You do need an honest, useful update.
Lead with what the person needs to know
Start with the current impact. Is the feature unavailable, slower than normal, or working with a limitation? Say which users or parts of the site are affected, if you know. Don’t say “the website is down” when only one form is failing.
Then split confirmed facts from open questions. You might know a recent change is connected to the problem, without yet knowing whether the cause is the theme, a plugin or an outside service. Say exactly that. People cope with uncertainty much better when you name it than when it’s hidden behind technical-sounding certainty.
Explain the next step in plain language. “I’m checking whether the form submissions reach the email service” is more useful to a site owner than a wall of logs or an unexplained error code. Add technical detail only when it helps them make a decision. When I write these updates, I imagine the client reading it on a phone between meetings. If it doesn’t make sense there, it’s too technical.
Give a time for the next update
A delayed fix may not have a reliable finish time yet. Don’t invent one to make the conversation feel settled. Give a time for the next update instead: after a vendor reply, after a test, or at an agreed time that day.
The next update is in your control even when the repair isn’t. If things change sooner, update them then. If nothing changes, send the promised note anyway and say what’s still the same. Missing update times again and again does more damage than admitting the investigation’s still open.
Be clear about time zones when people work in different places. Working from Nigeria with London clients, I write the actual date and their local time, not “later today”, because “later today” can be tomorrow for someone.
Describe the workaround and its limits
If there’s a safe workaround, explain how to use it and what it doesn’t fix. A temporary manual process might let staff finish an urgent task while the real fix is investigated. Don’t present a workaround as a permanent repair, and don’t ask a site owner to change settings unless the step is safe and understood.
If there’s no reliable workaround, say so. You can still help them choose a next step, like pausing a campaign that sends people to a broken page, or pointing visitors to a contact route that works. Those decisions belong to the people responsible for the business and the site.
Don’t speculate about data loss, security exposure or financial impact. If you don’t know whether data was affected, say it’s being checked and who’ll confirm it.
Keep the update structured
A short message can follow a repeatable shape without sounding scripted:
- What is affected right now?
- What do we know, and what are we still checking?
- What is the next action or workaround?
- When will the next update arrive?
Keep updates in one agreed channel, so nobody’s working from a different version. Log the issue, timeline, decisions and owner in the support record. Never put passwords, personal data or raw customer information in an update.
Choose the right level of detail
A site owner usually needs to know whether to act, not how the server stack fits together. Lead with the practical effect, then offer technical detail if it explains the next step. If a form’s failing, say what’s affected, whether submissions are arriving and what the temporary route is. Don’t bury the answer under logs.
If the fix depends on a third party, explain the dependency without hiding behind it. Say when the request went in, what response is pending and what you can test meanwhile. If there’s no safe check to run in parallel, say that too.
Keep the language calm and specific. “We’re investigating” is too vague on its own. Add the current question and the next checkpoint. Don’t blame anyone until the evidence supports it. If later testing changes the explanation, correct the earlier update plainly.
Close the loop after the fix
When the repair’s done, say what changed and what you tested. Be precise. “The form now submits and the confirmation email arrived in the test inbox” beats “everything’s perfect”. If monitoring or a follow-up check remains, name it and its owner.
Later, look at whether the delay exposed a gap in access, documentation, monitoring or vendor support. The lesson might be to prepare a rollback, keep a backup contact route or agree an escalation path. Keep the review about improving the process, not blaming people without evidence.
Decide when the issue is safe to close
Agree what “fixed” means before closing the conversation. A page loading doesn’t prove the form, payment or notification flow works. Test the path that failed and, where it makes sense, confirm the message reached its destination. Tell the site owner what you tested and what you didn’t.
If the final repair depends on a later vendor change or a monitoring period, separate the immediate workaround from the real resolution. Give the owner a clear way to report a recurrence. Otherwise you get the awkward situation where a ticket’s marked done and the business has no reliable way to notice the problem’s back.
A short post-incident note can capture the cause if known, the fix and any follow-up. Keep it factual and useful for the next person who sees the same symptom.
Related reading
- Saying no to SEO requests that won’t help
- How to prepare a client for a planned website outage
- Domain expiry and DNS hijacking: protecting client domains
Clear updates reduce confusion because they give people something solid to act on, even before the fix is ready. Draft your four-line update template today, before you need it. What will you tell the site owner first the next time a fix runs late?