Delivering Bad News to a Client
Report a delay or problem with credibility.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Prepare to tell a client about a problem. The problem and cause: [PROBLEM_AND_CAUSE]. Impact on scope, dates, cost: [IMPACT]. What we have done so far and options: [ACTIONS_AND_OPTIONS]. Contract context: [CONTRACT_CONTEXT].
Produce: a call plan (opening that states the problem in two sentences; impact; what we are doing; options with pros and cons; recommendation; what we need from them; next update date); an email (150 words) to confirm the call; a Q&A of eight likely questions ("Whose fault is it?", "Will this cost us more?") with honest answers; and a list of things not to say.
Include a pre-call checklist (facts verified, options costed, decision makers identified, internal alignment) and a post-call summary. Check contractual implications such as notice requirements, liability, and remedies with a lawyer in [JURISDICTION] [VERIFY] before sending written statements.
Provide the call script in full sentences for the first two minutes, since that is where tone is set, and list the three questions to ask the client before offering options so that the options match their priorities.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.
See an example result (fictional data)
Call opening (about 45 words): "Thanks for taking the call, Ravi. I need to tell you that the portal launch will be delayed by two weeks, from 12 to 26 June, because the payment integration failed testing. I want to explain what we are doing and ask what matters most to you." Questions first: Is the launch date driven by a campaign? What would a partial launch be worth? Options: A full launch 26 June, no extra cost; B launch without payments on 12 June, payments on 26 June; C add a second engineer, 3,000, launch 19 June. Recommendation: B. Q&A: "Whose fault is it?" "The integration had a flaw we should have caught earlier; we have changed our testing." Check contract notice requirements with a lawyer [VERIFY].
Illustrative only, made-up data. Your results will differ and must be reviewed.