To deliver bad news to a client by email, lead with the news in the first sentence — do not bury it in context. Then cover what happened, the impact on them, the options available, and the decision you need from them by a specific date. Keep the tone direct, factual, and brief.
12 copy-paste bad-news email templates for clients: cost overruns, missed deadlines, errors, and hard decisions — with a clear four-part structure.
Delivering bad news to a client in an email is one of the harder professional communication tasks, not because it is technically difficult but because the instinct is always to soften it first — to front-load the context, the caveats, the relationship warmth — and that instinct is exactly what makes the emails fail. The reader gets to paragraph three before understanding what you are telling them, then has to re-read the whole message with the new frame. Good bad-news emails do the opposite: the news is in the first sentence, and everything that follows is facts, options, and next steps.
This post is a practical template library. Twelve copy-paste bad-news email templates cover the situations that arise most in client relationships: a project over budget, a deliverable you cannot provide, a key person leaving the account, results that missed the target, a data error in a previous report, and a decision that went against them. Every template follows a four-bracket structure — what happened, the impact, the options, and the decision needed by a specific date — that separates the facts from the feelings and gives the client something actionable rather than leaving them with a problem and no clear next step.
When email is the right choice for delivering bad news#
The email-versus-call question comes up with every difficult client situation. There is no universal rule, but there is a useful test: what does the client need first — to absorb information, or to be heard? If they need to review specific numbers, assess options, and come back to you with a decision, email is the right starting point, because a call delivers the news faster but leaves them with nothing to re-read, share with a colleague, or refer back to when responding. If they are likely to be shocked or distressed, and the relationship carries enough weight that your presence matters, call first, then follow up with the email so the details are in writing.
Email alone is appropriate when the news comes with specific numbers to review, a revised timeline with a plan attached, a corrected document, or a decision with defined options and a clear deadline. A phone call first is better when the news represents a significant project failure, when the client has been building on a deliverable that is now not happening, or when you know the response will be emotional. In those cases, the email becomes written confirmation of a conversation you have already had, not the first time they hear it.
What is never appropriate: sending bad news by email specifically to avoid the conversation. The templates here assume you are using email because it is the right channel for that type of information, not because calling felt harder.
When in doubt, call first
If you are not certain whether to email or call, default to calling. The email can follow as the written record. An email that delivers genuinely difficult news cold — without a prior conversation — is harder to recover from than a call that goes awkwardly, because the client has time to build a story around the written words before you can respond.
The best structure for a bad-news message to a client is four elements in a fixed order: what happened, the impact on the client, the options available, and the decision needed by a specific date. Every template in this post uses that structure. It works because it separates facts from feelings, gives the client something to act on, and prevents the most common failure mode — an email that describes a problem at length but leaves the reader unclear on what they are supposed to do next.
The table below shows what each bracket should and should not include.
Element
What to include
What to avoid
[WHAT HAPPENED]
One to three sentences stating the factual cause. Date it if relevant. Name the specific failure point, not a general category.
Excuses, attribution of blame to third parties, or defensive framing. Facts only.
[IMPACT]
The concrete effect on the client's project, budget, or timeline. Be specific about what is delayed, changed, or affected.
Minimising or hedging. If the impact is real, name it. The client already suspects.
[OPTIONS]
Two or three genuine paths forward, each with enough detail to evaluate. Include which option you recommend and why.
False choices where only one path is viable, or so many options the client cannot decide.
[DECISION NEEDED BY]
A specific date tied to a concrete consequence or next step. Explain briefly why the date matters.
Open-ended requests ('whenever you have a moment') or no ask at all. Every bad-news email needs a confirmed next step.
Copy any template below, fill in the bracketed placeholders with your specifics, and send. Subject lines are designed to be opened rather than avoided: they name the topic directly, because a vague subject on a bad-news email creates exactly the dread you are trying to manage. The closing line in each template is intentionally brief.
Cost overruns are the bad news clients find hardest to receive, because the surprise compounds the problem. The first template covers a clean overrun where the cause is identifiable and the project is otherwise complete. The second covers a mid-project discovery, where work is still running and the client must decide whether to continue.
Template 1 — Project over budget
Subject[Project name]: costs have exceeded the agreed budget — here is where we stand
[WHAT HAPPENED]During [phase, e.g., the final development sprint], actual costs for [specific line item, e.g., third-party data licensing] came in at [amount], compared to the [amount] we had budgeted. The difference was caused by [specific cause: e.g., a vendor price change confirmed after the project started / hours required to reach spec that our estimate did not account for]. I should have flagged the risk earlier, and I did not.
[IMPACT]The total project cost is now [amount], which is [amount or percentage] above the agreed figure of [original amount]. All deliverables are complete [or: the remaining work represents X% of the project and is on track to finish by date].
[OPTIONS]Option A: approve the revised total of [amount] and we close out the project. Option B: review the cost breakdown together on a call — I can walk you through each line — and decide then. I recommend Option A if the deliverables meet your expectations, but I want you to have full visibility before you agree.
[DECISION NEEDED BY][Date], so we can process the final invoice and formally close the engagement. I will hold the project file open until then.
I am available for a call at any point if it would help to talk through the numbers.
The second budget template is for a mid-project discovery. In this case the options must be genuine choices, not the appearance of choice. If there is really only one viable path forward, say so rather than presenting an implausible alternative alongside it.
Template 2 — Mid-project cost increase (work still in progress)
Subject[Project name]: revised budget required to complete — three options for you
[WHAT HAPPENED]We are [X%] through [project name] and have discovered that [specific cause, e.g., the API we are building against requires a paid tier for your data volume / the design revision cycle took three rounds rather than the one we estimated]. We cannot complete the project at the original budget of [amount].
[IMPACT]To finish the full scope as agreed, the total cost will be [revised amount]. Work completed to date represents approximately [amount or % of total] of that revised figure. If you choose not to proceed, we can deliver what is complete now.
[OPTIONS]Option A: approve the revised budget of [amount] and we complete the project as scoped. Option B: descope to [specific reduced scope], which we can complete within [adjusted amount]. Option C: pause here and take delivery of the work completed to date at [amount].
[DECISION NEEDED BY][Date] — we have the team scheduled through [date], and beyond that we would need to replan resources. I need your direction by then to avoid wasted time on both sides.
Happy to get on a call today or tomorrow to walk through the numbers in detail.
Missing a deadline is the most common delivery failure. The first template is for a clean miss where you owe the client a new firm date and an honest account of the cause. The second is for a longer-running timeline slip where the client needs an updated plan, not just an apology.
Template 3 — Missed deadline
Subject[Deliverable] was not delivered by [original date] — here is the new date
[WHAT HAPPENED]We did not deliver [deliverable] by [date]. The cause was [specific: e.g., an integration dependency on [system] that resolved later than our estimate / a rework cycle on [element] that our QA process caught and required us to fix before release]. This is our miss, and I will not attribute it to circumstances.
[IMPACT]You are [waiting to launch / blocked on a downstream dependency / missing a specific output for a stated purpose]. I understand that has a real cost and I am not going to minimise it.
[OPTIONS]We will deliver the completed [deliverable] by [new date — be specific: day and time]. If that creates a downstream problem you need help navigating, tell me what it is and we will address it.
[DECISION NEEDED BY]No decision required from you. We will deliver by [new date] and send a progress note at [interim checkpoint] so you are not left waiting.
I am sorry for the disruption. The next communication you receive from us will be the delivery.
The second delivery template addresses a longer-running timeline slip, where the final date has moved and the client needs a revised plan rather than a single new date.
Subject[Project name]: revised delivery timeline — updated plan attached
[WHAT HAPPENED][Phase, e.g., the data migration stage] has taken longer than our original estimate by [N] days or weeks. The specific delay is [cause: e.g., a third-party data format we had not encountered before that required a custom parser / a compliance review that came back with changes we needed to implement]. We caught this on [date] and I am raising it now rather than waiting to see if we could recover quietly.
[IMPACT]The new expected delivery date for [final deliverable] is [new date], [N] days or weeks beyond the original date of [original date]. [Name any knock-on effects on the client's own schedule or downstream dependencies as specifically as you can.]
[OPTIONS]We are committed to the revised date of [new date]. The updated project plan is attached, showing each remaining phase and its target date. If there are specific milestones within the remaining work you need to prioritise, tell me and we will reorder the plan around them.
[DECISION NEEDED BY]Please review the revised plan and let me know by [date] if any part of it conflicts with your own planning. I would rather know now than discover it at delivery.
Available this week to walk through the plan if it would help.
This is often the hardest bad-news email to write, because the client may have built a plan on the assumption that you would deliver something. The key move is to lead with the decision, not the reasoning, and to offer the most useful alternative in the options block. The explanation of why you cannot deliver belongs in the what-happened bracket — it does not belong in front of the news.
Template 5 — Cannot deliver a promised capability
Subject[Deliverable or capability]: we cannot deliver this — and here is what we can do
[WHAT HAPPENED]After [attempting / reviewing / testing] [specific deliverable or capability], we have determined that [what you cannot do] is not something we are able to deliver. The reason is [honest and specific: e.g., it requires a direct integration with [system] that their API does not support at your data volume / it falls outside our regulatory authorisation / a technical constraint we did not identify until we were deep in the work].
[IMPACT]The part of your project that depended on [capability] will need a different approach. [Describe the concrete effect on the client's timeline, workflow, or expected outcome as specifically as you can.]
[OPTIONS]Option A: [the closest alternative we can deliver, with enough detail to evaluate]. Option B: [a recommended third-party provider who handles this — include a name if you have a reliable one]. Option C: redesign that element of the project to remove the dependency entirely. I can help you think through any of these.
[DECISION NEEDED BY][Date] — so we can keep the rest of the project moving. Let us know which direction you want to take and we will plan from there.
I am sorry we did not surface this constraint earlier. Available to talk through options any time this week.
Losing a key contact on an account damages trust if the client hears it late, from someone other than you, or without a clear handover plan. Send this proactively, with enough lead time for the client to adjust, and pair the news with a direct introduction to the new contact.
Template 6 — Key person leaving the account
SubjectA change on your account team — and your new point of contact
[WHAT HAPPENED][Name], who has been your [role] on this engagement, is [leaving the company / moving to a different team within our organisation] on [date]. I wanted to let you know directly rather than have you hear it another way.
[IMPACT]There will be a transition period. [Name] is spending [time period] documenting every open item, outstanding deliverable, preference, and context note before their last day, and I am reviewing the handover personally before it transfers to your new contact.
[OPTIONS]Your new [role] is [new contact name]. [One or two sentences of credibility: e.g., they have worked on accounts in your sector for X years and have been briefed on your project in detail.] I am arranging an introduction call for the three of us on [proposed date — or: let me know what works and I will set it up].
[DECISION NEEDED BY]No immediate action needed from you. [New contact name] will reach out to introduce themselves by [date]. Let us know if you want to bring the introduction call forward.
I am committed to making this transition as smooth as possible for your work.
Underperformed results are the bad news most often delivered badly, because the instinct is to spin the data before presenting it. The rule here is the same as everywhere else: lead with the number, not the context. The context becomes credible after the number. Before it, it reads as an excuse being constructed in advance.
Template 7 — Campaign or project results fell short
Subject[Campaign or project name] results — an honest read and what we do next
[WHAT HAPPENED][Campaign or project] ran from [date] to [date] and came in below the targets we set. The key gap: [specific metric] was [actual result] against a target of [target]. My read on the cause is [one to two specific, honest reasons: e.g., the audience segment we targeted had lower intent than our model predicted / the offer needed a stronger value proposition for this market]. I can go deeper on the data on a call if it would help.
[IMPACT][Name the downstream effect specifically: e.g., the Q3 pipeline target will need to be sourced from other channels, as this programme is not on a trajectory to fill it / the budget allocated to this approach is partially unrecoverable and we need to replan the quarter].
[OPTIONS]Option A: run a revised version with [specific changes], targeting [date] for a relaunch. Option B: redirect the remaining budget to [better-performing alternative] and set new targets for [period]. Option C: pause further spend and do a deeper diagnostic first — I can have a findings report ready by [date].
[DECISION NEEDED BY][Date] — so we can reallocate resources before [milestone or billing cycle]. I will send you the full results data before then so you have everything you need to decide.
This result is not what we planned for, and I want us to get the next one right.
When a third-party vendor or platform caused the failure, be careful not to use them as a shield. The client hired you, and part of what they paid for is vendor management. Acknowledge the failure, explain the cause, and then describe what you are doing about the supplier relationship.
Template 8 — Third-party failure affecting your delivery
Subject[Project name]: service issue caused by [vendor or platform] — what happened and our plan
[WHAT HAPPENED][Vendor or platform name] experienced [specific incident: e.g., an API outage / a data processing delay / a change to their access terms] on [date]. This caused [specific effect on our work: e.g., data collection was interrupted for N hours / the scheduled delivery could not go out as planned]. I became aware of it at [time] and have been managing the situation since.
[IMPACT]As a result, [specific effect on you: e.g., the weekly report for [date] is delayed by N hours / [deliverable] will arrive on [new date] rather than [original date]]. [If there is a data gap or lost information, say so directly and describe the scope.]
[OPTIONS]We are actively working with [vendor] to resolve the issue [or: have already recovered and are rebuilding the affected data]. The revised delivery date is [date]. I am also reviewing whether we should add a contingency for this dependency going forward and will propose an approach as part of the next project plan.
[DECISION NEEDED BY]No decision required from you right now. I will update you at [time or date] with the confirmed status. If the delay creates a downstream problem for your own planning, tell me and we will work around it.
You hired us to manage this, and we are managing it.
A data error in a previous report requires speed above everything else. The longer the error sits uncorrected, the more decisions may have been made on the wrong figures. Send the correction the same day you discover it, attach the corrected version, and be precise about what changed.
Template 9 — Error in a previous report or deliverable
SubjectCorrection: error in [report name] sent on [date] — corrected version attached
[WHAT HAPPENED]We found an error in [report name] sent to you on [date]. Specifically: [what was wrong, stated exactly — e.g., the conversion rate figures in the summary table used raw sessions rather than qualified sessions, overstating performance by approximately X%. The error is in column D of the attached spreadsheet, rows 14 through 22].
[IMPACT]The corrected figures show [summary of the change]. If any decisions were made on the basis of the original figures — [name the specific decisions that might be affected, e.g., budget allocation for the next quarter, reporting to your board] — those may need to be revisited with the corrected data in view.
[OPTIONS]The corrected version is attached. Please use this and archive or discard the original. If you forwarded the original to anyone on your team or to external stakeholders, this correction is worth passing along. I am available to walk through the differences on a call if that would help.
[DECISION NEEDED BY]Please confirm receipt by [date] so I can be certain the correction has reached you. If the error affected decisions you need help revisiting, let me know and we will work through it together.
I am sorry for the error. It should not have left us unchecked.
When your mistake caused a material outcome for the client — not just a reporting error but something that affected their actual results — the email needs to go further. Acknowledge the consequence directly and address what, if anything, you are doing to remedy it.
Template 10 — Our error affected your outcome
Subject[Project or campaign]: our error — what happened and what we are doing about it
[WHAT HAPPENED]We made an error in [what we did, specifically: e.g., the audience targeting configuration for [campaign] / the data feed setup for [integration]]. The error was [specific description]. We discovered it on [date] through [how: e.g., your team flagged an anomaly / our internal QA review]. I should have caught it at [the stage it should have been checked], and I did not.
[IMPACT]As a result of the error, [specific consequence: e.g., the campaign ran to the wrong audience segment for [N] days, with [N] impressions and [budget] in spend affected / the integration fed incorrect data into your system for [period], affecting [specific records or reports]]. [If there is a financial or downstream consequence, name it explicitly rather than leaving it for the client to calculate.]
[OPTIONS]We are [correcting / have corrected] the error and [specific remediation: e.g., re-running the affected campaign segment with equivalent budget at no additional charge / rebuilding the affected data records and will have a corrected export to you by date]. [State any additional remediation you are offering, with specifics.]
[DECISION NEEDED BY]Please review the remediation plan above and let me know by [date] if there is anything additional you need from us to make this right. I want to resolve this fully rather than close it administratively.
We take responsibility for this. Our job is to get it right.
Delivering a decision that went against the client — a rejected request, a failed appeal, a policy that holds — requires the most direct language of any template in this collection. The decision goes in the first sentence of the what-happened bracket, not the last. Burying a negative decision inside an explanation is the single most reliable way to make a client feel managed rather than informed.
Template 11 — Decision that went against the client
[WHAT HAPPENED]After reviewing [your request for / the question of] [specific ask], our decision is [state the decision plainly, in this first sentence: e.g., we are not able to offer a refund for the [service] / the contract does not support the scope change you have requested without a change order / the appeal has been reviewed and the original decision stands]. I am not going to lead with context, because the decision is what matters here.
[IMPACT]For your planning: [the concrete consequence — e.g., the original invoice amount stands and is due on [date] / the project will proceed under the current scope, with any additions priced as change orders / you will need to find an alternative provider for [element]]. If this creates a downstream issue for you, I want to hear about it.
[OPTIONS][If a process exists: e.g., if you would like to raise a formal dispute, the process is [describe]. If you want to explore what a change order for the revised scope would look like, we can scope that together.] [If no path exists, say so directly: there is no further appeals process at this point, but I am happy to explain the reasoning in more detail if it would help you plan.]
[DECISION NEEDED BY]If you want to pursue [any available next step], please let me know by [date]. If I do not hear from you, I will proceed on the understanding that you have received and noted our decision.
I appreciate that this is not the outcome you were looking for.
A rate or price increase is one of the most routine pieces of commercial bad news professionals need to deliver. Give adequate notice, state the reason briefly without over-explaining, and make the effective date and the new amount unambiguous from the subject line.
Template 12 — Rate or price increase
SubjectOur rates are increasing from [date] — here is what that means for your account
[WHAT HAPPENED]Our rates for [service or engagement type] will increase from [current amount] to [new amount] effective [date]. The increase reflects [brief, honest reason: e.g., input costs that have risen since we last adjusted our rates in [year] / an expansion of what is included in the service level at your tier]. I wanted to give you as much notice as possible rather than a last-minute change.
[IMPACT]Your [monthly retainer / project rate / renewal] from [effective date] will be [new amount]. [If the increase affects a mid-engagement, be specific about exactly when it applies and how work already in progress is handled — e.g., the new rate applies to new statements of work only, with current work billed at the agreed rate.]
[OPTIONS]If you would like to lock in the current rate for a defined period, we can do that with a signed extension by [date]. Alternatively, if you would like to review the scope of your engagement at the new rate to confirm it still makes sense for your budget, I am happy to have that conversation.
[DECISION NEEDED BY][Date] — if you want to exercise the option to extend at the current rate, we need written confirmation by then to process the paperwork in time.
Thank you for your continued business. I am available to talk through this at any point before the change takes effect.
The hard version: news you should have raised sooner#
The hardest bad-news email to write is the one where you are delivering news that is already a month old — a problem you noticed, hoped might resolve itself, and eventually had to acknowledge once it was too late to course-correct quietly. These emails carry two pieces of bad news: the original problem, and the delay in raising it.
The instinct when writing this email is to front-load the explanation: to spend two paragraphs establishing why you waited before telling the client what you are actually telling them. This makes the email significantly worse. The client reads the explanation, reaches the news, and then re-reads the explanation knowing what you were building context around. It reads as an attempt to manage their reaction before they have had one.
For late-disclosure emails, the rule applies more strictly than usual: the news goes in the first sentence of the body. Lead with it. Then acknowledge the delay — briefly, in one sentence — and move directly to the current status, impact, and options. The acknowledgement of the delay belongs inside the what-happened bracket, not in front of it.
A reworked version of the cost-overrun template showing this in practice:
Template — Late disclosure (news you held too long)
Subject[Project name]: I should have told you this sooner — here is the full picture now
[WHAT HAPPENED]The project budget is going to be exceeded by [amount]. I identified a potential overrun [N] weeks ago and waited to see whether we could recover it before raising it with you. We have not been able to recover it, and I should have told you when I first saw the risk. I am telling you now.
[IMPACT]The total cost will be [amount], which is [amount] above the agreed figure. [If decisions the client might have made differently are now constrained by the delay, name that explicitly — e.g., you would have had the option to descope at that point, and that window is now closed. Do not gloss over this consequence of the delay itself.]
[OPTIONS]Option A: proceed to completion at [revised total]. Option B: descope to [specific], completing within [adjusted amount]. Option C: call to discuss before deciding — I can have a full cost breakdown ready within [timeframe].
[DECISION NEEDED BY][Date]. I owe you a direct response to any questions before then, and I will pick up the phone rather than wait for email if that helps us get there faster.
I am sorry I did not raise this when I should have. That was the wrong call.
Bad-news emails sometimes get no response, and the silence is its own problem — you do not know whether the client has absorbed it, is upset, is waiting for more information, or simply missed the email. The follow-up here is different from a standard chasing message: you are not following up on an outstanding action item, you are following up on a difficult conversation.
Wait two business days before following up, unless the decision you requested has a deadline inside that window. Send a single short message that references the original email, restates the decision you need and the date, and asks directly whether they have questions or want to get on a call. Do not send a second copy of the full original — that reads as repetition rather than engagement.
If there is still no reply after the follow-up, and the decision is consequential, call. An email that is not being replied to is not a problem you solve with more email.
Silence is not agreement
Do not proceed on the assumption that no reply means approval. In a bad-news context, silence is far more likely to mean the client has not decided, is still processing, or is uncomfortable and avoiding the thread. Follow up, offer a call, and make it easy for them to respond — but do not move forward without a confirmed answer on anything consequential.
Drafting bad-news emails without starting from a blank page#
The templates above solve the blank-page problem, but they still require you to write the specifics under each bracket, calibrate the tone, and send them at the right moment — often while you are managing the very situation the email is about. That is where the pressure accumulates: the harder the situation, the harder it is to write the email calmly and clearly.
We build AI Emaily, an AI-native email client that connects to Gmail, Outlook, and any IMAP account and acts as an autonomous chief of staff for your inbox. In Copilot mode, it prepares a draft using the structure and tone you configure — including high-stakes messages like the ones in this post — and holds it for your review and approval before anything is sent. The draft is not generic fill-in content: it draws from your user-set Personal Context brain and per-client profiles, so the voice, the relevant history, and the right framing come through, not just the bracket placeholders. You review, adjust, and approve.
The human judgment — whether to send this at all, whether to call first, what the real options are — stays with you. What changes is that the draft is waiting for your decision rather than waiting for you to write it, so the cognitive load stays on the situation rather than the wording. Every action logs to a full audit trail with undo, so nothing goes out that you did not approve. Try it free at app.aiemaily.com/signup.
Nafiul Hasan is an entrepreneur and AI automation system builder with 10+ years of experience turning messy, manual workflows into reliable automated systems. He designs and ships AI enterprise solutions end-to-end — the agent logic, the data plumbing, and the product people actually use — and founded AI Emaily to give busy professionals their attention back. He writes here from the builder's seat: what works, what breaks, and how to put AI to work without giving up control.
EntrepreneurAI Automation System BuilderAI EnthusiastBuilds AI Enterprise Solutions10+ years experience
AI Emaily drafts difficult client emails in your voice, holds them for your approval in Copilot mode, and logs every action with undo and an audit trail. Try it free.
