Rewritten
Yesterday a configuration change went out without being tested first, which caused the checkout page to break for a few hours. We've identified the root cause and rolled back the change. Going forward, all config changes will go through the same testing process as code changes to prevent this from happening again.
About this tool
Sometimes what's needed isn't an emotional apology but a clear, factual account of what went wrong and what's being done about it — the kind of message a manager, client, or teammate needs before they can move forward. This tool focuses specifically on the explanation itself: a plain description of the mistake, the cause if known, and the fix, phrased honestly without either over-apologizing or sounding evasive. It pairs well with the apology to team generator when you need both the accountability and the explanation in one message.
Frequently asked questions
Is this the same as an apology?+
It's more focused on the facts — what happened and what's changing — than on emotional language. For a more personal, feelings-forward message, use one of the apology generators instead.
Does it need to include a technical root cause?+
Only if you provide one. If you don't know the exact cause yet, describe that in your input and the tool will phrase it as still under investigation.
Can I use this for a postmortem summary?+
Yes, the output works well as the opening summary of an incident postmortem or status update, though a full postmortem will need more technical detail.