Week 2: Taking an Apology Apart
A public apology gets marked up line by line into four separable components, and the marking reveals how few of them most apologies actually contain
1 March 2027
Week 1 landed on a one-line test: an apology names the wrong and accepts responsibility for it. That test is good enough to catch a justification dressed as an apology, but it treats “apology” as one move. It isn’t.
Take a real one, from a company statement after a data breach:
We’re sorry this happened. Our systems were compromised by a sophisticated attack. We are resetting all passwords and offering a year of credit monitoring. We take the trust our customers place in us extremely seriously.
Marked up, that statement contains:
- Acknowledgment of harm — “We’re sorry this happened.” Names that something bad occurred, to someone.
- Acceptance of responsibility — conspicuously absent. “Our systems were compromised” describes an event that happened to the company, not something the company did or failed to do.
- Expression of regret — folded into the same opening sentence as the acknowledgment, and doing no separate work of its own here.
- Commitment to change or remedy — present, concretely: password resets and credit monitoring are real actions with a real cost.
Three of four components are there. The one that’s missing is responsibility — and its absence is why the statement reads, correctly, as damage control rather than an apology, no matter how expensive the remedy is.
Why four, and why they’re separable#
Each component answers a different question a wronged person actually asks: did you notice? do you accept it was on you? do you feel bad about it? will it happen again? A statement can answer three of those and dodge the fourth, and readers reliably notice which one is missing even when they can’t name it. That’s the diagnostic value of the split: it turns “that didn’t feel like a real apology” into “which component was missing,” a question with an answer.
A component that’s granted and then taken back#
A harder case than a missing component: one that’s present and then quietly withdrawn by a later clause in the same statement. Take a variant of the breach notice: “We take full responsibility for this incident, though we want to be clear the vulnerability was disclosed to us less than 24 hours before it was exploited.” The first clause is a real acceptance of responsibility. The second doesn’t contradict it outright — it’s phrased as context — but its actual function is to pre-argue a defence for the company before anyone has asked for one, which is Week 1’s justification move, smuggled in after the responsibility clause has already done its job of sounding accountable. Marking this up as “responsibility: present” would miss what the sentence is actually doing; the components aren’t just checked off individually, they have to be checked against what the rest of the statement does to them.
None of this ranks the four against each other yet — that’s next week’s question, once the anatomy is on the table.
Teaching team
- Idris Fenn — tutor